Troubleshooting Methodology

Tools and component knowledge are ammunition; methodology is marksmanship. This module is the universal process that makes you efficient (fewest measurements to the answer) and accurate (the answer is actually the root cause). Memorize the sequence; the rest of your career is refining it.

The sequence

1. Understand the complaint → 2. Look → 3. Power-off checks → 4. Power-on: rails → 5. Heartbeat (clock & reset) → 6. Localize (half-split) → 7. Confirm the component → 8. Root-cause → 9. Repair, verify, document

1. Understand the complaint

Read the work order / ATE failure ticket / squawk completely before touching the board. What test failed, with what measured value, against what limit? Intermittent or hard? Any history (repeat offender)? The failure ticket tells you where to look — it does not always tell you what is broken (a "failed resistor" at ICT may be a cracked solder joint, a bent test pin, or a neighbor loading the net — see 09 — Teradyne Machines & Automated Test (ATE)). Define "known good": get the schematic, the test spec (expected voltages/currents/waveforms), and ideally a golden board for comparison.

2. Look (and smell)

Five disciplined minutes under magnification beats an hour of probing. Aerospace shops will give you a stereo microscope — use it. Hunt for:

• Burnt/discolored parts or board areas; the smell of burnt epoxy
• Bulged/vented electrolytics; cracked MLCCs/tantalums
• Cracked, dull, or ring-fractured solder joints; lifted leads; tombstones
• Bent/recessed/corroded connector pins; broken connector tails
• Corrosion, dendrites, flux residue, liquid ingress staining
• Foreign object debris (FOD) — a loose screw or solder ball does real damage
• Missing, wrong, or backwards components (compare to the assembly drawing; remember DNP parts are supposed to be absent)
• Conformal coating damage — often marks the spot of mechanical insult
• Prior rework — a repeat-failure board's history is written in its touched-up joints

3. Power-off checks

• Fuses: continuity (never by eye).
• Each power rail to ground: ohms/diode-mode signature. Note values; compare to golden board. Dead short found here saves you from powering into it.
• Input protection parts (TVS, reverse diode) not shorted.
• Connector pins to their first destination: continuity.

4. Power-on: rails first

• Current-limited bench supply whenever the setup allows: set expected voltage, limit current just above expected draw. The current readout is your first diagnostic — too high (short/latch-up) or too low (something not starting) each prune half the fault tree.
• Measure every rail at its test point, in dependency order (28V in → 5V → 3.3V → 1.2V...). Each must be present, in tolerance, and (scope) clean. A missing rail: check its regulator's input first — don't condemn a regulator that's never been fed. A sagging rail: regulator weak, or load heavy? Lift the load (link/bead) to decide.
• A huge fraction of all dead boards die right here, in the power chain. Master modules 08 — Analog Board Troubleshooting §power supplies.

5. Heartbeat: clock and reset

For anything with a processor/FPGA: rails good → clock running (scope) → reset releasing properly (scope, single-shot on power-up). No clock or perpetual reset explains almost any "board is totally dead but rails are fine" complaint. See 07 — Digital Board Troubleshooting.

6. Localize: half-split / signal tracing

The efficiency engine. The board is a signal chain: stimulus in one end, response out the other.

• Half-split: measure at the chain's midpoint. Good there? Fault is downstream. Bad? Upstream. Each measurement halves the territory — a 16-stage chain falls in 4 measurements. Use natural midpoints: connectors, buffers, test points, stage boundaries.
• Signal tracing: inject/apply a known stimulus at the input, follow it stage by stage with the scope until it disappears or corrupts. The fault lives between the last good node and the first bad one.
• Signal injection (reverse): drive a known signal into successive points walking backward from the output until the output responds.
• Comparison: any measurement you can't interpret, make on the golden board. Diode-signature comparison (04 — DMM Mastery §5) localizes digital damage astonishingly fast.

7. Confirm the component

Before condemning a part: isolate it (lift a leg / remove it) and verify it actually fails out of circuit, or prove it with an in-circuit measurement that has no alternative explanation. The joint, the via, and the trace are suspects of equal rank with the component — "R47 open" at the tester is just as often "R47's pad cracked."

8. Root-cause

Ask why it failed before closing:

• Burnt resistor → what overloaded it? (Find the short before installing the new one.)
• Shorted TVS → what transient? (It did its job.)
• Cracked joints/via → thermal or mechanical stress; will the replacement crack too?
• Repeat-failure unit → the previous repair treated a symptom. For intermittents, root-cause requires making it fail on demand: heat (hot air), cold (freeze spray), flex (gentle board torsion), vibration (tapping with an insulated tool) while a scope in Normal/Single trigger watches the symptom. A fault you can summon is a fault you can find; a fault you can't reproduce is not yet diagnosed — never ship "could not duplicate" without a serious provocation effort.

9. Repair, verify, document

• Repair per IPC-7711/7721 and shop procedure (10 — Aerospace Standards, ESD, and Workmanship) — correct part (BOM revision!), correct orientation, coating restored.
• Verify: re-run the failing test AND the full acceptance test (your repair must not have broken something else).
• Document: symptom → cause → action → verification, with measured values. In aerospace this is the product.

Failure statistics — where to bet first

Industry experience across electronics reliability consistently ranks the usual suspects roughly:

1. Solder joints and interconnects (joints, vias, traces) — the plurality of all board faults, rising with thermal cycles and vibration (aerospace life is exactly that)
2. Connectors and contacts — fretting, corrosion, bent pins, cable strain
3. Capacitors — electrolytics dry out, tantalums short, MLCCs crack
4. Mechanical/electromechanical — relays, switches, fans
5. Semiconductors — usually killed by something else: overvoltage, ESD, heat, the shorted cap next door

So: the boring physical stuff first, exotic IC failures last. The microscope and the continuity beeper out-diagnose the logic analyzer most days.

Efficiency habits

• Predict before you probe. Write the expected value, then measure. A measurement without a prediction teaches nothing.
• Change one thing at a time, re-test after each change.
• Don't trust your memory of a measurement — log values as you go.
• Beware the second fault. Lightning/overvoltage events and cascading failures produce multiple casualties; fixing one and re-testing is how you find the next.
• Beware your own probe. A slipped tip bridges pins; a probe's capacitance can stop a marginal oscillator. If behavior changes when you touch it, that's data — and possibly your fault.
• Time-box rabbit holes. Twenty minutes without progress → step back to the sequence: what do I know, what's the cheapest measurement that splits the remaining possibilities?

Self-check

1. Recite the 9-step sequence from memory.
2. Board draws 10× expected current at power-up. Which steps does this prune? Reveal answer
3. ATE says C31 failed, measuring 2nF vs 100nF expected. Give three explanations beside "bad cap." Reveal answer
4. What's the fastest way to halve a 12-stage signal chain fault? Reveal answer
5. Why must a burnt resistor never be just replaced and shipped? Reveal answer

Next: 07 — Digital Board Troubleshooting