Refine Your Search

Topic

Search Results

Standard

OBD-II Communications Anomaly List

2021-05-07
WIP
J1699/4
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

Vehicle OBD II Compliance Test Cases

2021-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 Cases

2021-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: OBDonUDS

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

J1979-DA, Digital Annex of E/E Diagnostic Test Modes

2021-04-21
CURRENT
J1979DA_202104
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.
Standard

Guidelines for Developing and Revision SAE Nomenclature and Definitions

2021-04-16
WIP
J1115
Historically SAE has been concerned with nomenclature as an integral part of the standards development process. Guidelines for automotive nomenclature were written in 1916, were last revised in 1941, and were included in the SAE Handbook until 1962. The present diversity of groups working on nomenclature in the various ground vehicle committees led to the organization of the Nomenclature Advisory Committee under SAE Automotive Council.
Standard

SAE J1850 Verification Test Procedures

2021-04-16
WIP
J1699/1
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

Worldwide On-Board Diagnostic Requirements Overview

2021-03-03
WIP
J3248
This document focuses on the latest in-force regulation in each region. However, in addition to latest information, the report may include historical information. For example, some regions may require an older version of a regulation than the current in force regulation. Additionally, as regulations are superseded, the previous entry will remain to help understand the change in requirements. The initial focus of the document includes light, medium, and heavy duty on-road vehicles with internal combustion engine and hybrid propulsion systems. The document will include information from all regions where regulatory requirements information is reliably known. Forecasts for future requirements 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.
Standard

Pass-Thru Extended Feature – GM_UART

2021-02-03
WIP
J2534-2/2_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement GM_UART within the 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.
Standard

Pass-Thru Extended Feature – UART Echo Byte

2021-02-03
WIP
J2534-2/3_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement UART Echo Byte within the 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.
Standard

Pass-Thru Extended Feature – Fault-Tolerant CAN

2021-02-03
WIP
J2534-2/8_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement Fault-Tolerant CAN (FT CAN) within the 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.
Standard

Pass-Thru Extended Feature – J1708

2021-02-03
WIP
J2534-2/6_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement J1708 within the 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.
Standard

Pass-Thru Extended Feature – TP2.0

2021-02-03
WIP
J2534-2/7_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement TP2.0 within the 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.
Standard

Pass-Thru Extended Feature – HONDA_DIAGH

2021-02-03
WIP
J2534-2/4_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement HONDA_DIAGH within the 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.
Standard

Pass-Thru Extended Feature – Analog Input

2021-02-03
WIP
J2534-2/10_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement Analog Input within the 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.
Standard

Pass-Thru Extended Feature – Single Wire CAN

2021-02-03
WIP
J2534-2/1_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement Single Wire CAN (SW CAN) within the 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.
Standard

Pass-Thru Extended Feature – J1939

2021-02-03
WIP
J2534-2/5_0500
This SAE Recommended Practice is part of the J2534-2/X_0500 set of documents that extends the J2534-1_0500 API (version 05.00) specification, and defines how to implement J1939 within the 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.
X