Blog

What Is J1939-91C? An In-Depth Guide

November 16, 2026

What Is J1939-91C? An In-Depth Guide

To understand what J1939-91C is, you first need to know how SAE J1939 works. These standards are used extensively in heavy vehicles, commercial vehicles, buses, agricultural vehicles, construction vehicles, and industrial power systems. They allow ECUs (Electronic Control Units) to communicate with one another.

Modern commercial vehicles have many electronic systems monitoring different parts of the vehicle, such as engine performance, transmission, braking and speed. These systems need a reliable method of communication, and SAE J1939 allows them to communicate in a structured manner.

J1939-91C is a reference, so it should be checked against the relevant SAE International publication to confirm what it actually refers to.

What Is SAE J1939?

SAE J1939 is a set of standards designed to allow ECUs to communicate with one another in heavy vehicle applications. This is commonly done over a Controller Area Network (CAN).

On a J1939 network, multiple ECUs can communicate with each other. For example, an engine control module can send messages containing engine speed and temperature information. The dashboard module can receive this information and show it to the driver, and other systems can use it as well.

J1939 defines how messages are identified, which parameters are used, and how addressing and networking work.

Why Is J1939 Used in Heavy Vehicles?

Heavy vehicles use many electronic systems. To make integration easier between components from different manufacturers, they need a common communication system. J1939 helps by providing a standardised one.

Some examples of where J1939 is used:

  • Engine Management – provides information on engine speed, temperature and load.
  • Transmission – provides information on transmission conditions.
  • Vehicle Instrumentation – provides information for dashboards.
  • Diagnostics – retrieves fault codes and monitors electronic systems.
  • Fleet Management – provides information on vehicle performance.
  • Off-Highway Vehicles – provides communication for agricultural, construction and industrial vehicles.

Not all messages will be available. This depends on the vehicle, the ECUs fitted and the J1939 specification being used.

How Does J1939 Work?

A standard J1939 network uses CAN communications to send messages. All connected ECUs communicate with each other following the protocol. When a message is sent, an identifier is included to help other devices know what the message is and how important it is.

J1939 commonly uses 29-bit CAN identifiers. The extra bits carry information on message priority, Parameter Group Numbers, and addressing (depending on the message being sent).

Electronic Control Units (ECUs)

An ECU is a piece of electronics used to monitor or control a function within the vehicle. Examples include:

  • Engine module
  • Transmission module
  • Braking module
  • Instrument cluster
  • Body controller
  • Telematics unit
  • Diagnostic tool

Each ECU can send information, receive messages, or both. For example, the engine ECU could send engine speed information, and the telematics gateway could receive it and pass it on to the fleet monitoring system.

Controller Area Network (CAN)

The Controller Area Network (CAN) is commonly used for J1939 communications. A standard high-speed CAN system uses a differential two-wire system. The electrical setup of the network affects how reliably messages can be sent.

J1939 defines how messages are sent at a higher level, using a compatible network. CAN and J1939 are not the same: CAN is a communication system, whilst J1939 provides extra rules on top of it.

Parameter Group Numbers (PGNs)

One of the most important concepts in J1939 is the Parameter Group Number (PGN). It identifies which group of parameters is being sent in a message, which helps the receiving device know what type of information it is.

Standard J1939 messages can provide information on engine performance, vehicle speed, diagnostics, and networking. A PGN does not identify a specific measurement; it identifies a group of parameters.

Suspect Parameter Numbers (SPNs)

Suspect Parameter Numbers (SPNs) identify specific parameters in the J1939 system, such as engine speed or coolant temperature.

When an ECU sends a message containing multiple parameters, the PGN identifies the group being sent, and the SPNs identify the individual measurements. Understanding both helps when interpreting raw J1939 data.

For example, if a diagnostic tool receives a message containing engine information, it must identify it correctly. Once identified, the right parameter definitions can be applied to the data, including scaling, units, and operating conditions. If the wrong definitions are applied, the data shown can be misleading even though the CAN communication is working.

J1939 Diagnostic Messages

Another important use of J1939 is diagnostics. Electronic control units can send standardised messages to report abnormal conditions. Depending on the implementation, these can show which faults have been found.

A diagnostic trouble code (DTC) may provide information on which parameter is affected, what type of failure it is, and how many times it has occurred. Technicians can retrieve this using compatible diagnostic tools.

How Can J1939 Help With Maintenance?

By using diagnostic communications, technicians can:

  • Find out which electronic systems are reporting faults.
  • Retrieve diagnostic information.
  • Understand what fault codes mean by using the correct parameter definitions.
  • Compare reported values with expected values.
  • Investigate wiring, sensor, actuator or ECU issues.
  • Confirm that an issue has been fixed.

A diagnostic code should not automatically be assumed to mean a failed component. It only means that an issue has been reported. For example, an engine temperature fault could be due to a sensor issue, a wiring issue, a cooling system issue, or something else affecting engine temperature.

The correct service information, measuring tools and knowledge of the vehicle are needed to diagnose the issue accurately.

