Criteria

Text:
Display:

Results

Viewing 1 to 30 of 88
Standard
2014-08-11
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.
WIP Standard
2014-06-26
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
2014-06-10
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
2014-04-09
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.
Software
2014-03-04
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.
WIP Standard
2013-08-07
This document will define the P1.6 Diagnostics Message Transport Protocol and its application with SAE J2534.
WIP Standard
2013-08-07
The TP 1.6 Diagnostics Message Transport Protocol Information Report provides technical details on the operation of the protocol. This protocol is used to transmit diagnostics and ECU programming data from an off board tool to a vehicle.
Standard
2013-03-07
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).
Software
2013-01-31
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.
Standard
2012-07-26
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.
WIP Standard
2012-07-11
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
2012-05-11
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.
WIP Standard
2012-04-23
Recommendations for remote OBD vehicle interface devices. These recommendations are intended to provide definitions for remote OBD equipment requiring to comply to the following documents: SAE J1978/ ISO 15031-4 SAE J1962/ ISO 15031-3 SAE J1699/2 SAE J1699/4 SAE J1979/ISO 15031-5
Standard
2012-02-23
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.
WIP Standard
2011-09-09
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
2011-06-30
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.
WIP Standard
2011-06-10
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.
WIP Standard
2011-02-08
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. Only those provisions of ISO 15765-4 that pertain to 500 kbps are required to be supported by an SAE J1978 diagnostic scan tool. b.
Standard
2010-10-26
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.
WIP Standard
2010-10-04
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
2010-09-28
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. This document specifies: a. message formats for request and response messages, b. timing requirements between request messages from external test equipment and response messages from vehicles, and between those messages and subsequent request messages, c. behavior of both the vehicle and external test equipment if data is not available, d. a set of diagnostic services, with corresponding content of request and response messages, to satisfy OBD regulations, This document includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types.
WIP Standard
2010-06-28
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.
Standard
2009-12-03
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
2008-10-16
SCOPE - Purpose This SAE Recommended Practice supersedes SAE J1930 Apr 2002, and is technically equivalent to ISO 15031-2. This document is applicable to all light-duty gasoline and diesel passenger vehicles and trucks, and to heavy-duty gasoline vehicles. Specific applications of this document include diagnostic, service and repair manuals, bulletins and updates, training manuals, repair data bases, underhood emission labels, and emission certification applications. SAE J1930 Revised Proposed Draft SEP2008 - 3 - This document should be used in conjunction with DAE J1930-DA Digital Annexes, which contains all of the information previously contained within the SAE J1930 tables. These documents focus on diagnostic terms applicable to electrical/electronic systems, and therefore also contains related mechanical terms, definitions, abbreviations, and acronyms. Even though the use and appropriate updating of these documents is strongly encouraged, nothing in these documents should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by these documents.
Standard
2008-10-02
This SAE Recommended Practice describes the implementation of Enhanced Diagnostic Test Modes, which are intended to supplement the legislated Diagnostic Test Modes defined in SAE J1979. Modes are defined for access to emission related test data beyond what is included in SAE J1979, and for non-emission related data. This document describes the data byte values for diagnostic messages transmitted between diagnostic test equipment, either on-vehicle or off-vehicle, and vehicle electronic control modules. No distinction is made between test modes for emission related and non-emission related diagnostics. These messages can be used with a diagnostic serial data link such as described in SAE J1850 or ISO 9141-2. For each test mode, this document includes a functional description of the test mode, request and report message data byte content, and an example if useful for clarification.
WIP Standard
2008-08-04
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
WIP Standard
2008-07-31
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. Environmental Protection Agency (EPA) and the California Air Resources Board (ARB) have proposed requirements for reprogramming vehicles for all manufacturers by the aftermarket repair industry.
WIP Standard
2008-07-28
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 DaimlerChrysler Corporation (Chrysler Group) 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. It further specifies additional requirements for the application of a flash strobe voltage multiplexed on the SCI communication link for purposes of ECU reprogramming.
Standard
2008-05-13
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
2008-02-01
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.
Viewing 1 to 30 of 88