Measuring current — and the fuse trap
The fourth multimeter measurement — current — is the most intrusive and carries the instrument's single most famous, fuse-blowing trap. Master this one and you've mastered the multimeter.
Current must be measured in series
Unlike voltage (measured across, in parallel), current flows through things — so to measure it, the meter must be in the path of the flow. You break the circuit and insert the meter so all the current goes through it on its way around:
Source ──► [ break here ] ──► Load ──► back to source
│
insert meter (in SERIES) — current flows THROUGH it
This is fundamentally more disruptive than measuring voltage: you have to open the circuit to insert the meter. That's why current is measured less often than voltage — and why it's worth knowing why you'd do it (e.g., "how much current is this load actually drawing?" / "is something drawing way too much?").
The separate current jack — and the trap
Here's the critical hardware detail. To measure current, the red probe moves to a different jack — usually marked "A" (or "mA"). Internally, that jack connects through a near-zero-resistance shunt, because the meter must let current pass through it freely (in series) without disturbing the circuit.
That near-zero resistance is exactly what makes the famous mistake so destructive:
The trap: you measure current (probe in the A jack), then forget to move the probe back and try to measure a voltage by placing the probes across a source — like a battery or supply.
Now you've connected a near-zero-resistance path directly across a voltage source. That's a dead short. A huge current surges through the meter's shunt:
- Best case: the meter's fuse blows (its job — to protect you and the meter).
- Worse case: with a strong source (a charged LiFePO4 from L6, a bench supply), sparks, damage to the source, or injury.
The habit that prevents it
The fix is one disciplined habit:
After measuring current, immediately return the red probe to the V/Ω jack.
Leave the meter "at rest" in voltage mode, in the voltage jack. Then a careless next measurement is harmless. Nearly every blown multimeter fuse in the world traces back to skipping this one step. Build the habit now and you'll never be the person sheepishly replacing a fuse mid-diagnosis.
Summary
- Current → series (break the circuit, route flow through the meter).
- Uses a separate low-resistance "A" jack — and that low resistance is why…
- …leaving the probe in the A jack and probing a voltage = dead short → blown fuse.
- Always move the probe back to V/Ω after a current measurement.
The next slide covers the remaining handy modes — diode test and capacitance — and how they pinpoint specific component failures.
Measuring CURRENT requires connecting the meter in series, and the classic costly mistake is:
Diode test, capacitance, and the other modes
Beyond the big four (voltage, current, resistance, continuity), a modern multimeter has two more modes that pinpoint specific component failures fast: diode test and capacitance. Both reach back to components you met earlier in the ladder.
Diode test: is this junction healthy?
Diode-test mode is purpose-built for diodes (L2) — and, usefully, for the junctions inside transistors too. It sends a small current one way, then the other, and reports the forward voltage drop.
A healthy diode behaves asymmetrically (its whole point — the one-way valve from L2):
- Forward (red on anode, black on cathode): the meter shows a small voltage drop — roughly 0.3–0.7V for typical silicon (an LED shows more, and may even glow faintly).
- Reverse (probes swapped): the meter shows "OL" (open) — no conduction.
From that, the diagnosis is instant:
| Reading | Diode is… |
|---|---|
| ~0.3–0.7V one way, OL the other | Healthy |
| Near 0V / beep both ways | Shorted (failed closed) |
| OL both ways | Open (failed open / blown) |
Because transistors are built from junctions (L2), the same test gives a quick "is this transistor obviously dead?" check. Diode test is one of the fastest ways to find a specific blown component on a board.
Capacitance: checking caps
Capacitance mode measures a capacitor's value (in farads — µF, nF, pF — recall L1). The meter charges and discharges the cap and computes its capacitance.
It's useful to:
- Confirm a capacitor's value matches what it should be.
- Spot a failed cap reading far from its rating (or near zero / open).
For best accuracy, measure capacitance out of circuit (or with one leg lifted) and with the cap discharged — like resistance, surrounding components and residual charge skew the reading. (A large charged capacitor should be safely discharged before handling, especially in power circuits from L6.)
These are pinpoint tools
Voltage and continuity tell you where a problem is (no power here, broken connection there). Diode test and capacitance help confirm which specific component has failed once you've narrowed it down. They turn "something in this area is wrong" into "this diode is shorted" — the final step of a diagnosis.
The full multimeter toolkit
You now have the complete multimeter:
- DCV / ACV — is power present and correct? (most-used)
- Current (A jack, series) — how much is it drawing? (mind the fuse trap)
- Resistance / continuity (power off) — connected? right value? broken? shorted?
- Diode test / capacitance — is this specific component healthy?
The next slide ties them into an actual debugging workflow — the order an experienced tech uses them to corner a fault.
The diode-test mode is useful because it:
A multimeter debugging workflow
Knowing what each multimeter mode does is half the skill. The other half is the order you use them in — a workflow that corners a fault efficiently instead of poking around at random. This is how an experienced technician approaches a dead board.
The golden rule: follow the power
Faults hide, but power doesn't lie. The workflow is essentially trace the power from source toward the fault, measuring as you go.
A worked multimeter workflow
Imagine a small board that "does nothing." Here's the disciplined sequence:
1. Is power even arriving? (DCV) Black probe on ground, red on the input power pin. Expected: the supply voltage (say 5V).
- Reads 0V → the problem is upstream (cable, connector, source). Stop here — you've localised it.
- Reads correct → power arrives; move on.
2. Does power reach the key chips? (DCV) Probe the supply pin of the microcontroller / regulator output.
- Input present but regulator output 0V → the regulator or its surroundings are suspect.
- All rails correct → power is fine; the fault is in signals or a specific part.
3. Are connections intact? (continuity, power OFF) Suspect a broken trace, cold joint, or connector? Power down and beep through the suspect path.
- No beep where there should be one → found a break / bad joint.
4. Is a component shorted or dead? (resistance / diode test, power OFF) If a rail reads low or the supply struggled (next lesson's current-limit clue), look for a short: probe across the rail to ground (very low resistance = short), and diode-test suspect diodes/transistors.
5. Confirm the specific culprit. Once narrowed to an area, diode test / capacitance / resistance confirms which part failed.
Why this order works
Each step eliminates a whole category of fault before moving deeper:
- Power present? rules out the most common failure first.
- Connections intact? rules out the second most common (broken joints/wires).
- Only then do you hunt individual components.
Jumping straight to "swap the microcontroller" skips the 80% of faults that are power or connection problems — wasting parts and time. Cheap, fast measurements first; expensive assumptions last.
Safety and good habits (recap)
- Power off for continuity, resistance, diode test, capacitance.
- Probe back to V/Ω after any current measurement (the fuse trap).
- Be deliberate with probe placement near high-energy points (L6's batteries store real energy).
- Write down readings as you go — a diagnosis is a chain of evidence, and the notes help you see the pattern.
You've now mastered the multimeter — voltage, current, resistance, continuity, diode test, capacitance, and the workflow that turns them into diagnoses. The next lesson adds a tool that's both a power source and a debugging instrument: the bench power supply.