How to Diagnose Network Communication Codes Without Replacing Good Modules

A cluster of U-codes can make a vehicle look as if several control modules failed at once. In practice, the list often records one shared event: low system voltage, a missing power or ground, an open network branch, a loose terminal, water intrusion, or one module that stopped communicating temporarily.

The module named in a code description is not automatically the failed part. It may be the module that another controller could not hear, or it may have transmitted invalid data because one of its inputs was wrong. The right diagnostic sequence preserves the evidence, identifies the network pattern, and proves the circuit before any module is ordered.

Treat a U-Code as a Symptom, Not a Parts Verdict

Network DTCs describe a communication problem observed by a controller. “Lost communication with ABS,” for example, means the reporting module stopped receiving an expected message from the ABS controller for a calibrated period. It does not explain whether the cause was the ABS module, its fuse, a ground, a connector, the gateway, or the data bus between them.

Also separate “lost communication” from “invalid data received.” A controller can be online and sending messages, yet another module may reject a value as implausible. General Motors service information shows how an intermittent wheel-speed input can create multiple invalid-data U-codes in other systems. Diagnose the original input or managing module before blaming every receiver.

Preserve the Full Scan Before Clearing Anything

Start with a complete vehicle scan, not a single-module code read. Record every module that responds, every module that is missing, the DTC and status, freeze-frame data, failure counters, timestamps, and mileage. Save the report before disconnecting the battery or unplugging a controller.

Subaru’s technician guidance specifically warns against clearing intermittent network codes just to see which ones return. The event may not repeat in the bay, leaving the most useful clues erased. Our guide to current, pending, and history DTC status explains how status and timing help separate today’s failure from an old battery event.

Find the Pattern in Reporting and Missing Modules

Build a simple map with two columns: modules that report a communication code and modules that do not respond to the scan tool. Then compare that map with the OEM network topology. A single missing module points toward its local power, ground, connector, or branch. Several missing modules on one branch point toward a shared splice, gateway path, connector, or bus circuit.

When many online modules all report losing the same controller at the same time, investigate the named controller’s shared supplies and network path first. When codes name several unrelated modules and share a low-voltage timestamp, test the battery and charging history before opening the harness.

Prove Battery Voltage, Power, and Ground First

Low voltage during cranking, a jump-start, a weak battery, or a disturbed ground can make modules reset at different thresholds. That creates a burst of communication codes even when the network wiring is intact. Check resting voltage, cranking voltage, charging behavior, and relevant low-voltage DTCs before deeper network testing.

For each noncommunicating module, use the wiring diagram to identify every battery feed, ignition feed, wake-up circuit, and ground. Load-test power and ground at the connector instead of relying only on an unloaded voltage reading. Confirm fuse integrity on both sides and inspect shared ground points for looseness, corrosion, paint, or voltage drop. A module with no supply cannot communicate, and replacing it will not restore the missing feed.

Use the Wiring Diagram to Identify the Correct Bus

Modern vehicles may contain several high-speed CAN channels, lower-speed networks, LIN sub-buses, Ethernet, and a central gateway. The diagnostic connector may not connect directly to the affected controller. Identify the exact bus, gateway, splices, termination locations, and connectors between the reporting and missing modules before measuring.

Do not assume every communication fault is on pins 6 and 14 of the diagnostic connector. An OEM topology may place the problem behind a gateway or on a private branch. For door, seat, and climate sub-networks, our LIN bus diagnostic guide covers the different single-wire test strategy.

Test the Network Without Creating New Faults

Follow OEM procedures and observe electrical safety before probing. With the network powered down as specified, resistance across a conventional high-speed CAN pair is commonly near 60 ohms because two 120-ohm terminating resistors are connected in parallel. A reading near 120 ohms can indicate one missing terminator or an open path; a much lower reading can suggest extra termination or a short.

That 60-ohm check is not universal. Low-speed CAN, single-wire networks, switched termination, gateways, and isolated branches can produce different readings. Kvaser’s CAN guidance confirms the standard high-speed principle while noting that other physical layers may use different termination. Always compare the measurement with the vehicle manufacturer’s specification and test location.

Next check each bus wire for shorts to ground, power, and the companion wire. If resistance checks pass but communication remains unstable, use an oscilloscope to inspect differential signal shape, amplitude, bias, and error activity. Avoid piercing insulation when a breakout lead or back-probe is available, and never use an ohmmeter on an energized circuit.

Isolate Branches Carefully

If the bus is shorted, disconnect approved junctions or branches one at a time while watching resistance or communication recover. Use the topology to minimize unnecessary disconnections. A branch that restores the network narrows the fault to its wiring, connectors, or connected nodes, but it still does not prove the first unplugged module is defective.

Inspect terminal tension, backed-out pins, water tracks, chafing near brackets, recent collision work, and aftermarket alarms, remote starters, trackers, audio equipment, or telematics devices. Wiggle-test suspect sections while monitoring module status. If your diagnostic software connects to the vehicle but misses selected controllers, the workflow in our missing-ECU communication guide provides additional interface and protocol checks.

When Module Replacement Is Justified

Condemn a controller only after its specified powers and grounds pass under load, the correct wake-up and enable conditions are present, network circuits meet OEM specifications, connector fit is sound, and the bus works when the controller is isolated according to the service procedure. Check applicable service bulletins and software updates before replacement.

Remember that replacement can require programming, security authorization, configuration, or network enrollment. A new module installed into an unresolved wiring fault may remain offline or be damaged. Document the measurements that support the decision so replacement is the conclusion of the diagnosis, not the starting guess.

Verify the Repair Across the Whole Vehicle

After repair, reconnect every component, restore normal battery support, and run another complete scan. Confirm all expected modules respond, the original current codes are absent, no new communication codes appeared, and related functions operate correctly. Repeat the conditions that triggered the complaint when safe, then compare the post-scan with the original report.

A disciplined network diagnosis follows the evidence from system-wide scan to topology, supplies, wiring, signal quality, and only then the controller. That order prevents expensive good-module replacement and produces a repair that remains fixed after the vehicle leaves the workshop.