SAE J 2012-2016 Diagnostic Trouble Code Definitions (See Also SAE J2012DA).pdf

《SAE J 2012-2016 Diagnostic Trouble Code Definitions (See Also SAE J2012DA).pdf》由会员分享，可在线阅读，更多相关《SAE J 2012-2016 Diagnostic Trouble Code Definitions (See Also SAE J2012DA).pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、_SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising theref

2、rom, is the sole responsibility of the user.”SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions.Copyright 2016 SAE InternationalAll rights reserved. No part of this publi

3、cation may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE.TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)Tel: +1 724-776-4970 (out

4、side USA)Fax: 724-776-0790Email: CustomerServicesae.orgSAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedback on thisTechnical Report, please visitHTTP:/STANDARDS.SAE.ORG/J2012_201612SURFACE VEHICLERECOMMENDED PRACTICEJ2012 DEC2016Issued 1992-06Revised 2016-12Superseding J2012

5、MAR2013Diagnostic Trouble Code DefinitionsRATIONALEAs DTC usage has increased with the introduction of new technology to vehicle systems (hybrid, diesel, etc.) it has become necessary to restructure the document to accommodate these changes. This restructuring includes the removal of Table Titles, a

6、nd DTCs will no longer be grouped by functional areas. Also being updated are the usage notes to provide further guidance in the usage of DTCs with the new technology (i.e., smart sensors and actuators).FOREWORDOn-Board Diagnostic (OBD) regulations require passenger cars, and light and medium duty t

7、rucks, to report standardized fault codes for malfunctions detected by the OBD system. This document with SAE J2012DA defines the standardized set of fault codes.SAE J2012 was originally developed to meet U.S. OBD requirements for 1996 and later model year vehicles. ISO 15031-6was based on SAE J2012

8、 and was intended to meet European OBD requirements for 2000 and later model year vehicles. This document is technically equivalent to ISO 15031-6, with new and revised fault codes included.TABLE OF CONTENTS1. SCOPE 21.1 Purpose. 21.2 Differences from ISO Document. 32. REFERENCES 32.1 Applicable Doc

9、uments 33. DEFINITIONS . 64. GENERAL SPECIFICATIONS 75. FORMAT STRUCTURE 75.1 Description 75.2 ISO/SAE Controlled Codes (Core DTCs) . 95.3 Manufacturer Controlled Codes (Non-Uniform DTCs) 95.4 Body System Groupings . 105.5 Chassis System Groupings. 105.6 Powertrain System Groupings 105.7 Network and

10、 Vehicle Integration Groupings . 10SAE INTERNATIONAL J2012 DEC2016 Page 2 of 166. DIAGNOSTIC TROUBLE CODE DESCRIPTIONS 116.1 Diagnostic Trouble Code Application 116.2 Powertrain Systems 116.3 Body Systems . 126.4 Chassis Systems. 126.5 Network and Vehicle Integration Systems 127. CHANGE REQUESTS 128

11、. NOTES 138.1 Marginal Indicia . 13APPENDIX A (NORMATIVE) DIAGNOSTIC TROUBLE CODE NAMING GUIDELINES. 14FIGURE 1 SAE DIGITAL ANNEX DOCUMENT REFERENCE . 5FIGURE 2 SAE DIGITAL ANNEX TO WWH-OBD DOCUMENT REFERENCE 5FIGURE 3 STRUCTURE OF DIAGNOSTIC TROUBLE CODES 8FIGURE 4 EXAMPLE OF 2 BYTE DIAGNOSTIC TROU

12、BLE CODE STRUCTURE . 8FIGURE 5 EXAMPLE OF 3 BYTE DTC WITH DTC FORMAT IDENTIFIER 0X00 DIAGNOSTIC TROUBLE CODE STRUCTURE. 9FIGURE 6 EXAMPLE OF 3 BYTE DTC WITH DTC FORMAT IDENTIFIER 0X04 DIAGNOSTIC TROUBLE CODE STRUCTURE. 9TABLE 1 LEGISLATED EMISSIONS-RELATED OBD/WWH-OBD DIAGNOSTIC SPECIFICATIONS APPLI

13、CABLE TO THE OSI LAYERS . 4TABLE 2 GENERAL CODE SPECIFICATIONS 7TABLE A1 DTC NAMING GUIDELINES FOR SIGNALS FROM COMPONENTS 14TABLE A1 DTC NAMING GUIDELINES FOR SIGNALS FROM COMPONENTS (CONTINUED) 15TABLE A2 DTC NAMING GUIDELINES FOR SIGNALS TO COMPONENTS 15TABLE A3 DTC NAMING GUIDELINES INVOLVING SE

14、VERAL COMPONENTS OR SYSTEMS 16TABLE A4 DTC NAMING GUIDELINES FOR SIGNALS USING A SUBFAULT STRATEGY. 161. SCOPE1.1 PurposeThis 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 standard

15、ized 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 i

16、ncludes: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

17、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).SAE INTERNATIONAL J2012 DEC2016 Page 3 of 161.2 Differences from ISO DocumentThe differences to the ISO document 15031-6:2010 are descriptions of th

