Diagnostic Trouble Code Definitions
- Ground Vehicle Standard
- J2012_201612
- Revised
Scope
-
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).
Rationale
Recommended Content
Ground Vehicle Standard | Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions |
Ground Vehicle Standard | E/E Diagnostic Test Modes |
Topic
Data Sets - Support Documents
Title | Description | Download |
---|---|---|
Table 1 | Legislated emissions-related OBD/WWH-OBD diagnostic specifications applicable to the OSI layers | |
Unnamed Dataset 2 | ||
Table 2 | General code specifications | |
Table A1 | DTC naming guidelines for signals from components | |
Table A2 | DTC naming guidelines for signals to components | |
Table A3 | DTC naming guidelines involving several components or systems | |
Table A4 | DTC naming guidelines for signals using a subfault strategy |
Issuing Committee
Vehicle E E System Diagnostic Standards Committee
The committee shall increase customer satisfaction and lower product life cycle costs by investigating and recommending standards that will promote more effective diagnosis of vehicle electrical and electronic system problems. The resulting recommended practices will focus on model year 1992 and beyond. However, they may be useful for prior vehicle diagnosis/repair and may serve as a basis for additional recommended practices and pre-model year 1992 vehicles.Vision Statement: A standard disgnostic connector (in a standard location) will be in all vehicles. Pin assignments for a portion of the connector will also be standardized.All vehicles will implement a set of industry standard diagnostic test modes that can be executed over a standard communication data line (i.e., SAE J1850, ISO 9141-2). Industry standard test information will be associated with some of these diagnostic test modes.An OBD II scan tool will be able to utilize a minimum set of standardized diagnostic test modes and test information.A system will be in place that will allow standard electronic access of all E/E diagnostic service information. Future diagnostic legislation will be in harmony with this vision and the resulting SAE Recommended Practices.