Search Results

The J2012 Digital Annex of Diagnostic Trouble Code Definitions Spreadsheet provides DTC information in an excel format for use in your organization's work processes. The column headings include the same information as contained in the J2012 standard. Information in the excel spreadsheet will be updated several times annually and the spreadsheet includes a column heading denoting which DTCs have been updated in the current version.

This document focuses on the latest in-force regulations. However, in addition to latest information, the report may include historical information. As regulations are superseded, the previous entry will remain to help understand the change in requirements over time. The initial focus of the document includes light-, medium-, and heavy-duty on-road vehicles with all propulsion systems. The document will include information from the United States and Canada, with later publications expanding to other regions. Forecasts for future regulations will not be included in the spreadsheet but be kept in a separate document. The document may be expanded to other types of applications/vehicles as information becomes available.

This document is intended to satisfy the data reporting requirements of standardization regulations in the United States and Europe, and any other market 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. e Standardized source and target addresses for clients and vehicle. This document includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types. At the time of publication many regional regulations are not yet final and are expected to change in the future.

Continuation of the digital annex of terms and definitions for use by scantools and maintain alignment of terms with other committees such as J2012, J1979, J1939 etc. and with regulatory bodies.

SAE J1979-3 describes the communication between the zero emissions propulsion systems and test equipment required by government regulations. Standardization 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-3 is based on the Open Systems Interconnection (OSI) Basic Refer to Model in accordance with ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers.

SAE J1979-3 describes the communication between the zero emissions propulsion systems and test equipment required by government regulations. Standardization 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-3 is based on the Open Systems Interconnection (OSI) Basic Refer to Model in accordance with ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers.

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 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.

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 analog input 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/10_0500 interface shall be compliant to the analog input 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 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.

To define a list of anomalies related to OBD Communications. Misinterpretations of various OBD Communications Standards and Recommended Practices have resulted in OBD “no-communications” situations in the field. This Information Report identifies the most prevalent of these.

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 recommends test methods, test procedures, and specific test parameters to help verify that vehicles and test tools can communicate using the SAE J1850. This document only verifies the portion of SAE J1850 that is used for OBD-II communications. The term “test tool” is synonymous with OBD-II Scan tool.

This Digital Annex contains all of the information previously found within the SAE J1930 tables, including diagnostic terms applicable to electrical/electronic systems and related mechanical terms, definitions, abbreviations, and acronyms.

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.”