Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding SAE J2205: The Expanded Diagnostic Protocol for OBD II Scan Tools
What Is the Expanded Diagnostic Protocol?
The Expanded Diagnostic Protocol (EDP) defined in SAE J2205 is a set of encoding techniques that enables SAE J1978 OBD II Scan Tools to communicate with vehicles for advanced emissions-related powertrain diagnostics. Its purpose is threefold:
- To describe to the scan tool the messages to be transmitted to a vehicle and how they are to be transmitted.
- To describe the messages to be received and processed by the scan tool.
- To describe how to process the data in the received messages.
This protocol builds on existing communication interfaces—SAE J1850 and ISO 9141-2—and references SAE J1979 for message definitions. While the overall message structure must conform to these standards, the protocol allows vehicle-specific headers and data fields, providing flexibility for manufacturers to implement proprietary diagnostic extensions.
Key Requirements and Design Insights 🔍
SAE J2205 establishes clear responsibilities for both vehicles and scan tools to ensure interoperability:
| Component | Requirement |
|---|---|
| Vehicle | Must support a message protocol compatible with the scan tool and capable of accessing services required for emissions diagnostics. |
| Scan Tool | Must allow the user to enter, edit, select, and transmit messages; identify and receive expected messages; and define and execute data processing steps. A user manual or help facility is also required. |
| Communication | Messages must conform to SAE J1979, SAE J1850, and ISO 9141-2, with the exception that header and data fields may be vehicle-specific. |
Engineering Design Insight: The structured encoding approach of the Expanded Diagnostic Protocol strikes a critical balance between flexibility and interoperability. By allowing vehicle-specific message definitions while mandating conformance to core standards, it enables manufacturers to innovate without fragmenting the diagnostic ecosystem. However, engineers must carefully handle vehicle-specific fields to avoid violating the underlying protocol requirements.
Regulatory Context: This standard supports compliance with the California Code of Regulations Title 13 Section 1968.1, which requires manufacturers to provide diagnostic access using the SAE J1978 scan tool. Understanding the EDP is essential for developing tools that meet OBD II legal requirements.
Standard Status: SAE J2205 was cancelled in July 1999 and superseded by earlier versions. Engineers should verify current applicable standards for OBD II scan tool communication, as newer documents may have replaced or deprecated this protocol.
Frequently Asked Questions
1. What was the main goal of SAE J2205?
The standard aimed to define encoding techniques that allow OBD II scan tools to handle vehicle-specific messages for emissions diagnostics, ensuring a consistent interface across different vehicle manufacturers.
2. How does the protocol handle vehicle-specific messages?
Messages may have vehicle-specific headers and data fields, but they must still conform to the framework of SAE J1979, J1850, and ISO 9141-2. The scan tool uses the encoding techniques to dynamically describe, transmit, receive, and process these messages.
3. What are the encoding techniques used for?
The techniques describe to the scan tool how to format outgoing messages, which incoming messages to expect, and how to interpret the data within received messages. This enables the tool to adapt to different vehicle models without needing hardware changes.
4. Why is this standard relevant despite being cancelled?
Many legacy vehicles and scan tools rely on the Expanded Diagnostic Protocol, and understanding it provides insight into the evolution of OBD II communication standards. It also highlights the balance between manufacturer-specific needs and regulatory compliance.
🛠️ Mastering the Expanded Diagnostic Protocol is a key step for engineers working on automotive diagnostics and OBD II compliance systems.
