J1939 vs J1708: Key Differences in Heavy-Duty Truck Communication Protocols

J1939 and J1708 are heavy-duty vehicle communication standards, but they belong to different generations of truck networking. J1939 is commonly associated with newer commercial vehicles and CAN-based communication. J1708 is an older serial data bus that is commonly used with J1587 for exchanging diagnostic and operating information.
The distinction matters when selecting a scanner, identifying a diagnostic connector, or investigating a communication failure. A tool that supports J1939 does not automatically support J1708, and a connector that fits the truck does not prove that the scanner can communicate with every module.
J1939 and J1708 at a glance
| Item | J1939 | J1708 |
|---|---|---|
| Typical vehicle context | Common on newer heavy-duty vehicles and equipment | Common on older commercial vehicles and equipment |
| Network technology | CAN-based network communication | Serial vehicle data bus |
| Related diagnostic or application standard | J1939 messages, including parameter and diagnostic information | J1587 is commonly paired with J1708 for application and diagnostic messages |
| Common fault-data format | SPN and FMI, often carried in J1939 diagnostic messages | J1587 identifiers such as MIDs, PIDs, SIDs, and FMIs |
| Scanner requirement | J1939-compatible interface and software coverage | J1708/J1587-compatible interface and software coverage |
| Compatibility warning | Support does not guarantee access to every ECU or function | Support does not guarantee coverage for every older truck or module |
What J1939 is
J1939 is a family of SAE standards used for communication among electronic control units in heavy-duty vehicles and equipment. It operates over a CAN-based network, allowing modules such as the engine, transmission, ABS system, instrument cluster, and aftertreatment controller to exchange structured data.
J1939 messages can carry operating parameters, commands, status information, and diagnostic information. Many diagnostic scanners display J1939 faults using an SPN, or Suspect Parameter Number, together with an FMI, or Failure Mode Identifier. The SPN identifies the parameter or item associated with the report. The FMI describes the type of fault condition reported.
An SPN and FMI combination provides a useful starting point for diagnosis. It does not automatically prove that a particular sensor, wire, ECU, or mechanical component has failed. Related live data, event information, wiring checks, service information, and vehicle-specific tests may still be needed.
What J1708 is
J1708 is an older SAE heavy-duty vehicle data bus standard. It defines how electronic modules share data across a serial communication network. J1587 is commonly used with J1708 to define the higher-level messages and data structure exchanged over that network.
This distinction is useful because J1708 and J1587 are related, but they are not identical terms. J1708 describes the communication bus. J1587 describes application-level information commonly transmitted across it, including diagnostic data.
Older trucks may report faults through identifiers such as a Message Identifier, Parameter Identifier, Subsystem Identifier, and Failure Mode Identifier. The exact information available depends on the vehicle, module, scanner software, and system implementation.
J1708/J1587 systems can remain relevant for older engines, transmissions, ABS controllers, body controllers, and other commercial-vehicle modules. A truck may also contain more than one communication network, so identifying the vehicle’s actual architecture is more reliable than assuming a protocol from the truck’s age alone.
How the diagnostic information differs
J1939 fault information
J1939 diagnostic information is commonly presented with SPN and FMI values. The network may also provide occurrence counts, lamp status, source-address information, and other details when supported by the vehicle and scanner.
These details can help narrow the investigation, but the displayed fault remains evidence rather than a complete repair instruction. A communication fault, for example, may require inspection of power, ground, wiring, termination, connectors, and related network devices.
J1708 and J1587 fault information
J1708/J1587 diagnostics commonly use identifiers such as MID, PID, SID, and FMI. A MID can identify the reporting module, while a PID or SID can identify the parameter or subsystem associated with the message. FMI information describes the reported failure condition.
Older diagnostic data may be presented differently from J1939 information. Scanner menus, code descriptions, and available live data can vary considerably by truck, engine, module, and software package. A tool may communicate with one J1708/J1587 module while lacking coverage for another module on the same vehicle.
J1939 versus J1708 for scanner compatibility
The protocol listed by a scanner is one part of compatibility. A reliable match requires several layers to line up:
- Vehicle and model year: The truck’s network architecture can vary by platform and production year.
- Engine and ECU: Engine coverage does not establish access to the transmission, ABS, chassis, body, or aftertreatment modules.
- Communication protocol: The interface must support the network used by the target module.
- Connector and cable: The physical connection must match the truck and scanner, but fit alone proves only physical compatibility.
- Software coverage: The application must recognize the vehicle and module and know how to interpret the messages.
- Diagnostic function: Code reading, live data, active tests, resets, and other functions may have separate coverage.
A 9-pin heavy-duty connector is often associated with J1939 or older heavy-duty networks, but the connector itself does not guarantee a specific protocol or complete system access. Older vehicles may use different connector arrangements, adapters, or multiple network connections. A passive adapter changes the physical connection and does not automatically convert one communication protocol into another.
Can a J1939 scanner read J1708 faults?
Sometimes, but J1939 support alone is not enough. The scanner, vehicle communication interface, cable, and software must specifically support J1708/J1587 communication and the applicable vehicle modules.
Some heavy-duty diagnostic platforms support both protocols. Others focus primarily on J1939 applications. A scanner may also list J1708 or J1587 support while limiting that access to selected manufacturers, model years, engines, or modules. The coverage documentation should be checked against the exact truck and the required diagnostic function.
The reverse situation also applies. A J1708/J1587-capable tool may be useful on an older truck but lack the J1939 interface or software needed for a newer vehicle. Protocol support should therefore be treated as a compatibility requirement, rather than as proof of universal heavy-duty coverage.
Which protocol is newer?
J1939 is generally the newer network standard compared with J1708. Many later heavy-duty platforms use J1939 for communication among electronic systems, while J1708/J1587 is more strongly associated with earlier commercial vehicles.
Model year alone is still an incomplete guide. Manufacturers introduced network changes at different times, and a vehicle may contain legacy and newer networks together. Equipment, vocational trucks, buses, and specialty applications may follow different implementation patterns.
What to check before connecting a scanner
Before attempting communication, identify the truck’s make, model, model year, engine, and target module. Then check the scanner’s coverage information for the specific protocol and function required.
- Confirm whether the target system uses J1939, J1708/J1587, or another network.
- Identify the correct vehicle-side connector and cable.
- Check that the scanner interface supports the required communication protocol.
- Verify coverage for the target ECU, rather than relying on engine or truck-brand support alone.
- Separate code reading from live data, active tests, resets, and other service functions.
- Record existing fault information before clearing anything.
If a scanner powers up but cannot establish communication, check the physical connection, interface power, selected vehicle application, cable or adapter, and protocol selection first. A failed connection can also result from missing module coverage, software limitations, network faults, or vehicle-specific conditions. The symptom does not identify one cause by itself.
J1939 and J1708 in practical truck diagnostics
J1939 is more likely to be encountered on newer electronically controlled heavy-duty platforms, while J1708/J1587 remains relevant for many older commercial vehicles. Neither protocol should be treated as a universal label for every truck system.
The most useful scanner is the one that matches the vehicle network, the target ECU, and the diagnostic task. Reading a fault code through either protocol does not establish the root cause or confirm that continued operation is safe. The code should be interpreted alongside the vehicle’s service information and the conditions under which the fault was reported.