Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Heavy Vehicle Event Data Recorders (HVEDR): Data Elements and Triggers per SAE J2728-1-2020
This article provides a practical overview of SAE J2728-1-2020, which defines a minimum set of data elements and heavy vehicle–specific triggers for event data recording. Engineers designing or integrating HVEDR systems will find guidance on trigger configurations, data formatting, and common implementation pitfalls. 🛠️
Understanding Event Triggers
Three primary trigger types cause an HVEDR event record to be saved to non-volatile memory. Proper configuration of these triggers is essential for reliable event capture.
Acceleration Trigger
The acceleration trigger activates when the vehicle’s speed changes at a rate higher than a programmable threshold set between 8.0 km/h/s (5.0 mph/s) and 22.5 km/h/s (14.0 mph/s). The change can be positive or negative, and must persist beyond the threshold for at least 0.5 second. The event start is the time the threshold is crossed. A common default is 11.3 km/h/s (7.0 mph/s). The standard recommends using appropriate filtering to minimize false events from ABS cycling or noise in the VSS signal.
Last Stop Trigger
The last stop trigger captures an event after the vehicle has come to a complete stop for a defined period. The suggested threshold is when vehicle speed falls below 3.0 km/h (1.9 mph) for 15 seconds or more. To prevent overwriting of critical data, the trigger cannot rearm until the vehicle reaches 24.0 km/h (14.9 mph) or more for at least 6 seconds. Turning the ignition off does not directly trigger a last stop event.
Safety System Triggers
Safety systems that provide control or driver alerts should trigger an event record. The standard defines specific signals from systems such as the safety restraint, ABS, adaptive cruise control/automated braking, and electronic stability control. The table below summarizes the recommended trigger signals and their J1939 message sources.
| System | Message | Trigger Condition |
|---|---|---|
| Safety restraint system | PGN 61483 / SPN 4973 (CN.Crash Type) | Non‑zero crash type |
| ABS system | PGN 61441 / SPN 563 (EBC1.ABSActive) | ABS active |
| Adaptive cruise control/automated braking | PGN 64964 / SPN 2918 (EBC5.XBR Active Control Mode) | External brake request |
| Electronic stability control | PGN 65103 / SPN 1819 (VDC1.YCBrakeControl = 1) or PGN 65103 / SPN 1818 (VDC1.ROPBrakeControl = 1) | Yaw control or roll over brake control active |
🛠️ Design Insight: The acceleration threshold is programmable within the 8.0–22.5 km/h/s range. For typical on‑highway heavy trucks, a default of 11.3 km/h/s is recommended, but vocational vehicles may require adjustments. The 0.5‑second persistence requirement helps reduce false events from signal noise.
Data Element Requirements and Recording Management
The standard specifies a minimum set of data elements to be recorded, including header data and data element buffers. The buffer design must prevent overwriting of event data, especially for the last stop event. The HVEDR must support defined sampling and write rates, and the event record duration must meet the standard’s recommendations. Data elements should be formatted according to SAE J1939-71 where applicable, and the output should comply with the CSV specification (RFC 4180) if exported.
⚠️ Common Pitfall: Failing to implement the last stop trigger rearm condition can lead to valuable event data being overwritten. Always ensure that the system requires vehicle speed ≥24 km/h for at least 6 seconds before rearming. Also verify that all required data elements, such as vehicle speed and crash type, are included and formatted correctly.
Frequently Asked Questions
What is the recommended acceleration trigger threshold for heavy trucks?
The SAE J2728-1-2020 standard recommends a default of 11.3 km/h/s (7.0 mph/s) for typical on‑highway heavy trucks, with a programmable range of 8.0 to 22.5 km/h/s.
How does the last stop trigger prevent overwriting of event data?
The last stop trigger cannot reoccur until the vehicle speed reaches 24.0 km/h (14.9 mph) or more for a minimum of 6 seconds. This rearm condition ensures that short stops after an incident do not overwrite the event of interest.
What are the minimum data recording capabilities required by the standard?
The standard requires recording header data, defined data element buffers, and event record duration. The HVEDR must sample and write data at the specified rates and ensure that event data is not overwritten unintentionally. At minimum, vehicle speed and crash type should be recorded if available.
How should the HVEDR interface with J1939 safety system messages?
The HVEDR should monitor the specific PGNs and SPNs listed in the safety systems trigger table. It must recognize trigger conditions, such as a non‑zero crash type from the safety restraint system or an ABS active signal, and initiate an event record accordingly.
