CAN Bus Explained: Your Car’s Nervous System

ByGreedy Wheels

The Controller Area Network (CAN bus) is the two-wire communication system that lets your car’s electronic modules talk to each other. Instead of dedicated wires between every sensor and computer, all modules share a twisted pair of wires (CAN High and CAN Low). When the CAN bus fails, you see everything from a no-start to scattered warning lights. This guide covers how the system works, common failure modes, and a practical diagnostic flow you can run yourself.

How It Works – CAN High and CAN Low

Every modern vehicle has multiple Electronic Control Units (ECUs) – engine computer, transmission control, ABS, airbag module, body control module, instrument cluster. Each ECU connects to the bus and broadcasts messages that any other module can read. Messages have priority: airbag deployment or engine RPM gets through before window position.

Most vehicles use two separate CAN networks: a high-speed powertrain CAN (500 kbps) and a low-speed body CAN (125 kbps), linked by a gateway module. The bus relies on two 120‑ohm termination resistors (one at each end) to prevent signal reflections. Measured across the two wires, you should see 60 ohms total.

On every OBDII-compliant vehicle, the CAN bus must transmit mandatory diagnostic data from OBD addresses Mode $01 PID $00 (supported PIDs) and Mode $01 PID $01 (monitor status since DTCs cleared). This isn’t optional – it’s part of the federal emissions regulation. If your scanner can’t pull those PIDs, the bus is compromised at the powertrain gateway level.

Applicability boundary: This description fits most gasoline and diesel cars from roughly 2008 onward. Some luxury models (BMW, Mercedes, Audi) add third networks like FlexRay or CAN‑FD, and older vehicles (pre‑2003) may use ISO 9141 or K‑line instead. Always verify your specific vehicle’s wiring diagram before assuming a standard CAN bus.

Symptoms That Point to a CAN Bus Fault

CAN bus failures rarely give one clear symptom. Instead you get a cluster of odd behaviors that don’t add up. Common patterns:

Failure Typical Cause Symptom
Bus short to ground/voltage Chafed wire, corrosion, water intrusion Multiple modules offline, no communication, no-start
Missing termination resistor Open circuit near connector Intermittent communication, random codes
Gateway failure Internal module fault One network dead (e.g., body CAN), other works
Shorted transceiver in one ECU Overvoltage, lightning strike, bad solder One module pulls the whole bus down; unplugging it restores communication
Electromagnetic interference Aftermarket accessories, bad ground Sporadic errors only when headlights or AC are on

One failure mode to catch early: a module with a shorted transceiver. That module holds CAN High or CAN Low at a fixed voltage, stopping all traffic on its bus segment. If a non-critical module (seat control, ambient light) goes silent first, check that module before replacing the main ECU.

Practical implication: When you have multiple unrelated warning lights (engine, ABS, airbag) plus lost‑communication codes, the CAN bus is likely the root cause. Do not throw parts at individual systems – repair the bus first.

Concrete Examples of Symptom Patterns

  • 2014 Toyota Camry: No-start, dash lights dim, scanner reads “U0100 – Lost Communication with ECM/PCM.” Resistance between pins 6 and 14 reads 120 ohms instead of 60. One termination resistor is open near the ECM connector – fix is a splice repair.
  • 2012 Ford F-150: Intermittent check engine light, radio cuts out when headlights are turned on. Voltage on CAN Low drops to 0 V during headlight use. Aftermarket HID kit wiring chafed the CAN pair near the passenger kick panel – repair the insulation.
  • 2010 Honda CR-V: Multiple U-codes for ABS, airbag, and body control modules. Resistance is 60 ohms, but CAN High is stuck at 0 V. Unplugging the aftermarket remote-start module brings the bus back to normal – defective interface is shorting CAN High.

Diagnosing a Fault – Step by Step

You need a digital multimeter. An oscilloscope helps for deeper timing checks but isn’t required for most wiring faults.

Step 1 – Resistance Test

With the battery disconnected, measure resistance between OBD2 pins 6 (CAN High) and 14 (CAN Low). You should read 60 ohms.

  • 120 ohms → one termination resistor missing (check connector near the far end of the bus).
  • Open/infinite → broken wire or completely disconnected module.
  • Near 0 ohms → short circuit between the two wires.

Concrete verification step: Write down your actual reading. If it’s not 60±5 ohms, the bus wiring or termination is compromised before you go any further.

Step 2 – Voltage Check

Key on, engine off. Measure CAN High to ground – should be roughly 2.5–3.5 V. CAN Low to ground – about 1.5–2.5 V.

  • If either pin is stuck at 0 V or near battery voltage (12 V), you have a short to ground or power.
  • If both pins read the same voltage (e.g., both 2.5 V), the transceivers are not driving the bus – possible gateway issue.

