Refine Your Search

Search Results

Standard

Tracking Parameter Accuracy Requirement Standardization

2019-11-26
WIP
J3349
This standard will define test procedures and calculations to determine accuracy of tracking parameters, including: - NOx tracking accuracy - Fuel consumption accuracy - EI-AECD NOx control tracking (timer accuracy)
Standard

Vehicle OBD II Compliance Test Cases for J1979-2

2019-08-23
WIP
J1699-5
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
Standard

J1979-2 Compliant OBDII Scan Tool

2019-08-23
WIP
J1978-2
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.
Standard

E/E Data Link Security

2019-07-12
CURRENT
J2186_201907
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.
Standard

TP2.0 Vehicle Diagnostic Protocol

2019-05-20
CURRENT
J2819_201905
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.
Standard

Optional Pass-Thru Features

2019-02-14
WIP
J2534/2

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

Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions

2018-12-19
CURRENT
J2012DA_201812
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.
Standard

Recommended Practice for Pass-Thru Vehicle Programming

2018-06-14
WIP
J2534/1
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

Vehicle OBD II Compliance Test Cases

2017-11-12
WIP
J1699/3
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.
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

J1979-DA, Digital Annex of E/E Diagnostic Test Modes

2017-02-16
HISTORICAL
J1979DA_201702
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.
Standard

Guidelines for Developing and Revision SAE Nomenclature and Definitions

2015-04-19
WIP
J1115
Historically SAE has been concerned with nomenclature as an integral part of the standards development process. Guidelines for automotive nomenclature were written in 1916, were last revised in 1941, and were included in the SAE Handbook until 1962. The present diversity of groups working on nomenclature in the various ground vehicle committees led to the organization of the Nomenclature Advisory Committee under SAE Automotive Council.
Standard

J1979-DA, Digital Annex of E/E Diagnostic Test Modes

2014-06-10
HISTORICAL
J1979DA_201406
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.
Standard

OBD II Scan Tool -- Equivalent to ISO/DIS 15031-4:December 14, 2001

2011-02-08
WIP
J1978
This SAE Recommended Practice supersedes SAE J1978 FEB1998, and is technically equivalent to ISO/DIS 15031-4:December 14, 2001. 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, c. Conformance criteria for the external test equipment. Differences from ISO Document The ISO 15031-4 document is intended to satisfy the requirements of OBD requirements in countries other than the U.S., and includes functionality not required or not allowed in the U.S. Notable exceptions are: a. Proposed U.S. OBD regulations will allow ISO 15765-4 as an allowable OBD serial data link at 500 kbps only.
Standard

SAE J1850 Verification Test Procedures

2010-10-04
WIP
J1699/1
This SAE Recommended Practice recommends test methods, test procedures, and specific test parameters to help verify that vehicles and test tools can communicate using the SAE J1850. This document only verifies the portion of SAE J1850 that is used for OBD-II communications. The term "test tool" is synonymous with OBD-II Scan tool.
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
X