18、e SAE J2012DA containing the latest industry standardized DTC and FTB definitions. 2. REFERENCES2.1 Applicable DocumentsThe following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest issue of SAE publications shall apply.SAE J2012

19、Diagnostic trouble codes are communicated on communication link between a vehicles OBD systems and test equipment. To achieve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model in accordance with ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems

20、into seven layers. When mapped on this model, the services specified are broken into:Diagnostic services (layer 7), specified in:ISO 15031-5/SAE J1979 (emissions-related OBD),ISO 27145-3 (WWH-OBD),Presentation layer (layer 6), specified in:ISO 15031-2, SAE J1930-DA, ISO 15031-5, SAE J1979-DA, ISO 15

21、031-6, SAE J2012-DA,ISO 27145-2, SAE J2012-DA,Session layer services (layer 5), specified in:ISO 14229-2 supports ISO 15765-4 DoCAN and ISO 14230-4 DoK-Line protocols,ISO 14229-2 is not applicable to the SAE J1850 and ISO 9141-2 protocols,Transport layer services (layer 4), specified in:DoCAN: ISO 1

22、5765-2 Transport protocol and network layer services,SAE J1850: ISO 15031-5/SAE J1979 Emissions-related diagnostic services,ISO 9141-2: ISO 15031-5/SAE J1979 Emissions-related diagnostic services,DoK-Line: ISO 14230-4, ISO 15031-5/SAE J1979 Emissions-related diagnostic services,Network layer service

23、s (layer 3), specified in:DoCAN: ISO 15765-2 Transport protocol and network layer services,SAE J1850: ISO 15031-5/SAE J1979 Emissions-related diagnostic services,ISO 9141-2: ISO 15031-5/SAE J1979 Emissions-related diagnostic services,DoK-Line: ISO 14230-4, ISO 15031-5/SAE J1979 Emissions-related dia

24、gnostic services,Data link layer (layer 2), specified in:DoCAN: ISO 15765-4, ISO 11898-1, -2,SAE J1850,ISO 9141-2, DoK-Line: ISO 14230-2, Physical layer (layer 1), specified in:DoCAN: ISO 15765-4, ISO 11898-1, -2,SAE J1850,ISO 9141-2, DoK-Line: ISO 14230-1, in accordance with Table 1SAE INTERNATIONA

25、L J2012 DEC2016 Page 4 of 16Table 1 - Legislated emissions-related OBD/WWH-OBD diagnosticspecifications applicable to the OSI layersApplicability OSI 7 layers Emissions-related OBD communication requirements Emissions-related WWH-OBD communication requirementsSeven layer according to ISO/IEC7498-1an

26、dISO/IEC10731Application (layer 7) ISO 15031-5 / SAE J1979 ISO 27145-3Presentation (layer 6)ISO 15031-2, -5, -6SAE J1930-DA / SAE J1979DAISO 27145-2SAE J1930-DA / SAE J1979DASAE J2012-DA SAE J2012-DASession (layer 5) Not Applicable ISO 14229-2Transport (layer 4)ISO 15031-5 ISO14230-4 ISO15765-2ISO15

27、765-4ISO15765-2ISO15765-4ISO13400-2Network (layer 3)Data link (layer 2)SAEJ1850ISO9141-2ISO14230-2 ISO11898-1, -2ISO11898-1, -2ISO13400-3Physical (layer 1) ISO14230-1SAE document reference conceptISO 15031 references several SAE documents which contain all terms, data and DTC definitions.See Figure

28、1 - SAE Digital Annex document reference with the following definition of content in ISO 15031 parts:SAE J1930: the document is concerned with a procedure for naming objects and systems and with the set of words from which names are built. It references SAE J1930DA which contains all standardized na

29、ming objects, terms and abbreviations.SAE J1979: the document is concerned with the definition of emissions-related diagnostic services (diagnostic test modes). It references SAE J1979DA which contains all standardized data items like PIDs, Test Ids, Monitor IDs and InfoType IDs.SAE J2012: the docum

30、ent is concerned with the procedure for defining emissions-related diagnostic trouble codes. It references SAE J2012DA which contains all standardized data items like DTCs and FTBs.On-Board Diagnostic (OBD) regulations require passenger cars, and light, medium and heavy duty trucks, to support a min

31、imum set of diagnostic information to external (off-board) “generic” test equipment. Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or +1 724-776-4970 (outside USA), www.sae.org.SAE INTERNATIONAL J2012 DEC2016 Page 5 of

32、16Key1 SAE Digital AnnexesFigure 1 - SAE Digital Annex document referenceFigure 2 - SAE Digital Annex to WWH-OBD document reference2.1.1 ISO PublicationsCopies of these documents are available online at http:/webstore.ansi.org/ISO/TR 15031-2:2010 Road vehicles - Communication between vehicle and ext

33、ernal equipment for emissions-related diagnostics - Part 2: Terms, definitions, abbreviations and acronymsISO 15031-4:2005 Road vehicles - Communication between vehicle and external test equipment for emissions-related diagnostics - Part 4: External test equipmentISO 27145 -2WWH-OBDCommon data dicti

