Electronics & Circuits · Study deck
Common Circuit Mistakes
Picture a board that resets each time a relay turns off.
Voltage Vera is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: For the chapter case of 5 V, a 2.0 V red LED, and 20 mA, the correct value is 150 Ω; ignoring the LED gives 250 Ω and only 12.0 mA, a 40% shortfall.
- Explain: If the voltage collapses, a part warms, a pin exceeds its expected current, or a sensor reference shifts when a load switches, stop and trace the loop before retrying with higher power.
- Explain: If you only need the intuition, use this rule: before powering a circuit, prove the voltage budget, current budget, power budget, polarity, ground path, and measurement plan.
Major section
Start Simple
A loose return path, supply drop, reversed part, or switching spike can create the same symptom and survive every software change.
- Firmware means the software stored on a device.
- This check does not replace safe isolation or a full circuit review.
- The deeper sections show unit conversion, voltage headroom, power loss, inductive loads, grounding, measurement limits, and pre-power evidence for common faults.
Major section
Overview: Most Pitfalls Are Review Failures Before They Are Circuit Failures
Electricity mistakes in IoT projects usually happen before power is applied.
- A design mixes units, forgets a voltage drop, ignores current limits, treats a power rating as optional, shares a noisy return path, or uses a formula outside the condition where it applies.
- Thermal Limits Resistance alone is not enough.
Major section
Overview: Most Pitfalls Are Review Failures Before They Are Circuit Failures (continued)
The hardware then fails quickly, intermittently, or only after deployment stress.
- The practical response is a pre-power evidence habit.
- “Before you blame the code, follow the current — most ‘bugs’ are a loose ground or a wrong resistor.”.
- Loads, inductive devices, and shared grounds need drivers and return-path review.
Major section
Overview: Most Pitfalls Are Review Failures Before They Are Circuit Failures (continued)
LEDs, diodes, transistors, regulators, wires, and connectors can leave less headroom than expected.
- In this chapter Vera probes each pitfall before power is applied, not after a part overheats.
- This pre-power sequence connects basic electrical arithmetic to the chapter's running habit of preventing overheated parts and unexplained resets at schematic review.
- The part also needs a power rating, temperature margin, and mounting condition that match the real circuit.
Major section
Overview: Most Pitfalls Are Review Failures Before They Are Circuit Failures (continued)
If you only need the intuition, use this rule: before powering a circuit, prove the voltage budget, current budget, power budget, polarity, ground path, and measurement plan.
- Pin And Return Limits GPIO pins are control signals, not general power supplies.
- This evidence connects the pin limit to the complete current loop rather than treating the GPIO label as permission to power the load.
- Wrong?: treating resistance as the whole rating — thermal margin is a separate check.
Major section
Practitioner: Use A Pitfall Ledger
A pitfall ledger is a short review record for every risky interface.
- It should be used for LEDs, sensors, relays, motors, heaters, long cables, power rails, analog inputs, and any circuit connected near mains-powered equipment.
- The ledger makes the reviewer ask whether the design has a calculation, a datasheet limit, and a measurement plan.
- The key distinction is between a schematic that can be drawn and a circuit that can survive.
Major section
Practitioner: Use A Pitfall Ledger (continued)
Pin limit from the datasheet, driver device, external supply, flyback path, common ground plan, and firmware safe state.
- A GPIO can draw a line to a load in a diagram, but the physical pin still has current, voltage, protection, and thermal limits.
- Another reviewer can repeat the calculation and get the same units and result.
- A motor, relay, solenoid, strip LED, or long cable is connected as though a microcontroller pin were a power output.
Major section
Under The Hood: Why Small Errors Become Field Failures
A unit error can choose the wrong resistor.
- The wrong resistor can raise current.
- Heat changes component behavior and may stress a driver.
- The physics is simple but unforgiving.
- Current needs a complete loop.
Major section
Under The Hood: Why Small Errors Become Field Failures (continued)
Inductors resist sudden current changes.
- Semiconductor pins and packages have absolute limits, recommended operating limits, thermal limits, and failure modes that are not reset by power cycling.
- A current-limited supply, a meter on the supply rail, and a written stop condition turn a fault into evidence instead of damage.
- Voltage Drop To Brownout Regulator dropout, diode drops, cable resistance, and load pulses can leave the microcontroller below its reliable operating range.
Major section
Under The Hood: Why Small Errors Become Field Failures (continued)
If the voltage collapses, a part warms, a pin exceeds its expected current, or a sensor reference shifts when a load switches, stop and trace the loop before retrying with higher power.
- Inductive Spike To Latent Damage A relay, motor, or solenoid can generate a turn-off spike that damages the driver immediately or weakens it for later failure.
- When current through an inductive load is interrupted, stored magnetic energy still needs a path.
- The resulting waveform and component limits—not a single successful activation—decide whether the protection is adequate.
Major section
Under The Hood: Why Small Errors Become Field Failures (continued)
A device that survives one bench cycle may still accumulate avalanche or thermal stress, so repeat the measurement at the highest supply, hottest enclosure, and fastest commanded switching.
- Wrong?: assuming a part is safe because it worked once — failure modes “are not reset by power cycling.”.
- Retest when a change can alter available voltage, current demand, impedance, coupling, or heat.
- The supply, regulator, battery chemistry, cable length, connector, or load current changes.
Major section
Under The Hood: Why Small Errors Become Field Failures (continued)
A new battery chemistry or regulator changes source behaviour; a longer cable or different connector changes resistance and interference pickup; a new package or substitute driver changes ratings and thermal paths.
- Firmware can be an electrical change too when it alters startup ordering, PWM duty, sampling cadence, sleep current, relay timing, or radio bursts.
- If the circuit moves near motors, heaters, or mains equipment, add those noise and load states explicitly instead of assuming the bench result survives.
- A firmware update changes sleep state, PWM duty cycle, relay timing, sampling rate, or startup behavior.
Major section
Phoebe's Field Notes: Where the "Forgotten Vf" Current Actually Goes
The mathematical gist.: Kirchhoff requires V_{supply}=IR+V_f, so the resistor must be R=(V_{supply}-V_f)/I.
- For the chapter case of 5 V, a 2.0 V red LED, and 20 mA, the correct value is 150 Ω; ignoring the LED gives 250 Ω and only 12.0 mA, a 40% shortfall.
Deck summary
Key takeaways
A loose return path, supply drop, reversed part, or switching spike can create the same symptom and survive every software change.
- Electricity mistakes in IoT projects usually happen before power is applied.
- The hardware then fails quickly, intermittently, or only after deployment stress.
- LEDs, diodes, transistors, regulators, wires, and connectors can leave less headroom than expected.
- If you only need the intuition, use this rule: before powering a circuit, prove the voltage budget, current budget, power budget, polarity, ground path, and measurement plan.
Retrieval practice
Recall check 1 of 3
Voltage Vera says: answer from memory, then check your reasoning.
Q1A circuit review says an LED resistor was calculated from the full supply voltage, but the LED forward drop was not subtracted. What is the strongest finding?
Show answer
Answer: A A pre-power review should confirm each voltage drop and the actual voltage available to current-limiting parts.
Retrieval practice
Recall check 2 of 3
Voltage Vera says: answer from memory, then check your reasoning.
Q2A relay coil is shown connected directly to a microcontroller output. The schematic has no transistor or MOSFET driver and no flyback path. What should the review require?
Show answer
Answer: A The practitioner review should separate control signaling from load power and handle inductive energy safely.
Retrieval practice
Recall check 3 of 3
Voltage Vera says: answer from memory, then check your reasoning.
Q3A prototype works on USB power, but in the enclosure the radio transmit pulse resets the microcontroller and analog readings jump when a motor starts. Which failure chain should be investigated first?
Show answer
Answer: D Electrical failures often appear as resets, noisy readings, or intermittent behavior when supply and return-path margins are weak.
Print reference
Answers
Answer key.
- A · A pre-power review should confirm each voltage drop and the actual voltage available to current-limiting parts.
- A · The practitioner review should separate control signaling from load power and handle inductive energy safely.
- D · Electrical failures often appear as resets, noisy readings, or intermittent behavior when supply and return-path margins are weak.