Refine Your Search

Topic

Search Results

Standard

Conformance Test Cases

2008-08-04
WIP
J2534/3
The purpose of this document is to define tests necessary to verify that an SAE J2534-1 interface device meets all the requirements specified in SAE J2534-1: Recommended Practice for Pass-Thru Vehicle Programming. Recent Activity Date Type
Standard

Diagnostic Connector

2015-09-11
HISTORICAL
J1962_201509
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
Standard

Diagnostic Connector

2016-07-12
CURRENT
J1962_201607
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
Standard

Diagnostic Connector Equivalent to ISO/DIS 15031-3:December 14, 2001

1992-06-01
HISTORICAL
J1962_199206
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This SAE Recommended Practice: a. Defines the functional requirements for the vehicle electrical/electronic diagnostic connector. These functional requirements are separated into two principal areas: connector location/access and connector design; b. Establishes termainl assignments to conform to either of two categories: Standards or Manufacturer Discretionary. Rationale relative to intent is provided, where applicable, to minimize ambuiguity.
Standard

Diagnostic Connector Equivalent to ISO/DIS 15031-3:December 14, 2001

1993-06-01
HISTORICAL
J1962_199306
This document supersedes SAE J1962 FEB1998, and is technically equivalent to ISO/DIS 15031-3:December 14, 2001. The SAE J1962 diagnostic connector consists of two mating connectors, the vehicle connector and the test equipment connector. 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 assigments; b. Defines the functional requirements for the external test equipment connector. These functional requirementsare separated into two principal areas: connector design and connector terminal assignements. 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.
Standard

Diagnostic Connector Equivalent to ISO/DIS 15031-3:December 14, 2001

1994-06-01
HISTORICAL
J1962_199406
This document supersedes SAE J1962 FEB1998, and is technically equivalent to ISO/DIS 15031-3:December 14, 2001. The SAE J1962 diagnostic connector consists of two mating connectors, the vehicle connector and the test equipment connector. 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 assigments; b. Defines the functional requirements for the external test equipment connector. These functional requirementsare separated into two principal areas: connector design and connector terminal assignements. 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.
Standard

Diagnostic Connector Equivalent to ISO/DIS 15031-3:December 14, 2001

2002-04-30
HISTORICAL
J1962_200204
This document supersedes SAE J1962 FEB1998, and is technically equivalent to ISO/DIS 15031-3:December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a. The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b. The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
Standard

Diagnostic Connector Equivalent to ISO/DIS 15031-3: December 14, 2001

2012-07-26
HISTORICAL
J1962_201207
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
Standard

Diagnostic Connector Equivalent to Iso/Dis 15031-3:December 14, 2001

1995-01-01
HISTORICAL
J1962_199501
This document supersedes SAE J1962 FEB1998, and is technically equivalent to ISO/DIS 15031-3:December 14, 2001. The SAE J1962 diagnostic connector consists of two mating connectors, the vehicle connector and the test equipment connector. 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 assigments; b. Defines the functional requirements for the external test equipment connector. These functional requirementsare separated into two principal areas: connector design and connector terminal assignements. 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.
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 Equivalent to ISO/DIS 15031-6:April 30, 2002

2002-04-30
HISTORICAL
J2012_200204
This SAE Recommended Practice supersedes SAE J2012 MAR1999, and is technically equivalent to ISO/DIS 15031-6:April 30, 2002. 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. Diagnostic Trouble Code format. A standardized set of Diagnostic Trouble Codes and descriptions a. Differences from ISO Document b. There are no technical differences between this document and ISO/DIS 15031-6:April 30, 2002.
Standard

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

2018-12-19
CURRENT
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

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

1991-09-16
HISTORICAL
J2186_199109
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 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.
Standard

E/E Diagnostic Test Modes

2017-05-19
WIP
J1979-2
SAE J1979/ISO 15031-5 set includes the communication between the vehicle's OBD systems and test equipment implemented across vehicles within the scope of the legislated emissions-related OBD.
Standard

E/E Diagnostic Test Modes

2017-05-18
WIP
J1979
SAE J1979/ISO 15031-5 set includes the communication between the vehicle's OBD systems and test equipment implemented across vehicles within the scope of the legislated emissions-related OBD.
Standard

E/E Diagnostic Test Modes

1994-06-01
HISTORICAL
J1979_199406
SAE J1979 / ISO 15031-5 set includes the communication between the vehicle's OBD systems and test equipment implemented across vehicles within the scope of the legislated emissions-related OBD.
X