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. 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 four principal areas: connector location/access, connector design, connector terminal assignments, and connector electrical interface requirements. b Defines the functional requirements for the test equipment connector. These functional requirements are separated into three principal areas: connector design, connector terminal assignments, and connector electrical interface requirements. 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.

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.

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.

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 provides the mechanism to satisfy requirements included in regulations, and not all capabilities included in this document are required by regulations. This document also 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.

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.

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e., test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.

This SAE Recommended Practice defines the requirements of OBD II Scan Tools, i.e., test equipment that will interface with vehicle modules in support of the OBD II diagnostic requirements. It covers the required capabilities of and conformance criteria for OBD II Scan Tools.

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.

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.

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 (ECU’s) 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. The U.S.

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 (ECU’s) 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. The U.S.

The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in Fiat Chrysler Automobiles (FCA) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU.

The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in Fiat Chrysler Automobiles (FCA) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU.

The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in DaimlerChrysler Corporation (Chrysler Group) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU.

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.