OSPCB.011 advances the printed-circuit-board engineering course from production inspection to systematic fault diagnosis. A PCB that looks undamaged may contain a fractured copper path, an unintended solder bridge, or a failed connection. The correct starting point is an intended circuit and testable hypothesis, not a multimeter beep. Review OSPCB.010, How Circuit Boards Are Inspected and Tested, before proceeding.
Objectives and prerequisites
- Distinguish an open from a short and from legitimately low resistance.
- Identify nets and test pads using a schematic or KiCad layout.
- Apply a safe, power-off continuity-testing procedure.
- Document evidence and explain when a reading remains inconclusive.
Prerequisites: elementary DC circuits, multimeter functions, schematic symbols, and OSPCB.002 on pads and vias. Practice with an unpowered isolated training board rather than operational mining or data-center hardware.
Open circuits versus short circuits
An open circuit interrupts an intended electrical path: a cracked trace, damaged via, lifted solder pad, or broken connector can leave two points disconnected. A short circuit adds an unintended conductive path between points that should remain isolated: a solder bridge, metal fragment, or insulation failure may connect two separate nets. A net is the set of nodes that the circuit design intends to connect.
Low resistance cannot establish a short without context. Ground copper, coil windings, current-sensing resistors, and certain power rails may read low by design. Likewise, a continuity beep represents an instrument-dependent resistance threshold, not proof of correct operation. Fluke explains why beep behavior and resistance values require careful interpretation.
Safety: measure resistance only when isolated
Disconnect every power source before continuity, resistance, or diode measurements. Stored charge can persist even after disconnection. Follow equipment-specific shutdown, lockout, discharge, and absence-of-voltage procedures; hazardous circuits require authorized qualified personnel. Never treat a disconnected mains supply, power conversion unit, ASIC hashboard, or battery pack as automatically safe. See Fluke’s official multimeter guidance.
Trace the designed path using a schematic and netlist
Start with the correct board revision and locate the suspected net in the schematic. Follow it through pads, vias, copper traces, connectors, and test points. KiCad’s Highlight Net function illuminates the selected connection, while cross-probing links schematic elements to PCB elements. Its Design Rules Checker identifies selected layout errors against the configured netlist and design constraints, but cannot prove that a manufactured board has no cracked traces. Consult KiCad’s PCB Editor documentation and OSPCB.008 on fabrication handoff.
A reproducible seven-step fault-finding workflow
- Identify the assembly: record board model, revision, serial reference when permitted, symptom, and tested nets.
- Inspect under magnification: look for mechanical damage, solder bridges, corrosion, lifted pads, or residue. Photograph suspect regions.
- Confirm the expected topology: read the schematic or approved test map before deciding which points should connect.
- Verify the meter: select the correct input terminals and mode. Short the tips together to estimate lead and contact resistance.
- Check intended continuity: test separated accessible points on one net. An open reading may indicate a break, incorrect endpoint, or poor contact.
- Check intended isolation: test nets expected to remain separate. Low readings may be caused by components or parallel paths, not necessarily a fault.
- Document and escalate: log units, probe locations, meter model, readings, board condition, and the next permitted inspection. Avoid speculative power injection.
Interpret the measurement rather than the beep
| Observation | Possible causes | Next evidence |
|---|---|---|
| No continuity across an expected connection | Open trace, bad probe contact, or wrong test points | Confirm net and check intermediate exposed pads |
| Low resistance from supply to ground | Designed low impedance or an unintended bridge | Compare with schematic and equivalent known-good board |
| Adjacent pads show continuity | Same assigned net or solder bridge | Inspect layout net labels and magnified assembly image |
Illustrative calculation: suppose shorted meter leads read 0.3 Ω, and an unpowered training-board connection reads 0.5 Ω. Subtracting yields an apparent 0.2 Ω contribution from the test path. The estimate is vulnerable to probe pressure, resolution, and parallel conductive paths. No specific component failure threshold follows from an invented example. For a mining-hardware comparison, review OSHRE.008 on hashboard resistance baselines.
Hands-on lab: a removable-jumper open fault
Equipment: an isolated unpowered practice circuit with two test pads joined by a removable jumper, a digital multimeter, and a hand-drawn connection map. The described exercise is instructional, not an editor-verified hardware test. Never use a plugged-in board.
- Predict which two test points should show continuity with the jumper installed.
- Check the meter’s probe-short baseline and record the connection reading.
- Remove the jumper to create a controlled open; test the same pair again.
- Reinstall the jumper, repeat the check, and document why the changing readings support the hypothesis.
Knowledge check with answer key
Q1: Does a beep between a supply rail and ground prove a short? Answer: No. Low impedance may be intentional, and in-circuit components can affect readings. Check the design and validated reference.
Q2: Can a physical PCB fail even after the KiCad design passes DRC? Answer: Yes. Manufacturing defects and service damage occur after the design stage.
Q3: What supports diagnosis of the training-board open? Answer: A repeatable open reading after removing the jumper and restored continuity after reinstalling it, assuming no alternate current path.
References and next steps
Review Fluke’s resistance-measurement instructions and OSPCB.007 on signal integrity. The engineering principle is to correlate test results with circuit intent, not to replace reasoning with a single beep.
We volunteer daily to ensure the credibility of the information on this platform is Verifiably True. If you would like to support to help further secure the integrity of our research initiative, please scan the QR code below.


Leave a Reply