CAN-bus — when the car's control units communicate

The learning outcomes for car mechanics mention it by name: you must have knowledge of the special standards and protocols for data communication related to CAN-bus. It's not academic ornament. When a customer comes in with an instrument cluster that is 'dead' or ten error codes about lost communication, it is the network understanding that determines whether you find the fault in an hour or stumble for days.

§Why a network at all?

Before bus systems each signal needed its own wire. With 30–80 control units in a modern car that would be miles of cable. CAN (Controller Area Network) solves this by letting all units share the same wire pair: each message is sent with an identifier, and all units listen and accept messages relevant to them. CAN is standardized in the ISO 11898 series and has been the backbone of car electronics since the 1990s. Requirements for standardized self-diagnosis came with EU rules on EOBD, which became mandatory for new petrol cars from 2001 and diesel cars from 2004.

§How the signal looks

CAN sends differentially on a twisted conductor pair CAN-High and CAN-Low. When the bus sends a dominant bit CAN-H is pulled up and CAN-L is pulled down; the signals are mirror images of each other. The receiver reads the difference between the two conductors so the signal is not significantly disturbed by electrical noise — the noise hits both conductors equally and cancels out in the difference. The twisted pair helps ensure exactly that. High-speed CAN for engine control and safety systems typically runs at 500 kbit/s while comfort systems often run on a slower bus.

Multiple nets in the same vehicle

• 01Highspeed-CAN — engine, gearbox, ABS/ESC and other time-critical systems.
• 02Comfort-CAN — lower speed for doors, climate, seats and similar.
• 03LIN bus — cheap single-conductor bus for simple subsystems like mirrors and window lifts.
• 04Gateway — the control unit that connects and translates between the networks, often also the entry point for the diagnostic tool.
• 05Newer cars supplement with CAN FD and automotive Ethernet for large data volumes e.g. camera systems.

§Troubleshooting on the bus

The most important diagnostic clue is the pattern in error codes. If one control unit reports an internal error you investigate it. If many control units simultaneously report 'lost communication' with the same unit that unit or its power supply is the main suspect. If all units on a network report communication error the fault is probably in the bus itself: a broken wire a short circuit to ground or positive or a defective unit that 'pulls the bus down'. A systematic method is to disconnect units one by one while monitoring the bus with an oscilloscope until the faulty participant is found.

Remember the craftsmanship around the electronics: crooked pins in connectors, IR in joints, chewed cable bundles at feedthroughs, and water in control units stand behind a large part of all communication failures. Repair of the cable network must be carried out using correct assembly technique and sealing according to the manufacturer's method — poor crimping will be the next intermittent failure.

“The bus does not lie — but you must understand its language to hear what it is saying.”

— Diagnostic technician authorized workshop