Contents

SAE J1939 — the language of trucks and buses

The CAN-based protocol family used across commercial vehicles, agricultural and construction machines — standard parameter groups that let ECUs from different suppliers understand each other.

Why it exists

Trucks combine engines, transmissions, brakes and bodies from many suppliers. Instead of each OEM inventing proprietary messages, the industry agreed on J1939: a shared vocabulary on top of CAN.

What it is

  • Uses 29-bit CAN identifiers that encode a Parameter Group Number (PGN), a priority and a source address.
  • Defines standard parameters (SPNs) such as engine speed or fuel level.
  • Address claiming lets ECUs negotiate addresses at startup.
  • A transport protocol carries messages longer than 8 bytes.
J1939 29-bit CAN identifier
Priority3 bits
EDP1 bitExtended data page
DP1 bitData page
PDU format8 bits
PDU specific8 bitsDestination address or group extension
Source address8 bits

Fields run from bit 28 to bit 0; PDU specific is a destination address when PDU format is below 240, otherwise a group extension.

How it is used

Powertrain, braking, body and telematics ECUs exchange standardised messages. Fleet telematics read J1939 data for fuel, maintenance and driver monitoring; trailers communicate over ISO 11992.

Best practices

  • Filter J1939 traffic at gateways to telematics and body-builder interfaces.
  • Monitor for unexpected source addresses and diagnostic commands.

Common pitfalls

  • Assuming obscurity: J1939 is publicly documented, so standard messages are easy to forge.

What it means for your discipline

  • Networks & communication Core

    Most commercial-vehicle networks are J1939: parameter group numbers, address claiming and transport protocols must be mastered.

  • Cybersecurity Core

    J1939's openness and standard messages make attacks easier to transfer between vehicles; fleets and telematics add exposure.

  • Base software Partial

    AUTOSAR provides J1939 modules (J1939Tp, J1939Nm, J1939Rm, J1939Dcm).

  • Diagnostics & lifecycle Partial

    J1939-73 defines diagnostic messages (DM1 active faults, etc.) used in workshops and telematics.

  • E/E architecture Partial

    Trailer, body-builder and aftermarket interfaces in trucks rely on J1939 — they shape the platform for decades.

No direct stake: Functional safety · HPC & application software · Hardware & silicon · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)
  • Classic RTE & COM — Hosts J1939 transport and network management when the safety island connects to commercial-vehicle CAN networks.
  • Vehicle services — Interprets J1939 vehicle parameters for fleet, maintenance and gateway services.
MCU-based ECU · AUTOSAR Classic
  • Communication — Handles J1939 transport, address claiming and routing of parameter groups.
  • Diagnostics — Produces and processes J1939 diagnostic messages, including active fault reports.
  • Microcontroller abstraction (MCAL) — Transmits and receives CAN frames using the extended 29-bit identifiers required by J1939.