Logic Analyzers, Signal Generators & Choosing the Tool

The scope is brilliant at analog shapes, but it struggles with one thing: watching many digital lines at once and telling you what the data actually is. For that, there's a specialised tool — the logic analyzer — and it pairs beautifully with everything you learned about protocols in L5.

What a logic analyzer does

A logic analyzer captures many digital signals simultaneously (8, 16, or more channels) and — crucially — decodes protocols into human-readable form. Instead of showing you wiggly voltage traces, it shows you the actual bytes, addresses, and characters being transmitted.

Point a logic analyzer at an I²C bus and it doesn't just show SDA and SCL wiggling — it tells you: "controller addressed device 0x48, wrote 0x01, read back 0x7F." That's a different level of insight from a scope.

Scope vs logic analyzer: the division of labour

Both look at signals over time, but they answer different questions:

A scope typically shows 1–2 channels with rich analog detail. A logic analyzer shows many channels but only as digital 1s and 0s — and turns those into decoded transactions. They're complementary, not competing.

Where it shines (the L5 payoff)

The logic analyzer is the natural debugging tool for the protocols of L5:

• "Is the microcontroller sending the right I²C address?" → logic analyzer decodes it; you instantly see if it's addressing the wrong device.
• "Are the SPI bytes correct?" → it shows the actual bytes on MOSI/MISO against the clock.
• "Is my UART sending the characters I think?" → it decodes the bytes; mismatched baud (L5) shows up as garbage, confirming the cause.
• "Which line is misbehaving?" → watching SDA, SCL, CS, clock, and data lines together reveals timing relationships a 2-channel scope can't.

When a digital bus "isn't working" and the scope confirms the lines are wiggling but you need to know what they're saying, the logic analyzer is the answer. It's how you debug L5's protocols in practice.

A note on accessibility

Affordable USB logic analyzers (paired with PC software) have made this tool widely accessible — you don't need an expensive bench instrument. For anyone working with sensor buses and microcontroller communication (the heart of embedded products), it's one of the highest-value tools to have.

The next slide covers the signal generator — a source of test signals rather than a measurement tool — plus awareness of the specialist instruments you'll occasionally meet.

Most instruments measure a circuit. The signal generator is the opposite — it produces a known signal to feed into a circuit, so you can watch how the circuit responds. Plus, there's a handful of specialist tools worth knowing by name.

The signal generator: a source of known test signals

A signal generator (or function generator) outputs clean, precisely-defined waveforms — sine, square, triangle, and more — at a frequency and amplitude you set. You inject that signal into a circuit's input and observe the output (usually on a scope).

The classic test pairing is generator in, scope out:

   Signal generator ──► [ circuit under test ] ──► Oscilloscope
       (known input)                                (observed output)

This lets you characterise a circuit's behaviour deliberately rather than waiting for a real signal:

