Search Results

SAE J1978/ISO 15031-4 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which is compliant with SAE J1978/ISO 15031-4. The SAE J1978 content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. on-board diagnostic (OBD) regulations. The ISO 15031-4 content of this document is intended to satisfy the requirements of OBD requirements in countries other than the U.S., and includes functionality not required or not allowed in the U.S. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979/ISO 15031-5.

This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement SAE J1708 within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/6_0500 interface shall be compliant to the SAE J1708 feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents.

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534 2 feature “Mixed Format Frames on a CAN Network.”

The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature “Mixed Format Frames on a CAN Network.”

SAE J1979-2 describes the communication between the vehicle's OBD systems and test equipment required by OBD regulations. On-Board Diagnostic (OBD) regulations require passenger cars and light-, medium-, and heavy-duty trucks to support a minimum set of diagnostic information to external (off-board) “generic” test equipment. To achieve this, SAE J1979-2 is based on the Open Systems Interconnection (OSI) Basic Reference Model in accordance with ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers.

SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year, as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 specification. It is not required for an interface to be fully compliant with SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/EDiagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics - Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 specification. It is not required for an interface to be fully compliant with SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.

This document supersedes SAE J1979 May 2007, and is technically equivalent to ISO 15031-5 2010, with the addition of new capabilities required by revised regulations from the California Air Resources Board and revised regulations from the European Commission. This document is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future.

This document supersedes SAE J2012 APR2002, and is technically equivalent to ISO 15031-6:2005 with the exceptions described in Section 1.2. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. This document includes: a Diagnostic Trouble Code format. b A standardized set of Diagnostic Trouble Codes and descriptions c A standardized set of Diagnostic Trouble Codes subtypes known as Failure Types

This document supersedes SAE J1979 Apr 2002, and is technically equivalent to ISO 15031-5:2006, with the addition of new capabilities required by revised regulations from the California Air Resources Board (see Section 1.2). This document is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future.

This document supersedes SAE J1962 FEB1998, and is technically equivalent to ISO/DIS 15031-3:December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.

This document supersedes SAE J1979 SEP1997, and is technically equivalent to ISO/DIS 15031-5:April 30, 2002. This SAE Recommended Practice is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future. This document specifies: a Message formats for request and response messages, b Timing requirements between request messages from external test equipment and response messages from vehicles, and between those messages and subsequent request messages, c Behavior of both the vehicle and external test equipment if data is not available, d A set of diagnostic services, with corresponding content of request and response messages, to satisfy OBD regulations, This document includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types.

This SAE Recommended Practice supersedes SAE J2012 MAR1999, and is technically equivalent to ISO/DIS 15031-6:April 30, 2002. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. This document includes: a Diagnostic Trouble Code format b A standardized set of Diagnostic Trouble Codes and descriptions

This SAE Recommended Practice is applicable to all light-duty and medium-duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair databases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e., test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.

This SAE Recommended Practice is applicable to all light-duty and medium-duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair databases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

This SAE Recommended Practice defines the Expanded Diagnostic Protocol (EDP), the requirements for the SAE J1978 OBD II Scan Tool for supporting the EDP protocol, and associated requirements for diagnosis and service information to be provided by motor vehicle manufacturers. Appendix A includes worked examples of the use of the protocol.