To develop OBD-compliant engines or service tools, engineers must cross-reference their work with the exact requirements laid out by the SAE committee.
While lower layers of the J1939 standard dictate the physical wires and data formatting, the application layer is where the shared "vocabulary" lives. that allow on-board ECUs and off-board service tools (like diagnostic laptops or handheld scanners) to talk to one another.
"J1939-73 identifies the diagnostic connector to be used for the vehicle service tool interface and defines messages to accomplish diagnostic services."
SAE J1939-73 represents the backbone of diagnostic communication for heavy-duty vehicles and industrial equipment. Whether you are developing ECUs, designing diagnostic tools, or maintaining fleets, understanding this standard is essential for effective vehicle diagnostics. Sae J1939-73 Pdf
Ensuring aftermarket or OEM diagnostic tools can correctly request and interpret vehicle data. ECU Programming:
Modern J1939-73 (especially versions after 2013) includes DM14, which allows a diagnostic tool to request a specific DTC from a specific ECU. This replaces older broadcast methods and is essential for high-speed, targeted diagnostics on a busy CAN bus.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. To develop OBD-compliant engines or service tools, engineers
The SAE J1939-73 standard defines the recommended practice for diagnostic communication in heavy-duty vehicles. Developed by the Society of Automotive Engineers (SAE), this protocol operates on top of the Controller Area Network (CAN) physical layer. It provides the framework that diagnostic tools, electronic control units (ECUs), and fleet management systems use to identify faults, run tests, and read vehicle state information.
John, a seasoned truck mechanic, was working on a particularly stubborn Peterbilt 389. The truck's dashboard lit up like a Christmas tree, with multiple warning lights indicating various problems. The truck wouldn't start, and the engine control unit (ECU) displayed a string of cryptic error codes. Frustrated and under pressure to get the truck back on the road, John knew he needed to dive deeper into the SAE J1939-73 standard.
If you are building an application that needs to extract engine data, emissions readiness, or DTCs, relying on the ensures that your system adheres to global industry protocols. Reverse-engineering these standards or guessing how an ECU will respond to a diagnostic request can lead to faulty CAN bus traffic, communication errors, or failures during emissions inspections. How to Access the Standard "J1939-73 identifies the diagnostic connector to be used
It defines the structure of the 4-byte DTC, which consists of the Suspect Parameter Number (SPN), Failure Mode Identifier (FMI), Occurrence Count (OC), and SPN Conversion Method. Diagnostic Messages (DM):
While DM1 shows currently active faults, DM2 is used to log that may no longer be present. These are historical trouble codes, which are incredibly valuable for diagnosis. They provide a record of intermittent faults or issues that have been resolved but not yet cleared from memory.