ISO 27145-2:2012

Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 2: Common data dictionary

ISO 27145-2:2012 defines all regulatory data elements of the ISO 27145 series. The data elements are used to provide the external test equipment with the diagnostic status of the vehicle on-board diagnostics (VOBD) system in the vehicle. All data elements are communicated with the unified diagnostic services as defined in ISO 27145-3. The data elements are diagnostic trouble codes (DTCs), data identifiers (DIDs) and routine identifiers (RIDs). The mapping from parameter identifiers (PIDs), monitor identifiers (MIDs) and info type identifiers (ITIDs) is described in ISO 27145-2:2012. If new legislated WWH-OBD GTR modules are established, it is intended that ISO 27145 be applicable with possible extensions, which can be included in ISO 27145-2:2012, can be specified as enhancements of the SAE Digital Annexes or can even be part of other referenced documents which are intended to include the applicable data definitions. ISO 27145 is intended to become the single communication standard for access to OBD-related information (VOBD). To allow for a smooth migration from the existing communication standards to this future world-wide communication standard, the communication concept as specified in ISO 27145-4 is based on two different data links: ISO 15765-4 and ISO 13400 (all parts).

Véhicules routiers — Mise en application des exigences de communication pour le diagnostic embarqué harmonisé à l'échelle mondiale (WWH-OBD) — Partie 2: Dictionnaire de données communes

General Information

• Status: Published
• Publication Date: 13-Aug-2012
• ICS: 43.040.10 - Electrical and electronic equipment
• ICS: 43.180 - Diagnostic, maintenance and test equipment
• Technical Committee: ISO/TC 22/SC 31 - Data communication
• Drafting Committee: ISO/TC 22/SC 31/WG 2 - Vehicle diagnostic protocols
• Current Stage: 9093 - International Standard confirmed
• Start Date: 05-Mar-2024
• Completion Date: 13-Dec-2025

Relations

• Amended By: ISO 27145-2:2012/Amd 1:2023 - Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 2: Common data dictionary - Amendment 1
• Effective Date: 03-Dec-2022
• Revises: ISO/PAS 27145-2:2006 - Road vehicles - Implementation of WWH-OBD communication requirements - Part 2: Common emissions-related data dictionary
• Effective Date: 15-Apr-2008

Overview

ISO 27145-2:2012 specifies the common data dictionary for World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication. As Part 2 of the ISO 27145 series, it defines the regulatory data elements that external test equipment uses to obtain the diagnostic status of a vehicle’s on-board diagnostics (VOBD) system. The standard covers the structure and semantics of diagnostic trouble codes (DTCs), data identifiers (DIDs) and routine identifiers (RIDs), and the mapping from parameter identifiers (PIDs), monitor identifiers (MIDs) and info type identifiers (ITIDs).

Keywords: ISO 27145-2:2012, WWH-OBD, common data dictionary, DTC, DID, RID, VOBD, vehicle diagnostics.

Key topics and requirements

• Regulatory data elements: Defines DTCs, DIDs and RIDs used for regulatory WWH-OBD communication.
• Mapping and interoperability: Describes mapping from PIDs, MIDs and ITIDs to the ISO 27145 data elements to ensure consistent interpretation by external test equipment.
• Presentation layer requirements: Specifies presentation conventions for data exchange (referencing SAE documents such as SAE J1930-DA, SAE J1979-DA, SAE J2012-DA and SAE J1939).
• Data record and layout rules: Details DID/RID data record structures and diagnostic trouble code range/layout conventions used by VOBD servers/ECUs.
• Migration and multi-link support: Designed to be the single worldwide communication standard for OBD-related information while supporting a smooth migration via two data links (ISO 15765-4 DoCAN and ISO 13400 DoIP).
• Extensibility process: Anticipates future WWH-OBD GTR modules and points to SAE digital annex revision procedures for adding new data definitions.

Applications and who uses it

ISO 27145-2 is used by:

• Vehicle manufacturers (OEMs) to implement harmonized OBD reporting for global regulatory compliance.
• Automotive diagnostic tool and test equipment vendors to build generic external testers that read and interpret VOBD data.
• ECU and gateway suppliers to standardize diagnostic data exposure in vehicles.
• Regulatory agencies and test labs to define and validate emissions and OBD conformance.
• Standards and integration engineers working on UDS (ISO 14229) and network-layer implementations.

Practical uses include reading regulatory DTCs, retrieving standardized DIDs/RIDs, implementing presentation-layer conventions, and ensuring consistency across DoCAN and DoIP communication channels.

Related standards

• ISO 27145 series (Parts 1–4; Part 3: message dictionary, Part 4: connection)
• ISO 14229 (Unified Diagnostic Services / UDS)
• ISO 15765-4 and ISO 13400 (transport/network for DoCAN and DoIP)
• SAE J1979-DA, SAE J2012-DA, SAE J1930-DA, SAE J1939 (digital annexes and DTC/SPN definitions)

ISO 27145-2:2012 is essential for anyone implementing or using WWH-OBD-compliant vehicle diagnostics and for achieving consistent, global access to vehicle OBD information.

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 27145-2
First edition
2012-08-15
Road vehicles — Implementation of
World-Wide Harmonized On-Board
Diagnostics (WWH-OBD) communication
requirements —
Part 2:
Common data dictionary
Véhicules routiers — Mise en application des exigences de
communication pour le diagnostic embarqué harmonisé à l'échelle
mondiale (WWH-OBD) —
Partie 2: Dictionnaire de données communes