• Test a filter (L1's RC filter): sweep the input frequency and watch which frequencies pass and which get attenuated — you see the filter working.
• Check an amplifier's gain: feed a known small sine, measure how much bigger it comes out.
• Stimulate a circuit that needs an input to test, when you don't have the real source handy.

The key mental shift: a signal generator is a source, not a meter. It asks the circuit a known question; the scope reads the answer.

Awareness-level tools

You won't reach for these daily, but you should recognise them:

• LCR meter — measures L(inductance), C(apacitance), and R(esistance) with more precision than a multimeter, including properties like a capacitor's quality. Used when you need accurate component characterisation beyond what a multimeter's basic capacitance mode gives.
• Hot-air rework station — not a measurement tool but a repair tool: directed hot air to remove and replace surface-mount components. It's how a tech replaces a tiny failed chip once measurement has identified it. (Pairs with the soldering skills from L0.)
• Bench DMM — a high-precision benchtop multimeter for when the handheld's accuracy isn't enough.

These fill out the bench, but the four core tools — multimeter, bench supply, oscilloscope, logic analyzer — handle the vast majority of real work.

The bench, assembled

Step back and see how the instruments cover the whole space:

• Static electrical values (voltage, current, resistance, continuity, component health) → multimeter.
• Controllable, protective power + consumption insight → bench supply.
• Signals changing over time (shape, timing, ripple, frequency) → oscilloscope.
• Digital data on many lines, decoded → logic analyzer.
• Inject a known stimulus → signal generator.
• Precision component / repair / specialist → LCR, hot-air, bench DMM.

Between them, you can measure essentially anything an embedded product does. The final slide turns this into a clean decision — which tool for which question — plus the safe-measurement habits that protect you and the hardware.

The final skill of L7 is picking the right instrument for the question in front of you — quickly and correctly — and doing it safely. This is what turns a box of tools into competent diagnosis.

The tool-selection decision

Match the question to the tool:

"Is this voltage / value right?" (a steady number) → Multimeter. "Is this connected / this component healthy?" → Multimeter (continuity, resistance, diode test — power off). "How much current is it drawing / is it shorted?" → Bench supply (watch current + CC/CV), or multimeter in series. "What does this signal look like over time?" (shape, frequency, ripple, edges) → Oscilloscope. "What data is on this digital bus?" (I²C addresses, SPI/UART bytes) → Logic analyzer. "How does this circuit respond to a known input?" → Signal generator (+ scope).

The skill is recognising which kind of question you're asking. "Is the rail 5V?" is a steady-value question → multimeter, not scope. "Is the rail noisy?" is a shape-over-time question → scope, not multimeter. Same rail, different question, different tool.

Worked examples

• "Customer's solar generator won't turn on." → Multimeter first: is the battery voltage present at the output? Follow the power (Lesson 2 workflow). If a board is suspect, bench supply with a current limit.
• "The display is blank but the unit powers on." → Multimeter to confirm the display has power, then scope/logic analyzer to see if the microcontroller is actually driving the display's bus (SPI/I²C from L5).
• "This sensor reads garbage." → Logic analyzer on its I²C/SPI lines: is the right data being requested and returned? (Recall L5's baud/address pitfalls.)
• "This filter isn't doing anything." → Signal generator in, scope out: sweep frequency, watch the response.

Safe-measurement habits (the L7 discipline)

Measurement is hands-on with real, sometimes dangerous energy (L6's batteries store a lot of it). Carry these habits always:

• Set up before you probe — pick the mode, jack, and range first.
• Return the multimeter probe to V/Ω after measuring current — the fuse-blowing trap (Lesson 2).
• Power off for continuity, resistance, diode test, capacitance.
• Current-limit a suspect board on first power-on (Lesson 3).
• Clip the scope ground first, and respect that a slipped probe can short a source.
• Treat mains and high-energy points with real caution — and know when a job belongs with someone more experienced.

The L7 picture, and the ladder so far

You now have the full measurement toolkit:

• Multimeter — the everyday workhorse (voltage, current, resistance, continuity, diode, capacitance) + a power-first workflow.
• Bench supply — adjustable, current-limited, CC/CV-readable: a protective diagnostic source.
• Oscilloscope — see signals over time (V/div, time/div, trigger, coupling, probes).
• Logic analyzer — decode digital buses (the L5 payoff).
• Signal generator + awareness tools (LCR, hot-air, bench DMM).

L7 is the instrument that proves everything earlier in the ladder: it measures the voltages and components of L0–L2, the digital signals of L3, the microcontroller outputs of L4, the protocols of L5, and the power systems of L6. It's the bridge from understanding circuits to diagnosing them — exactly the competence behind real technical support.

Next: the K-Check tests all five instruments and the tool-selection instinct, and the P-Check asks you to write a real fault-diagnosis procedure — choosing the right instrument at each step, stating expected readings, and narrowing from power to root cause. That procedure is the job.