Step 3 – Isolate the Bad Module

Disconnect the battery. Unplug modules one at a time while watching the resistance at the OBD2 port. When resistance jumps back to 60 ohms, the module you just unplugged is dragging the bus down. Common suspects: aftermarket stereo interface, non‑OEM alarm module, or a water‑damaged body module.

Step 4 – Inspect Physical Wiring

Look for chafed wires near sharp brackets, melted insulation near exhaust, rodent damage, and corrosion inside connectors. Trouble spots: behind the glovebox, under door sills, near the battery tray, and along the firewall.

Likely Causes and Friction Points

  • Rodent damage: Most common in vehicles parked outdoors or near fields. Signs: missing insulation fragments, droppings near wires. Repair requires splicing or harness section replacement.
  • Water intrusion: Sunroof drains, cowl leaks, or windshield gaps. Water wicks into connectors and corrodes CAN pins. Inspect under carpets and inside connector housings – green or white corrosion is a giveaway.
  • Aftermarket add-ons: Alarm systems, remote starters, stereo interfaces, and trailer brake controllers are top causes of bus faults. They often use low-quality components or improper wiring taps. When in doubt, disconnect all aftermarket modules first.

Friction point: If you’ve replaced a damaged wire but the bus still shows 120 ohms, the termination resistor may be inside a module that was unplugged during your test. Reconnect that module and retest.

Quick Decision Aid – Is the CAN Bus the Likely Culprit?

Before diving deeper, run these checks:

  • [ ] Do you have two or more modules reporting U‑codes (lost communication)?
  • [ ] Does the OBD2 scanner itself disconnect when you turn on an accessory (headlights, AC)?
  • [ ] Is resistance between pins 6 and 14 not 60 ohms? (Record the actual reading.)
  • [ ] Is CAN High or CAN Low stuck at 0 V or 5 V instead of ~2.5 V?
  • [ ] Does unplugging one module bring all other modules back online?

If you answered “yes” to three or more, the CAN bus is almost certainly at fault.

Success check: After completing the diagnostic steps and repairing the fault, repeat the resistance and voltage checks. You should see 60 ohms at the OBD2 port and both CAN wires within their normal voltage range. The scanner should now communicate with all modules, and warning lights should clear.

Mismatches, Limitations, and Trade-Offs

Mismatch risk: Using aftermarket components that are not CAN‑bus compatible (e.g., old‑school LED flasher relays, generic trailer wiring adapters) can inject noise or short the bus. Always confirm the part is designed for your vehicle’s CAN protocol (high‑speed vs. low‑speed).

Limitation of DIY repair: Splicing a broken CAN wire works if you use a twisted‑pair splice of the same gauge and keep the pair twisted close to the repair. A single splice that separates the two wires by more than an inch can create a reflection point, causing intermittent errors that are nearly impossible to diagnose. If you don’t have experience with data wiring, consider replacing the entire harness section.

Trade-off: Replacing a failed module (e.g., body control module) costs hundreds and usually requires dealer programming. However, many shops can rebuild a module with a bad transceiver for much less. Sending the module to a repair service is often the better option if the wiring checks out fine.

What You Can Fix and When to Escalate

You can fix yourself:

  • Open or shorted wires (splice, repair, replace)
  • Corroded connectors (clean with contact cleaner)
  • Damaged OBD2 port pins
  • Missing termination resistor (if accessible in a separate harness)

Escalate to a shop if:

  • The gateway module is bad (needs programming)
  • The fault is inside a major ECU (engine, transmission, ABS) that requires specialized repair
  • The bus continues to fail after you’ve repaired all visible wiring – you may have an intermittent internal failure that only appears under temperature or vibration

FAQ

Will a bad CAN bus prevent my car from starting?

Yes. Most modern cars require the engine control module, immobilizer, and body control module to communicate before the starter engages. A dead CAN bus kills that handshake, often producing a crank‑no‑start.

Can I just bypass the CAN bus to get one sensor working?

No. The CAN bus is a shared network – bypassing one module still leaves the rest of the system disrupted. Always repair the root cause.

What does a 60 ohm reading tell me?

It confirms that both termination resistors are present and the bus wiring has continuity. If you see 60 ohms but still have communication faults, the issue is likely a bad transceiver inside a module rather than a wiring problem.

Do I need a special scanner to diagnose CAN bus faults?

A standard OBD2 scanner that reads generic OBD2 codes can tell you which modules are not communicating (U-codes). However, you will need a multimeter to check resistance and voltage. Many DIYers also use a scan tool that supports live data from multiple modules to cross‑reference.

Explore This Topic

Related guides in this cluster:

Similar Posts