Network Communication Diagnosis

Modern vehicles have dozens of computers — modules — that constantly talk to each other over a data network. The most common network type is CAN bus — Controller Area Network. Think of it like a group phone call where every module can hear every other module. The engine computer shares RPM data with the transmission computer. The body control module tells the instrument cluster what to display. The ABS module shares wheel speed data with the stability control system. When the network works, everything coordinates seamlessly. When a module stops talking, the vehicle falls apart in ways that seem unrelated.

A U-code is a communication fault code. It means a module expected to hear from another module and did not get a response. U0100 means lost communication with the ECM. U0101 means lost communication with the TCM. The first module is fine — it is the one reporting the problem. The second module is the one that stopped talking. Multiple U-codes for different modules all going silent at the same time usually means the network itself has failed — not all those individual modules. One network fault can generate a dozen U-codes across the vehicle.

CAN bus uses two wires — CAN High and CAN Low. They carry the same data signal but in opposite polarity. CAN High swings up toward 3.5 volts when transmitting. CAN Low swings down toward 1.5 volts. The difference between them is what the modules read. This two-wire design gives the network resistance to electrical noise. Each end of the CAN bus has a 120-ohm terminating resistor. These resistors prevent signal reflections that would corrupt the data.

This is the fastest CAN bus health check. Turn the ignition off. Disconnect the battery. Measure resistance between CAN High and CAN Low at the DLC — the diagnostic connector under the dash. Pins 6 and 14 on the standard OBD-II connector. You should read approximately 60 ohms. That is the two 120-ohm terminating resistors in parallel. If you read 120 ohms, one terminating resistor is open — one end of the bus is not terminated. If you read near zero ohms, CAN High and CAN Low are shorted together. If you read infinite or OL, both terminators are open or the bus wires are broken.

When a single module fails and shorts the CAN bus, it drags down every other module on the network. The entire vehicle may go dark — no communication on the scan tool at all. To find the offending module, start unplugging modules one at a time while monitoring the CAN bus resistance. When you unplug the failed module and the resistance returns to 60 ohms — that module was the one killing the network. Start with the modules closest to the fault codes you had before communication was lost. On some vehicles you can pull fuses to isolate groups of modules rather than crawling to each one individually.

For advanced diagnosis, a dual-channel scope on CAN High and CAN Low shows the actual data traffic. Healthy CAN bus shows clean, square-edged digital pulses on both lines — CAN High pulsing up to about 3.5V and CAN Low pulsing down to about 1.5V, always mirroring each other. Noise, ringing, or irregular pulse shapes indicate wiring problems, poor connections, or a module corrupting the bus. A flat line on either channel means that wire is open or shorted. The scope shows you exactly what the network is doing in a way that resistance testing alone cannot.