Standard
Pass-Thru Extended Feature - TCP CLIENT2022-01-17
CURRENT
J2534-2/18_0500_202201
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 transmission control protocol (TCP) 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/18_0500 interface shall be compliant to the TCP CLIENT 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/16_0500 (IPv4), SAE J2534-2/15_0500 (IPv6), SAE J2534-2/BA_0500, and SAE J2534-2/RE_0500 documents.
Standard
Pass-Thru Extended Features - Ethernet NDIS2022-01-17
CURRENT
J2534-2/9_0500_202201
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 ethernet NDIS 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/9_0500 interface shall be compliant to the ethernet NDIS feature only when all the required functionality in this 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 J2534-2/RE_0500 documents.
Standard
Pass-Thru Extended Feature - Analog Input2022-01-17
CURRENT
J2534-2/10_0500_202201
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.
Standard
Pass-Thru Interface - Alternate Platforms for API Version 05.002022-01-17
CURRENT
J2534-5_0500_202201
This SAE Recommended Practice details the changes needed to support the SAE J2534 (API Version 05.00) on operating systems other than 32-bit Microsoft Windows®.
Standard
Pass-Thru Extended Features - CAN with Flexible Data Rate2022-01-17
CURRENT
J2534-2/11_0500_202201
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 CAN with flexible data rate (CAN FD) 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/11_0500 interface shall be compliant to the CAN with flexible data rate (CAN FD) 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.
Standard
Pass-Thru Interface - Alternate Platforms for API Version 04.042022-01-17
CURRENT
J2534-5_0404_202201
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®.
Standard
Pass-Thru Extended Feature - Base Document2022-01-17
CURRENT
J2534-2/BA_0500_202201
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.
Standard
Pass-Thru Extended Feature - Resource Document2022-01-17
CURRENT
J2534-2/RE_0500_202201
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.
Standard
Pass-Thru Extended Feature - UDP2022-01-17
CURRENT
J2534-2/17_0500_202201
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 user datagram protocol (UDP) 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/17_0500 interface shall be compliant to the UDP 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/16_0500 (IPv4), SAE J2534-2/15_0500 (IPv6), SAE J2534-2/BA_0500, and SAE J2534-2/RE_0500 documents.
Standard
Recommended Practice for Pass-Thru Vehicle Programming2022-01-05
CURRENT
J2534-1_0500_202201
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.
Standard
Permanently or Semi-Permanently Installed Diagnostic Communication Devices2021-12-29
CURRENT
J3005_202112
The scope of the document is to define communication best practices in order to minimize problems for the vehicle owner when installing equipment which has a permanently or semi-permanently diagnostic communication device connected to the SAE J1962 connector or hardwired directly to the in-vehicle network.
Standard
OBD-II Communications Anomaly List2021-12-13
CURRENT
J1699/4_202112
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.
Standard
Guidelines for Implementing OEM Diagnostic Applications using J2534 API2021-11-17
WIP
J2534-4
This document will define the P1.6 Diagnostics Message Transport Protocol and its application with SAE J2534.
Standard
NOx Tracking Parameter Accuracy2021-10-19
HISTORICAL
J3349_202110
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.
Standard
Guidelines for Developing and Revising SAE Nomenclature and Definitions2021-07-23
CURRENT
J1115_202107
Standard
SAE J1850 Verification Test Procedures2021-07-16
CURRENT
J1699/1_202107
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.
Standard
J1930 Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms Web Tool Spreadsheet2021-05-25
HISTORICAL
J1930DA_202105
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.
Standard
Vehicle OBD II Compliance Test Cases2021-05-04
WIP
J1699/3
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.”
Standard
Vehicle OBD II Compliance Test Cases2021-04-28
CURRENT
J1699/3_202104
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.”
Standard
E/E Diagnostic Test Modes: OBDonUDS2021-04-22
CURRENT
J1979-2_202104
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.
