Your Breadboard Works, but Can Anyone Rebuild It? From Wires to a Schematic
Series navigation: Episode 1: The Roadmap · Episode 7: Reading Arduino Pin-Current Specifications · Episode 13
The problem: The prototype works, but its meaning exists only in wire colors and memory.
The goal: Convert physical connections into named, reviewable electrical intent.
The result: A schematic checklist that becomes the source of truth for PCB design.
AI-generated illustration of the documentation transition. It is not a circuit to copy.
The prototype failed after I cleaned the desk
The breadboard had worked the night before. I disconnected a few wires to organize them, rebuilt the circuit from a photo, and the sensor disappeared.
The photo showed where the wires appeared to go. It did not explain which nodes were power, ground, I2C, reset, or an intentionally unused pin. It also did not reveal the breadboard's hidden internal strips.
A working breadboard proves that one physical arrangement worked once. A schematic explains the intended electrical relationships.
A schematic is not a picture of the breadboard
A useful schematic optimizes for meaning, not physical resemblance.
| Representation | Best question |
|---|---|
| Breadboard | Where is this part physically inserted? |
| Netlist/connectivity | Which pins are electrically connected? |
| Schematic | What does each functional block do, and why? |
If two ground symbols share the same net name, they are electrically connected even if no long wire crosses the page. If two lines merely cross without a junction, they may not connect. The CAD tool's rules—not visual intuition—define the result.
Start from an inventory
Before drawing, list each real component:
- exact part number or value;
- package or module variant;
- every pin used;
- every supply voltage;
- connector pinout and orientation;
- required pull-ups, pull-downs, decoupling, and protection;
- test points and programming connections.
Then divide the design into blocks: power input, regulator, controller, sensor interface, driver, connectors, and protection. Draw power flowing generally from left to right and use consistent ground symbols.
Name nets by purpose
Wire colors change. Net names survive.
Prefer names such as:
+5V_INPUT
+3V3
I2C_SDA
I2C_SCL
MOTOR_GATE
RESET_N
SENSOR_INT
Avoid using one generic SIGNAL name or relying on pin numbers alone. A good name helps a reviewer notice that a 5 V signal entered a 3.3 V-only input or that two outputs were accidentally joined.
Active-low signals are often marked with a suffix such as _N. Choose a convention and explain it.
Capture the parts the breadboard hides
Beginner prototypes often omit or obscure the components that make a product reliable:
- a decoupling capacitor close to each IC supply pin;
- bulk capacitance near load or power entry;
- pull resistors that define reset and enable states;
- flyback or clamp paths for inductive loads;
- reverse-polarity or overcurrent protection;
- connectors with voltage and ground labels;
- programming and debug headers;
- test points on important rails and buses;
- unused-pin treatment required by the data sheet.
Do not add these by habit alone. Link each one to a manufacturer recommendation or a written design requirement.
Pins need identity at both ends
For every connection, verify:
- connector or board label;
- component symbol pin name;
- physical package pin number;
- alternate function selected by firmware;
- allowed voltage and startup state.
This prevents a common failure: a schematic symbol looks correct while its footprint maps signals to the wrong pads.
Power pins deserve explicit attention. Hidden power pins in a schematic library can make a page look clean while concealing a missing rail. For a first board, showing important power pins and decoupling connections explicitly is often safer.
Run ERC, then review what ERC cannot know
Electrical Rules Check can detect many unconnected pins, conflicting driver types, and power-net problems. It cannot know every design intention.
After ERC, perform a human review:
- Are voltage domains compatible?
- Does every IC have the required power and ground connection?
- Are default reset, boot, chip-select, and enable states safe?
- Are pull-up values appropriate for bus capacitance and voltage?
- Can the power source handle startup and fault current?
- Does every connector tolerate being inserted incorrectly?
- Can important rails and signals be measured?
- Does the BOM identify real orderable parts?
Every ERC waiver should contain a reason. “Ignore” is not an explanation.
A reconstruction test
The strongest test is simple:
Could someone rebuild the circuit using only the schematic and BOM?
Ask that person to mark every ambiguity instead of asking you verbally. Each question reveals missing design information.
Version the schematic with the firmware and design notes. When the breadboard changes, update the schematic before the memory of the change disappears.
Completion checklist
- [ ] Every physical component appears in the schematic and BOM.
- [ ] Nets are named by function rather than wire color.
- [ ] Supply voltages and grounds are explicit.
- [ ] Symbol pins match the exact package footprint.
- [ ] Reset, enable, boot, and unused pins have defined treatment.
- [ ] Protection, decoupling, programming, and test access are shown.
- [ ] ERC passes or every waiver has a written reason.
- [ ] Another person could rebuild the circuit without my memory.
Next experiment
Once the schematic expresses the intent, PCB layout turns those logical connections into copper and physical geometry. Next, I will review a first board before manufacturing files make its mistakes expensive.
Comments
Post a Comment