Criteria

Text:
Display:

Results

Viewing 1 to 30 of 94
2015-04-19
WIP Standard
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.
2015-04-19
WIP Standard
J2740
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 fully implement GM UART in an SAE J2534 interface. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECU) 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 aftermarket SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
2015-02-12
WIP Standard
J1979
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.
2015-02-10
WIP Standard
J1962
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a. The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b. The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
2015-01-15
Standard
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.
2015-01-15
Standard
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.
2014-12-03
Standard
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.
2014-08-11
Standard
J1979_201408
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.
2014-06-26
WIP Standard
J1979DA
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.
2014-06-10
Standard
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.
2014-04-09
Standard
J1699/4_201404
To define a list of anomalies related to OBD Communications. Misinterpretations of various OBD Communications Standards and Recommended Practices have resulted in OBD “no-communications” situations in the field. This Information Report identifies the most prevalent of these.
2014-03-04
Standard
J1930DA_201403
This Digital Annex contains all of the information previously found within the SAE J1930 tables, including diagnostic terms applicable to electrical/electronic systems and related mechanical terms, definitions, abbreviations, and acronyms.
2013-08-07
WIP Standard
J2534/4
This document will define the P1.6 Diagnostics Message Transport Protocol and its application with SAE J2534.
2013-03-07
Standard
J2012_201303
This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in Section 1.2. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. SAE J2012 may also be used for decoding of enhanced diagnostic DTCs and specifies the ranges reserved for vehicle manufacturer specific usage. This document includes: a. Diagnostic Trouble Code format. b. A description of the standardized set of Diagnostic Trouble Codes and descriptions contained in SAE J2012-DA. The two most significant bytes of a DTC may be decoded according to two different lists; DTC Format Identifier 0x00 and 0x04. c. A description of the standardized set of Diagnostic Trouble Codes subtypes known as Failure Types contained in SAE J2012-DA (applies only when three byte DTCs are used).
2013-01-31
Standard
J2012DA_012013
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. There is also a column heading denoting which DTC have been updated in the current version.
2012-07-26
Standard
J1962_201207
This document supersedes SAE J1962 200204, and is technically equivalent to ISO/DIS 15031-3: December 14, 2001. This document is intended to satisfy the requirements of an OBD connector as required by U.S. On-Board Diagnostic (OBD) regulations. The diagnostic connection specified in this document consists of two mating connectors, the vehicle connector and the external test equipment connector. This document specifies: a. The functional requirements for the vehicle connector. These functional requirements are separated into four principal areas: connector location/access, connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits, b. The functional requirements for the external test equipment connector. These functional requirements are separated into three principal areas: connector design, connector contact allocation, and electrical requirements for connector and related electrical circuits.
2012-07-11
WIP Standard
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.
2012-05-11
Standard
J1699/3_201205
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.
2012-02-23
Standard
J1979_201202
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.
2011-10-10
Standard
J1979DA_201110
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.
2011-09-09
WIP Standard
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.
2011-06-30
Standard
J2901_201106
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. 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. This requirement assumes that the user has a fundamental understanding of misfire diagnostics as well as ignition controls. This requirement is not intended to be an introductory misfire guideline or interpretation of regulatory requirements.
2011-06-10
WIP Standard
J2450
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.
2011-02-08
WIP Standard
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.
2010-10-26
Standard
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.
2010-10-04
WIP Standard
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.
2010-09-28
Standard
J1979DA_201009
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.
2010-09-28
Standard
J1979_201009
This document supersedes SAE J1979 May 2007, and is technically equivalent to ISO 15031-5 2010, with the addition of new capabilities required by revised regulations from the California Air Resources Board and revised regulations from the European Commission. This document is intended to satisfy the data reporting requirements of On-Board Diagnostic (OBD) regulations in the United States and Europe, and any other region that may adopt similar requirements in the future.
2010-06-28
WIP Standard
J1699/2
To define test cases for the OBD-2 interface on external test equipment (such as a Generic OBD-2 Scan Tool, I/M Tester, etc.) which can be used to verify compliance with the applicable standards.
2009-12-03
Standard
J1699/3_200912
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.
Viewing 1 to 30 of 94