An oscilloscope shows one or two channels of analogue truth. A logic analyzer watches eight or sixteen lines as digital states and decodes the protocols running on them. For debugging I²C address conflicts or UART framing, it is the only tool that speaks the language.
At a glance: 6 minute guide · part 7 of 10 in the tools and equipment complete guide track · includes a worked example and a quick-reference table.
What it does differently
Here is the working theory in one pass. The analyzer samples channels as 1/0 at a set rate and records a long history you scroll. Protocol decoders then overlay meaning: I²C addresses, SPI bytes, UART characters. You stop guessing what the bus said and start reading it.
| Task | Tool of choice |
|---|---|
| One waveform, analogue detail | Oscilloscope |
| I²C address conflict | Logic analyzer + decode |
| SPI byte errors | Logic analyzer |
| UART baud mismatch | Either (scope for level) |
| Power rail ripple | Oscilloscope |
| Glitch hunting (rare) | LA with long capture |
Cheap analyzers, real results
The £10-class 8-channel USB analyzers with open-source software (sigrok/PulseView) decode I²C. SPI, UART and more competently for hobby and much professional work. Sample rate limits apply 24 MHz class captures are ample for 100-400 kHz I²C.
Workflow that finds bugs
Connect ground, attach channels to the documented pins, arm, then trigger the transaction. Read the decode timeline. The first wrong byte, missing ACK or shifted bit is usually the entire story. Export captures for issue reports.
How to apply this in your build
Work through the sequence below each step assumes the previous one passed. For numbers that need calculating, the linked tools at the end of this guide do the arithmetic instantly. 1. 2. 3. 4.
Worked example
A sensor “ignoring” commands showed its address byte NAKed in the decode the breakout was jumpered 0x76 while code spoke to 0x76 vs 0x77’s twin. One capture, no guessing. Run the numbers yourself with the related calculator and the result should agree to within rounding.
Practical note from the bench. The analyzer pays for itself the first time a bus “talks nonsense” the decode turns an argument into a reading.
Common mistakes to avoid
- Sampling too slowly and seeing invented glitches
- Floating grounds between analyzer and target
- Overwhelming captures with minutes of idle recorded
Key takeaways
- What it does differently the foundation of this guide; revisit it if any measurement here surprises you.
- Cheap analyzers, real results the foundation of this guide; revisit it if any measurement here surprises you.
- Workflow that finds bugs the foundation of this guide; revisit it if any measurement here surprises you.
Who this guide is for
Beginners get a single focused topic instead of a whole textbook chapter. It assumes the track’s earlier pages in the tools and equipment complete guide path. Intermediate readers use it as a reference the table. The worked example and the mistake list answer the questions that come up mid-build. If you teach, the structure (theory, application, example, failure modes) maps cleanly onto a lab session.
What you need before starting
Nothing exotic: the parts or tools named in the guide, a multimeter. A notebook for the numbers. Document which channel maps to which signal before you begin the guide assumes it and keep the quick-reference table above within sight while you work through the steps.
Quick reference card
| Aspect | Where to find it in this guide |
|---|---|
| Core theory | What it does differently |
| Application steps | How to apply this in your build |
| Worked numbers | Worked example |
| Failure modes | Common mistakes to avoid |
How this fits the tools and equipment complete guide track
This guide is one stop in the structured learning path. Start from the tools and equipment complete guide complete guide for the full map, or continue with scope skills and I2C versus SPI.
Frequently asked questions
Do I still need a scope if I have an analyzer? Yes they answer different questions; voltage levels, ringing and analogue behaviour belong to the scope.
Can it decode USB/Ethernet? Practical hobby analyzers stop around I²C/SPI/UART/1-Wire speeds; higher buses need dedicated instruments.
Where do I go next? Back to the tools and equipment complete guide complete guide it indexes every guide in this track and updates as new ones are published.
Continue this track
- Building a foundation? The tools & equipment complete guide maps every step in order.
- Next: Bench Power Supplies: Choosing and Using Yours Well
- Next: ESD-Safe Workspace: Protecting Parts You Cannot See Failing
- Next: Hot Air Rework: Removing and Replacing SMD Parts
- Work the numbers: frequency converter · trace width tool
Your next step in this track
- The complete tools & equipment guide: Tools & Equipment complete guide
- Read next: how to use a multimeter: every mode that matters
- Also in this track: oscilloscope triggering: the skill that makes waveforms stand still
- Continue with: probe compensation: the one-minute scope calibration
- Calculate as you go: frequency and wavelength tool · trace width calculator · resistor decoder
- From here, the natural continuation is the next guide in the track index. It assumes exactly the vocabulary this page built and adds the next layer of practice.
Practical working notes
Component substitution is a legitimate experiment as long as it is deliberate. Swap one part, predict the effect, measure, and record. That single habit converts a parts bin into a teaching lab and makes every future guide in this track faster to absorb.
The fastest way to internalise this topic is to change one variable deliberately and predict the result before measuring. Wrong predictions are the curriculum, they show exactly which mental model needs revisiting, and the bench grades honestly.
Formulas and checks from this guide
Verification checklist for this track: compensate probes before trusting amplitudes, verify meter fuses before current work. Keep one known-good reference to sanity-check instruments. Calibration you can demonstrate beats calibration you assume.
Bookmark this page against your next build in the track. The checklist above is the same one used across 12 guides in this series.
Experience notes
Warm-up drift is real in both. Swap in a known-good reference to decide which side drifts.
After every move between scopes, and monthly as ritual. It costs one minute.
Extended Application Notes
This section expands the practical application of logic analyzers: watching digital buses talk beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.
Failure Analysis in Depth
The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. Sampling too slowly and seeing invented glitches Floating grounds between analyzer and target Overwhelming captures with minutes of idle recorded. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.
Pre-Build Checklist
Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.
What Comes Next
Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.
Theory in Practice, Extended
The theory section of logic analyzers: watching digital buses talk deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.
Component Sourcing and Substitution Notes
Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.
Instrumentation for This Design
Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.
Documentation Template for This Build
Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.
Last updated 23 August 2026