Home / Tools & Equipment /Logic Analyzers: Watching Digital Buses Talk

Logic Analyzers: Watching Digital Buses Talk

When scopes end and analyzers begin capturing I²C, SPI and UART with $10 tools and reading the decode.

Oliver Adam 6 min read 805 views 7 August 2026
Logic Analyzers: Watching Digital Buses Talk

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

Your next step in this track

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.

Last updated 23 August 2026

Logic Analyzers: Watching Digital Buses Talk | Procirel