Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J1939-73-2024: Application Layer Diagnostics for Heavy-Duty Vehicles
The SAE J1939-73-2024 standard defines the application layer for diagnostics in heavy-duty vehicle communication networks based on CAN (ISO 11898-1). This document provides a comprehensive set of diagnostic messages (DM) for reporting trouble codes, handling memory access, and meeting global on-board diagnostics (OBD) regulations. The 2024 revision introduces support for CSERS parameter groups (PGs) and China 6 Non-Road requirements, along with updates to FMI definitions and new diagnostic messages like DM57 for plug-in hybrid ignition cycle counts.
Understanding Key Diagnostic Messages
The standard specifies a series of Diagnostic Messages (DM) that cover all aspects of vehicle diagnostics, from active trouble code reporting to boot load data. Below is a summary of essential messages:
| DM Number | Purpose | Key Usage |
|---|---|---|
| DM1 | Active Diagnostic Trouble Codes | Broadcasts currently active faults in real-time |
| DM2 | Previously Active DTCs | Reports faults that have occurred but are no longer present |
| DM3 | Clear/Reset DTCs | Clears previously active diagnostic trouble codes |
| DM4 | Freeze Frame Parameters | Captures vehicle state at time of fault |
| DM5 | Diagnostic Readiness 1 | Indicates supported DMs and monitor status |
| DM12 | Emission-Related MIL-On DTCs | For OBD compliance, reports faults that cause MIL illumination |
| DM14-DM18 | Memory Access and Security | Secure access to ECU memory for calibration and diagnostics |
Engineering Design Insights and OBD Compliance
Implementing the diagnostic services defined in SAE J1939-73-2024 requires careful attention to the combination of Suspect Parameter Number (SPN) and Failure Mode Identifier (FMI) for accurate fault isolation. Additionally, supporting OBD regulations demands precise handling of emission-related DTCs and readiness monitors.
🔍 Design Insight: The use of DM1/DM2 with proper SPN/FMI encoding is the foundation of effective diagnostic troubleshooting. Engineers should also implement the Diagnostic Readiness messages (DM5, DM21, DM26) to allow external testers to discover supported services and monitor status.
⚠️ Common Pitfall: Forgetting to implement security mechanisms for memory access (DM14-DM18) can lead to unauthorized calibration changes. Always ensure that the appropriate authentication and data protection measures are in place per the standard’s recommendations.
Frequently Asked Questions
- What does SAE J1939-73-2024 cover? It defines the application layer for diagnostic services in heavy-duty vehicle networks, including DTC reporting, memory access, and OBD-related functions.
- How do I interpret a Diagnostic Trouble Code? A DTC is formed by the combination of a Suspect Parameter Number (SPN), Failure Mode Identifier (FMI), and occurrence count. Understanding the SPN-FMI mapping is crucial for pinpointing the fault.
- Why are DM5 and DM21 important? These messages provide diagnostic readiness information, allowing a diagnostic tool to query which DM messages are supported by an ECU and the status of monitors.
- What changes were introduced in the 2024 revision? The revision added support for CSERS PGs, China 6 Non-Road requirements, DM57 for plug-in hybrid counters, and updated FMI definitions (e.g., FMI 24).
