Refine Your Search

Topic

Search Results

Standard

Recommended Practice for Pass-Thru Vehicle Programming

2002-02-28
CURRENT
J2534_200202
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.
Standard

Translation Quality Metric

2005-08-22
HISTORICAL
J2450_200508
This SAE Standard is applicable to translations of automotive service information into any target language. The metric may be applied regardless of the source language or the method of translation (i.e., human translation, computer assisted translation or machine translation). Note that the current version of the metric does not measure errors in style, making it unsuitable for evaluations of material in which style is important (e.g., owner's manuals or marketing literature). The metric can be expanded to accommodate style and other requirements of particular new media.
Standard

Translation Quality Metric

2016-08-17
CURRENT
J2450_201608
This SAE Standard is applicable to translations of automotive service information into any target language. The metric may be applied regardless of the source language or the method of translation (i.e., human translation, computer assisted translation or machine translation). Note that the current version of the metric does not measure errors in style, making it unsuitable for evaluations of material in which style is important (e.g., owner's manuals or marketing literature). The metric can be expanded to accommodate style and other requirements of particular new media.
Standard

Translation Quality Metric

2001-12-19
HISTORICAL
J2450_200112
This SAE Recommended Practice is applicable to translations of automotive service information into any target language. The metric may be applied regardless of the source language or the method of translation (i.e., human translation, computer assisted translation or machine translation). Note that the current version of the metric does not measure errors in style, making it unsuitable for evaluations of material in which style is important (e.g., owner's manuals or marketing literature). The metric can be expanded to accommodate style and other requirements of particular new media.
Standard

TP1.6 Vehicle DIAGNOSTIC Protocol

2015-01-15
CURRENT
J3054_201501
This Technical Information Report defines the diagnostic communication protocol TP1.6. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP1.6 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface. This Technical Information Report describes how a tester can be connected to a vehicle to perform diagnostics using the TP1.6 protocol. Details regarding ECU to ECU communication have been left out.
Standard

E/E Diagnostic Data Communications

2001-06-21
CURRENT
J2054_200106
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 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

Off-Board Diagnostic Message Formats

2001-06-21
CURRENT
J2037_200106
The utilities defined for J2037 are designed to facilitate manufacturing and service diagnosis requirements. Definition of the capability includes definition of standard messages and the dialogue necessary to provide the capability. The standard messages will be distinguished by the contents of the first data byte which specifies the diagnostic operation. Note that some vehicle applications will not require the implementation of all the defined diagnostic capabilities, and consequently, these applications will not support all message modes.
Standard

Off-Board Diagnostic Message Formats

1990-11-01
HISTORICAL
J2037_199011
This SAE Information Report is an example of how J1850 might be used to implement diagnostics in a vehicle. The utilities defined for J2037 are designed to facilitate manufacturing and service diagnosis requirements. Definition of the capability includes definition of standard messages and the dialogue necessary to provide the capability. the standard messages will be distinguished by the contents of the first data byte which specifies the diagnostic operation. Note that some vehicle applications will not require the implementation of all the defined diagnostic capabilities, and consequently, these applications will not support all message modes.
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

Expanded Diagnostic Protocol for OBD II Scan Tools

1999-07-22
CURRENT
J2205_199907
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

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

Universal Interface for Obd Ii Scan

1993-06-01
HISTORICAL
J2201_199306
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 requirement connector to the hardware/software of the SAE J1978 OBD II scan tool that will use this interface to communicate with vehicles for thr pupose of accessing required OBD II functions. Included in this SAE Recommended Practice are several definitions relating to the interface, and interafce functionality evaluation. Appendix A—Examples include several example interface circuit implementation, 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. Appenidx B—Supporting Documents includes a list of supporting documents for the examples shown in Appendix A.
Standard

Universal Interface for OBD II Scan

1999-07-20
CURRENT
J2201_199907
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 requirement connector to the hardware/software of the SAE J1978 OBD II scan tool that will use this interface to communicate with vehicles for thr pupose of accessing required OBD II functions. Included in this SAE Recommended Practice are several definitions relating to the interface, and interafce functionality evaluation. Appendix A—Examples include several example interface circuit implementation, 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. Appenidx B—Supporting Documents includes a list of supporting documents for the examples shown in Appendix A.
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

Serial Data Communication Interface

2015-01-15
CURRENT
J2610_201501
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.
X