Reference number
©
ISO 2012
©  ISO 2012
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO 2012 – All rights reserved

Contents Page
Foreword . iv
0  Introduction . v
1  Scope . 1
2  Normative references . 2
3  Terms, definitions and abbreviated terms . 2
3.1  Terms and definitions . 2
3.2  Abbreviated terms . 4
4  Conventions . 5
5  Document overview . 5
6  Common data dictionary requirements . 7
6.1  Data range layout . 7
6.2  Diagnostic trouble code (DTC) range layout . 7
7  Data identifier and routine identifier data record requirements . 8
7.1  Data identifier and routine identifier definitions . 8
7.2  DID and RID data record definition . 8
8  Diagnostic trouble code definition . 14
8.1  Overview . 14
8.2  SAE J2012-DA and SAE J1939-73 DTCs . 15
9  Presentation layer requirements . 18
Annex A (normative) DID (PID, MID, ITID) and RID supported definition . 19
Annex B (normative) WWH-OBD server/ECU supported mandatory DID . 22
Annex C (informative) GTR WWH-OBD emissions system parameters . 23
Annex D (normative) GTR WWH-OBD DTCExtendedDataRecord content . 30
Annex E (informative) Definition guidelines for new DID (PID, MID, ITID) assignments . 31
Bibliography . 34

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 27145-2 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
This first edition of ISO 27145-2 cancels and replaces ISO/PAS 27145-2:2006, which has been technically
revised.
ISO 27145 consists of the following parts, under the general title Road vehicles — Implementation of World-
Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements:
 Part 1: General information and use case definition
 Part 2: Common data dictionary
 Part 3: Common message dictionary
 Part 4: Connection between vehicle and test equipment
The following parts are under preparation:
 Part 6: External test equipment
iv © ISO 2012 – All rights reserved

0 Introduction
0.1 Overview
The ISO 27145 series includes the communication between the vehicle's on-board diagnostics (OBD)
systems and external test equipment within the scope of the World-Wide Harmonized On-Board Diagnostics
Global Technical Regulations (WWH-OBD GTR).
It has been established in order to apply the unified diagnostic services (specified in ISO 14229-1) to WWH-
OBD systems.
The ISO 27145 series includes the communication between the vehicle's WWH-OBD systems and external
(off-board) "generic" test equipment within the scope of the country-specific regulatory requirements.
To achieve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model in
ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers. Where
mapped on this model, the services specified by ISO 27145 are divided into
 diagnostic services (layer 7), specified in ISO 27145-3 with reference to ISO 14229-1,
 presentation layer (layer 6), specified in this part of ISO 27145 with reference to SAE J1930-DA,
SAE J1939 Companion Spreadsheet (SPNs), SAE J1939-73:2010, Appendix A (FMIs), SAE J1979-DA
and SAE J2012-DA,
 session layer services (layer 5), specified in ISO 14229-2,
 transport layer services (layer 4), specified in ISO 27145-4 with reference to ISO 13400-2, ISO 15765-2
and ISO 15765-4,
 network layer services (layer 3), specified in ISO 27145-4 with reference to ISO 15765-4, ISO 15765-2
and ISO 13400-2,
 data link layer (layer 2), specified in ISO 27145-4 with reference to ISO 11898-1, ISO 11898-2,
ISO 15765-4, ISO 13400-3 and IEEE 802.3, and
 physical layer (layer 1), specified in ISO 27145-4 with reference to ISO 11898-1, ISO 11898-2,
ISO 15765-4, ISO 13400-3 and IEEE 802.3,
in accordance with Table 1.
Table 1 — WWH-OBD specification reference applicable to the OSI layers
Applicability OSI seven layer WWH-OBD reference
Application (layer 7) ISO 14229-1, ISO 27145-3
This part of ISO 27145,
Presentation (layer 6) SAE J1930-DA, SAE J1939 Companion Spreadsheet (SPNs),
SAE J1939-73:2010, Appendix A (FMIs), SAE J1979-DA, SAE J2012-DA
Seven layers
according to
Session (layer 5) ISO 14229-2
ISO/IEC 7498-1
Transport (layer 4)
and
ISO 15765-2 DoCAN, ISO 13400-2 DoIP
ISO/IEC 10731
ISO 15765-4 DoCAN TCP and IP
Network (layer 3)
ISO 27145-4
ISO 11898-1 CAN DLL,
Data link (layer 2)
ISO 13400-3 DoIP,
ISO 11898-2 CAN HS,
IEEE 802.3
ISO 15765-4 DoCAN
Physical (layer 1)
0.2 SAE document reference concept
ISO 27145 makes reference to several SAE documents which contain the relevant terms, data and diagnostic
trouble code (DTC) definitions.
ISO 27145-2 defines a common data dictionary for the ISO 27145 series, according to the definitions in the
following documents (see Figure 1):
 SAE J1930-DA: this digital annex contains all standardized naming objects, terms and abbreviations.
 SAE J1939 Companion Spreadsheet and SAE J1939-73: SAE J1939 Companion Spreadsheet indexes
names for suspect parameter numbers (SPNs), which provide an alternative presentation format for
SAE J2012-DA DTCs. SPNs are combined with failure mode indicators (FMIs) to form the full alternative
presentation. FMIs are described in SAE J1939-73:2010, Appendix A.
NOTE The SAE J1939 Companion Spreadsheet is a document which supplements the SAE J1939 family of
standards and contains SPNs and PGNs.
 SAE J1979-DA: this digital annex contains all standardized data items such as data identifiers (DIDs), test
