EmbeddedRelated.com

10 Software Tools You Should Know

Jason SachsJason Sachs May 20, 201215 comments

Embedded work gets a lot easier when you have the right software stack, and Jason Sachs lays out the tools he leans on every day. From revision control and file comparison to build systems, scripting, analysis, documentation, QA, and command-line utilities, he focuses on practical picks that save time and reduce mistakes. The list is opinionated, but it is full of the kind of workflow advice that helps engineers stay productive.


Have You Ever Seen an Ideal Op-Amp?

Jason SachsJason Sachs April 30, 2012

Forget the ideal op-amp fantasy, Jason Sachs walks through the practical nonidealities that make textbook gain formulas fail in real circuits. Using the uA741C and TLC081C as examples, he explains offset voltage, input bias and offset currents, common-mode and supply rejection, gain-bandwidth and slew-rate limits, plus capacitive loading, RF rectification and overload recovery. Read to learn which datasheet specs matter and why.


Hot Fun in the Silicon: Thermal Testing with Power Semiconductors

Jason SachsJason Sachs April 20, 2012

Bringing hundreds of amps into the lab for low-Rds(on) MOSFET thermal tests is impractical. Jason Sachs demonstrates a clever workaround using a zener diode, a series resistor, and a constant-current lab supply to dump the same watts into the device at much lower current. He also explains how to use datasheet RθJC values and type T thermocouples to estimate junction temperature and size heatsinking or airflow.


How to Build a Fixed-Point PI Controller That Just Works: Part II

Jason SachsJason Sachs March 24, 20122 comments

Jason Sachs walks through practical, battle-tested rules for implementing PI controllers in fixed-point arithmetic. He explains Q-format choices, why the integrator needs extra fractional bits, and why scale-then-integrate simplifies design. The post also covers proportional gain scaling, saturation and anti-windup, and common C pitfalls that cause overflow or lost resolution on 16/32-bit microcontrollers.


How to Build a Fixed-Point PI Controller That Just Works: Part I

Jason SachsJason Sachs February 26, 20127 comments

Jason Sachs digs into the implementation choices that make a fixed-point PI controller reliable in real embedded systems. He focuses on practical fixes rather than tuning: prefer scale-then-integrate, fold the timestep into the integral gain, and apply anti-windup so saturations and sensor noise do not break the loop. Part I covers discrete-time pitfalls and sets up fixed-point scaling issues for Part II.


10 More (Obscure) Circuit Components You Should Know

Jason SachsJason Sachs February 5, 20121 comment

Jason Sachs follows up his earlier primer with ten more underused but practical parts that can simplify embedded hardware designs. From MOSFET-based ideal diode controllers that eliminate diode drops to TAOS light-to-frequency sensors that expand dynamic range, the post explains what each component does, when to choose it, and real-world tradeoffs learned from field use. Ideal for engineers looking to broaden their parts toolbox.


Oscilloscope Dreams

Jason SachsJason Sachs January 14, 20125 comments

Jason Sachs walks through practical oscilloscope buying criteria for embedded engineers, focusing on bandwidth, channel count, hi-res acquisition, and probing. He explains why mixed-signal scopes and hi-res mode matter, when a 100 MHz scope is sufficient and when to keep a higher-bandwidth instrument, and how probe grounding and waveform export can ruin measurements. Real-world brand notes and try-before-you-buy advice round out the guidance.


Stairway to Thévenin

Jason SachsJason Sachs December 31, 2011

Jason Sachs strips away classroom mystique to show how Thevenin and Norton equivalents are practical tools for real embedded work. Using a simple two-terminal black-box example he shows how two measurements give Vth and Rth, then applies that model to voltage-divider references, potentiometer RC filters, and combining multiple sources with Millman's theorem. Read it for fast, practical ways to predict output impedance, droop, and filter time constants.


Organizational Reliability

Jason SachsJason Sachs December 22, 20111 comment

Here is a compact playbook for making your engineering team reliable, pulled from a handout Jason Sachs saved from Doug Field. It highlights disciplined commitment habits, clear absence and missed-commitment notifications, explicit handoffs and read-back practices, and resisting "manytasking" through ruthless prioritization. These are simple, immediately actionable behaviors that can lift a team's delivery and reduce chaos heading into the new year.


Help, My Serial Data Has Been Framed: How To Handle Packets When All You Have Are Streams

Jason SachsJason Sachs December 11, 201110 comments

Framing byte streams is easier to get wrong than you think, and a bad scheme can leave your embedded device acting on the wrong packet. Jason Sachs walks through common plaintext and binary framing approaches, explains why CRCs alone can still permit false resynchronization, and demonstrates COBS as a simple, low-overhead byte-stuffing method that prevents delimiter collisions and guarantees resynchronization.


