Looking for the complete picture? Explore our CAN Bus and Network Diagnostics: The Complete Guide to U-Codes for an in-depth guide.

CAN (Controller Area Network) is a robust, fault-tolerant serial bus designed for reliable communication in noisy automotive environments. Unlike traditional point-to-point wiring, CAN allows multiple modules (ECUs) to share just **two twisted-pair wires** (CAN High and CAN Low) while prioritizing messages and resisting interference. Its differential signaling and arbitration make it ideal for real-time control systems like powertrain, ABS, and body functions. Understanding how CAN actually transmits data helps you diagnose why a short, open, or noise issue can bring down the entire network.

Practical takeaway: CAN is extremely noise-resistant due to differential signaling, but it’s fragile when one wire is compromised—damage to a single conductor or incorrect termination often causes total communication collapse, U-codes, and “lost module” symptoms across the vehicle.

CAN High and CAN Low: Differential Signaling Explained

CAN does not send a simple “0” or “1” on one wire like older serial protocols. Instead, it uses **differential signaling** on two wires that move in opposite directions:

• Recessive state (logical 1, idle/bus free) — Both CAN High and CAN Low sit near the same bias voltage (typically ~2.5V on high-speed CAN, varies by network type).
• Dominant state (logical 0, transmitting) — CAN High rises (~3.5V) while CAN Low drops (~1.5V) simultaneously. The difference (delta) between the two wires carries the data.
• Why differential? — External electrical noise affects both wires equally (common-mode noise), so the delta remains clean. A single-wire fault (short/open) destroys the delta → communication fails quickly.
• Scope view — Clean, mirrored square waves: CAN High up when CAN Low down, with sharp transitions. Noise shows as hash/ripple; shorts pin lines high/low; opens cause flatline or reflection glitches.

Arbitration: How CAN Avoids Collisions

Multiple modules can transmit simultaneously on CAN—no central clock or token. Arbitration ensures the highest-priority message wins without data corruption:

• Every message starts with an identifier (ID) — lower ID number = higher priority.
• During transmission, each module monitors the bus while sending its ID bits.
• If a module sends a recessive 1 but sees dominant 0 on the bus, it backs off and retries later.
• The highest-priority (lowest ID) message continues uninterrupted; others wait.
• This is non-destructive—collisions don’t corrupt data, and no time is wasted.

Real-world result: Critical messages (e.g., ABS wheel speed, engine RPM) always get through first, even during heavy bus traffic.

What Breaks CAN Communication in the Real World

• Short to ground or power on either wire — Pins CAN H or L to fixed voltage → delta collapses, bus shuts down (most common hard failure).
• Open circuit on one wire — Broken conductor, loose connector, corroded pin → differential signal lost, communication fails (often intermittent with movement).
• Missing or incorrect termination resistance — No/lost 120Ω terminators (usually at network ends) → signal reflections, ringing, bit errors (termination explained).
• Module transceiver failure — Stuck dominant (holds bus low) or shorted internally → drags entire bus offline, flooding U-codes.
• Excessive noise or EMI — Poor shielding, bad grounds, alternator ripple → corrupts bits, causes retries or dropouts (scope reveals hash on signals).
• Power/ground issues to modules — Brownout resets or no supply → module drops offline, appears as “lost communication.”

Because CAN is differential and relies on the delta between wires, damage to a single wire or termination often kills communication faster than you’d expect on a single-wire system. Always start with power/ground stability, then termination, then signal integrity (testing CAN H/L).

Updated March 2026 – Part of our Complete Guide to CAN Bus & Network Diagnostics.