CAN Bus U-Codes Explained: Tracing a Module Not Communicating Fault
A car comes in with the instrument cluster showing warning lights for systems that are almost certainly fine, ABS, airbag, transmission, all lit at once. A scan reveals a string of U-codes and one genuine fault buried somewhere in the CAN network. That pattern, several modules complaining at once, is the classic sign of a communication fault rather than several unrelated component failures.
What U-codes actually mean
U0xxx codes cover the vehicle’s communication network, most commonly CAN bus but also LIN and other networks depending on the platform. U0100 means lost communication with the ECM/PCM, U0121 means lost communication with the ABS module, and so on, one code per module the network has stopped hearing from. The important thing to understand is that a U-code is often reported by a module that’s perfectly healthy itself, it’s just no longer receiving messages from another module or from the bus as a whole.
Tracing a “module not communicating” fault
- Check which modules are reporting U-codes and which aren’t. A single module missing points at that module, its connector, or the wiring specific to it. Multiple modules missing the same one module points at that module or its power/earth supply. All modules losing each other points at the bus wiring itself or a short somewhere on the network.
- Check bus resistance at the diagnostic socket with the ignition off and the battery disconnected, a healthy two-wire CAN bus with correct termination should read close to 60 ohms across CAN-H and CAN-L.
- Use an oscilloscope on CAN-H and CAN-L to look at signal quality, a healthy bus shows clean, consistent voltage swings, a damaged or poorly terminated bus shows noise, reflections or a flat line.
- A breakout box on the suspect module’s connector lets you check individual pins without disturbing the harness further, useful when a connector is hard to access or suspected of intermittent contact.
- Check for a module that’s dropped off entirely due to internal failure or lost power, which shows as that specific module’s U-code across every other module on the network.
Common causes worth checking first
- Connector corrosion, especially at underbody or engine bay connectors exposed to water and salt.
- Wiring chafe where a harness runs against a chassis edge, a door hinge area, or near a component that vibrates.
- A dead module, sometimes from a previous water ingress event or a failed component drawing the bus down.
- Aftermarket wiring, alarms, towbar electrics or trailer modules spliced into the network incorrectly.
Check what’s changed recently
It’s also worth checking the vehicle’s service history for any recent work near the affected wiring, a battery replacement, an infotainment upgrade, a towbar fitted by a third party, since aftermarket work is one of the most common causes of a bus fault that otherwise looks completely random. A fault that appeared the same week as unrelated work is rarely a coincidence. On older platforms with a single-wire or low-speed CAN segment feeding comfort modules, don’t assume the same termination values apply as on the high-speed powertrain bus, checking the wrong segment’s resistance and signal quality against the wrong reference figures is a common way to waste an afternoon chasing a fault that was never there.
Why this is worth doing properly
Replacing modules one at a time based on which one shows a U-code is one of the most expensive ways to chase a wiring fault, because the module reporting the code is very often not the module at fault. A scope and a methodical trace through the bus wiring finds the actual break or short far faster, and far cheaper, than swapping electronics. For background on ECU and module identification while you’re tracing a network, see how to read ECU label numbers, and for scope and breakout box options, the Tools & Equipment category has more.
More ECU guides
Fuel Rail Pressure Codes P0087 and P0193: Pump, Injector, Sensor or Wiring?
A common-rail diesel limps in, power down, P0087 and P0193 both stored. The customer wants to know if it's the pump before you've even opened the…
Manufacturer-Specific P1 Fault Codes Explained: Why the Same Number Differs
Two identical-looking P1 codes, one on a Vauxhall Astra and one on a Peugeot 308, mean two completely different things. A tech who looks up "P1336"…
How to Read an OBD-II Fault Code: What P0, P1, P2, P3 and U-Codes Mean
An apprentice plugs in a scan tool, gets a P0301, and reads it out like the job is done: "misfire on cylinder 1." It isn't. That…