Search Results

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 API version 04.04 of the SAE J2534-1 specification. It is not required for an interface to be fully compliant with API version 04.04 of the 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.

The scope of the document is to define the cyber-security best practices to reduce interference with normal vehicle operation, or to minimize risk as to unauthorized access of the vehicle's control, diagnostic, or data storage system; access by equipment (i.e., permanently or semi-permanently installed diagnostic communication device, also known as dongle, etc.) which is either permanently or semi-permanently connected to the vehicle's OBD diagnostic connector, either SAE J1939-13, SAE J1962, or other future protocol; or hardwired directly to the in-vehicle network. This document only specifies requirements and guidance for those diagnostic communication devices and not for the vehicle. Refer to SAE J3138 for requirements for the vehicle side.

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.

The main purpose is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979-2: E/E Diagnostic Test Modes

This document is intended to satisfy the requirements of an OBD scan tool as required by U.S. On-Board Diagnostic (OBD) regulations. The document specifies: a. A means of establishing communications between an OBD-equipped vehicle and external test equipment, b. A set of diagnostic services to be provided by the external test equipment in order to exercise the services defined in SAE J1979-2, c. Conformance criteria for the external test equipment.

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 establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. 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 does not imply that other security measures are not required nor possible.

This Technical Information Report defines the General Motors UART Serial Data Communications Bus, commonly referred to as GM UART. 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.

This Technical Information Report defines the diagnostic communication protocol Keyword Protocol 1281 (KWP1281). 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.

This Technical Information Report defines the diagnostic communication protocol TP2.0. 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.

On-Board Diagnostic (OBD) regulations require passenger cars, and light and medium duty trucks, to support communication of a minimum set of diagnostic information to off-board “generic” test equipment. This document specifies the diagnostic data which may be required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to motor vehicle emission-related data. SAE J1979 was originally developed to meet U.S. OBD requirements for 1996 and later model year vehicles. ISO 15031 5 was based on SAE J1979 and was intended to combine the U.S. requirements with European OBD requirements for 2000 and later model year vehicles.

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 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 CAN communication device connected to the SAE J1962 connector, or hardwired directly to the in-vehicle network.

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.

The J2012 Digital Annex of Diagnostic Trouble Code Definitions Spreadsheet provides DTC information in an excel format for use in your organization's work processes. The column headings include the same information as contained in the J2012 standard. Information in the excel spreadsheet will be updated several times annually, and the spreadsheet includes a column heading denoting which DTC have been updated in the current version.

This Technical Information Report defines the proprietary diagnostic communication protocol for ABS or VSA ECU (Electronic Control Unit) implemented on some Honda vehicles. This protocol does not apply to all Honda vehicles. 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.

To define test cases for the OBD-II interface on external test equipment (such as an OBD-II Scan Tool, Inspection/Maintenance Tester, etc.) which can be used to verify compliance with the applicable standards such as SAE J1978 and SAE J1979 for Passenger Cars, Light-Duty Trucks, and Medium-Duty Vehicles and Engines (OBD II).

The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.

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.