Chapters

3 Voltage, Current, and Resistance

electronics-controller-design
electricity

3.1 Start Simple

Imagine a small sensor node powered by a coin cell. Voltage is the push available between two points, current is the flow through the chosen path, and resistance is what keeps that flow under control. Start with one source, one load, one return path, and one measurement that proves the circuit is behaving as intended.

The mathematical gist. For the chapter’s 5.00 cm of 24 AWG copper, (A=\pi(d/2)^2) and (R=\rho L/A) give about 4.10 milliohms. At 50.0 mA, (J=I/A) and (v_d=J/(nq)) give about 17.9 micrometres per second, so an electron takes roughly 46.5 minutes to drift along the wire even though the electric field traverses it in about 167 ps; the rail drop is only about 0.205 mV.

Math Bridge · guided foundationsHow can a circuit respond fast when electrons drift slowly?Let Eddie connect wire geometry, resistance, current density, drift speed, transit time, and voltage drop.

3.2 Overview: Electricity Needs a Complete Loop

Electricity is the movement of charge through a circuit. In IoT hardware, that movement powers processors, sensors, radios, indicators, and actuators. A useful beginner model starts with a source, a load, conductors, and a return path. If the path is incomplete, current does not flow through the load in the intended way.

The four quantities that appear in almost every circuit review are voltage, current, resistance, and power. Voltage is the potential difference between two points. Current is charge flow through a path. Resistance limits current. Power is energy use per time and is the reason parts heat up and batteries drain.

The source does not create energy from nothing; it transforms another stored or delivered form into electrical potential. A battery begins with chemical energy, a generator begins with mechanical motion, a solar cell begins with radiant energy, and a power station may begin with non-renewable fuel, renewable flow, or nuclear heat. The upstream source matters for sustainability and capacity, but the circuit still has to prove the same voltage, current, resistance, and power claims.

Voltage Vera, the circuits guide

Voltage Vera

“Before you blame the code, follow the current — most ‘bugs’ are a loose ground or a wrong resistor.”

In this chapter Vera turns each of the four ideas into a probe point: name it, measure it, then check it against the rating.

Inspect this evidence before proceeding: the four electrical quantities are related, but they answer different diagnostic questions. Use Figure 3.1 to establish the causal order before applying the chapter’s complete-loop review to a real load.

Electrical units hierarchy showing voltage as the cause, resistance as opposition, current as the effect, and power as the result.
Figure 3.1: Cause-and-effect hierarchy for voltage, resistance, current, and power.

At the top of Figure 3.1, VOLTAGE (V) = CAUSE supplies the push, while RESISTANCE (R) = OPPOSES limits the response. Those two lead to CURRENT (I) = EFFECT, the actual charge flow through the closed path, and finally POWER (P) = RESULT, which connects the circuit to heating and battery drain. The inset’s “Check voltage first” and “Then check resistance path” make the drawing a troubleshooting sequence: verify the voltage across the load and its return path before treating a current or power symptom as a software fault.

That order keeps beginner debugging grounded. First ask what voltage difference is actually available across the load, not just whether one wire is labeled 3.3 V. Next ask what resistance or impedance is in the path: a resistor, sensor element, wire fault, transistor channel, or accidental short can all change the current. Then ask where current really flows. Finally, calculate or measure power in the parts that drop voltage while carrying current.

The quantities are connected, but they are not interchangeable. A circuit can show a supply voltage while no useful current flows through the load. A low-resistance path can pull too much current even when the voltage looks normal. A small current can still matter if the device sleeps for months on a battery. Useful electricity notes therefore name the two voltage nodes, the current path, the current limit, and the state where the measurement was taken.

If you only need the intuition, keep this sentence: voltage is measured across, current flows through, resistance limits, power heats and drains, and ground is the shared reference.

3.2.1 The First Four Ideas

Voltage

A difference in electrical potential. It is measured between two points and gives context to every signal level.

Current

Charge flow through a closed path. It must be limited so wires, pins, regulators, and parts stay within their ratings.

Resistance

Opposition to current. It is used in current limiting, pull-ups, dividers, sensing elements, and protection networks.

Power