J1939 in Commercial Vehicles

J1939 is particularly useful in vehicles that require multiple electronic systems to communicate with each other.

Heavy-Duty Trucks

Commercial trucks use electronic communications to control engine management, transmission, instrumentation and diagnostics. Fleet operators can use compatible interfaces to retrieve vehicle data.

Agricultural Vehicles

Tractors, harvesters and other agricultural vehicles often have multiple controllers. These control the engine, implements, instrumentation and the machine itself. Standardised communications make it easier for compatible components to exchange information.

Construction Vehicles

Excavators, loaders, bulldozers and other construction vehicles use electronic systems to monitor conditions. J1939 communications help compatible systems send relevant information and diagnostics.

Buses and Specialist Vehicles

Buses and specialist vehicles can use electronic communications to link engine systems, instrumentation, monitoring and other compatible systems. The network will differ depending on the vehicle design.

What Is the Relationship Between J1939-91C and Other Documents?

There are many documents relating to J1939. Each one should be understood based on its title, publication number, version and scope.

J1939-91C may relate to an official SAE document, but the full reference should be checked. The "91C" should not be assumed to mean anything specific without checking the official publication.

Before implementing a specification, engineers should check whether it refers to:

  • An official SAE J1939 document.
  • A version of a technical document.
  • A supplier reference.
  • A software or diagnostic reference.
  • A reference to another technical document.

This ensures the correct specification is implemented. If the wrong specification is used, incorrect assumptions can be made about messages, networking requirements and device compatibility.

For official information, visit the SAE International website, as SAE International publishes the SAE standards.

Troubleshooting J1939 Issues

If electronic systems are not communicating correctly, start by checking the network.

Check the Wiring

Look for damaged insulation, loose connections, corrosion, incorrect repairs and other issues. Electrical faults can stop compatible ECUs from communicating.

Check CAN Termination

Many standard high-speed CAN networks use termination resistors, and the resistance depends on the network design. In a standard network with two 120-ohm resistors in parallel, you would typically measure around 60 ohms between CAN-H and CAN-L when the network is switched off and isolated.

This is a common value but is not required for every J1939 implementation. Always follow the manufacturer's diagnostic procedure.

Check the Power and Ground

Sometimes an ECU has communication problems because of poor power or grounding. Check the relevant circuits against the manufacturer's specifications.

Capture Data

A compatible CAN interface and analysis tool can help identify whether the correct messages are being sent. Look at the message identifiers, how often they are sent, and any network errors.

Check Message Decoding

If messages are being sent but the data is not correct, check the PGN, SPN, scaling, offset, byte order, and parameter definitions. If messages are not decoded correctly, the results can be inaccurate even though the network is working.

Check the Right Documentation

Use the relevant SAE publication, the vehicle service manual and the ECU manufacturer's documentation to confirm what the network should be doing. Not all vehicles support all J1939 messages and parameters.

Implementing J1939: Best Practices

A reliable J1939 implementation needs the hardware and software to be set up correctly.

  • Hardware: Engineers should use compatible CAN hardware, follow the correct electrical requirements and use the correct protocol definitions.
  • Software: Developers should check message identifiers and parameter definitions against the official documentation. They should also consider what happens when messages are missing, communication issues occur, data is invalid, or vehicle setups differ.
  • Testing: Testing should be carried out under normal operating conditions and relevant fault conditions.
  • Remote data: If the system collects remote data from the vehicle, care should be taken when there are communication issues, so that incorrect or outdated data is not shown.
  • Security: Diagnostic interfaces and telematics gateways should be set up to prevent unauthorised access. Where possible, they should be set to monitor-only.

This helps improve compatibility, diagnostics and reliability.

Frequently Asked Questions

This needs to be checked against the original technical source. J1939 relates to the J1939 standards family, but the full reference should be checked to see what it actually refers to.

No. CAN is the communication system commonly used with J1939. J1939 adds extra rules to identify messages, parameters, addressing and networking.

A PGN identifies a group of related parameters in a J1939 message. This helps receiving devices know what type of information is being sent.

An SPN identifies a specific parameter within the J1939 system. It is commonly used when interpreting vehicle measurements and diagnostics.

Yes. J1939 can be used for diagnostics in compatible applications. Diagnostic tools can retrieve fault information to help technicians investigate issues with electronic systems.

J1939 is commonly associated with heavy-duty trucks, buses, agricultural vehicles, construction vehicles, and other commercial and industrial applications. The exact implementation depends on the equipment manufacturer.

The best way is to check the original document, manufacturer reference or SAE International publication. This ensures you have the full reference and avoids confusion with other standards, versions, or proprietary references.

Conclusion

The SAE J1939 standards provide a structured method of communication between electronic systems in heavy vehicles and industrial machinery. Through CAN messaging, Parameter Group Numbers, Suspect Parameter Numbers, and diagnostics, compatible ECUs can exchange data.

Understanding these concepts helps engineers, technicians, and software developers interpret vehicle data, investigate communication issues, and integrate compatible monitoring and diagnostic systems.