Search Results

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.

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.

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.

This SAE Recommended Practice is applicable to all light duty and medium duty passenger vehicles and trucks with feedback fuel control system. Specific applications of this document include diagnostic, service and repair manuals, repair data bases, and off-board readout devices. This document focuses on a diagnostic code format and code messages for automotive electronic control systems. The use and appropriate updating of this document is strongly encouraged; however, this document does not prohibit the use of additional codes for additional diagnostics.

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.

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.

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.

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.

This document supersedes SAE J2012 APR2002, and is technically equivalent to ISO 15031-6:2005 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. This document includes: a Diagnostic Trouble Code format. b A standardized set of Diagnostic Trouble Codes and descriptions c A standardized set of Diagnostic Trouble Codes subtypes known as Failure Types

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. This document includes: a Diagnostic Trouble Code format b A standardized set of Diagnostic Trouble Codes and descriptions

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.

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.

This document supersedes SAE J1979 Apr 2002, and is technically equivalent to ISO 15031-5:2006, with the addition of new capabilities required by revised regulations from the California Air Resources Board (see Section 1.2). This document is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future.

This document supersedes SAE J1979 May 2007, and is technically equivalent to ISO 15031-5 2010, with the addition of new capabilities required by revised regulations from the California Air Resources Board and revised regulations from the European Commission. This document is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future.

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. To achieve this, it 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.

This document supersedes SAE J1979 SEP1997, and is technically equivalent to ISO/DIS 15031-5:April 30, 2002. This SAE Recommended Practice is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future. This document specifies: a Message formats for request and response messages, b Timing requirements between request messages from external test equipment and response messages from vehicles, and between those messages and subsequent request messages, c Behavior of both the vehicle and external test equipment if data is not available, d A set of diagnostic services, with corresponding content of request and response messages, to satisfy OBD regulations, This document includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types.

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.

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.

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.

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.