Energy per time. Power checks connect electrical design to heat, battery life, regulator capacity, and safety margin. Calculate it from voltage and current measured in the same operating state, because an idle voltage paired with a transmit current describes no real condition. Follow the energy path from source through regulator and load, noting every element that drops voltage while carrying current. Those losses become heat and reduce usable battery energy. Compare both average and peak power with the source, package, enclosure, and thermal limits before calling the circuit sustainable.

Vera’s Probe Points

  • Measure: voltage as “a difference in electrical potential,” current as “charge flow through a closed path.”
  • Expect: resistance as “opposition to current,” power as “energy per time” — the four ideas this chapter opens with.
  • Wrong?: treating one quantity’s label as proof of another — a voltage rating is not a current or power claim.

3.2.2 Beginner Checks

Review a beginner circuit as one closed energy path. Identify the source and return before measuring anything, then place the voltmeter across the load so both reference points are explicit. If current is the question, insert the ammeter in the branch that actually feeds the load rather than placing it across a supply. Compare the observed current and voltage with the source, conductor, pin, and component ratings, and translate their product into power and possible heat. When two boards exchange a signal, verify a common reference and compatible logic levels. This sequence prevents a labelled rail or an idle reading from being mistaken for proof that the complete circuit works safely.

  • Confirm the circuit has a source, a load, and a return path.
  • Measure voltage across the load, not at a single point without a reference.
  • Measure current in the path that actually feeds the load.
  • Check component ratings for voltage, current, and power before assuming the circuit is safe.
  • Use a common ground when two parts must compare signal voltages.

3.2.3 Overview Knowledge Check

3.3 Practitioner: Review the Circuit as Evidence

A practical electricity review turns a schematic or breadboard into a set of claims that can be checked. The review asks where current flows, what voltage each part sees, which element limits current, where heat may appear, and how measurements prove the design matches the intended operating state.

For IoT work, this review should include both steady behavior and transitions. A board may be safe while idle but fail when a radio transmits, a motor starts, a sensor heater turns on, or a GPIO pin changes mode. The electrical record should name the states that were checked.

3.3.1 How to Review a Simple IoT Circuit

Carry the review from topology to measurement. Trace the source, limiting element, controlled device, load, and return as one loop, noting every rail and ground reference that crosses a connector or board boundary. Estimate branch current with the appropriate model, then compare it with GPIO, regulator, wiring, and load limits. Convert voltage drop and current into dissipation wherever a part may heat. Finally reproduce the intended firmware state—startup, transmit, sleep, or actuator movement—and record the actual voltages, currents, and behaviour. If the measured state differs, return to the first boundary where the expected and observed evidence separate instead of changing several parts at once.

  1. Trace the loop. Mark the source, load, current-limiting element, switch or transistor, and return path.
  2. Check voltage references. Confirm ground, supply rails, logic thresholds, and signal references are compatible.
  3. Estimate current. Use Ohm's Law where it applies, then check current against pin, regulator, sensor, and load ratings.
  4. Check power. Identify where voltage drop and current become heat, and compare against component ratings.
  5. Measure the real state. Record voltage, current, and behavior with the actual wiring, firmware state, and load.

3.3.2 Circuit Review Ledger

Item
Question
Useful Evidence
Common Failure
Loop
Where does current leave the source, pass through the load, and return?
Annotated schematic, continuity check, and measured voltage across the load.
A missing return path or loose ground makes the circuit look unpredictable.
Reference
Do the communicating parts share a valid voltage reference?
Ground check, rail measurement, logic-level check, and pull-up or pull-down value.
A signal is read without a shared ground or stable bias.
Current
What limits current, and are pins, wires, regulators, and loads within ratings?
Ohm's Law calculation, current measurement, and component datasheet limits.
A GPIO pin drives a load directly without a current limit or driver stage.
Power
Where does heat appear, and can the part or package dissipate it?
Power calculation, thermal observation, regulator margin, and measured current state.
The circuit works briefly but overheats, resets, or drains the source too quickly.

3.3.3 Practitioner Knowledge Check

3.4 Under the Hood: References and Ratings Define Trust

