Search Results

This document is applicable to all light duty gasoline and diesel vehicles (LDV), light duty gasoline and diesel trucks (LDT), and heavy duty gasoline vehicles (HDGV). Specific applications of this document include service and repair manuals, training manuals, repair data bases, under-hood emission labels, and emission certification applications. Even though the use and appropriate updating of this document and its companion documents is strongly encouraged, nothing in these documents should be construed as prohibiting the introduction of a term or acronym not covered by these documents.

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 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 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).

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).

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

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.

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 is applicable to all light-duty gasoline and diesel passenger vehicles and trucks, and to heavy-duty gasoline vehicles. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair data bases, underhood emission labels, and emission certification applications. This document focuses on diagnostic terms applicable to electrical/electronic systems, and therefore also contains related mechanical terms, definitions, abbreviations, and acronyms. Even though the use and appropriate updating of this document is strongly encouraged, nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document.

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 is applicable to all light-duty gasoline and diesel passenger vehicles and trucks, and to heavy-duty gasoline vehicles. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair data bases, underhood emission labels, and emission certification applications. This document focuses on diagnostic terms applicable to electrical/electronic systems, and therefore also contains related mechanical terms, definitions, abbreviations, and acronyms. Even though the use and appropriate updating of this document is strongly encouraged, nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.

The intent of the specification is to present a functional set of requirements which define the user and hardware interfaces while providing sufficient capability to meet the misfire patterns for compliance demonstration and engineering development. Throughout this requirement, any reference to “ignition or injector control signal” is used interchangeably to infer that the effected spark ignition engine’s ignition control signal or the compression ignition engine’s injector control signal is interrupted, timing phased, or directly passed by the misfire generator. For spark ignition engines, the misfire generator behaves as a spark-defeat device which induces misfires by inhibiting normal ignition coil discharge. It does so by monitoring the vehicle’s ignition timing signals and suspends ignition coil saturation for selected cylinder firing events. The misfire generator will thereby induce engine misfire in spark ignited gasoline internal combustion engines; including rotary engines.

The intent of the specification is to present a functional set of requirements which define the user and hardware interfaces while providing sufficient capability to meet the misfire patterns for compliance demonstration and engineering development. The misfire generator behaves as a spark-defeat device which induces misfires by inhibiting normal ignition coil discharge. It does so by monitoring the vehicle’s ignition timing signals and suspends ignition coil saturation for selected cylinder firing events. The misfire generator will thereby induce engine misfire in spark ignited gasoline internal combustion engines; including rotary engines. This requirement assumes that the user has a fundamental understanding of misfire diagnostics as well as ignition controls. This requirement is not intended to be an introductory misfire guideline or interpretation of regulatory requirements.