Standard
Vehicle Electronic Identification
2002-07-23
CURRENT
J1724_200207
Search Results
Standard
SAE J2450 Supplemental Training Document
2008-05-13
HISTORICAL
J2450/1_200805
This supplement, which is a living document, is meant to provide both clients and translation suppliers with some suggestions for integrating SAE J2450 into their business practices. It is intended for the use of clients, trainers who wish to develop new evaluators, and those who wish to self-train.
Standard
Enhanced E/E Diagnostic Test Modes
2008-10-02
CURRENT
J2190_200810
This SAE Recommended Practice describes the implementation of Enhanced Diagnostic Test Modes, which are intended to supplement the legislated Diagnostic Test Modes defined in SAE J1979. Modes are defined for access to emission related test data beyond what is included in SAE J1979, and for non-emission related data. This document describes the data byte values for diagnostic messages transmitted between diagnostic test equipment, either on-vehicle or off-vehicle, and vehicle electronic control modules. No distinction is made between test modes for emission related and non-emission related diagnostics. These messages can be used with a diagnostic serial data link such as described in SAE J1850 or ISO 9141-2. For each test mode, this document includes a functional description of the test mode, request and report message data byte content, and an example if useful for clarification.
Standard
UNIVERSAL INTERFACE FOR OBD II SCAN
1993-06-01
HISTORICAL
J2201_199306
SAE J1978 defines the requirements of the OBD II scan tool. SAE J2201 defines the minimum requirements of the vehicle communications interface for the SAE J1978 OBD II scan tool. This interface connects the SAE J1962 test equipment connector to the hardware/software of the SAE J1978 OBD II scan tool that will use this interface to communicate with vehicles for the purpose of accessing required OBD II functions. Included in this SAE Recommended Practice are several definitions relating to the interface, and interface functionality evaluation. Appendix A - Examples include several example interface circuit implementations, which are believed to meet the requirements of this document and of SAE J1978. These examples are NOT requirements of this document. They are provided to assist circuit designers in developing interface circuits. Appendix B - Supporting Documents includes a list of supporting documents for the examples shown in Appendix A.
Standard
EXPANDED DIAGNOSTIC PROTOCOL FOR OBD II SCAN TOOLS
1995-12-01
HISTORICAL
J2205_199512
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.
Standard
EXPANDED DIAGNOSTIC PROTOCOL FOR OBD II SCAN TOOLS
1994-06-01
HISTORICAL
J2205_199406
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.
Standard
E/E Data Link Security
2019-07-12
CURRENT
J2186_201907
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Standard
E/E Data Link Security
2005-06-27
HISTORICAL
J2186_200506
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Standard
E/E DATA LINK SECURITY
1996-10-01
HISTORICAL
J2186_199610
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Standard
E/E DATA LINK SECURITY
1991-09-16
HISTORICAL
J2186_199109
This SAE Recommended Practice establishes a uniform practice for protecting vehicle modules from "unauthorized" intrusion through a vehicle diagnostic data communication link. The security system represents a recommendation for motor vehicle manufacturers and provides flexibility for them to tailor their system to their specific needs. The vehicle modules addressed are those that are capable of having solid-state memory contents altered external to the electronic module through a diagnostic data communication link. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document is intended to meet the "tampering protection" provisions of California Air Resources Board OBD II regulations and does not imply that other security measures are not required nor possible.
Standard
SAE J1850 Verification Test Procedures
2006-06-05
HISTORICAL
J1699/1_200606
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
Test Cases for OBD-II Scan Tools and I/M Test Equipment
2017-09-13
CURRENT
J1699/2_201709
To define test cases for the OBD-II interface on external test equipment (such as an OBD-II Scan Tool, Inspection/Maintenance Tester, etc.) which can be used to verify compliance with the applicable standards such as SAE J1978 and SAE J1979 for Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II).
Standard
Pass-Thru Extended Feature - SAE J1708
2022-01-17
CURRENT
J2534-2/6_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 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.
Standard
Worldwide On-Board Diagnostic Requirements Overview
2024-02-28
CURRENT
J3248_202402
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.
Standard
Permanently or Semi-Permanently Installed Diagnostic Communication Devices
2014-12-03
HISTORICAL
J3005_201412
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
Recommended Practice for Pass-Thru Vehicle Programming
2015-10-28
CURRENT
J2534/1_201510
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
Recommended Practice for Pass-Thru Vehicle Programming
2004-12-01
HISTORICAL
J2534/1_200412
This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECUs) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. U.S.
Standard
Pass-Thru Extended Feature - Analog Input
2022-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
TP1.6 Vehicle DIAGNOSTIC Protocol
2015-01-15
HISTORICAL
J3054_201501
This Technical 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 Technical 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.
Standard
DIAGNOSTIC CONNECTOR
1994-06-01
HISTORICAL
J1962_199406
The SAE J1962 diagnostic connector consists of two mating connectors, the vehicle connector (see Figure 1) and the test equipment connector (see Figure 2). This document: a Defines the functional requirements for the vehicle connector. These functional requirements are separated into three principal areas: connector location/access, connector design, and connector terminal assignments. b Defines the functional requirements for the test equipment connector. These functional requirements are separated into two principal areas: connector design and connector terminal assignments. The scope of this document does not include the needs of long-term retention, such as in-flight recorder type applications. To ensure long-term retention, additional steps outside of the scope of this document must be taken.