34、onary SAE J 1979 -DADigital Annex of E /EDiagnostic Test ModesSAE J 2012 -DA Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte DefinitionsSAE J 1930-DADigital Annex of Electrical /Electronic Systems Diagnostic Terms , Definitions ,Abbreviations , and AcronymsSAE J 1939Append

35、ix C SAE J 1939-73Appendix A 1SAE INTERNATIONAL J2012 DEC2016 Page 6 of 16ISO 15031-5:2011 Road vehicles - between vehicle and external test equipment for emissions-related diagnostics -Part 5: Emissions related diagnostic servicesISO 15031-6:2010 Road vehicles - Communication between vehicle and ex

36、ternal test equipment for emissions-related diagnostics - Part 6: Diagnostic trouble code definitionsISO 14229-1:2006 Road vehicles - Unified diagnostics services (UDS) - Part 1: Specification and requirementsISO 27145-2 Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (W

37、WH-OBD) communication requirements - Part 2: Common data dictionaryISO/DIS 14229-1 Road vehicles - Unified diagnostic services (UDS) - Part 1: Specification and requirements3. DEFINITIONSThis document is not intended to be used for terms and definitions of vehicle component terminology. Many related

38、 vehicle technologies are defined in SAE J1930. 3.1 CIRCUIT/OPENFixed value or no response from the system where specific high or low detection is not feasible or can be used in conjunction with circuit low and high codes where all three circuit conditions can be detected.3.2 RANGE/PERFORMANCECircui

39、t is in the normal operating range, but not correct for current operating conditions, it may be used to indicate stuck or skewed values indicating poor performance of a circuit, component, or system.3.3 LOW INPUTCircuit voltage, frequency, or other characteristic measured at the control module input

40、 terminal or pin that is below the normal operating range.3.4 HIGH INPUTCircuit voltage, frequency, or other characteristic measured at the control module input terminal or pin that is above the normal operating range.3.5 BANKSpecific group of cylinders sharing a common control sensor, bank 1 always

41、 contains cylinder number 1, bank 2 is the opposite bank.NOTE: If there is only one bank, use bank #1 DTCs and the word bank may be omitted. With a single “bank“ system using multiple sensors, use bank #1.3.6 SENSOR LOCATIONLocation of a sensor in relation to the engine air flow, starting from the f

42、resh air intake through to the vehicle tailpipe or fuel flow from the fuel tank to the engine in order numbering 1, 2, 3 and so on.3.7 LEFT/RIGHT AND FRONT/REARComponent identified by its position as if it can be viewed from the drivers seating position.3.8 “A“ “B“Where components are indicated by a

43、 letter (e.g., A, B, C, etc.) this would be manufacturer defined.SAE INTERNATIONAL J2012 DEC2016 Page 7 of 163.9 INTERMITTENT/ERRATICThe signal is temporarily discontinuous, the duration of the fault is not sufficient to be considered an open or short, or the rate of change is excessive.4. GENERAL S

44、PECIFICATIONSThe following table specifies systems, code categories, hexadecimal values and particular sections of electrical/electronic systems diagnostic. Table 2 - General code specificationsSystem Code Categories Hex Value AppendixBody B0xxx - B3xxx 8xxx - Bxxx B0Chassis C0xxx - C3xxx 4xxx - 7xx

45、x C0Powertrain P0xxx - P3xxx 0xxx - 3xxx P0Network the least significant byte is decoded based upon SAE J2012DA failure type byte (FTB) table.EXAMPLE: A 2 byte DTC as a data bus value $9234 would be displayed to technicians as the manufacturer controlled body code B1234, see Figure 4.DTC HIGH BYTE D

46、TC LOW BYTE$9 $2 $3 $41 0 0 1 0 0 1 0 0 0 1 1 0 1 0 0B 1 2 3 4Figure 4 - Example of 2 BYTE diagnostic trouble code structureEXAMPLE: A 3 byte DTC using DTC Format Identifier 0x00 as a data bus value $923411 would be displayed to technicians as the manufacturer controlled body code B1234-11, see Figu

47、re 3. See SAE J2012DA FTB tables for DTC Low Byte (Failure Type Byte) definitions. The low byte shall be displayed in hexadecimal format, e.g., $11 shall be displayed as 11. When the most significant 2 bytes of this DTC is contained within the SAE controlled range, it is decoded according to the DTC

48、 Format Identifier 0x00 list from SAE J2012-DA. See Figure 5.b7 b6 b5 b4 b3 b2 b1 b0 b7 b6 b5 b4 b3 b2 b1 b0 Byte 1 Byte 24th character of code(Hexadecimal 0 . F)display character 53rd character of code(Hexadecimal 0 . F)display character 4Area of vehicle system(Hexadecimal 0 . F)display character 3

49、00 = ISO/SAE controlled01 = manufacturer controlled10 = ISO/SAE controlled11 = ISO/SAE controlleddisplay character 200 = pow ertrain (P)01 = chassis (C)10 = body (B)11 = netw ork and vehicle integration(U)display character 1for powertrain: these bits are ISO/SAE controlled, for all others they are manufacturer controlled.Display character 3 is used to identify a specific vehicle area. Within any area, d