How to Troubleshoot a PCB Design?
π Overview
A freshly fabbed PCB that refuses to work when you power it up is a moment every electronics hobbyist knows. This guide lays out a systematic troubleshooting flow: check the soldering, test the power rails, verify the connections, review the schematic and layout, search online, ask a forum, and finally fix it by hand.
Rather than guessing and desoldering parts at random, work through a routine that narrows the problem down step by step - that is what this article is.
π§° What you need
- Multimeter (essential)
- Oscilloscope (optional, for tracing signals)
- Soldering iron + hot air station (for repairs)
- Magnifier/microscope (to inspect joints)
π§ Step by step
Finish all the soldering
Make sure the soldering is complete first: cold joints and missed pads are the number one culprit
Inspect the board under magnification, especially IC pin alignment and electrolytic capacitor orientation
Power it up
Test the supply voltage with no load connected first
If anything gets hot or smokes, cut the power immediately and start at the power section
Check the connections
Use the multimeter continuity beeper to verify each critical net
Work through ground, power, and signals against the schematic one at a time
Review the schematic and layout
Look again at the schematic: component pinout, polarity, and pin numbering
Check the layout: footprint orientation, silkscreen, and keep-out conflicts
Search online
Read the datasheet and search for 'chip name not working'
Common traps: missing decoupling, reset circuitry, missing pull-ups
Ask a forum
When posting, include: schematic, PCB image, measured voltages, and a description of the symptom
The more specific your description, the easier it is for others to pinpoint the problem
Fix it by hand
Bodge wires, cut traces, swap parts - whatever gets it working
Change one thing at a time and retest; never make several changes at once
Takeaway
Write down what the fault was so you avoid it in the next design
Debugging skill = soldering + measurement + research + communication
π‘ Tips
- Get into the order: visual inspection, then power rails, then signals - do not pull components at random
- Keep spare chips on hand; plenty of faults are bad parts rather than bad design
- Record every debugging session - it is the fastest way to improve