Reference · built on requestConnectorIndustrial & building protocols

SAE J1939

Engine, fuel, aftertreatment, and diagnostic data from the SAE J1939 CAN network on trucks, off-road equipment, and generator sets.

Request accessPricing ↗

About

SAE J1939 is the controller network for heavy-duty vehicles. SAE International's Truck and Bus Control and Communications Network Committee publishes it as a family of documents: J1939-21 for the data link, J1939-71 for the vehicle application layer, J1939-73 for diagnostics, and J1939-81 for network management. The network runs on CAN with 29-bit identifiers as defined in ISO 11898-1. Every parameter (SPN) and message (PGN) is listed in the J1939 Digital Annex, a spreadsheet SAE sells separately. The documents cover on-road and off-road trucks, trailers, construction and agricultural equipment, and stationary applications built from vehicle components, such as generator sets.

Through Fibric, an operator listens to the bus through a gateway you install, decodes the parameter groups you choose, and proposes a service ticket, a fuel review, or a hold on a unit for your approval. Each proposal leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from SAE J1939 and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Parameter groups (PGs) and suspect parameters (SPs), decoded with the resolution, offset, units, and SLOT identifier from the J1939 Digital Annex
  • Active diagnostic trouble codes and operator lamp status, broadcast periodically by each control module as J1939-73 defines
  • Diagnostic readiness and engine parametric data, the services J1939-73 specifies for the vehicle service tool interface
  • Address claims and NAME fields from each controller on the network, as J1939-81 defines them
  • The transmission rate and default priority the Digital Annex lists for each message, so a missing broadcast is noticed
  • Multipacket messages carried over the J1939-21 data link

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Open a service ticket on a live fault

    When a control module broadcasts an active trouble code, decode the SPN and FMI, check whether it repeats, and propose a work order with the code and the hours reading.

    With Vehicle Fault, Parts Readiness

  • Catch fuel that leaves without the truck

    Read the fuel parameters the engine broadcasts, compare consumption against distance and engine hours, and propose a review when a unit's fuel drops while it is parked.

    With Fuel Anomaly, Idle Watch

  • Watch a generator set like a truck

    J1939-21 covers stationary applications built from vehicle components. Read the engine parameters from a standby generator and propose maintenance before a test run fails.

    With Predictive Maintenance, Generator Test

Requirements

  • A CAN interface or telematics gateway with physical access to the vehicle's J1939 network
  • A licensed copy of the J1939 Digital Annex, sold by SAE, for the PGN and SPN definitions you decode
  • The list of parameter groups you want read, with the source addresses that send them
  • For manufacturer-specific parameter groups, the manufacturer's own definitions
Authentication
There is no authentication on a J1939 network. Access is physical: a CAN interface on the diagnostic connector that J1939-73 identifies, or a telematics gateway already on the bus.

Limits

  • SAE sells the J1939 documents and the Digital Annex. They are not free downloads, so the decode tables depend on your licence
  • J1939-73 defines services that clear codes and write control module memory. This listing does not send them; they stay with the service tool
  • A listen-only reader sees only what modules broadcast on their own; parameters sent on request need a bus write this listing does not make
  • The top-level document is at revision J1939_202603 and each subordinate document revises on its own schedule, so decode tables need review per revision

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SAE J1939 ↗

Questions and answers

What does SAE J1939 run on?
CAN. J1939-21 specifies the data link layer using the Classical Extended Frame Format with 29-bit identifiers as defined in ISO 11898-1, and permits no alternative data link layer.
Where are the PGN and SPN definitions?
In the J1939 Digital Annex (J1939DA), a spreadsheet SAE sells separately or as part of the J1939 Standards Collection. It lists each PGN with its transmission rate, default priority, and data length, and each SPN with resolution, offset, units, and SLOT identifier.
Does this connector clear fault codes?
No. J1939-73 defines diagnostic messages for reading and clearing trouble codes and for writing control module memory, but this listing reads the bus only. Clearing codes stays with the service tool.
Ask about SAE J1939

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SAE J1939 through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy