Search Results

Standard

DIAGNOSTIC CONNECTOR

1993-06-01

HISTORICAL

J1962_199306

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.

Standard

DIAGNOSTIC CONNECTOR

1992-06-01

HISTORICAL

J1962_199206

This SAE Recommended Practice: a Defines the functional requirements for a vehicle electrical/electronic diagnostic connector. These functional requirements are separated into two principal areas: connector location/access and connector design. b Establishes terminal assignments to conform to either of two categories: Standard or Manufacturer Discretionary. Rationale relative to intent is provided, where applicable, to minimize ambiguity.

Standard

Diagnostic Trouble Code Definitions

2016-12-13

CURRENT

J2012_201612

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. This document includes: a Diagnostic Trouble Code format. b A description of the standardized set of Diagnostic Trouble Codes and descriptions contained in SAE J2012DA. The two most significant bytes of a DTC may be decoded according to two different lists; DTC Format Identifier 0x00 and 0x04. c A description of the standardized set of Diagnostic Trouble Codes subtypes known as Failure Types contained in SAE J2012-DA (applies only when three byte DTCs are used).

Standard

Diagnostic Trouble Code Definitions

2013-03-07

HISTORICAL

J2012_201303

This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in Section 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. This document includes: a Diagnostic Trouble Code format. b A description of the standardized set of Diagnostic Trouble Codes and descriptions contained in SAE J2012-DA. The two most significant bytes of a DTC may be decoded according to two different lists; DTC Format Identifier 0x00 and 0x04. c A description of the standardized set of Diagnostic Trouble Codes subtypes known as Failure Types contained in SAE J2012-DA (applies only when three byte DTCs are used).

Standard

Diagnostic Trouble Code Definitions

2022-07-15

WIP

J2012

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.

Standard

Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

2024-03-06

CURRENT

J2012DA_202403

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.

Standard

Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

2018-12-19

HISTORICAL

J2012DA_201812

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 DTC have been updated in the current version.

Standard

Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

2013-01-31

HISTORICAL

J2012DA_012013

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. There is also a column heading denoting which DTC have been updated in the current version.

Standard

Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

2016-12-13

HISTORICAL

J2012DA_201612

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 DTC have been updated in the current version.

Standard

Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

2010-08-16

HISTORICAL

J2012DA_072010

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 DTC have been updated in the current version.

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

E/E DIAGNOSTIC DATA COMMUNICATIONS

1990-11-01

HISTORICAL

J2054_199011

This SAE Information Report describes the diagnostic data communications required for implementation of a set of diagnostic test modes for all electronic systems on the vehicle's serial data link. These test modes can be used by off-board test equipment for both service and assembly plant testing. The goal of this document is to provide standard methods to perform common functions for all electronic systems. This standard set of procedures will aid development, production, and field service of those systems. Use of the standard data communications in this specification will potentially result in the following benefits: This specification includes:

Standard

E/E DIAGNOSTIC TEST MODES

1994-06-01

HISTORICAL

J1979_199406

This SAE Recommended Practice defines diagnostic test modes, and request and response messages, necessary to be supported by vehicle manufacturers and test tools to meet the requirements of the California OBD II and Federal OBD regulations, which pertain to vehicle emission-related data only. These messages are intended to be used by any service tool capable of performing the mandated diagnostics. Diagnostic Test Modes included in this document are: For each test mode, this specification includes: a Functional descriptions of test mode b Request and response message formats For some of the more complex test modes, an example of messages and an explanation of the interpretation of those messages is included.

Standard

E/E DIAGNOSTIC TEST MODES

1996-07-01

HISTORICAL

J1979_199607

This SAE Recommended Practice defines diagnostic test modes, and request and response messages, necessary to be supported by vehicle manufacturers and test tools to meet the requirements of the California OBD II and Federal OBD regulations, which pertain to vehicle emission-related data only. These messages are intended to be used by any service tool capable of performing the mandated diagnostics. In addition, capabilities are defined that are intended to meet other Federal and State regulations pertaining to related issues such as Inspection and Maintenance (I/M) and service information availability. This document is not considered a final authority for interpretation of the regulations, so the reader should determine the applicability of the capabilities defined in this document for their specific need.

Standard

E/E DIAGNOSTIC TEST MODES

1991-12-01

HISTORICAL

J1979_199112

This SAE Recommended Practice defines diagnostic test modes, and request and response messages, necessary to be supported by vehicle manufacturers and test tools to meet the requirements of the California OBD II regulations, which pertain to vehicle emission-related data only. These messages are intended to be used by any service tool capable of performing California OBD II mandated diagnostics. Diagnostic Test Modes included in this document are: For each test mode, this document includes: a Functional descriptions of test mode b Request and response message formats

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

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.