Debugging a Circuit
A circuit that doesn't work isn't one problem — it's a signal that stopped somewhere specific along a chain of stages, whether that circuit is a pedal, a guitar's wiring, or an amp's preamp. This chapter covers how to inject signal at the input and check AC voltage swing or DC bias point stage by stage, left to right, so 'it doesn't work' becomes 'stage two isn't passing signal.'
“It doesn’t work” is not a diagnosis — it’s the absence of one. Every circuit — a pedal, a guitar’s wiring, an amp’s preamp — is a chain of stages, and a silent or broken one almost always means the signal is getting through some of those stages and stopping at one specific point. Debugging is the process of finding that point, and once you find it, “it doesn’t work” turns into “stage two isn’t passing signal” — a problem with an obvious next step, instead of a dead end.
The relay-race mental model
Think of the signal path as a relay race, with each stage a runner handing a baton to the next. If the race stops, you don’t need to inspect every runner at once — you walk the course and find exactly where the baton stopped moving. Everything before that point ran fine; everything after it never got the chance to run at all. Any circuit works the same way: instead of staring at a fully populated board wondering what’s wrong with it, you check each stage in order and find the one place the signal handoff failed.
Inject signal at the input, then follow it stage by stage
Start by feeding a known signal into the circuit’s input — a guitar, a signal generator, or even a simple audio source — so there’s something to actually trace. Then, moving left to right through the circuit in the same stage order used throughout this book (see reading schematics and the workflow chapter), check each stage in turn with a multimeter set to measure two different things depending on what the stage does:
- AC voltage swing — at a point where audio signal should be present, a multimeter’s AC range (or, more precisely, an oscilloscope if you have one) should show a swinging voltage that tracks whatever you’re feeding into the input. No swing at a point where the previous stage clearly had one means the signal died between those two points.
- DC bias point — at a transistor’s base, collector, or emitter, or an op-amp’s output, there’s a specific resting DC voltage the circuit is designed to sit at with no signal present, usually derivable from the schematic’s resistor values using Ohm’s Law. A bias point that’s wildly off from what the schematic predicts points to a wrong part value, a bad joint, or a part installed backwards at that specific stage, before you’ve even gotten to checking whether AC signal passes.
Stop at the first stage that fails
The critical discipline here is to stop checking forward the moment you find a stage that doesn’t pass signal or doesn’t bias correctly — that stage is where the problem lives, and everything after it is irrelevant until it’s fixed. It’s tempting to keep probing every remaining stage “just to be thorough,” but a stage downstream of a broken one will always look broken too, for the trivial reason that nothing is reaching it. Fix or re-inspect the failing stage first — check its solder joints, its part values, and its orientation against the schematic — then retest from the input again before moving further down the chain.
Common mistake: treating a silent pedal as one unknown
The same trap that shows up in planning a build (see the workflow chapter’s common mistake) shows up again in debugging one: treating “the pedal is silent” as a single, undifferentiated failure instead of a chain of individually testable handoffs. A board with twenty components isn’t twenty things that could be wrong at once from a debugging standpoint — it’s four or five stages, and a stage-by-stage sweep with a multimeter finds the actual failure in minutes instead of hours of re-checking parts at random.
Where this book leaves off, and what comes next
This book — Fundamentals — has covered the theory, the components, and the workflow needed to read a schematic, plan a build, and debug it stage by stage when something goes wrong, and every other book on this site builds on it rather than repeating it. Where you go next depends on what you’re building: Assembly and Effects cover finishing and circuit types for a pedal — footswitch and true-bypass wiring, jack wiring, LED indicator wiring, power supply conventions, and the individual circuit families (fuzz, overdrive, delay, modulation) once the fundamentals to read any one of them are in place. Guitar Electronics and Guitar Mods apply this same theory to the instrument itself — pickups, pots, switching, wiring, and the mod recipes built on top of that theory. Amp Design applies it to tube, solid-state, and hybrid amplifiers. And when something goes wrong in any of those domains, Diagnostics extends the stage-by-stage method taught in this chapter into symptom-first fault trees specific to guitars, pedals, and amps. If you’ve made it this far, you have the foundation every one of those books assumes.