Under the hood, electricity in IoT circuits is about boundaries. Voltage only has meaning between two nodes. Current only flows through a complete path. Resistance, capacitance, inductance, semiconductor behavior, and wiring all shape the actual current path. Ground is not magic; it is the reference node that parts use to compare signal voltages.

Ratings are also boundaries. A part can tolerate only certain voltages, currents, power dissipation, and temperature conditions. Exceeding a rating may cause immediate failure, gradual damage, misleading readings, or intermittent resets. That is why electrical evidence should include both calculations and measurements under real operating states.

The deeper rule is that circuit claims must balance. Around a closed loop, the voltage rises from sources and the voltage drops across loads must account for one another. At a node, current entering and current leaving must have a path. If those balances do not match the sketch, the sketch is missing a path, a reference, or a load state. This is why a breadboard that looks connected can still fail when a ground rail is split, a jumper lands one row off, or a meter lead measures against the wrong reference.

Measurements also change the evidence depending on where the instrument is placed. A voltmeter is placed across two nodes and usually draws very little current, so it can show a plausible voltage on a weak or floating node. An ammeter is placed in series with the path and changes the circuit if it is put across a source by mistake. A current-limited supply, bench meter, and temperature check together give a safer picture than any single number.

3.4.1 Boundary Checks

Node Boundary

Voltage measurements need named nodes: supply to ground, signal to ground, or voltage across a specific component.

Path Boundary

Current follows available paths, including unintended paths through protection diodes, pull-ups, shields, or shared grounds.

Rating Boundary

Part ratings set allowed voltage, current, power, temperature, polarity, and transient behavior.

State Boundary

A measurement applies only to the firmware state, load, wiring, source, and environment where it was taken.

3.4.2 Failure Patterns

Diagnose these patterns by the evidence they disturb. A floating input changes logic state without a valid driver, so inspect its pull network and leakage paths. A ground mismatch shifts the reference used to interpret every signal crossing the boundary. A hidden load appears when startup, heating, motor movement, or radio transmission demands more current than an idle measurement revealed. An optimistic measurement hides all three by sampling only the easiest state. Recreate the failing state, measure the supply at the load and the return path under current, and compare the trace with the expected limits. The first boundary that departs from expectation identifies the corrective action and the condition that must be retested.

Keep time alignment between the symptom and the electrical observations. If a sensor value jumps exactly when the radio transmits, capture the rail at the sensor and the shared ground during that burst; a bench supply display or slow multimeter may average away the dip. If an input changes when a cable is touched, compare its driven and undriven states and verify the pull resistor at the receiving pin. The useful outcome is not merely a named failure pattern but a reproduced trigger, a measured boundary violation, and a post-fix trace under the same trigger.

  • Floating input: a signal has no stable pull-up, pull-down, or driver, so it reads random values.
  • Ground mismatch: two devices exchange signals without a valid common reference.
  • Hidden load: an LED, sensor heater, motor start, or radio burst pulls more current than the source can supply.
  • Optimistic measurement: voltage and current are measured only at idle, not during startup, transmit, switching, or fault states.

Vera’s Probe Points

  • Measure: check for a floating input, a ground mismatch, and a hidden load before trusting an idle reading.
  • Expect: “a signal has no stable pull-up, pull-down, or driver” reads random values; a hidden load “pulls more current than the source can supply.”
  • Wrong?: measuring only at idle — this chapter’s own fix is to check startup, transmit, switching, and fault states too.

3.4.3 Under-the-Hood Knowledge Check

3.5 Summary

Electricity in IoT circuits is about controlled charge flow through a complete path. Voltage is a difference between nodes, current flows through loads, resistance limits current, and power connects electrical behavior to heat and energy use. Reliable circuit work combines a clear schematic, rating checks, and measurements taken in the real operating state.

3.6 Key Takeaway

Start every electricity review by tracing the loop, naming the reference, checking current limits, and measuring the real circuit state.

3.7 See Also

Electricity Fundamentals

Review the broader electricity evidence model for IoT circuits.

Ohm's Law

Use voltage, current, resistance, and power equations for resistive circuit checks.

Electricity Common Pitfalls

Avoid common wiring, grounding, unit, current-limit, and power-rating mistakes.

Electricity Applications

Apply these checks to pull-ups, dividers, loads, protection, and sensor circuits.