CAN Bus

When communication faults appear, techs who don't understand the network replace modules at random; techs who do can isolate a bus fault to a wire, a terminator, or a single dead node with a meter and a scope.

How CAN works

CAN bus — Controller Area Network — is a serial communication network that lets multiple modules (ECU, transmission controller, ABS, body control module, and dozens more) share data over just two twisted wires, CAN-High and CAN-Low. Each module broadcasts its messages onto the shared bus — RPM, coolant temperature, vehicle speed, switch states — and every module sees every message, responding to the ones relevant to it. This design eliminates the need for a dedicated wire for every signal between every pair of modules. The trade-off: because the infrastructure is shared, a bus fault tends to affect multiple modules simultaneously, which is itself a diagnostic clue.

CAN uses differential signaling: CAN-H and CAN-L carry mirror-image versions of the same data, which lets receivers reject noise that hits both wires equally. Modern vehicles actually run several CAN networks at different speeds — a high-speed bus for critical systems like powertrain and ABS, a low-speed bus for body electronics, and often separate chassis and infotainment buses. A gateway module bridges these networks, translating and filtering messages between them and providing security and rate limiting between buses. Your scan tool usually connects through that gateway, which affects what data you can reach and how.

Diagnosing communication faults

The pattern of failure tells you where to look. When multiple modules show communication errors at once, the problem is almost certainly shared infrastructure, not several modules dying together. Check power and ground at the affected modules first — supply problems are common and cheap to find. Then move to the bus itself: inspect CAN wiring for shorts and breaks, and measure the terminating resistors. With the modules powered down, resistance between CAN-H and CAN-L should read approximately 60 ohms — that's two 120-ohm terminating resistors at the ends of the bus in parallel. A missing or failed terminator corrupts communication across the entire network. Don't forget gateway modules, since a dead gateway can silence a whole bus segment.

When a single module shows no communication, the sequence is: verify battery and ignition power and ground at the module's connector, then confirm CAN signals are actually reaching the module. If power, ground, and bus signals are all present and the module still won't respond to the scan tool, the module itself is likely internally failed — but only condemn it after confirming all of its supporting infrastructure. Modules are expensive and often require programming; wiring is cheap.

For intermittent or subtle bus faults, the lab scope is the tool. Put one channel on CAN-H and one on CAN-L: a healthy bus shows mirror-image waveforms centered around 2.5 volts, with CAN-H peaking near 3.5 volts as CAN-L drops to about 1.5 volts. A wire shorted to power or ground shows as a stuck, flat line. Damage to the twisted pair shows as asymmetric noise between the channels. Corrupted, malformed patterns point to a failing transceiver somewhere on the bus.

Aftermarket accessories and the bus

The CAN bus is a precision-engineered network, and careless accessory installation is a common source of mystery network faults. Improperly wired or unlicensed devices can flood the bus with messages, change the bus impedance, or interfere with the terminating resistors — all of which produce network faults that are miserable to trace later. Use manufacturer-approved connection methods: add-a-fuse taps and designated accessory power points for anything that just needs power, and certified aftermarket CAN gateway interfaces designed for the specific vehicle when a device genuinely needs to talk on the network. Never splice directly into CAN wires to power an accessory.