identifiers (TIDs), monitor identifiers (MIDs) and info type identifiers (ITIDs).
 SAE J2012-DA: this digital annex contains all standardized data items such as DTC definitions and failure
type byte (FTB) definitions.
ISO 27145-2
WWH-OBD
common data dictionary
1 2
SAE J1930-DA
SAE J1939
digital annex of
SAE J1939-73:2010
SAE J2012-DA
[Companion
SAE J1979-DA electrical /electronic
[Appendix A]
digital annex of
Spreadsheet]
digital annex of E/E systems diagnostic
diagnostic trouble
diagnostic test modes terms, definitions,
code definitions
abbreviations and
acronyms
Key
1 SAE digital annexes: data definitions
2 SAE J1939 series of documents: DTC definitions
Figure 1 — SAE digital annex document reference
0.3 SAE digital annex revision procedure
New regulatory requirements drive new in-vehicle technology to lower emissions, improve safety, etc. It is
important to standardize new technology-related OBD monitor data and diagnostic trouble codes in order to
support the external (off-board) "generic" test equipment. All relevant information is proposed by the
automotive industry represented by members of the appropriate SAE task force.
This part of ISO 27145 references a "Change request form" for use with new data items to be defined by the
SAE task force for standardization. It is intended that the standardized data items be defined in
SAE J1930-DA, SAE J1979-DA, SAE J2012-DA and SAE J1939. It is intended that the documents be
published on the SAE store website once the information has been balloted and approved.
vi © ISO 2012 – All rights reserved

The revision request forms and instructions for updating the registers to ISO 27145 can be obtained on the
following data registration websites.
 For SAE J1930-DA: http://www.sae.org/servlets/works/committeeHome.do?comtID=TEVDS7
The column entitled "Resources" shows a document with the title: J1930-
DA_Revision_Request_Form.doc. Double click on the name to download the document with the filename:
"SAE_J1930-DA_Revision_Request_Form.doc".
 For SAE J1939: http://www.sae.org/
Search "J1939 Request", select "J1939 Request Processing Group", and select " J1939 Request
Processing Form and Guidelines".
 For SAE J1979-DA: http://www.sae.org/servlets/works/committeeHome.do?comtID=TEVDS14
The column entitled "Resources" shows a document with the title: J1979-
DA_Revision_Request_Form.doc. Double click on the name to download the document with the filename:
"SAE_J1979-DA_Revision_Request_Form.doc".
 For SAE J2012-DA: http://www.sae.org/servlets/works/committeeHome.do?comtID=TEVDS9
The column entitled "Resources" shows a document with the title: J2012-
DA_Revision_Request_Form.doc. Double click on the name to download the document with the filename:
"SAE_J2012-DA_Revision_Request_Form.doc".
It is intended that the revision request form be filled out with the request.
It is intended that e-mails with completed revision request forms as attachments be sent to:
E-mail: [e-mail]
E-mail: [e-mail]
E-mail: [e-mail]
E-mail: [e-mail]
INTERNATIONAL STANDARD ISO 27145-2:2012(E)

Road vehicles — Implementation of World-Wide Harmonized
On-Board Diagnostics (WWH-OBD) communication
requirements —
Part 2:
Common data dictionary
1 Scope
This part of ISO 27145 defines all regulatory data elements of the ISO 27145 series. The data elements are
used to provide the external test equipment with the diagnostic status of the vehicle on-board diagnostics
(VOBD) system in the vehicle. All data elements are communicated with the unified diagnostic services as
defined in ISO 27145-3. The data elements are diagnostic trouble codes (DTCs), data identifiers (DIDs) and
routine identifiers (RIDs). The mapping from parameter identifiers (PIDs), monitor identifiers (MIDs) and info
type identifiers (ITIDs) is described in this part of ISO 27145.
If new legislated WWH-OBD GTR modules are established, it is intended that ISO 27145 be applicable with
possible extensions, which can be included in this part of ISO 27145, can be specified as enhancements of
the SAE Digital Annexes or can even be part of other referenced documents which are intended to include the
applicable data definitions.
ISO 27145 is intended to become the single communication standard for access to OBD-related information
(VOBD). To allow for a smooth migration from the existing communication standards to this future world-wide
communication standard, the communication concept as specified in ISO 27145-4 is based on two different
data links: ISO 15765-4 and ISO 13400 (all parts).
In view of the usage of standard network layer protocols, future extensions to optional physical layers (e.g.
wireless) are possible.
NOTE It is expected to extend ISO 27145-4 as necessary upon introduction of additional communication media.
ISO 27145-4 is the entry point to establish communication with the vehicle. Based on the results of the
initialization, the external test equipment determines which protocol and diagnostic services are supported by
the vehicle's emissions-related system, i.e.
 legislated OBD: ISO 15031 series, and
 legislated WWH-OBD: ISO 27145.
