An electric field is created by voltage (stationary or moving charges), while a magnetic field is created by current (moving charges), and a change in one inevitably generates the other. That is the fundamental relationship between the two. On the workbench, you don't see these fields directly, but you see their consequences: a transformer stepping down 120V AC to 12V, or a noisy PWM trace corrupting your microcontroller's ADC readings. Understanding how electric and magnetic fields interact is the difference between a circuit that works in simulation and one that survives in the real world.
The Core Relationship: Voltage Pushes, Current Twists
To understand how these fields relate, we have to look at Maxwell’s equations through the lens of practical electronics. An electric field (E-field) exists whenever there is a difference in potential (voltage) between two points. It points from higher to lower potential and is measured in Volts per meter (V/m). A magnetic field (B-field) is generated exclusively by the movement of charge (current) or a changing E-field, forming concentric loops around the conductor, measured in Tesla (T) or Gauss (G).
The critical link between them is change. A static DC voltage creates a static E-field, and a steady DC current creates a static B-field. They coexist but do not interact. However, the moment voltage or current changes over time, the fields couple. A changing magnetic field induces an electric field (Faraday’s Law of Induction), and a changing electric field induces a magnetic field (Maxwell’s addition to Ampère’s Law). This is the exact mechanism that allows alternating current to propagate through space as electromagnetic waves, and it is the foundational principle behind every inductor, transformer, and motor you will ever wire.
What People Commonly Confuse (And Why It Ruins Your PCB)
The most common mistake hobbyists and junior engineers make is confusing capacitive coupling (E-field interference) with inductive coupling (B-field interference) when troubleshooting noise. Both cause crosstalk between traces, but they require entirely different mitigation strategies.
| Characteristic | Electric Field (Capacitive) | Magnetic Field (Inductive) |
|---|---|---|
| Source | High dv/dt (rapid voltage changes) | High di/dt (rapid current changes) |
| Coupling Mechanism | Parasitic capacitance between traces | Mutual inductance between loops |
| Victim Impedance | Worse in high-impedance circuits | Worse in low-impedance circuits |
| Shielding Solution | Copper foil, grounded guard traces | Twisted pairs, physical distance, ferrites |
If you try to fix a magnetic field loop issue by adding a copper ground plane directly under the trace, you might actually make it worse by creating a tighter parasitic capacitance loop for E-field noise. According to Analog Devices' guidelines on minimizing switching regulator emissions, identifying whether your noise is E-field or B-field driven dictates whether you should focus on shielding or loop-area reduction.
Worked Numeric Example: Calculating Induced Noise
Let’s put numbers to the relationship using a real-world PCB crosstalk scenario. You have a 5A PWM signal driving a motor, routed parallel to a sensitive 3.3V analog sensor trace.
• Motor trace current change (di): 5A
• MOSFET switching time (dt): 50 nanoseconds (50 × 10⁻⁹ s)
• Mutual inductance (M) between the two parallel traces: 12 nanoHenries (12 × 10⁻⁹ H)
When the MOSFET switches off, the current drops from 5A to 0A in 50ns. The rate of change of current (di/dt) is:
di/dt = 5A / 50ns = 100,000,000 A/s (10⁸ A/s)
The changing magnetic field from the motor trace induces a voltage in the sensor trace via Faraday's Law, simplified for mutual inductance as V = M × (di/dt):
V_noise = (12 × 10⁻⁹ H) × (10⁸ A/s) = 1.2 Volts
A 1.2V spike is injected directly into your 3.3V analog line. If this line feeds an ADC, your microcontroller will read massive, erratic jumps in sensor data every time the motor PWM switches. The magnetic field literally generated an electric field (voltage) in the adjacent wire. To fix this, you must reduce 'M' by increasing the physical distance between the traces or routing them orthogonally.
Where You Meet This In Practice
You interact with the E-field/B-field relationship constantly on the bench, usually when managing energy storage and transfer:
- Transformers and Flyback Converters: Current in the primary winding creates a magnetic field in the core. When the primary switch opens, the collapsing B-field induces a massive E-field (voltage) in the secondary winding. This is how isolated power supplies transfer energy without a direct electrical connection.
- Brushless DC (BLDC) Motors: As the permanent magnets spin past the stator coils, the changing magnetic field induces a back-EMF (an electric field) that opposes the supply voltage. You must account for this back-EMF when selecting the voltage rating for your ESC's MOSFETs.
- Snubber Circuits: When you place an RC snubber across a relay coil, you are providing a path to dissipate the energy of the collapsing magnetic field so it doesn't generate a destructive high-voltage E-field spike that arcs across the relay contacts.
Real-World Scenario Walkthrough: The Randomly Resetting ESP32
Here is a classic bench failure that perfectly illustrates what happens when you ignore field coupling.
The Setup: A maker was building an automated irrigation controller using an ESP32-WROOM-32 DevKit. The ESP32 drove a 24V, 1A water solenoid valve through a standard mechanical relay. The solenoid and the ESP32 shared a common ground plane on a custom PCB. The system worked perfectly on the bench when the solenoid was disconnected, but in the field, the ESP32 would randomly reboot every time the valve turned off.
The Numbers: The solenoid coil had an inductance of roughly 50mH. When the relay contacts opened, the current (1A) attempted to drop to zero in about 1 microsecond (1µs) before the relay contacts began to arc. The di/dt was 1,000,000 A/s. Using V = L × (di/dt), the collapsing magnetic field in the solenoid generated a theoretical inductive kickback of 50,000V. In reality, the relay arc clamped this, but it still created a massive, high-frequency dV/dt (changing electric field) across the relay contacts and the ground plane.
The Outcome: The ESP32’s watchdog timer triggered, and the chip browned out and reset.
What Went Wrong: The maker had routed the ESP32’s 'EN' (enable) pin trace parallel to the solenoid's ground return path. When the relay opened, the violent collapse of the solenoid's B-field generated a high-frequency E-field spike. This spike coupled capacitively into the high-impedance EN pin trace, pulling it momentarily low and resetting the chip. Furthermore, the shared ground plane caused a 'ground bounce'—the changing B-field induced an E-field across the plane's parasitic inductance, lifting the ESP32's local ground reference above its logic threshold.
The Fix: We added a 1N4007 flyback diode directly across the solenoid coil to clamp the inductive spike, physically separated the relay from the ESP32, and routed the EN pin trace over a solid, unbroken ground plane to shield it from E-field interference. As noted in Georgia State University's HyperPhysics reference on induction, clamping the rate of magnetic field collapse is the primary defense against inductive E-field generation.
FAQ: Electric vs Magnetic Fields on the Bench
Q: Can I shield against both electric and magnetic fields using copper tape?
A: No. Copper is highly conductive, making it an excellent Faraday cage for blocking electric fields (E-field). However, low-frequency magnetic fields (B-field) will pass right through copper. To shield against low-frequency B-fields, you need a material with high magnetic permeability, like Mu-metal or thick steel, which provides a low-reluctance path to divert the magnetic flux lines away from your sensitive circuitry.
Q: Does a steady DC current create an electric field?
A: Outside the wire, a steady DC current creates a static magnetic field, but virtually zero electric field. The electric field inside the wire is what pushes the electrons (manifesting as the voltage drop across the wire's resistance), but because the net charge on the outside of a standard conductor is neutral, there is no external E-field to worry about until the current changes.
Q: Why do twisted pair cables reduce magnetic interference?
A: Twisting the wires ensures that any external changing magnetic field induces an equal and opposite electric field (voltage) in each successive twist. The induced E-fields cancel each other out, preventing the B-field interference from corrupting the differential signal.
