What a J1939 Communication Error Means on a Heavy Truck
J1939 is the high-speed CAN-based communication network that connects the engine ECM, transmission controller, ABS module, instrument cluster, and other modules on a modern heavy truck. A J1939 communication error fault code means that one or more modules have stopped receiving expected messages from another module on the network. The module that logs the fault identifies the source address (SA) of the module it can no longer communicate with.
J1939 communication errors are cascade-generating faults — because all modules share the same network, a physical network fault (broken wire, bad termination resistor, failed CAN transceiver on a module) produces fault codes from every module affected. A single root cause can generate communication fault codes that appear to span multiple independent systems, which can be misleading if the cascade nature is not recognized.
Fault Code Data to Record for J1939 Communication Errors
Record: all active fault codes from all source addresses (not just the most prominent lamp), whether multiple codes appeared simultaneously at the same moment, any recent wiring work, harness repairs, or new device installations, and whether the error is constant or intermittent (appears under vibration, certain speeds, or specific conditions).
The key diagnostic check for J1939 communication errors is bus resistance — measured at the 9-pin diagnostic connector (pin C = CAN-H, pin D = CAN-L) with the ignition off. A healthy bus reads approximately 60 ohms (two 120-ohm termination resistors in parallel). Above 60 ohms suggests a missing terminator or broken wire; near-zero suggests a short. This test can be performed with a basic multimeter.
Physical Causes of J1939 Communication Errors
J1939 communication faults most commonly result from: physical damage to the J1939 backbone harness (the main two-wire CAN bus that runs through the truck's frame or cab), a broken or corroded termination resistor at either end of the bus (120-ohm resistors located at the two physical ends of the network), a corroded or damaged connector at a module's CAN interface (ECM connector, ABS module connector, diagnostic port), or a failed CAN transceiver inside a module.
Recently installed aftermarket devices — ELD units, trailer tracking adapters, fleet management hardware connected to the 9-pin diagnostic port — are a common source of J1939 network problems. Devices with improper termination, failed transceivers, or incorrect baud rate configuration can corrupt the bus or load it beyond specification. A bus that worked correctly before a new device was installed and fails after installation strongly suggests the device is the root cause.
Distinguishing J1939 Errors from Module-Specific Faults
When J1939 communication errors appear from multiple source addresses simultaneously, the root cause is almost always in the network infrastructure (wiring, termination, power supply) rather than in multiple individual modules. Multiple modules fail simultaneously only when they share a common cause — the J1939 bus, the shared power supply, or a common harness segment.
When a communication error appears from a single source address consistently (one module is repeatedly 'not heard' by others), the root cause may be the silent module's own failure (module lost power, module's CAN transceiver failed, module connector corroded). Systematically checking power and ground at the silent module's connector, and confirming the connector seating and wiring integrity, identifies most single-module communication faults.
Related Pages
Sources
- SAE J1939 Standards Collection SAE International · official · accessed 2026-05-05 · confidence medium
Source: SAE International, SAE J1939 Standards Collection. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Can a J1939 communication error cause multiple unrelated fault codes to appear at the same time?
Yes — this is one of the most important things to recognize about J1939 communication faults. If the network is degraded, every module that depends on receiving messages from other modules will report that those expected messages are missing or delayed. A single broken wire or failed termination resistor can produce communication-related codes from the engine ECM, ABS controller, transmission controller, and instrument cluster simultaneously.
Is a J1939 communication error always a wiring problem, or can a failed module cause it?
Both. A module with a failed CAN transceiver can hold the bus in a fault state, blocking communication from all other modules. In this case, the failed module won't report its own fault — it simply goes silent or continuously corrupts the bus — while every other module logs communication errors. Identifying a silent module through systematic disconnection or a bus monitor tool is needed to find this type of failure.
Can an aftermarket ELD or telematics device connected to the diagnostic port cause J1939 communication errors?
Yes, this has been documented. Aftermarket devices that are improperly terminated, have failed CAN transceivers, or draw too much bus load have caused communication faults on the J1939 network. If communication errors appeared after a new device was installed, disconnecting that device and confirming whether the errors clear is a logical first diagnostic step.