Vehicles according to ISO 27145 provide VOBD system support as envisioned for WWH-OBD by Global
Technical Regulation (GTR) No. 5.
IMPORTANT — Use cases deriving from country-specific implementation of GTR No. 5 into local
legislation are not included in this part of ISO 27145.
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
1 )
ISO 14229-1:— , Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and
requirements
ISO 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer interfaces
ISO 27145-1, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-
OBD) communication requirements — Part 1: General information and use case definition
ISO 27145-3, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-
OBD) communication requirements — Part 3: Common message dictionary
ISO 27145-4, Road vehicles — Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-
OBD) communication requirements — Part 4: Connection between vehicle and test equipment
SAE J1939, Companion Spreadsheet
SAE J1939-73:2010, Application layer — Diagnostics
SAE J1979-DA, Digital Annex of E/E Diagnostic Test Modes
SAE J2012-DA, Digital Annex of Diagnostic Trouble Code Definitions and Failure Type Byte Definitions
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions given in ISO 27145-1 and ISO 14229-1
apply.
3.1.1
calibration identifier
CALID
identification code for the software installed in the electronic control unit
3.1.2
calibration verification number
CVN
server/ECU calculated verification number used to verify the integrity of the software in the electronic control
unit
3.1.3
central gateway
CGW
electronic control unit that connects in-vehicle communication networks
3.1.4
data identifier
DID
indicator making reference to a data item in the server

1)
To be published. (Revision of ISO 14229-1:2006)
2 © ISO 2012 – All rights reserved

3.1.5
diagnostic trouble code
DTC
value making reference to a specific fault in a system implemented in the server
NOTE It is defined in SAE J2012-DA or as SPN and FMI as defined in SAE J1939 Companion Spreadsheet and
SAE J1939-73:2010, Appendix A.
3.1.6
info type identifier
ITID
indicator making reference to identification information
EXAMPLE Calibration identifier in the server.
NOTE The ITIDs are defined in SAE J1979-DA.
3.1.7
malfunction indicator
MI
display or gauge that clearly informs the driver of the vehicle in the event of a malfunction/failure
NOTE Additional details are included in the WWH-OBD GTR.
3.1.8
monitor identifier
MID
indicator making reference to an OBD monitor function
NOTE An example of an OBD monitor function is a misfire monitor in the server. The MID is defined in
SAE J1979-DA.
3.1.9
standard/manufacturer monitor test identifier
SMTID
OBD identifier which is defined in SAE J1979-DA or by the vehicle manufacturer
3.1.10
parameter identifier
PID
unique identifier used to refer to a specific data value within a server
3.1.11
routine identifier
RID
identifier making reference to a routine function
NOTE 1 An example of a routine function is an evaporation monitor routine in the server.
NOTE 2 Routine identifiers are defined in SAE J1979-DA.
3.1.12
suspect parameter number
SPN
numeral that identifies a particular element, a fault associated with a component, such as a sensor, or a
parameter associated with an ECU
3.1.13
uniform resource locator
URL
uniform resource identifier which, in addition to identifying a resource, provides a means of locating the
resource by describing its primary access mechanism
NOTE An example of primary access mechanism is its network location.
3.2 Abbreviated terms
CALID calibration identification
CAN controller area network
CGW central gateway
CM conversion method
CVN calibration verification number
DID data identifier
DoCAN diagnostics communication over controller area network
DoIP diagnostics communication over internet protocol
DP data parameter
DP_DB data parameter data byte
DTC diagnostic trouble code
ECM engine control module
ECU electronic control unit
ECUNAME electronic control unit name
EVAP evaporative system
FMI failure mode indicator
FTB failure type byte
GTR global technical regulation
ITID info type identifier
IUPT in-use performance tracking
ITP info type parameter
ITP_DB info type parameter data byte
MI malfunction indicator
MID monitor identifier
Mod module
MP monitor parameter
MP_DB monitor parameter data byte
N/A not applicable
OC occurrence count
Param parameter
PID parameter identifier
req requirement
RID routine identifier
4 © ISO 2012 – All rights reserved

RP_DB routine parameter data byte
SF sub-function
SID service identifier
SMTID standard/manufacturer monitor test identifier
SPN suspect parameter number
URL uniform resource locator
VIN vehicle identification number
VOBD vehicle on-board diagnostics
WWH-OBD world-wide harmonized on-board diagnostics
4 Conventions
The ISO 27145 series is based on the conventions discussed in the OSI Service Conventions
(ISO/IEC 10731) as they apply to diagnostic services.
5 Document overview
Figure 2 shows the reference documents for the ISO 27145 series.
The ISO 27145 series specifies or includes the following references.
a) ISO 27145-1 specifies the general structure of the ISO 27145 series and the WWH-OBD GTR applicable
use cases.
b) This part of ISO 27145 specifies the common data dictionary with references to the following documents:
1) SAE J1930-DA, which defines the terms, definitions, abbreviated terms, etc.;
2) SAE J1939 Companion Spreadsheet, which specifies the SPNs;
3) SAE J1939-73:2010, Appendix A, which specifies the FMIs;
4) SAE J1979-DA, which specifies all data items;
5) SAE J2012-DA, which specifies the DTC definitions and FTB definitions.
NOTE The SAE J1939 series of documents are concerned with the definition of emissions-related SPNs and FMIs
for use as DTCs.
c) ISO 27145-3 specifies the diagnostic services defined in ISO 14229-1 that are applicable to WWH-OBD
GTR.
d) ISO 14229-2 specifies the standardized service primitive interface to separate application and session
layers from protocol transport and network layers.
e) ISO 27145-4 specifies the initialization procedure and includes references to
1) ISO 15765-4 DoCAN, and
2) ISO 13400 (all parts) DoIP.

