Refine Your Search

Date

Date

Topic

Topic

Computer software and hardware Identification Vehicle E E System Diagnostic Standards Committee

Search Results

Viewing 1 to 20 of 42
123Next >Last >>
Sort by title
Standard

SAE J2450 Supplemental Training Document
2019-10-31
CURRENT
J2450/1_201910
This supplement, which is a living document, is meant to provide both clients and translation suppliers with some suggestions for integrating SAE J2450 into their business practices. It is intended for the use of clients, trainers who wish to develop new evaluators, and those who wish to self-train.
Standard

SAE J2450 Supplemental Training Document
2008-05-13
HISTORICAL
J2450/1_200805
This supplement, which is a living document, is meant to provide both clients and translation suppliers with some suggestions for integrating SAE J2450 into their business practices. It is intended for the use of clients, trainers who wish to develop new evaluators, and those who wish to self-train.
Standard

Recommended Practice for Pass-Thru Vehicle Programming
2022-07-22
WIP
J2534-1_5
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.
Standard

Recommended Practice for Pass-Thru Vehicle Programming
2022-01-05
CURRENT
J2534-1_0500_202201
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.
Standard

Recommended Practice for Pass-Thru Vehicle Programming
2015-10-28
CURRENT
J2534/1_201510
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.
Standard

Recommended Practice for Pass-Thru Vehicle Programming
2004-12-01
HISTORICAL
J2534/1_200412
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.
Standard

Recommended Practice for Pass-Thru Vehicle Programming
2002-02-28
HISTORICAL
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

Recommended Practice for Pass-Thru Vehicle Programming
2019-07-29
CURRENT
J2534_201907
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

Permanently or Semi-Permanently Installed Diagnostic Communication Devices
2014-12-03
HISTORICAL
J3005_201412
The scope of the document is to define communication best practices in order to minimize problems for the vehicle owner when installing equipment which has a permanently or semi-permanently diagnostic communication device connected to the SAE J1962 connector or hardwired directly to the in-vehicle network.
Standard

Pass-Thru Extended Features - Ethernet NDIS
2022-01-17
CURRENT
J2534-2/9_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement ethernet NDIS within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/9_0500 interface shall be compliant to the ethernet NDIS feature only when all the required functionality in this Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Features - CAN with Flexible Data Rate
2022-01-17
CURRENT
J2534-2/11_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement CAN with flexible data rate (CAN FD) within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/11_0500 interface shall be compliant to the CAN with flexible data rate (CAN FD) feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Feature - UDP
2022-01-17
CURRENT
J2534-2/17_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement user datagram protocol (UDP) within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/17_0500 interface shall be compliant to the UDP feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/13_0500 (ethernet), SAE J2534-2/16_0500 (IPv4), SAE J2534-2/15_0500 (IPv6), SAE J2534-2/BA_0500, and SAE J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Feature - UART Echo Byte
2022-01-17
CURRENT
J2534-2/3_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement UART Echo Byte within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/3_0500 interface shall be compliant to the UART Echo Byte feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Feature - TP2.0
2022-01-17
CURRENT
J2534-2/7_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement TP2.0 within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/7_0500 interface shall be compliant to the TP2.0 feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Feature - TCP CLIENT
2022-01-17
CURRENT
J2534-2/18_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification and defines how to implement transmission control protocol (TCP) within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/18_0500 interface shall be compliant to the TCP CLIENT feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/13_0500 (ethernet), SAE J2534-2/16_0500 (IPv4), SAE J2534-2/15_0500 (IPv6), SAE J2534-2/BA_0500, and SAE J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Feature - Single Wire CAN
2022-01-17
CURRENT
J2534-2/1_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement single wire CAN (SW CAN) within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/1_0500 interface shall be compliant to the single wire CAN feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents.
Standard

Pass-Thru Extended Feature - SAE J1939
2022-01-17
CURRENT
J2534-2/5_0500_202201
This SAE Recommended Practice is part of the SAE J2534-2/X_0500 set of documents that extends the SAE J2534-1_0500 API (version 05.00) specification, and defines how to implement SAE J1939 within the SAE J2534 API framework. This document details only the changes from SAE J2534-1_0500 and items not specifically detailed in this document are assumed to have not changed. An SAE J2534-2/5_0500 interface shall be compliant to the SAE J1939 feature only when all the required functionality in this SAE Recommended Practice is implemented. Any functionality not required for compliance will be specifically marked as “optional” in this document. This document must be used in conjunction with the SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents.
123Next >Last >>
X