A Wish for Things That Work

Jason SachsJason Sachs January 1, 20182 comments

Jason Sachs revisits his long-running gripe with poor user interfaces, cataloguing annoyances from his Toyota Prius dashboard to desktop apps and browsers. He mixes sharp, real-world examples with a short, practical wishlist for 2018 aimed at making embedded displays, update behavior, security cues, and developer tools noticeably less frustrating for engineers and end users alike.


April is Oscilloscope Month: In Which We Discover Agilent Offers Us a Happy Deal and a Sad Name

Jason SachsJason Sachs April 19, 2014

Jason Sachs grabbed an MSOX3034 during Agilent's bandwidth deal, used a 30-day trial to debug UART issues, and then discovered Agilent's 'Happy Deal' lets you enable all MSOX software for the price of a single option. He walks through which MSOX3000 modules are worth buying, explains memory and waveform features, and delivers a wry take on the company's new Keysight name.


Python Code from My Articles Now Online in IPython Notebooks

Jason SachsJason Sachs May 1, 20152 comments

Jason M. Sachs has published the Python code from his EmbeddedRelated articles as standalone IPython notebooks. He automated extraction of example code and pushed the notebooks to a public Bitbucket repository under the Apache license, and they are viewable via nbviewer. The post lists available notebooks and asks readers to link back to EmbeddedRelated and share feedback on how they used the code.


A Second Look at Slew Rate Limiters

Jason SachsJason Sachs January 14, 2022

Picking the right slew rate can cut overshoot dramatically while keeping delay reasonable, Jason shows. He numerically analyzes a feedforward slew-rate-limited step into a normalized second-order system and proposes a simple empirical rule R = Δx/(2π α τ) with α ≈ 1. The post includes Python/Scipy code and a 3→5 V example that demonstrates about a 3× overshoot reduction and a ≈5τ peak delay.


Book Review: "Turing's Cathedral"

Jason SachsJason Sachs November 20, 20146 comments

The early days of electronic computing are explored through George Dyson's Turing's Cathedral, which traces the IAS machine, John von Neumann, and Princeton's Institute for Advanced Study from 1940 to 1958. Jason Sachs praises Dyson's archival access and narrative detail, especially on hardware like vacuum tubes and delay lines, but warns the book's software explanations feel vague and would have benefited from diagrams.


Reading and Understanding Profitability Metrics from Financial Statements

Jason SachsJason Sachs March 29, 2022

Reading a company’s financial statements does not have to feel like accounting homework. Jason Sachs shows how engineers can pull out the most useful profitability signals, especially gross margin and operating margin, from SEC filings and earnings releases. Using semiconductor companies as examples, he explains what those ratios mean, how they’re computed, and why they can hint at business strength or weakness.


Musings on Publication — and Zero Sequence Modulation

Jason SachsJason Sachs May 30, 20141 comment

Publishing technical content involves more than writing, it requires tools, reviewers, and patience. Jason Sachs walks through his lean workflow for posting to EmbeddedRelated, contrasts it with the multi-person review cycles at semiconductor companies, and points out a neat trick for checking PDF metadata. He also highlights a Microchip tutorial on Zero Sequence Modulation that includes a 3-D HTML5 interactive viewer to make space vector concepts easier to grasp.


Organizational Reliability

Jason SachsJason Sachs December 22, 20111 comment

Here is a compact playbook for making your engineering team reliable, pulled from a handout Jason Sachs saved from Doug Field. It highlights disciplined commitment habits, clear absence and missed-commitment notifications, explicit handoffs and read-back practices, and resisting "manytasking" through ruthless prioritization. These are simple, immediately actionable behaviors that can lift a team's delivery and reduce chaos heading into the new year.


Garden Rakes Revisited: The Hall of Shame

Jason SachsJason Sachs April 12, 2014

Jason Sachs opens a Hall of Shame to catalog the everyday software "garden rakes" that steal time and focus. He walks through concrete examples from PowerPoint point editing and Office window behavior to Outlook undo bugs and TurboTax's opaque errors, showing how poor UI and hidden behaviors force you to work around the tool instead of with it. This is a short, cranky checklist for avoiding wasted effort.


Scorchers, Part 2: Unknown Bugs and Popcorn

Jason SachsJason Sachs April 5, 20202 comments

Jason Sachs likens bug hunting to popping popcorn to explain diminishing returns when preparing a release. He argues that the rate of new bug reports is a practical signal for whether to keep testing or ship, and that late fixes incur hidden costs like extra testing, branching, documentation, and lost focus. The piece also warns that embedded firmware needs stricter pre-release testing because updates are rarer.