Unified diagnostic services (UDS)
ISO 27145-1
WWH-OBD
general information and
use case definition
ISO 27145-3
ISO 14229-1 UDS SAE J1930-DA
1 : 1
WWH-OBD
subset Terms , .
specification and
OSI layer 7
common message
requirements
Application
dictionary
SAE J1979-DA
1 : 1
PIDs, MIDs, RIDs,
ITIDs
ISO 27145-2
WWH-OBD
OSI layer 6
common data
Presentation
dictionary
SAE J2012-DA
1 : 1
WWH-OBD DTCs
SAE J1939 Companion
ISO 14229-2 UDS ISO 14229-2 UDS
1 : 1
OSI layer 5
Spreadsheet
session layer interfaces session layer interfaces
subset
Session SAE J1939-73:2011,
Appendix A
Standardized service primitive interface
Diagnostic communication over CAN and Internet Protocol
DoCAN DoIP
OSI layer 4
Transport
ISO 15765-2 DoCAN
ISO 13400-2 DoIP
transport protocol
transport protocol
and
and
network
network
layer services
layer services
OSI layer 3
Network
ISO 27145-4
ISO 15765-4 DoCAN
WWH-OBD
requirements for
emissions-related connection between
vehicle and test
systems
equipment
OSI layer 2
ISO 11898-1 CAN
Data link
data link layer
ISO 13400-3 DoIP
and physical signalling
wired vehicle
interface based
ISO 11898-2 CAN
on IEEE 802.3
high-speed
medium access unit
OSI layer 1
Physical
Figure 2 — Reference documents for implementation of WWH-OBDonCAN and WWH-OBDonIP
according to the OSI model
6 © ISO 2012 – All rights reserved

6 Common data dictionary requirements
6.1 Data range layout
This subclause specifies the reserved ranges for DIDs and RIDs.
IMPORTANT — DIDs and RIDs do not share the same 2-byte range.
ISO 14229-1 reserves the DID/MID/ITID/RID ranges.
6.2 Diagnostic trouble code (DTC) range layout
This subclause specifies the data range layout for DTCs, which is backward compatible to the existing
standards:
 the DTC definition in SAE J2012-DA for all BaseDTCs and FailureTypeBytes (FTB);
 the DTC definition in SAE J1939 Companion Spreadsheet (SPN), and SAE J1939-73:2010, Appendix A
(FMI).
This part of ISO 27145 defines a 3-byte DTC range, which consists of a BaseDTC number and a
FailureTypeByte (FTB), both defined in SAE J2012-DA, or an SPN and an FMI, both defined in SAE J1939
Companion Spreadsheet (SPN) and SAE J1939-73:2010, Appendix A.
Figure 3 depicts an overview of the DTC range definitions.
LSB
MSB
SAE J2012-DA 16 bits WWH -OBD BaseDTC Number (SAE J2012-DA WWH-OBD) 8 bits FTB
ISO 27145-2 DTCHighByte DTCMiddleByte DTCLowByte
SAE J1939 Three most
Eight least significant bits of SPN Second byte of SPN significant 5 bits FMI
Companion
bits of SPN
Spreadsheet
Figure 3 — Overview of the DTC range definitions
Table 2 provides an overview of the available DTC range as specified in SAE J2012-DA and SAE J1939
Companion Spreadsheet (SPN) and SAE J1939-73:2010, Appendix A (FMI).
Table 2 — WWH-OBD DTC ranges as defined in this part of ISO 27145
DTC range BaseDTC range FTB/FMI range DTC mnemonic Description
0x000000
16 8
16 bits = 2 -1 = FTB: 8 bits 2 = SAE_J2012-DA_ DTCs as defined in
–
65535 256 DTCFormat_04 SAE J2012-DA WWH-OBD
0xFFFFFF
SPNs as defined in SAE J1939,
0x000000 19 5 Companion Spreadsheet,
19 bits = 2 -1 = FMI: 5 bits 2 =
– SAE_J1939-73_DTCFormat and FMIs as defined in
524287 32
0xFFFFFF SAE J1939-73:2010,
Appendix A
7 Data identifier and routine identifier data record requirements
7.1 Data identifier and routine identifier definitions
7.1.1 ISO 14229-1 and SAE J1979-DA DID/RID mapping
The DIDs and RIDs are of different size depending on the specification from which they derive:
 SAE J1979-DA specifies 1-byte DIDs (PIDs, MIDs, ITIDs) and RIDs;
 ISO 14229-1:—, Annex C, supports 2-byte DIDs and RIDs.
Figure 4 shows how the 2-byte data identifier and routine identifier are defined based on the SAE J1979-DA
specification.
The "low byte" of the 2-byte identifier is derived from the 1-byte SAE J1979-DA defined identifiers. The "high
byte" of the 2-byte data identifier is defined in ISO 14229-1.
ISO 27145-2
High Byte Low Byte
XX XX
ISO 14229-1:—,
SAE J1979-DA
Annex C
Figure 4 — 2-byte DID and RID assembly

7.1.2 DID (PID, MID and ITID) and RID-supported definition
The vehicle system supports a subset of DID (PID, MID, ITID) and RID based on the emissions regulation to
which the vehicle shall comply.
The concept of supporting DIDs (PIDs, MIDs, ITIDs) is carried out with service ReadDataByIdentifier with the
DID (PID, MID, ITID) (low byte = 0x00/0x20/0x40/0x60/0x80/0xA0/0xC0) as specified in SAE J1979-DA.
The concept of supporting RIDs is carried out with service RoutineControl with the RID (low byte = 0x00) as
specified in SAE J1979-DA.
7.2 DID and RID data record definition
7.2.1 Supported data types
7.2.1.1 General
The message format as specified in ISO 27145-3 uses a 2-byte DID in service ReadDataByIdentifier as a
label for a dataRecord[] including the data parameters, e.g. PID data, MID data, ITID data.
8 © ISO 2012 – All rights reserved

