Refine Your Search

Date

Date

Topic

Topic

Search Results

Viewing 41 to 60 of 82
<< First< Previous12345Next >Last >>
Sort by relevance
Standard

TP1.6 Vehicle Diagnostic Protocol
2022-05-02
CURRENT
J3054_202205
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 SAE Information Report describes how a tester can be connected to a vehicle to perform diagnostics using the TP1.6 protocol.
Standard

Optional Pass-Thru Features
2019-01-16
HISTORICAL
J2534/2_201901
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year, as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 specification. It is not required for an interface to be fully compliant with SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.
Standard

Optional Pass-Thru Features
2010-10-26
HISTORICAL
J2534/2_201010
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 specification. It is not required for an interface to be fully compliant with SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.
Standard

Optional Pass-Thru Features
2006-03-27
HISTORICAL
J2534/2_200603
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to an SAE J2534-1 interface. Together, these extensions provide the framework for a common interface to protect the software investment of the Vehicle OEMs and Scan Tool manufacturers. Only the optional features will be described by this document. Unless otherwise noted it is expected that these features are added to a fully compliant interface adhering to the December 2004 publication of SAE J2534-1.
Standard

General Motors UART Serial Data Communications
2019-05-20
CURRENT
J2740_201905
This document should be used in conjunction with SAE J2534-2 in order to enhance an SAE J2534 interface to also provide the capability to program ECUs with GM UART. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECUs) as required by U.S. regulations, and SAE J2534-2 defines enhanced functionality required to program additional ECUs not mandated by current U.S. regulations. ...The purpose of this document is to specify the requirements necessary to implement GM UART in an enhanced SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
Standard

Vehicle OBD II Compliance Test Cases
2021-04-28
CURRENT
J1699/3_202104
Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface.
Standard

Pass-Thru Extended Feature - Base Document
2022-01-17
CURRENT
J2534-2/BA_0500_202201
SAE J2534-1_0500 defines the pass-thru interface requirements for the reprogramming of emission related control modules. The SAE J2534-2/X_0500 document set adds extensions to the SAE J2534-1_0500 API (version 05.00) specification so that the API can be used for features not covered in the SAE J2534-1_0500 specification. Together, these features provide a comprehensive framework for a common standard, to protect the software investment of the vehicle OEMs and scan tool manufacturers. There is no required for an SAE J2534-2/X_0500 pass-thru interface to be fully compliant with SAE J2534-1_0500. SAE J2534-2/X_0500 interfaces can implement some or all of the features specified in the SAE J2534-2/X_0500 document set. This document must be used in conjunction with the SAE J2534-2/RE_0500 document.
Standard

TP2.0 Vehicle Diagnostic Protocol
2008-02-01
HISTORICAL
J2819_200802
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 TP2.0 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.
Standard

Honda Diagnostic Serial Data Link Protocol—ABS/VSA System
2007-10-11
HISTORICAL
J2809_200710
This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an enhanced SAE J2534 interface. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface. ...The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface.
Standard

Keyword Protocol 1281
2008-01-23
HISTORICAL
J2818_200801
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 ECUs, in which a KWP1281 proprietary diagnostic communication protocol is implemented. ...The purpose of this document is to specify the KWP1281 protocol in enough detail to support the requirements necessary to implement the communication protocol in an SAE J2534 interface device.
Standard

General Motors UART Serial Data Communications
2005-12-19
HISTORICAL
J2740_200512
This document should be used in conjunction with SAE J2534-2 in order to enhance an SAE J2534 interface to also provide the capability to program ECUs with GM UART. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECUs) as required by U.S. regulations, and SAE J2534-2 defines enhanced functionality required to program additional ECUs not mandated by current U.S. regulations. ...The purpose of this document is to specify the requirements necessary to implement GM UART in an enhanced SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
Standard

TP1.6 Vehicle DIAGNOSTIC Protocol
2015-01-15
HISTORICAL
J3054_201501
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.
Journal Article

Merge Ahead: Integrating Heavy Duty Vehicle Networks with Wide Area Network Services
2010-10-05
2010-01-2053
These standard protocols include SAE J1708 , J1587 , J1939 , J2534 , CAN (ISO 11898), and ATA/TMC RP1210. In order to illustrate how these standard protocols work, this paper provides a detailed overview of SAE J1939 including the J1939 -7 and J1939 -73 standards, as well as Heavy-Duty On Board Diagnostics (HD OB) standard Messaging and Diagnostics that use J1939 .
Standard

Vehicle OBD II Compliance Test Cases
2017-07-21
HISTORICAL
J1699/3_201707
Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.
Standard

Vehicle OBD II Compliance Test Cases
2015-07-28
HISTORICAL
J1699/3_201507
Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.
Standard

Vehicle OBD II Compliance Test Cases
2012-05-11
HISTORICAL
J1699/3_201205
Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.
Standard

Vehicle OBD II Compliance Test Cases
2009-12-03
HISTORICAL
J1699/3_200912
Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.
<< First< Previous12345Next >Last >>
X