Contents
StandardSAE

SAE J1939

Serial control and communications heavy duty vehicle network

SAE J1939 is a family of standards that gives electronic controllers in trucks, buses, and other heavy-duty equipment a common way to exchange operating data and diagnostic information.

What it is

SAE J1939 is a family of communication documents maintained by SAE International. It defines how electronic control units (ECUs) exchange information in heavy-duty vehicles and related equipment. The top-level document introduces the family; detailed requirements sit in separate parts and the J1939 Digital Annex.

Think of CAN as the mechanism that carries messages, while J1939 gives those messages an agreed structure and meaning. An engine controller and an instrument cluster can therefore exchange operating information using shared definitions rather than a completely private supplier protocol.

Who it applies to

J1939 is relevant to vehicle manufacturers, ECU suppliers, network integrators, diagnostic-tool developers, and test engineers. Typical applications include trucks, buses, construction machinery, agricultural equipment, and stationary equipment using vehicle-derived components.

Its use depends on the vehicle architecture, customer requirements, and applicable regulatory context. Being an SAE Recommended Practice does not by itself make the entire family a legal obligation. A project must identify the parts, revisions, and application requirements it actually needs.

What it covers

The family spans electrical connections, message exchange, controller identification, application data, and diagnostics. Important building blocks include:

Building block Purpose
Physical-layer parts Define the selected network’s electrical and wiring requirements.
J1939/21 Defines Classical CAN data-link behavior and transport for larger messages.
J1939/81 Defines network management, including address claiming.
J1939/71 and Digital Annex Provide application-layer conventions and parameter/message definitions.
J1939/73 Defines diagnostic messages and services.

A Parameter Group Number (PGN) identifies a message group. A Suspect Parameter Number (SPN) identifies a parameter, such as a measured operating value. Correct interpretation also requires the parameter’s encoding, units, scaling, and special states.

Address claiming allows controllers to establish their network addresses. Transport mechanisms carry information that does not fit in a single frame. Diagnostic messages communicate faults and other information used by controllers and service tools.

How it fits with other documents

J1939 builds on CAN technology defined in the ISO 11898 family. Supporting CAN alone does not establish J1939 compatibility: controllers must also agree on message definitions, timing, addressing, and the selected physical layer.

The Digital Annex is an important companion because it provides searchable assignments and technical data. It does not replace every detailed requirement in the individual parts. Keep its revision aligned with the project’s communication specification.

AUTOSAR Classic provides J1939-related basic software specifications for implementations using that platform. Those software specifications complement the SAE communication requirements.

J1939 also operates alongside functional-safety, cybersecurity, and emissions requirements. Protocol conformance alone does not demonstrate compliance with those separate obligations.

In practice

Start with a vehicle communication specification that names the applicable J1939 parts and revisions. Record each controller’s identity, addressing behavior, transmitted and received messages, timing, and diagnostic responsibilities. Identify any proprietary messages explicitly.

For example, when a display receives an engine operating value, verify more than whether frames arrive. Check the source, decoding, update timing, unavailable-value handling, and the display’s response when communication stops.

Integration testing should exercise address conflicts, controller restarts, missing messages, interrupted multi-frame transfers, and diagnostic-tool interaction. Test controllers together: two products advertised as supporting J1939 can still disagree about optional features or project configuration.

Purchase the required documents and Annex, then use them as controlled engineering references. A generic decoder or sample message database is useful for exploration, but needs checking against the agreed specification.

What it means for your discipline

  • Networks & communicationCore

    Own the network configuration, message traffic, addressing, and communication behavior. Verify that controllers from different suppliers work together under normal and fault conditions.

  • Base softwareCore

    Implement and configure the J1939 protocol stack, including transport, address claiming, and interfaces to application signals. Handle timeouts, unavailable data, and communication errors consistently.

  • Diagnostics & lifecycleCore

    Implement diagnostic messages, fault reporting, and service-tool behavior using the applicable diagnostic part. Align ECU fault information with vehicle service and applicable emissions requirements.

  • E/E architecturePartial

    Define which controllers and network segments use J1939, and specify gateway boundaries and supplier interfaces. Allocate communication responsibilities and agree the applicable document revisions.

  • HPC & application softwarePartial

    Map application values to standardized parameters with the correct units, scaling, and validity states. Design application responses to missing, stale, or implausible messages.

  • Hardware & siliconPartial

    Apply the selected physical-layer requirements to transceivers, wiring, termination, and connectors. Check electrical compatibility across the intended vehicle installation.

  • Functional safetyPartial

    Assess how delayed, missing, or incorrect network data affects safety-related functions. Define the necessary monitoring and fault reactions beyond basic protocol compliance.

  • CybersecurityPartial

    Assess exposure through vehicle networks, gateways, and diagnostic access. Determine the protections needed against unauthorized messages and diagnostic actions.

  • Software update & OTAPartial

    Check that ECU updates preserve agreed message definitions, addressing, and diagnostic behavior. Manage compatibility when updated and older controllers operate together.