The message format as specified in ISO 27145-3 uses a 2-byte RID in service RoutineControl as a label for a
routineStatusRecord[] including the data parameters, e.g. RID data.
A data parameter can either be of status type (discrete) or of measured type (analogue).
Status specifies the present state of a multi-state parameter or function as a result of action taken by the
transmitting server. This action is the result of a calculation, which uses local and/or network "measured" and
"status" information.
EXAMPLE 1 Status-type data are: engine brakes are enabled, cruise control is active, the cruise control is in the "set"
state of operation (as opposed to a measured indication that the "set" switch contacts are closed), diagnostic trouble
codes, torque/speed control override modes, desired speed/speed limit, engine torque mode, engine's desired operating
speed, engine's operating speed asymmetry adjustment, etc.
Measured data convey the current value of a parameter as measured or observed by the transmitting server
to determine the condition of the defined parameter.
EXAMPLE 2 Measured-type data are: boost pressure, ignition on/off, cruise set switch activated, maximum cruise
speed, cruise set speed, engine speed, % load at current speed, etc.
A RoutineControl can be either to request which routines are implemented in the server or to request that the
server start executing a routine.
EXAMPLE 3 RoutineStatusRecords are: Evaporative system leak test; Diesel particulate filter regeneration.
7.2.1.2 ISO LATIN 1 ASCII character set
The servers shall implement those characters which are required to report information as specified in
SAE J1979-DA.
7.2.2 dataRecord[] structure definition
7.2.2.1 Overview
The dataRecord[] is included in the response message of the ReadDataByIdentifier service as specified in
ISO 27145-3.
A dataRecord[] consists of one of the following three dataRecords[] and each dataRecord[] is specified by a
DID:
 PID dataRecord[] SAE J1979-DA Parameter Identifier data record including Data Parameter(s) (DP), or
 MID dataRecord[] SAE J1979-DA Monitor Identifier data record including Monitor Parameter(s) (MP), or
 ITID dataRecord[] SAE J1979-DA InfoType Identifier data record including InfoType Parameter(s) (ITP).
