A heavy truck can develop a surprising number of warning lights from one electrical problem. Gauges stop responding, the transmission refuses to select a gear, or the diagnostic tool suddenly loses contact with a controller.
The fault report may point toward J1939 communication. That does not automatically mean the engine computer, transmission controller, or ABS module has failed.
J1939 communication faults mean that required information is missing, late, invalid, or otherwise unavailable. The cause may be network wiring, a connector, termination, configuration, or a module that has lost its power supply.
For drivers, understanding the basics helps explain a breakdown. For technicians, it helps turn a long fault list into a sensible diagnostic plan.
What is J1939 on a diesel truck?
SAE J1939 is a communication framework used by electronic systems on heavy-duty vehicles and equipment. It uses CAN—Controller Area Network—to exchange messages.
A controller can transmit information that other controllers need. Engine speed, for example, may be required by several systems rather than just the engine controller.
Conventional J1939 networks commonly operate at 250 or 500 kbit/s. The diagnostic interface and software must support the network being accessed. J1939 uses extended 29-bit CAN identifiers, with message groups identified by Parameter Group Numbers, or PGNs. CSS Electronics provides a technical introduction to these features.
You do not need to memorise every message to begin diagnosis. You do need to identify which network carries the information that is missing.
CAN and J1939 are related, but not interchangeable
CAN provides the underlying communication mechanism. J1939 defines additional rules for organising and interpreting information.
Also, not every CAN circuit on a truck is the same network. A vehicle may have separate drivetrain, engine, body-builder, and other communication links. A module may connect to more than one link.
Navistar’s J1939 troubleshooting publication specifically distinguishes separate links and warns technicians to identify the correct one before testing. Its vehicle-specific details should not be transferred directly to another make.
A good reading at the diagnostic connector does not establish that every private network or every branch elsewhere on the truck is healthy.
What a communication fault looks like
Here is an illustrative diagnostic display based on a fault listed in Navistar’s publication:
| Reporting module | SPN | FMI | Description |
|---|---|---|---|
| Body controller | 639 | 9 | Drivetrain message timeout |
The display tells you which controller reported the problem, which parameter is involved, and the failure category. FMI 9 identifies an abnormal update rate. It does not establish that the reporting controller needs replacing.
Descriptions and diagnostic instructions depend on the manufacturer, controller, and vehicle configuration. Record the complete fault description instead of searching by the SPN alone.
A controller complaining about missing information may be functioning correctly. The problem could be at the controller expected to transmit it, or anywhere along the relevant communication path.
Symptoms that can suggest a communication problem
Depending on the affected system, symptoms may include:
● Gauges dropping out or displaying unavailable readings.
● Several controllers logging missing-message faults.
● A diagnostic tool losing access to a module.
● Transmission operation becoming restricted.
● Functions becoming unavailable after equipment installation or wiring repairs.
These symptoms are clues, not confirmation. A no-start complaint still needs normal starting-system diagnosis, and an ABS warning still requires the applicable brake-system procedure.
Why termination matters
A conventional high-speed CAN bus normally has a 120-ohm terminating resistor at each end of its backbone. Termination helps control signal reflections.
With both resistors connected in parallel, resistance measured between CAN High and CAN Low is approximately 60 ohms. Kvaser explains this powered-down test.
The basic relationship is:
120 ohms in parallel with 120 ohms = 60 ohms.
That is a useful starting point for a conventional network. It is not a universal specification for every CAN implementation, every isolated section, or every test location.
Some termination is built into controllers, and some equipment uses electronically switched termination. Enovation Controls notes that switched termination may require a different verification method.
What resistance readings can suggest
The following interpretations assume a de-energized, conventional high-speed CAN segment that should have two passive 120-ohm terminators connected. Confirm the manufacturer’s expected reading first.
| Approximate reading between CAN High and CAN Low | Possible direction for diagnosis |
|---|---|
| 60 ohms | Both expected termination paths appear accessible from this test point. |
| 120 ohms | Only one termination path may be accessible; investigate a missing terminator or an open path. |
| 40 ohms | Three 120-ohm termination paths may be present. |
| Near zero | Investigate a short between the lines or another very low-resistance path. |
| Open circuit or unusually high resistance | Investigate disconnected wiring, isolation from termination, or the wrong test points. |
These are diagnostic possibilities, not automatic replacement instructions. Enovation’s guide describes the 60-, 120-, and 40-ohm relationships and the need to account for equipment-specific termination.
Why 60 ohms does not prove the network is good
A branch to one controller can be open while the backbone still measures approximately 60 ohms. A controller can also have no power while the terminators remain connected.
A stationary resistance test may miss a harness fault that appears only with vibration. It also does not show whether messages are transmitted, received, or interpreted correctly.
Think of resistance testing as one piece of evidence. Combine it with module availability, power and ground checks, and operating-condition tests.
Check module power and grounds before condemning it
A controller needs more than intact communication wires. It also needs its specified power supplies, grounds, and wake-up conditions.
A failed fuse, poor terminal connection, or excessive voltage drop can make a module disappear from the diagnostic tool. Other controllers may then report missing information.
Detroit’s EPA10/GHG14 SPN 625/FMI 9 procedure includes connector inspection, power and ground checks, and CAN resistance tests at the aftertreatment control module. It demonstrates why communication diagnosis includes the module’s electrical supply.
Importantly, that procedure specifies approximately 120 ohms on particular disconnected component and harness sides. Applying a blanket “everything must be 60 ohms” rule would misinterpret those tests.
Use the correct procedure for the controller and engine generation. Do not transfer connector pin numbers from a similar-looking truck.
A practical diagnostic sequence
1. Save the fault report and describe the symptom
Record all reporting modules, active and inactive faults, and available timestamps before clearing codes.
Ask when the problem occurs: during cranking, after rain, over bumps, when hot, or after a recent repair. The answer helps determine what conditions the verification test needs to reproduce.
2. Confirm diagnostic access
Check that the interface is powered, the correct cable is fitted, and the software is configured for the vehicle and network.
If every module is unavailable, investigate the diagnostic connection and network access. If one module is missing, focus first on that module’s supply, branch, and applicable communication procedure. A gateway or interface limitation can also affect what the tool sees.
3. Identify the network on the wiring diagram
Locate the relevant backbone, branch connections, gateways, and terminators. Mark the module expected to send the missing information and the module reporting its absence.
That map gives each measurement a purpose. Testing an unrelated CAN pair can produce a perfectly normal reading while leaving the actual fault untouched.
4. Inspect likely damage areas
Inspect connectors and harnesses near recent work, moving components, frame contact points, and exposed locations.
Look for corrosion, pushed-back terminals, damaged seals, water intrusion, chafing, and strained wiring. Preserve the specified twisted-pair construction and approved repair method when repairing CAN wiring.
5. Test power, grounds, and termination as directed
Follow the specified key state, shutdown time, battery-disconnection requirements, and test connections. Confirm that the circuit is de-energized before resistance testing; key-off alone may not immediately remove power from every module.
Use appropriate voltage-drop or load tests where the manufacturer specifies them. Do not use a heavy test lamp on CAN terminals or inject battery voltage into network wiring.
6. Isolate branches methodically
Where the procedure calls for disconnection, document the starting condition and change one connection at a time.
If communication recovers after disconnecting a module, you have narrowed the investigation. You have not necessarily proved the module failed. Disconnecting it may also remove a damaged branch, alter termination, or disturb an intermittent connector.
7. Verify the original complaint
Restore the intended network configuration, reconnect equipment, and repeat the relevant operating conditions. Confirm module communication and check for returning faults.
What a voltmeter can—and cannot—tell you
On typical high-speed CAN, both lines sit near 2.5 volts in the recessive state. During dominant signalling, CAN High commonly rises toward 3.5 volts and CAN Low falls toward 1.5 volts. Pico Technology illustrates these signal states.
A digital multimeter usually displays an average rather than individual data pulses. Do not require it to show exactly 3.5 volts on High and 1.5 volts on Low during normal communication.
An oscilloscope can reveal transitions, disturbances, and intermittent signal changes that a meter misses. Proper setup, grounding, timebase, and manufacturer guidance matter. A plausible waveform alone does not confirm that all required messages are present and valid.
Three illustrative fault scenarios
One missing controller creates several complaints
A controller loses its ignition supply. Other systems continue working, but they log faults because its messages stop arriving. Repairing the supply restores communication; replacing the receiving controllers would not address the cause.
The backbone tests normally, but one branch is damaged
Resistance at the diagnostic connector is approximately 60 ohms. One controller remains unavailable because its branch connection is open. The next useful measurement is at that branch, using the wiring diagram.
Added equipment changes the network
A new device introduces extra termination, an incompatible configuration, or wiring damage. Check the equipment installation and approved connection method. Avoid adding a resistor merely to make one meter reading look correct.
These examples describe diagnostic possibilities, not documented customer repairs or universal fault-code combinations.
Frequently asked questions
Can one bad module affect several systems?
Yes. A module that stops sending required information can generate complaints elsewhere. An electrical fault on its communication connection can also affect a wider segment. Testing distinguishes those situations.
Is J1939 always 250 kbit/s?
No. Conventional J1939 applications include 250- and 500-kbit/s networks. Confirm the actual network and interface requirements.
Should I add a resistor if I measure 120 ohms?
First establish why only one termination path is visible. An open backbone, disconnected controller containing termination, or incorrect test location can produce that reading. Adding a resistor can conceal the original fault.
Can I drive with a communication fault?
That depends on the affected functions, warning lamps, and manufacturer instructions. A communication label does not establish that braking, transmission, or engine operation remains safe.
Diagnose the missing information, then find its cause
J1939 communication faults reward a systematic approach: identify the affected network, establish which information is missing, check the sending module’s supplies, and test the relevant wiring and termination.
A code list starts the investigation. Measurements and successful verification establish the repair.
Sources and technical references
1. CSS Electronics: J1939 explained—protocol structure and conventional network speeds.
2. Navistar: J1939 Data Link Troubleshooting, IK0800080—separate links, diagnostic examples, and vehicle-specific testing.
3. Kvaser: Testing CAN termination—powered-down termination measurement.
4. Enovation Controls: CAN Bus Troubleshooting Guide—termination readings, configuration, and equipment-specific exceptions.
5. Detroit: SPN 625/FMI 9, EPA10/GHG14—an OEM example combining connector, supply, ground, and CAN checks.
6. Pico Technology: Controller Area Network basics—signal voltages and oscilloscope context.
References checked October 2, 2026. This article explains general principles. Exact pinouts, termination arrangements, acceptable readings, and test sequences require the current service information for the vehicle being repaired.
Leave a Reply