Refine Your Search

Search Results

Viewing 1 to 7 of 7
Standard

SAE J2450 Supplemental Training Document

2019-10-31
CURRENT
J2450/1_201910
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

SAE J2450 Supplemental Training Document

2008-05-13
HISTORICAL
J2450/1_200805
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

Test Cases for OBD-II Scan Tools and I/M Test Equipment

2017-09-13
CURRENT
J1699/2_201709
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).
Standard

DIAGNOSTIC CONNECTOR

1992-06-01
HISTORICAL
J1962_199206
This SAE Recommended Practice: a Defines the functional requirements for a vehicle electrical/electronic diagnostic connector. These functional requirements are separated into two principal areas: connector location/access and connector design. b Establishes terminal assignments to conform to either of two categories: Standard or Manufacturer Discretionary. Rationale relative to intent is provided, where applicable, to minimize ambiguity.
Standard

Diagnostic Trouble Code Definitions

2016-12-13
CURRENT
J2012_201612
This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in 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 J2012DA. 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).
Standard

Diagnostic Trouble Code Definitions

2022-07-15
WIP
J2012
This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in 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.
Standard

E/E Diagnostic Test Modes

2007-05-30
HISTORICAL
J1979_200705
This document supersedes SAE J1979 Apr 2002, and is technically equivalent to ISO 15031-5:2006, with the addition of new capabilities required by revised regulations from the California Air Resources Board (see Section 1.2). 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.
X