IMPORTANT — The DID dataRecord always starts with A_Data byte #4 because it is preceded by the
Service Identifier (SID) of the message and the 2-byte Data Identifier (DID).
7.2.2.2 PID dataRecord[] with SAE J1979-DA PID data
Table 3 specifies the PID dataRecord[] with SAE J1979-DA derived parameters.
Table 3 — PID dataRecord[] definition
A_Data byte Parameter name Cvt Byte Value Mnemonic
PID dataRecord[] = [  PID_DREC_
#4 DP_DB#1 M 0x00-0xFF DP_DB#1
: : : : :
#n DP_DB#k] C 0x00-0xFF DP_DB#k
C : The parameter is only present if defined in the PID dataRecord[] of the referenced PID in SAE J1979-DA.
See ISO 27145-3 for the definition of the ReadDataByIdentifier service.
Table 4 specifies the parameters of the PID dataRecord[] included in the positive response message of the
ReadDataByIdentifier service.
Table 4 — PID dataRecord[] response message data parameter definition
Definition
PID dataRecord[]
This parameter is used by the ReadDataByIdentifier positive response message to provide the requested data record
values to the client. The content of the PID dataRecord[] is defined in SAE J1979-DA.
DP_DB#1–#k (Data Parameter Data Byte)
The Data Parameter data may consist of analogue (A/D converter), discrete (input/output states) or internal WWH-OBD
system data.
10 © ISO 2012 – All rights reserved

7.2.2.3 MID dataRecord[] with SAE J1979-DA Monitor ID data
Table 5 specifies the MID dataRecord[] with SAE J1979-DA derived parameters.
Table 5 — MID dataRecord[] definition
A_Data byte Parameter name Cvt Byte value Mnemonic
MID dataRecord[]#1 = [  MID_DREC#1_
#4 MP_SMTID; Monitor Param. Std/Manuf. Test ID M 0x00-0xFF MP_SMTID
#5 MP_UASID; Monitor Param. Unit and Scaling ID M 0x00-0xFF MP_UASID
#6 MP_TVHI; Monitor Param. Test Value (HB) M 0x00-0xFF MP_TVHI
#7 MP_TVLO; Monitor Param. Test Value (LB) M 0x00-0xFF MP_TVLO
#8 MP_MINTLHI; Monitor Param. Min. Test Limit (HB) M 0x00-0xFF MP_MINTLHI
#9 MP_MINTLLO; Monitor Param. Min. Test Limit (LB) M 0x00-0xFF MP_MINTLLO
#10 MP_MAXTLHI; Monitor Param. Max. Test Limit (HB) M 0x00-0xFF MP_MAXTLHI
#11 MP_MAXTLLO; Monitor Param. Max. Test Limit (LB) M 0x00-0xFF MP_MAXTLLO
]
: : : : :
MID dataRecord[]#k = [  MID_DREC#k_
#n-7 MP_SMTID; Monitor Param. Std/Manuf. Test ID C 0x00-0xFF MP_SMTID
#n-6 MP_UASID; Monitor Param. Unit and Scaling ID C 0x00-0xFF MP_UASID
#n-5 MP_TVHI; Monitor Param. Test Value (HB) C 0x00-0xFF MP_TVHI
#n-4 MP_TVLO; Monitor Param. Test Value (LB) C 0x00-0xFF MP_TVLO
#n-3 MP_MINTLHI; Monitor Param. Min. Test Limit (HB) C 0x00-0xFF MP_MINTLHI
#n-2 MP_MINTLLO; Monitor Param. Min. Test Limit (LB) C 0x00-0xFF MP_MINTLLO
#n-1 MP_MAXTLHI; Monitor Param. Max. Test Limit (HB) C 0x00-0xFF MP_MAXTLHI
#n MP_MAXTLLO; Monitor Param. Max. Test Limit (LB) C 0x00-0xFF MP_MAXTLLO
]
C : The parameter is only present if the monitor referred to by the MID uses more than one Monitor Parameter Standard/Manufacturer
Test ID (MP_SMTID).
Multiple Monitor Parameter Standard/Manufacturer Test IDs may be supported for a single OBD Monitor ID. In
such a case, a MID dataRecord[] is included in the response message for each Monitor Parameter
Standard/Manufacturer Test ID supported by the OBD Monitor ID.
NOTE The second and following MID dataRecords[] are not preceded by the 2-byte Monitor Identifier (MID). Those
MID dataRecords[] include Monitor Parameter Standardized/Manufacturer Test ID (MP_SMTID) specific data. An MID can
make reference to more than one MP_SMTID.
See ISO 27145-3 for definition of the ReadDataByIdentifier service.
Table 7 specifies the parameters of the MID dataRecord[] included in the positive response message of the
ReadDataByIdentifier service.
Table 6 — MID dataRecord response message data parameter definition
Definition
MID dataRecord[] (#1 to #k)
This parameter is used by the ReadDataByIdentifier positive response message to provide the requested data record
values to the client. The content of the MID dataRecord[] is defined in this part of ISO 27145.
MP_SMTID (Monitor Parameter Standardized and Manufacturer Test ID)
The Standardized and Manufacturer Defined Test ID is a 1-byte parameter. Many OBD monitors have multiple tests,
which are carried out in either a serial or parallel manner. If a monitor uses multiple OBD Monitor ID/Test ID
combinations and it is possible for them not to be completed at the same time, the following method shall be used to
update the stored test results at the time of monitor completion:
After the monitor completes, update all Monitor ID/Test ID combinations (or "test results") which were utilized by the
monitor with appropriate passing or failing results. If a test result (or “Monitor ID/Test ID”) was not utilized during this
monitoring event, set the Test Values and Minimum and Maximum Test Limits to their initial values (0x0000, test not
completed). Test results from the previously completed monitoring events shall not be mixed with test results from the
currently completed monitoring event.
In some cases, test results (or "Monitor ID/Test ID combinations") are displayed as being incomplete even though the
monitor (as indicated by PID 0xF441) was successfully completed and either passed or failed. In other cases, some Test
IDs show passing results while others show failing results after the monitor (as indicated by PID 0x41) was successfully
completed and failed. Note that OBD-II regulations prohibit a passing monitor from showing any failing test results. If an
initial, serial test indicates a failure and a subsequent retest of the system indicates a passing result, the test that was
utilized to make the passing determination should be displayed, while the failing test that was utilized to make the initial
determination should be reset to its initial values (0x0000, test not completed).
EXAMPLE A serial monitor, e.g. an evaporative system monitor, can fail for a large evaporative system leak and never continue to
test for small leaks or very small leaks. In this case, the Test ID for the large leak shows a failing result, while the small leak test and the very
small leak test show incomplete. As an example of the parallel monitor, a purge valve flow monitor can pass by having a large rich lambda
shift, a large lean lambda shift or a large engine r/min increase. If the purge valve is activated and a large rich lambda shift occurs, the Test
ID for the rich lambda shift shows a passing result while the other two Test IDs show incomplete. Since some Test IDs for a completed
monitor can show incomplete, DPID "Monitor status this driving cycle" shall be used to determine monitor completion status.
MP_UASID (Monitor Parameter Unit and Scaling ID)
The Unit and Scaling ID is a 1-byte identifier for making reference to the scaling and unit to be used by the external test
equipment to calculate and display the test values (results), Minimum Test Limit, and the Maximum Test Limit for the
Standardized and Manufacturer Defined Test ID requested. All standardized Unit And Scaling IDs are specified in
SAE J1979-DA.
MP_TVHI and MP_TVLO (Monitor Parameter Test Value)
Test Value (Result) — This value is a 2-byte parameter and shall be calculated and displayed by the external test
equipment based on the Unit and Scaling ID included in the response message. The Test Value shall be within the
Minimum and Maximum Test Limit to indicate a "Pass" result.
MP_MINTLHI and MP_MINTLLO (Monitor Parameter Minimum Test Limit High and Low )
The Minimum Test Limit is a 2-byte parameter and shall be calculated and displayed by the external test equipment
based on the Unit and Scaling ID included in the response message. The Unit and Scaling IDs are specified in
SAE J1979-DA. The Minimum Test Limit shall be the minimum value for the monitor identified by the On-Board
Diagnostic Monitor ID. For the Standardized Test IDs that are constant values, the Minimum Test Limit shall be the same
value as reported for the Test Value.
The following conditions apply:
 if the Test Value is less than the Minimum Test Value, this results in a "Fail" condition;
 if the Test Value equals the Minimum Test Value, this results in a "Pass" condition;
 if the Test Value is greater than the Minimum Test Value, this results in a "Pass" condition.
MP_MAXTLHI and MP_MAXTLLO (Monitor Parameter Maximum Test Limit High and Low)
The Maximum Test Limit is a 2-byte parameter and shall be calculated and displayed by the external test equipment
based on the Unit and Scaling ID included in the response message. The Unit and Scaling IDs are specified in
SAE J1979-DA. The Maximum Test Limit shall be the maximum value for the monitor identified by the OBD Monitor ID.
For the Standardized Test IDs, that are constant values, the Maximum Test Limit shall be the same value as reported for
the Test Value.
The following conditions apply:
 if the Test Value is less than the Maximum Test Value, this results in a "Pass" condition;
 if the Test Value equals the Maximum Test Value, this results in a "Pass" condition;
 if the Test Value is greater than the Maximum Test Value, this results in a "Fail" condition.
12 © ISO 2012 – All rights reserved

7.2.2.4 ITID dataRecord[] with SAE J1979-DA InfoType ID data
Table 7 specifies the ITID dataRecord[] with SAE J1979-DA derived parameters.
Table 7 — ITID dataRecord[] definition
A_Data byte Parameter name Cvt Byte value Mnemonic
ITID dataRecord[]#1 = [  ITID_DREC_
#4 ITP_DB#1; InfoType Param. Data Byte #1 C 0x00-0xFF ITP_DB#1
#5 ITP_DB#2; InfoType Param. Data Byte #2 C 0x00-0xFF ITP_DB#2
: : : : :
#n ITP_DB#k; InfoType Param. Data Byte #k C 0x00-0xFF ITP_DB#k
]
C : The parameter is only present if defined in the ITID dataRecord[] of the referenced ITID in SAE J1979-DA.
See ISO 27145-3 for the definition of the ReadDataByIdentifier service.
Table 8 specifies the InfoType parameters of the ITID dataRecord[] included in the positive response message
of the ReadDataByIdentifier service.
Table 8 — ITID dataRecord[] response message data parameter definition
Definition
ITID dataRecord[]
This parameter is used by the ReadDataByIdentifier positive response message to provide the requested data record
values to the client. The content of the ITID dataRecord[] is defined in SAE J1979-DA.
ITP_DB (InfoType Parameter Data Byte)
The InfoType Parameter data may consist of VIN, CALID, CVN, ECUNAME, IUPT and other InfoType data expected to
be defined in the future.
7.2.3 RID routineStatusRecord[] definition
Table 9 specifies the RID routineStatusRecord[] with SAE J1979-DA derived parameters.
Table 9 — RID routineStatusRecord[] definition
A_Data byte Parameter name Cvt Byte value Mnemonic
RID routineStatusRecord[] = [  RID_DREC_
#6 RP_DB#1; routineStatus #1 C 0x00-0xFF RP_DB#1
: : : : :
#n RP_DB#k; routineStatus #k C 0x00-0xFF RP_DB#k
]
C : The routineStatus #1–#k shall only be included in the RID routineStatusRecord[] if specified for the routineIdentifier (RID) in
SAE J1979-DA.
IMPORTANT — The RID routineStatusRecord[] always starts with A_Data byte #6 because it is
preceded by the Service Identifier 1-byte (SID) of the message, 1-byte sub-function, 2-byte
routineIdentifier (RID) and the 1-byte routineInfo (see ISO 27145-3) parameter.
See ISO 27145-3 for the definition of the RoutineControl service.
Table 10 specifies the parameters of the RID routineStatusRecord[] included in the positive response
message of the service RoutineControl.
Table 10 — RID routineStatusRecord[] response message data parameter definition
Definition
RID routineStatusRecord[]
This parameter is used by the RoutineControl positive response message to provide the requested data record values to
the client. The content of the RID routineStatusRecord[] is defined in SAE J1979-DA.
RP_DB (Routine Parameter Data Byte)
The Routine Parameter data (routineStatus #1 – routineStatus #k) are defined in SAE J1979-DA for each
routineIdentifier (RID).
8 Diagnostic trouble code definition
8.1 Overview
The ReadDTCInformation service as specified in ISO 27145-3 defines a 3-byte diagnostic trouble code format
in order to provide backward compatibility to the:
 SAE J2012-DA defined DTC format;
 SAE J1939 Companion Spreadsheet (SPN) and SAE J1939-73:2010, Appendix A (FMI), defined DTC
format.
Each DTC format is supported by the ReadDTCInformation or ClearDTCInformation service as specified in
ISO 27145-3. Each DTC format is identified by the DTCFormatIdentifier as specified in ISO 27145-3.
Figure 5 illustrates the mapping of DTCs defined by SAE J2012-DA and SAE J1939 Companion Spreadsheet
(SPN) and SAE J1939-73:2010, Appendix A, into the ISO 27145-3 format.
DTCHighByte DTCMiddleByte DTCLowByte
16 bits WWH -OBD BaseDTC number 8 bits FailureTypeByte
Any SAE J 2012-DA WWH-OBD DTC (16 bits ) SAE J2012-DA FTB (8 bits )
23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
ISO 27145-2 WWH-OBD DTC format (24 bits )
23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Three most
Eight least significant bits of SPN Second byte of SPN significant 5 bits FMI
Bits of SPN
Figure 5 — Overview of DTC format mapping

14 © ISO 2012 – All rights reserved

8.2 SAE J2012-DA and SAE J1939-73 DTCs
8.2.1 SAE J2012-DA DTC format definition
SAE J2012-DA defines 3-byte DTCs (2-byte BaseDTC + 1-byte FTB). Each DTC number represents a unique
fau
...