Refine Your Search

Topic

Search Results

Standard

Vehicle OBD II Compliance Test Cases

2015-07-28
HISTORICAL
J1699/3_201507
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/EDiagnostic 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

Vehicle OBD II Compliance Test Cases

2017-07-21
HISTORICAL
J1699/3_201707
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

Vehicle OBD II Compliance Test Cases

2021-04-28
CURRENT
J1699/3_202104
The main purpose of this SAE 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, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature “Mixed Format Frames on a CAN Network.”
Standard

Vehicle OBD II Compliance Test Cases

2012-05-11
HISTORICAL
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.
Standard

Vehicle OBD II Compliance Test Cases

2021-05-04
WIP
J1699/3
The main purpose of this SAE 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, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534 2 feature “Mixed Format Frames on a CAN Network.”
Standard

SAE J1850 Verification Test Procedures

2006-06-05
HISTORICAL
J1699/1_200606
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

OBD-II Scan Tool: First Generation Protocols

2023-12-13
CURRENT
J1978-1_202312
SAE J1978-1 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which complies to SAE J1978-1 The SAE J1978-1 content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. on-board diagnostic (OBD) regulations. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979 and SAE J1979-2. The presentation of the SAE J1978 document family, where SAE J1978-1 covers first generation protocol functionality defined in SAE J1979, and SAE J1978-2 covers second generation protocol functionality defined in SAE J1979-2.
Standard

OBD-II Scan Tool

2022-05-26
CURRENT
J1978_202205
SAE J1978/ISO 15031-4 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which is compliant with SAE J1978/ISO 15031-4. The SAE J1978 content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. on-board diagnostic (OBD) regulations. The ISO 15031-4 content of this 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. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979/ISO 15031-5.
Standard

OBD-II Related SAE Specification Verification Test Procedures1

1998-01-01
HISTORICAL
J1699/2_199801
This SAE Recommended Practice recommends test methods, test procedures, and specific test parameters to help verify that vehicles and test tools can communicate using SAE J1962. These test procedures are to be used whenever SAE J1850 communication parameters need to be verified. However, all specific details for testing are not specified, e.g., sample size, environment, vibration, etc.
Standard

Misfire Generator Functional Requirements

2019-04-11
CURRENT
J2901_201904
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.
Standard

Misfire Generator Functional Requirements

2011-06-30
HISTORICAL
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.
Standard

Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms—Equivalent to ISO/TR 15031-2:April 30, 2002

2002-04-30
HISTORICAL
J1930_200204
This SAE Recommended Practice 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. This document focuses 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 this document is strongly encouraged, nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.
Standard

Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms

1998-05-01
HISTORICAL
J1930_199805
This SAE Recommended Practice 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. This document focuses 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 this document is strongly encouraged, nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.
Standard

ELECTRICAL/ELECTRONIC SYSTEMS DIAGNOSTIC TERMS, DEFINITIONS, ABBREVIATIONS, AND ACRONYMS

1995-09-01
HISTORICAL
J1930_199509
This SAE Recommended Practice 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 databases, under-hood emission labels, and emission certification applications. This document focuses 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 this document is strongly encouraged, nothing in this document should be construed as prohibiting the introduction of a term, abbreviation, or acronym not covered by this document. Certain terms have already been in common use and are readily understood by manufacturers and technicians, but do not follow the methodology of this document.
X