__________________________________________________________________________________________________________________________________________ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The u of this report is entirely voluntary, and its applicability and suitability for any particular u, including any patent infringement arising therefrom, is the sole responsibility of the ur.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revid, or cancelled. SAE invites your written comments and suggestions. Copyright © 2007 SAE International
All rights rerved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwi, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA)
Fax: 724-776-0790
Email: CustomerService@sae SAE WEB ADDRESS:
h ttp://www.sae
answersJ2012
Issued Revid 2007-12 (R) Diagnostic Trouble Code Definitions
RATIONALE
The prior version of SAE J2012 was technically equivalent to a draft version of ISO 15031-6: April 30, 2002. The ISO document was subquently edited and published as an International Standard ISO 15031-6:2005, including minor editorial changes. This version of SAE J2012 includes all of the editorial changes that were included in the published version of the ISO document. This version is updated to include; the latest standardized fault codes and failure type byte subfaults, provide a new fault code appendix format and remove certain figures that belong in the SAE J1930 standard. SAE is offering the current Diagnostic Trouble Code (DTC) and Failure Type Byte (FTB) appendices in a new Digital DTC and FTB appendices web tool.
FOREWORD
On-Board Diagnostic (OBD) regulations require pasnger cars, and light and medium duty trucks, to report standardized fault codes for malfunctions detected by the OBD system. This document defines the standardized t of fault codes. SAE J2012 was originally developed to meet U.S. OBD requirements for 1996 and later model year vehicles. ISO 15031-6 was bad on SAE J1962 and w
as 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 revid fault codes included.
TABLE OF CONTENTS
1. 2 1.2 1.2 Differences from 3
2. .3 2.1 3 2.1.1 3
2.1.2 3
3. DEFINITIONS ...............................................................................................................................................4 3.1 4 3.2 4 3.3 4 3.4 4 3.4 3.6 4 3.7 Left/Right and Front/Rear .................................................................................................................
............4 3.8 "A" "B"...........................................................................................................................................................4 3.9
Intermittent/Erratic (4)
--``,,`,``,,`,`,``,``,,,``,``,`,-`-`,,`,,`,`,,`---
4.GENERAL SPECIFICATIONS (5)
5.FORMAT STRUCTURE (5)
5.1Description (5)
5.2ISO/SAE Controlled Codes (Core DTCs) (7)
5.3Manufacturer Controlled Codes (Non-Uniform DTCs) (7)
5.4Body System Groupings (7)
5.4.1B0XXX ISO/SAE Controlled (7)
5.4.2B1XXX Manufacturer Controlled (7)
5.4.3B2XXX Manufacturer Controlled (7)长官英语
5.4.4B3XXX Rerved by Document (7)
5.5Chassis System Groupings (7)
5.5.1C0XXX ISO/SAE Controlled (7)
5.5.2C1XXX Manufacturer Controlled (7)
5.5.3C2XXX Manufacturer Controlled (7)
5.5.4C3XXX Rerved by Document (7)
5.6Powertrain System Groupings (8)
5.6.1P0XXX ISO/SAE Controlled (8)
5.6.2P1XXX Manufacturer Control (8)
eta是什么意思5.6.3P2XXX ISO/SAE Controlled (8)
5.6.4P3XXX Manufacturer Controlled and ISO/SAE Rerved (8)
5.7Network Groupings (8)
5.7.1U0XXX ISO/SAE Controlled (8)
5.7.2U1XXX Manufacturer Controlled (8)
minutes是什么意思5.7.3U2XXX Manufacturer Controlled (8)
concept
5.7.4U3XXX Manufacturer Controlled and ISO/SAE Rerved (8)
6.DIAGNOSTIC TROUBLE CODE DESCRIPTIONS (8)
6.1Diagnostic Trouble Code Application (8)
6.2Powertrain Systems (8)
6.3Body Systems (9)
6.4Chassis Systems (9)
6.5Network and Vehicle Integration Systems (9)
7.CHANGE REQUESTS (9)
8.NOTES (11)
8.1Marginal Indicia (11)
APPENDIX A0 - (NORMATIVE) DIAGNOSTIC TROUBLE CODE NAMING GUIDELINES (12)
APPENDIX B0 - BODY SYSTEMS (15)内双怎么画眼妆
APPENDIX C0 - CHASSIS SYSTEMS (20)
APPENDIX D0 - POWERTRAIN SYSTEMS (24)
APPENDIX E0 - NETWORK SYSTEMS (110)
APPENDIX F0 - FAILURE TYPE BYTE (128)
1. SCOPE
1.1 Purpo
This document superdes SAE J2012 APR2002, and is technically equivalent to ISO 15031-6:2005 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.
--``,,`,``,,`,`,``,``,,,``,``,`,-`-`,,`,,`,`,,`---
This document includes:
a. Diagnostic Trouble Code format.
b. A standardized t of Diagnostic Trouble Codes and descriptions
c. A standardized t of Diagnostic Trouble Codes subtypes known as Failure Types
1.2 Differences from ISO Document
The differences to the ISO document 15031-6:2005 are the removal of figures in Section 3. The figures have been moved to SAE J1930. The DTC and FTB appendixes have been updated to reflect the latest industry standardized DTC and FTB definitions.
2. REFERENCES
2.1 Applicable Publications
The following publications form a part of this specification to the extent specified herein. Unless otherwi specified, the latest issue of SAE publications shall apply.
2.1.1 SAE
Publications
sat网校
Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.
SAE J1930 Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms
SAE J1978 OBD II Scan Tool韩语发音
SAE J1979 E/E Diagnostic Test Modes
--``,,`,``,,`,`,``,``,,,``,``,`,-`-`,,`,,`,`,,`---
2.1.2 ISO
Publications
Available from ANSI, 25 West 43rd Street, New York, NY 10036-8002, Tel: 212-642-4900, www.ansi.
ISO/TR 15031-2:2004 Road vehicles—Communication between vehicle and external equipment for emissions-related diagnostics—Part 2: Terms, definitions, abbreviations and acronyms
ISO 15031-4:2005 Road vehicles—Communication between vehicle and external test equipment for emissions-related diagnostics—Part 4: External test equipment
ISO 15031-5:2006 Road vehicles—Communication between vehicle and external test equipment for emissions-related diagnostics—Part 5: Emissions related diagnostic rvices
ISO 15031-6:2005 Road vehicles—Communication between vehicle and external test equipment for emissions-related diagnostics—Part 6: Diagnostic trouble code definitions
ISO 14229-1 Road vehicles—Unified diagnostics rvices (UDS)—Part 1: Specification and requirements
3. DEFINITIONS
This document is not intended to be ud for terms and definitions of vehicle component terminology. Many related vehicle technologies are defined in SAE J1930. 3.1 Circuit/Open
Fixed value or no respon from the system where specific high or low detection is not feasible or can be ud in conjunction with circuit low and high codes where all three circuit conditions can be detected. 3.2 Range/Performance
Circuit is in the normal operating range, but not correct for current operating conditions, it may be ud to indicate stuck or skewed values indicating poor performance of a circuit, component, or system. 3.3 Low Input
Circuit voltage, frequency, or other characteristic measured at the control module input terminal or pi
n that is below the normal operating range. 3.4 High Input
Circuit voltage, frequency, or other characteristic measured at the control module input terminal or pin that is above the normal operating range. 3.5 Bank
Specific group of cylinders sharing a common control nsor, bank 1 always contains cylinder number 1, bank 2 is the opposite bank.
NOTE: If there is only one bank, u bank #1 DTCs and the word bank may be omitted. With a single "bank" system
using multiple nsors, u bank #1. 3.6 Sensor Location
Location of a nsor in relation to the engine air flow, starting from the fresh 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/Rear
Component identified by its position as if it can be viewed from the drivers ating position. 3.8 "A" "B"
Where components are indicated by a letter (e.g., A, B, C, etc.) this would be manufacturer defined. 3.9 Intermittent/Erratic
The 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 SPECIFICATIONS
The following table specifies systems, code categories, hexadecimal values and particular ctions of electrical/electronic systems diagnostic.
TABLE 1 - GENERAL CODE SPECIFICATIONS
my apology
System Code Categories Hex Value Appendix
Body B0xxx - B3xxx8xxx - B xxx B0
Chassis C0xxx - C3xxx4xxx - 7xxx C0
Powertrain P0xxx - P3xxx0xxx - 3xxx P0
Network U0xxx - U3xxx C xxx - F xxx U0
The recommended DTCs consist of a three digit hexadecimal code preceded by an alphanumeric designator. The alphanumeric designators are "B0", "B1", B2", "B3", "C0", "C1", C2", "C3", "P0", "P1", P2", "P3", "U0", "U1", U2", "U3", corresponding to four ts of body, four ts of chassis, four ts of powertrain and four ts of network trouble codes. The code structure itlf is partially open-ended. A portion of the available numeric quences (portions of "B0", "C0", "P0", “P2”, “P3”, "U0", and “U3”) is rerved for uniform codes assigned by this or future updates. Detailed specifications of the DTC format structure are specified in Section 5.
Most circuit, component, or system diagnostic trouble codes that do not support a subfault strategy are specified by four basic categories:
— General Circuit /Open
— Range/Performance
— Circuit Low
— Circuit High
Circuit Low is measured with the external circuit, component, or system connected. The signal type (voltage, frequency, etc.) shall be included in the message after Circuit Low.
Circuit High is measured with the external circuit, component, or system connected. The signal type (voltage, frequency, etc.) may be included in the message after Circuit High.
5. FORMAT STRUCTURE
--``,,`,``,,`,`,``,``,,,``,``,`,-`-`,,`,,`,`,,`---
5.1 Description
The diagnostic trouble code consists of an alphanumeric designator, B0 -- B3 for body, C0 -- C3 for chassis, P0 -- P3 for powertrain, and U0 -- U3 for network communication, followed by a hexadecimal number. The assignment of the proper alpha designator should be determined by the area most appropriate for that function. In most cas, the alpha designator will be implied since diagnostic information will be requested from a particular controller. However, this does not imply that all codes supported by a particular controller shall have the same alphanumeric designator. The
提供英文codes are structured as in Figure 1.
