Search Results

This SAE Information Report provides SAE’s recommendations for meeting the requirements for REAL NOx accuracy demonstration and for the implementation of REAL NOx binning requirements as defined in OBD regulations 13 CCR 1971.1 and 13 CCR 1968.2.

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. It defines the common data structures and constants that will be used to implement the extension to the SAE J2534 API. This document will only include the items that are used by the V05.00 API and that are NOT included in SAE J2534-1_0500. It will not include items from older API versions unless they are used by the V05.00 API.

This SAE Recommended Practice describes a standardized interface that connects between a standard personal computer (PC) and vehicle.The purpose of this interface is to enable the reprogramming of emission-related control modules, in 2004 and later model year vehicles. The interface shall consist of the necessary hardware and/or software to support the requirements defined in this document. It is expected that vehicle manufacturers will provide the software application that will control the pass-thru interface, to perform the actual reprogramming. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with interface supplied by any tool manufacturer. A common interface for all vehicle manufacturers reduces the tool costs for aftermarket garages, while allowing each vehicle manufacturer to control the programming sequence for the electronic control units (ECUs) in their vehicles.

This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in 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. SAE J2012 may also be used for decoding of enhanced diagnostic DTCs and specifies the ranges reserved for vehicle manufacturer specific usage.

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 Information Report defines the diagnostic communication protocol TP1.6. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP1.6 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface. This SAE Information Report describes how a tester can be connected to a vehicle to perform diagnostics using the TP1.6 protocol. Details regarding ECU to ECU communication have been left out.

On-Board Diagnostic (OBD) regulations require passenger cars, and light and medium duty trucks, to support communication of a minimum set of diagnostic information to off-board “generic” test equipment. This document specifies the diagnostic data which may be required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to motor vehicle emission-related data. SAE J1979 was originally developed to meet U.S. OBD requirements for 1996 and later model year vehicles. ISO 15031 5 was based on SAE J1979 and was intended to combine the U.S. requirements with European OBD requirements for 2000 and later model year vehicles.

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. It defines the common data structures and constants that will be used to implement the extension to the SAE J2534 API. This document will only include the items that are used by the V05.00 API and that are NOT included in SAE J2534-1_0500. It will not include items from older API versions unless they are used by the V05.00 API.

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 UART Echo Byte 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/3_0500 interface shall be compliant to the UART Echo Byte 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.

SAE J2534-1_0500 defines the pass-thru interface requirements for the reprogramming of emission related control modules. The SAE J2534-2/X_0500 document set adds extensions to the SAE J2534-1_0500 API (version 05.00) specification so that the API can be used for features not covered in the SAE J2534-1_0500 specification. Together, these features provide a comprehensive framework for a common standard, to protect the software investment of the vehicle OEMs and scan tool manufacturers. There is no required for an SAE J2534-2/X_0500 pass-thru interface to be fully compliant with SAE J2534-1_0500. SAE J2534-2/X_0500 interfaces can implement some or all of the features specified in the SAE J2534-2/X_0500 document set. This document must be used in conjunction with the SAE J2534-2/RE_0500 document.

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.

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 fault-tolerant CAN (FT CAN) 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/8_0500 interface shall be compliant to fault-tolerant CAN (FT CAN) 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.

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 HONDA_DIAGH 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/4_0500 interface shall be compliant to the HONDA_DIAGH 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.

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 single wire CAN (SW CAN) 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/1_0500 interface shall be compliant to the single wire CAN 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.

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 GM_UART 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/2_0500 interface shall be compliant to the GM_UART 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.

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 TP2.0 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/7_0500 interface shall be compliant to the TP2.0 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.

This SAE Recommended Practice details the changes needed to support the SAE J2534 (API Version 04.04) on operating systems other than 32-bit Microsoft Windows®.

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 J1939 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/5_0500 interface shall be compliant to the SAE J1939 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.

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 the internet protocol version 6 (IPv6) 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/15_0500 interface shall be compliant to the internet protocol version 6 (IPv6) 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/13_0500 (ethernet), SAE J2534-2/BA_0500, and SAE J2534-2/RE_0500 documents.

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 the Internet Protocol version 4 (IPv4) 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/16_0500 interface shall be compliant to the Internet Protocol version 4 (IPv4) 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 SAE J2534-2/13_0500 (ethernet), SAE J2534-2/BA_0500, and SAE J2534-2/RE_0500 documents.