Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Implementing SAE J1698-2-2023: A Protocol Guide for EDR Retrieval Tools
Standard Interface and Protocol Foundations
This SAE Recommended Practice establishes a common framework for developing EDR retrieval tools. It designates the SAE J1962 diagnostic connector as the primary physical interface for on-board retrieval and defines the protocols for imaging, translating, and reporting EDR records in light duty vehicles. Adhering to this standard is essential for ensuring consistency and reliability across tools and vehicle platforms. The table below summarizes the key requirements every engineering team must address when implementing the protocol.
| Component | Specification / Requirement |
|---|---|
| Physical Interface (On-Board) | SAE J1962 diagnostic connector; tool must accommodate manufacturer-specific discretionary pin assignments and electrical architectures. |
| Physical Interface (Off-Board) | Direct ECU connection; tool must supply power to the ECU and adapt to different connectors, protocols, and baud rates. |
| Data Security | All imaged data must be authenticated and encrypted per NIST SP 800-38C (CCM mode) or an equivalent standard. |
| Data Integrity | A minimum of three automated imaging passes with byte-level comparison. Discrepancies must result in an error message and prevent saving or translation. |
| Data Neutrality | Only read-only diagnostic services that suppress Diagnostic Trouble Code (DTC) setting during the imaging process shall be used. |
| Vehicle Configuration | The tool uses the Vehicle Identification Number (VIN) to determine the correct communication protocol, physical IDs, and translation rules. |
Ensuring Data Integrity, Security, and Forensic Neutrality 🔍
The standard places a strong emphasis on maintaining the forensic quality of retrieved EDR data. This involves three critical pillars: integrity, security, and neutrality.
Data Integrity. To guarantee consistent data capture, the SAE J1698-2 protocol requires the tool to automatically image the EDR record a minimum of three times. If any of these imaging cycles yield different data, the tool must display an error and refuse to save or translate the record. This rigorous comparison prevents corrupted or transient data from entering the final report.
Data Security. All retrieved and stored EDR data must be protected. The standard mandates authentication and encryption per NIST SP 800-38C (CCM mode). Tool developers must integrate this to ensure the chain of custody remains intact and data cannot be tampered with undetected.
Data Neutrality. A crucial aspect of forensic integrity is ensuring the retrieval process itself does not alter the vehicle’s system state. The tool should use diagnostic services that request data without activating system diagnostics, thereby suppressing the setting of Diagnostic Trouble Codes (DTCs) during the imaging process.
Common Implementation Pitfall: A frequent mistake is failing to fully suppress DTC setting during ECU communication. Always verify that the specific diagnostic services used by the retrieval tool do not inadvertently trigger or clear system fault codes, as this can compromise the validity of the EDR evidence.
Engineering Design Insight. Developers must implement robust CCM encryption modules and triple-image comparison logic in the tool’s core firmware. The tool architecture should prioritize non-intrusive read commands over standard diagnostic requests to maintain strict forensic neutrality.
Frequently Asked Questions
Q1: What is the designated physical interface for on-board EDR retrieval?
A: The SAE J1962 diagnostic connector is the primary physical interface. The tool must accommodate different pin assignments and electrical architectures as defined by the vehicle manufacturer.
Q2: What security standard must be applied to imaged EDR data?
A: NIST SP 800-38C (CCM mode). All imaged data stored or transmitted by the tool must be both authenticated and encrypted according to this standard or an equivalent alternative.
Q3: How is data integrity verified during the imaging process?
A: The tool must automatically image the complete EDR record at least three times. These imaged records are compared byte-by-byte. If discrepancies are found, the tool must display an error and is prohibited from saving or translating the data.
Q4: How does the tool know which communication protocol and translation to use for a specific vehicle?
A: The tool reads the Vehicle Identification Number (VIN) from the vehicle. The VIN is used to select the correct communication protocol, physical identifiers, and translation rules. If the VIN cannot be read automatically, the operator may enter it manually.
🛠️ Off-Board Retrieval Note: When connecting directly to an ECU, the retrieval tool must supply adequate power and may require specialized adapters for physical connectors, network protocols, and baud rates that differ from the standard J1962 path.
