ISO/PAS 27145-2:2006

Road vehicles - Implementation of WWH-OBD communication requirements - Part 2: Common emissions-related data dictionary

ISO/PAS 27145-2:2006 defines all regulatory emissions-related data elements of ISO/PAS 27145. The data elements are used to provide the external test equipment with the diagnostic status of the emissions-related system in the vehicle. All data elements are communicated with the unified diagnostic services as defined in ISO/PAS 27145-3. Data elements are Diagnostic Trouble Codes (DTCs), Parameter Identifiers (PIDs), Monitor Identifiers (MIDs), Test Identifiers (TIDs)/Routine Identifiers (RIDs) and InfoType Identifiers (ITIDs).

Véhicules routiers — Mise en application des exigences de communication WWH-OBD — Partie 2: Dictionnaire de données liées aux émissions communes

General Information

• Status: Withdrawn
• Publication Date: 26-Sep-2006
• Withdrawal Date: 26-Sep-2006
• ICS: 43.040.10 - Electrical and electronic equipment
• ICS: 43.180 - Diagnostic, maintenance and test equipment
• Technical Committee: ISO/TC 22 - Road vehicles
• Drafting Committee: ISO/TC 22 - Road vehicles
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 14-Aug-2012
• Completion Date: 13-Dec-2025

Relations

• Revised: ISO 27145-2:2012 - Road vehicles - Implementation of World-Wide Harmonized On-Board Diagnostics (WWH-OBD) communication requirements - Part 2: Common data dictionary
• Effective Date: 15-Apr-2008

Standards Content (Sample)

PUBLICLY ISO/PAS
AVAILABLE 27145-2
SPECIFICATION
First edition
2006-09-15
Road vehicles — Implementation of
WWH-OBD communication
requirements —
Part 2:
Common emissions-related data
dictionary
Véhicules routiers — Mise en application des exigences de
communication WWH-OBD —
Partie 2: Dictionnaire de données liées aux émissions communes

Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2006
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 2006 – All rights reserved

Contents Page
Foreword. v
Introduction . vi
1 Scope . 1
2 Normative references . 2
3 Terms and definitions. 4
4 Symbols and abbreviated terms . 6
5 Conventions . 8
6 Common data dictionary. 8
7 Data identifier and data record requirements. 10
7.1 Legacy data identifiers. 10
7.1.1 ISO 15031-5 and ISO 14229-1 legacy DID definition. 10
7.1.2 Legacy ISO 15031-5 identifier supported definition. 12
7.1.3 Legacy data record definition. 12
7.1.4 SAE J1939 legacy data identifier definition .16
7.2 Unified data identifiers . 18
7.2.1 Unified data identifier range layout. 18
7.2.2 Unified data identifier supported definition . 19
7.3 Unified data record definition. 21
7.3.1 Overview . 21
7.3.2 Remotely received sub-node information and validity. 22
7.3.3 SignalAttribute (SA) A1 and A2 definition. 24
7.3.4 Supported data types . 29
7.3.5 Unified PID data record structure . 31
7.3.6 Unified MID data record structure. 37
7.3.7 Unified InfoType ID data record structure. 37
7.3.8 Unified RID data record structure . 37
7.3.9 Unified CID data record structure . 37
7.4 Manufacturer data identifier . 37
7.4.1 Manufacturer data identifier range layout. 37
7.4.2 Manufacturer data parameter requirements . 38
8 Diagnostic Trouble Code definition. 38
8.1 Overview . 38
8.2 Legacy DTCs . 40
8.2.1 ISO 15031 legacy DTC to unified DTC mapping . 40
8.2.2 ISO 15031-6 legacy DTC encoding. 40
8.2.3 SAE J1939-73 legacy DTC to unified DTC mapping. 41
8.2.4 SAE J1939-73 legacy DTC number encoding . 43
8.3 Unified DTC . 43
8.3.1 Unified DTC range layout. 43
8.3.2 Unified DTC format . 44
8.3.3 Unified DTC encoding . 44
8.3.4 BaseDTC supported Unified PID data record structure. 44
8.4 Manufacturer DTC. 45
8.4.1 Manufacturer DTC range layout . 45
8.4.2 Manufacturer DTC based on unified DTC format . 45
8.4.3 Manufacturer DTC encoding. 46
Annex A (informative) Referenced document information source and content description. 47
Annex B (normative) Standard and DTC specific set of emissions-related legacy PIDs. 49
Bibliography . 50

iv © ISO 2006 – All rights reserved

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.
In other circumstances, particularly when there is an urgent market requirement for such documents, a
technical committee may decide to publish other types of normative document:
⎯ an ISO Publicly Available Specification (ISO/PAS) represents an agreement between technical experts in
an ISO working group and is accepted for publication if it is approved by more than 50 % of the members
of the parent committee casting a vote;
⎯ an ISO Technical Specification (ISO/TS) represents an agreement between the members of a technical
committee and is accepted for publication if it is approved by 2/3 of the members of the committee casting
a vote.
An ISO/PAS or ISO/TS is reviewed after three years in order to decide whether it will be confirmed for a
further three years, revised to become an International Standard, or withdrawn. If the ISO/PAS or ISO/TS is
confirmed, it is reviewed again after a further three years, at which time it must either be transformed into an
International Standard or be withdrawn.
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/PAS 27145-2 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
ISO/PAS 27145 consists of the following parts, under the general title Road vehicles — Implementation of
WWH-OBD communication requirements:
⎯ Part 1: General information and use case definition
⎯ Part 2: Common emissions-related data dictionary
⎯ Part 3: Common message dictionary
⎯ Part 4: Connection between vehicle and test equipment
NOTE ISO/PAS 27145-4 will be extended as necessary due to introduction of additional communication media.

Introduction
This document set includes the communication between the vehicle's OBD systems and test equipment
implemented across vehicles within the scope of the WWH-OBD GTR (World Wide Harmonized On-Board
Diagnostics Global Technical Regulations).
It has been established in order to apply the unified diagnostic services (specified in ISO 14229-1) to WWH
OBD systems.
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 into seven layers. When
mapped on this model, the services specified by ISO/PAS 27145 are broken into:
⎯ Application layer (layer 7), specified in ISO/PAS 27145-3;
⎯ Presentation layer (layer 6), specified in ISO/PAS 27145-2;
⎯ Session layer services (layer 5), specified in ISO/PAS 27145-4;
⎯ Transport layer services (layer 4), specified in ISO/PAS 27145-4;
⎯ Network layer services (layer 3), specified in ISO/PAS 27145-4;
⎯ Data link layer (layer 2), specified in ISO/PAS 27145-4; and
⎯ Physical layer (layer 1), specified in ISO/PAS 27145-4;
in accordance with Table 1.
Table 1 — Enhanced and legislated OBD diagnostic specifications applicable to the OSI layers
Implementation of WWH-OBD communication
Applicability OSI 7 layers
requirements, e.g. emissions-related UDS
Application (layer 7) ISO/PAS 27145-3 / ISO 14229-1
Presentation (layer 6) ISO/PAS 27145-2
Session (layer 5)
Seven layers
according to
Transport (layer 4)
ISO/IEC 7498-1 and
ISO/IEC 10731
ISO/PAS 27145-4
Network (layer 3)
Data link (layer 2)
Physical (layer 1)
vi © ISO 2006 – All rights reserved

PUBLICLY AVAILABLE SPECIFICATION ISO/PAS 27145-2:2006(E)

Road vehicles — Implementation of WWH-OBD communication
requirements —
Part 2:
Common emissions-related data dictionary
1 Scope
ISO/PAS 27145 is intended to become the single communication standard for access to OBD-related
information. To allow for a smooth migration from the existing communication standards to this future
worldwide standardized communication standard, the initial communication concept will be based on CAN. In
a second step, ISO/PAS 27145 will be extended to define the world-wide harmonized OBD communication
standard based on existing industry communications standards (e.g. Internet Protocol) over Ethernet. Due to
the usage of standard network layer protocols, future extensions to optional physical layers (e.g. wireless) are
possible.
This part of ISO/PAS 27145 defines all regulatory emissions-related data elements of ISO/PAS 27145. A new
part may be added in the future upon availability of new legislated WWH-OBD GTR modules. The data
elements are used to provide the external test equipment with the diagnostic status of the emissions-related
system in the vehicle. All data elements are communicated with the unified diagnostic services as defined in
ISO/PAS 27145-3. Data elements are Diagnostic Trouble Codes (DTCs), Parameter Identifiers (PIDs),
Monitor Identifiers (MIDs), Test Identifiers (TIDs)/Routine Identifiers (RIDs) and InfoType Identifiers (ITIDs).
This part of ISO/PAS 27145 defines three (3) different sets of data elements:
a) A legacy (backward compatible) data set as defined in SAE J1939-71/-73 and ISO 15031-5/ISO 15031-6;
b) A unified data set (new data definition according to ISO/PAS 27145-2); and
c) A manufacturer data set (defined by manufacturer).
Each set of data elements uses its own scaling and encoding scheme. Legacy data elements are scaled and
encoded according the definitions in SAE J1939-71/-73 and ISO 15031-5/ISO 15031-6. Unified data elements
are scaled and encoded according to the definitions in ISO/PAS 27145-2. Manufacturer data elements are
recommended to be scaled and encoded according to the definitions of the unified data set. This will ease the
transfer of manufacturer defined data elements into the standardized (unified) data range.
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.
ISO 7498-1, Information technology — Open Systems Interconnection — Basic Reference Model — Part 1:
The Basic Model
ISO/IEC 10731, Information technology — Open Systems Interconnection — Basic Reference Model —
Conventions for the definition of OSI services
ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO/TS 15031-2, Road vehicles — Communication between vehicle and external equipment for emissions-
related diagnostics — Part 2: Terms, definitions, abbreviations and acronyms
ISO 15031-5, Road vehicles — Communication between vehicle and external test equipment for emissions-
related diagnostics — Part 5: Emissions-related diagnostic services
ISO 15031-6, Road vehicles — Communication between vehicle and external test equipment for emissions-
related diagnostics — Part 6: Diagnostic trouble code definitions
ISO/PAS 27145-1, Road vehicles — Implementation of WWH-OBD communication requirements — Part 1:
General information and use case definition
ISO/PAS 27145-3, Road vehicles — Implementation of WWH-OBD communication requirements — Part 3:
Common message dictionary
ISO/PAS 27145-4, Road vehicles — Implementation of WWH-OBD communication requirements — Part 4:
Connection between vehicle and test equipment
SAE J1939-21, Recommended Practice for a Serial Control and Communication Vehicle Network — Data link
layer
SAE J1939-71, Recommended Practice for a Serial Control and Communication Vehicle Network — Vehicle
application layer
SAE J1939-73, Recommended Practice for a Serial Control and Communication Vehicle Network —
Application layer — Diagnostics
OBD_E_LDATA, OBD emissions-related data definitions
OBD_E_LDTC, OBD emissions-related diagnostic trouble code definitions
WWH-OBD_E_UDATA_UDTC, WWH-OBD emissions-related unified data and DTC definitions
2 © ISO 2006 – All rights reserved

Figure 1 — WWH-OBD external document reference concept illustrates a master document (ISO/PAS 27145-2)
and the reference to existing standards (legacy emissions data and DTCs) as well as the reference to new
documents which define the Unified Data Identifiers and Unified DTCs based on the requirements deriving
from the WWH-OBD GTR.
The ISO/PAS 27145-2 referenced documents are available via download through a so-called Registration
Office Web Site. See Clause 2 for referenced document file names.

Referenced documents
(Registration Office)
OBD emissions-related
legacy data and DTCs
definitions:
⎝ SAE J1939-71 A
⎝ SAE J1939-73
OBD emissions-related
legacy data definitions:
Master document
⎝ ISO 15031-5
B
⎝ ISO 14229-1
ISO 27145-2
WWH-OBD
Common Emissions
Data Dictionary
OBD emissions-related
legacy DTC definitions:
⎝ ISO 15031-6
C
⎝ ISO 14229-1
WWH-OBD
emissions-related
unified data and DTC
D
definitions:
⎝ ISO 27145-2
Key
A External document “SAE J1939-71 and SAE J1939-73” defines emissions-related SPNs, DTCs and PGNs.
B External document “OBD emissions-related legacy data definitions” defines emissions-related data based on
ISO 15031-5 and ISO 14229-1.
C External document “OBD emissions-related legacy diagnostic trouble code definitions” defines emissions-related
DTCs based on ISO 15031-5 and ISO 14229-1.
D External document “WWH-OBD emissions-related Unified Data definitions” defines WWH-OBD emissions-related
unified data identifiers and DTCs required by the WWH-OBD GTR.
Figure 1 — WWH-OBD external document reference concept
See Annex A for detailed document location and content description.
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/PAS 27145-1 and the following
apply.
3.1
Analogue Parameter
AP
signal e.g. PID which is sensed from an Analogue to Digital Converter
3.2
ContinueList
CL
continuation of data records within a UPID_DataRecord[]
3.3
Discrete Parameter
DP
signal ,e.g. status signal, included in a PID which represents at least two digital states, e.g. on/off
3.4
DataFlow
concatenation of DataRecords for one UPID_DataRecord
NOTE Values are ContinueList and EndOfList.
3.5
DataLength
DL
length of a data item
3.6
DataType
DT
identifies in the context of this specification either an “Analogue” or “Discrete” parameter included in the data
record
3.7
EndOfList
EOL
termination (last data record) of data records within a UPID_DataRecord[]
3.8
Legacy Diagnostic Trouble Code
LDTC
Diagnostic Trouble Code which is already defined in a published standard, e.g. ISO 15031-6
3.9
Legacy Monitor Identifier
LMID
OBD Monitor Identifier which is already defined in a published standard, e.g. ISO 15031-5
3.10
Legacy Monitor Test Identifier
LMTID
OBD Monitor Test Identifier which is already defined in a published standard, e.g. ISO 15031-5
4 © ISO 2006 – All rights reserved

3.11
Legacy Routine Identifier
LRID
Routine Identifier which is already defined in a published standard, e.g. ISO 15031-5
3.12
Legacy InfoType Identifier
LITID
InfoType Identifier which is already defined in a published standard, e.g. ISO 15031-5
3.13
Malfunction Indicator
MI
indicator which clearly informs the driver of the vehicle in the event of a malfunction
NOTE Additional detail is included in the WWH-OBD GTR.
3.14
Parameter Group Number
PGN
group of SPNs
3.15
SignalAttribute
SA
DataType, DataFlow, DataLength and Validity of the data parameters included in the data record referenced
by the Unified Data Identifier of the transmitted data from the vehicle's server(s)
3.16
Suspect Parameter Number
SPN
used to identify a least repairable subsystem that has failed, to identify subsystems and or assemblies that
may not have hard failures but may be exhibiting abnormal system operating performance, to identify a
particular event or condition that will be reported and to report a component and non-standard failure mode
3.17
Supported Unified Data Identifiers
SUDID
data identifier specified in a reserved range to be used to reference a list of Unified Data Identifiers and
additional Supported Unified Data Identifiers to be supported by the server
3.18
Unified Control Identifier
UCID
references a control function, e.g. Input/Output in the server
NOTE The value of the control identifier is “Unified”, which is defined as a unique number standardized for the
specific control function.
3.19
Unified Diagnostic Trouble Code
UDTC
value which references a specific fault in a system implemented in the server
NOTE The value of the diagnostic trouble code is “Unified”, which is defined as a unique number standardized for the
specific fault.
3.20
Unified InfoType Identifier
UITID
references identification information, e.g. Calibration Identifier in the server
NOTE The value of the InfoType identifier is “Unified”, which is defined as a unique number standardized for the
specific identification information.
3.21
Unified Monitor Identifier
UMID
references an OBD Monitor function, e.g. Misfire Monitor in the server
NOTE The value of the OBD Monitor identifier is “Unified”, which is defined as a unique number standardized for the
specific OBD Monitor function.
3.22
Unified Parameter Identifier
UPID
references a control function, e.g. Input/Output in the server
NOTE The value of the control identifier is “Unified”, which is defined as a unique number standardized for the
specific control function.
3.23
Unified Routine Identifier
URID
references a routine function, e.g. Evaporation Monitor routine in the server
NOTE The value of the routine identifier is “Unified”, which is defined as a unique number standardized for the
specific control function.
3.24
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 (e.g. its network location)
3.25
Validity
V
indicates the validity of the data signals included in the data record referenced by a Parameter Identifier when
reported by the server
4 Symbols and abbreviated terms
AP Analogue Parameter
CALID Calibration Identification
CGW Central Gateway
CL ContinueList
CVN Calibration Verification Number
DF Data Format
DID Data Identifier
6 © ISO 2006 – All rights reserved

DL Data Length
DP Discrete Parameter
DT DataType
DTC Diagnostic Trouble Code
ECM Engine Control Module
ECU Electronic Control Unit
EOL EndOfList
GTR Global Technical Regulation
ITID InfoType Identifier
LDTC Legacy Diagnostic Trouble Code
LMID Legacy Monitor Identifier
LITID Legacy InfoType Identifier
LMTID Legacy Monitor Test Identifier
LPID Legacy Parameter Identifier
LRID Legacy Routine Identifier
MI Malfunction Indicator
MID Monitor Identifier
MTID Monitor Test Identifier
N/A Not Applicable
PID Parameter Identifier
PGN Parameter Group Number
RID Routine Identifier
SA Signal Attribute
SPN Suspect Parameter Number
SUDID Supported Unified Data Identifiers
UCID Unified Control (input/output) Identifier
UDTC Unified Diagnostic Trouble Code
UITID Unified InfoType Identifier
UMID Unified Monitor Identifier
UPID Unified Parameter Identifier
URID Unified Routine Identifier
URL Uniform Resource Locator
V Validity
VA Validity Attribute
VIN Vehicle Identification Number
VOBD Vehicle On-Board Diagnostics
WWH-OBD Word Wide Harmonized On-Board Diagnostics
5 Conventions
ISO/PAS 27145 is based on the conventions discussed in the O.S.I. Service Conventions (ISO/IEC 10731:1994)
as they apply for diagnostic services.
6 Common data dictionary
This part of the standard specifies a data range layout which considers three (3) data sets in the overall life
cycle of an automotive vehicle and its electronic systems.
These data sets are:
a) A “legacy” data set which includes all standardised data and DTCs used in electronic systems required to
be compliant to legislation prior to the applicability of GTR modules. Legacy data is not defined in this
standard (see Figure 2 — Overview of BaseDTC and DID ranges Page 0 and 1).
b) A “unified” data set which includes all standardised data and DTCs used in electronic systems required to
be compliant to an applicable GTR module. Unified data is defined in this standard (see Figure 2 —
Overview of BaseDTC and DID ranges Page 2).
c) A “manufacturer” data set which reserves a certain range for all vehicle and system supplier defined data
and DTCs used in electronic systems to meet the manufacturer's system life cycle requirements.
Manufacturer data is not defined in this standard but is recommended to be scaled as unified data (see
Figure 2 — Overview of BaseDTC and DID ranges Page 10).
Figure 2 — Overview of BaseDTC and DID ranges provides the layout of available data ranges.
8 © ISO 2006 – All rights reserved

Page 15 - 11 Page 10 Page 9 - 3 Page 1
Page 2 Page 0
0xFFFFFF – 0xBFFFFF 0xAFFFFF 0x9FFFFF – 0x3FFFFF 0x1FFFFF 0x0FFFFF
0x2FFFFF
ISO 27145
reserved data
range
0x0C0000
Manufacturer
0x0BFFFF
ISO 27145 ISO 27145 ISO 27145
Unified SAE J1939
defined
reserved data
reserved reserved DIDs
PGNs – 3
DIDs
data range data range range
(bits 23 . 0) Reserved for
(bits 23 . 0)
ISO 15765-3
0x0B0000
0x0AFFFF
SAE J1939
PGNs - 2
0x0A0000
0x09FFFF
SAE J1939
PGNs - 1
0x18FFFF
0x090000
0x08FFFF
ISO 15031
SAE J1939
ISO 14229-1
PGNs - 0
0xF80000 – 0xB80000 0xA80000 0x980000 – 0x380000 0x280000 Legacy DIDs
0x080000
0x180000
Manufacturer SAE J1939
ISO 27145 ISO 27145 Unified ISO 27145
Legacy
defined
reserved reserved
BaseDTC reserved data
BaseDTC (native)
data range data range (bits 31 . 8) range
SPNs
(bits 31 . 8)
0x10FFFF
ISO 15031
ISO 14229-1
Legacy DTCs
0xF00000 – 0xB00000 0xA00000 0x900000 – 0x300000 0x200000 0x100000 0x000000

Figure 2 — Overview of BaseDTC and DID ranges
The data range layout is based on a Unified Data and Component (DTC) Identifier concept which uses the
identical page select encoding and differentiation between “BaseDTC” and “DataID” category.
Table 2 provides an overview about the available data ranges.
Table 2 — Overview of BaseDTC and DID ranges
Data range Data page Page size Description
0x000000 – 0x07FFFF 0.0 - 0.7 8 x 64 K Legacy SPNs as defined in SAE J1939

0x080000 – 0x08FFFF 0.8 - 0.8 1 x 64 K Legacy PGNs page '0' as defined in SAE J1939

0x090000 – 0x09FFFF 0.9 - 0.9 1 x 64 K Legacy PGNs page '1' as defined in SAE J1939

0x0A0000 – 0x0AFFFF 0.10 - 0.10 1 x 64 K Legacy PGNs page '2' as defined in SAE J1939

Legacy PGNs page '3' as defined in SAE J1939 and
0x0B0000 – 0x0BFFFF 0.11 - 0.11 1 x 64 K

reserved for ISO 15765-3
0x0C0000 – 0x0FFFFF 0.12 - 0.15 4 x 64 K ISO/PAS 27145-2 reserved data range

0x100000 – 0x10FFFF 1.0 - 1.0 1 x 64 K Legacy DTCs as defined ISO 14229-1, ISO/PAS 27145-2

0x110000 – 0x17FFFF 1.1 - 1.7 7 x 64 K ISO/PAS 27145-2 reserved data range
Legacy Data Identifiers as defined in ISO 14229-1,
0x180000 – 0x18FFFF 1.8 - 1.8 1 x 64 K
ISO/PAS 27145-2
0x190000 – 0x1FFFFF 1.9 - 1.15 7 x 64 K ISO/PAS 27145-2 reserved data range
0x200000 – 0x27FFFF 2.0 - 2.7 8 x 64 K Unified DTCs as defined in ISO/PAS 27145-2
0x280000 – 0x2FFFFF 2.8 - 2.15 8 x 64 K Unified DIDs as defined in ISO/PAS 27145-2
0x300000 – 0x9FFFFF 3.0 - 9.15 7 x 16 x 64 K ISO/PAS 27145-2 reserved data range
0xA00000 – 0xA7FFFF 10.0 - 10.7 8 x 64 K Manufacturer defined DTCs
0xA80000 – 0xAFFFFF 10.8 - 10.15 8 x 64 K Manufacturer defined DIDs
0xB00000 – 0xFFFFFF 11.0 - 15.15 5 x 16 x 64 K ISO/PAS 27145-2 reserved data range
7 Data identifier and data record requirements
7.1 Legacy data identifiers
7.1.1 ISO 15031-5 and ISO 14229-1 legacy DID definition
The ISO legacy data identifiers are of different size depending on the deriving specification:
⎯ ISO 15031-5 Annex A - G supports 1-byte data identifiers (PID, MID, TID/RID and InfoType ID)
⎯ ISO 14229-1 Annex C supports 2-byte data identifiers (DID)
Figure 3 — ISO legacy 3-byte data identifier assembly shows how ISO/PAS 27145-2 defines 3-byte ISO
legacy data identifiers based on existing ISO specifications. The “low byte” of the 3-byte ISO legacy data
identifier derives from the 1-byte ISO 15031-5 defined data identifiers. The “middle byte” of the 3-byte ISO
legacy data identifier derives from the high byte of the 2-byte ISO 14229-1 defined data identifiers. The “high
byte” of the 3-byte ISO legacy data identifier is defined by this part of the standard.
The value is fixed to:
⎯ 0x10: Legacy DTC
⎯ 0x18: Legacy DID (PID, MID, RID, InfoType ID).
10 © ISO 2006 – All rights reserved

High Byte Middle Byte Low Byte
XX XX XX
Legacy
Fixed Legacy
ISO
High Byte ISO
15031 -5
0x10 LDTC 14229 -1
Annex
0x18 LDID Annex C
A - G
Figure 3 — ISO legacy 3-byte data identifier assembly
NOTE Existing server software supporting ISO 15031-5 and ISO 14229-1 standards with 1-byte and 2-byte data
identifiers may add the high byte of the 3-byte data identifier with the fixed value when creating the response message at
runtime. The high-byte value is fixed to 0x10 for ISO legacy DTCs and 0x18 for ISO legacy data.
Figure 4 — Emissions-related legacy Parameter/Monitor/Routine/InfoType identifier range illustrates the ISO
legacy data range of ISO 15031-5 and ISO 14229-1 within the 3-byte data identifier range. This is identified by
a value of 0x18 (fixed offset) in the High Byte of the Unified Data Identifier.

High Byte Middle Byte Low Byte
(0xF4 – 0xF8,)
(0x18) (0x00 – 0xFF)
(0xFB)
XX XX XX
ISO 15031 -5
ISO 14229 -1
ISO 15031-5
ISO 15031-5
ISO 14229-1 ISO 14229-1 Legacy ISO 14229 -1 ISO 15031-5 ISO 14229-1 ISO 15031 -5 ISO 14229-1
Legacy TIDs/
data range data range INFOTYPE Legacy MIDs Legacy MIDs Legacy PIDs Legacy PIDs data range
(LRID)
0xFC00 – 0xF900 – IDs 0xF700 – 0xF600 – 0xF500 – 0xF400 – 0x0000 –
0xFB00 –
0xFFFF 0xFAFF 0xF800 – 0xF7FF 0xF6FF 0xF5FF 0xF4FF 0xF3FF
0xFBFF
0xF8FF
Figure 4 — Emissions-related legacy Parameter/Monitor/Routine/InfoType identifier range
Table 3 defines the legacy data ranges deriving from the ISO 15031-5 and ISO 14229-1 standards.
Table 3 — ISO 15031-5 and ISO 14229-1 legacy PID/MID/RID/ITID ranges
Parameter type Mnemonic Data range Description
The DID value is represented in the High and Low
Legacy Data Identifiers LDID 0x180000 – 0x18F3FF Bytes of the DID as specified in ISO 14229-1 and
used with service ReadDataByIdentifier.
Two sets including the 1-byte native PIDs as defined
Legacy Parameter
LPID 0x18F400 – 0x18F5FF in ISO 15031-5 Annex B as the low byte in the LPID
Identifiers
to be used with service ReadDataByIdentifier.
Two sets including the 1-byte native MIDs as defined
Legacy Monitor
LMID 0x18F600 – 0x18F7FF in ISO 15031-5 Annex D as the low byte in the LMID
Identifiers
to be used with service ReadDataByIdentifier.
The 1-byte native InfoType IDs as defined in
Legacy InfoType
LITID 0x18F800 – 0x18F8FF ISO 15031-5 Annex G as the low byte in the LITID
Identifiers
to be used with service ReadDataByIdentifier.
The DID value is represented in the High and Low
Legacy Data Identifiers LDID 0x18F900 – 0x18FAFF Bytes of the DID as specified in ISO 14229-1 and
used with service ReadDataByIdentifier.
The 1-byte native TIDs as defined in ISO 15031-5
Legacy Routine
LRID 0x18FB00 – 0x18FBFF Annex F as the low byte in the LRID to be used with
Identifiers
service RoutineControl.
The DID value is represented in the High and Low
Legacy Data Identifiers LDID 0x18FC00 – 0x18FFFF Bytes of the DID as specified in ISO 14229-1 and
used with service ReadDataByIdentifier.
7.1.2 Legacy ISO 15031-5 identifier supported definition
The concept of supporting legacy Identifiers derives from ISO 15031-5 Annex A specification. The legacy
identifiers defined in this standard are based on a three (3) byte data identifier as defined in service 0x22
ReadDataByIdentifier of ISO/PAS 27145-3. The legacy identifiers specified in ISO 15031-5 are of one (1) byte
data size and are mapped to the low byte (LB) of the three (3) byte data identifier as defined in
ISO/PAS 27145-3.
ISO 15031-5 provides a range of 256 PIDs while ISO 14229-1 reserves a range of 512 PIDs for legislative use.
The detailed encoding of supported legacy data identifiers is specified in the document referenced in Annex A.
7.1.3 Legacy data record definition
7.1.3.1 Overview
The data record includes information depending on the service and data identifier(s) value included in the
request message.
Table 4 specifies the reference to the relevant ISO document and Annex, the Service Identifiers (SID)
depending on the data identifier value range specified in the data range column and the reference section
which includes the data record structure definition.
12 © ISO 2006 – All rights reserved

Table 4 — Legacy data parameter data record structure
Data #A … Data #M
ISO document
SID UDID Data range The service definition is specified in
reference
ISO/PAS 27145-3
Annex B 0x22 / 0x62 LPID 0x18F400 – 0x18F5FF Section 7.1.3.2
0x22 / 0x62
Annex A LMID 0x18F600 – 0x18F7FF Section 7.1.3.3
0x22 / 0x62
Annex A LITID 0x18F800 – 0x18F8FF Section 7.1.3.4
Annex A 0x31 / 0x71 LRID 0x18FB00 – 0x18FBFF Section 7.1.3.5
7.1.3.2 Legacy PID data record structure
The data record structure definition is compatible with the definition in ISO 15031-5.
st
LPID_DataRecord[] = [ ; data record of 1 supported PID#
LPID_DataByte#A ; data A of data record
LPID_DataByte#B ; data B of data record: data B is conditional, depends on PID#
LPID_DataByte#C ; data C of data record: data C is conditional, depends on PID#
LPID_DataByte#D ; data D of data record: data D is conditional, depends on PID#
]
Multiple LPIDs can be included in a ReadDataByIdentifier request message. In such case multiple
LPID_DataRecord[] are included in the response message for each supported LPID by the server. Refer to
ISO/PAS 27145-3 for definition of the ReadDataByIdentifier service.
7.1.3.3 Legacy MID data record structure
The data record structure definition is compatible with the definition in ISO 15031-5.
LMID_DataRecord[] = [ ; data record of supported OBDMID#
LMID_SMTID ; Standard/Manufacturer defined Test ID#
LMID_UASID ; Unit and Scaling ID#
LMID_TVHI ; Test Value (High Byte)
LMID_TVLO : Test Value (Low Byte)
LMID_MINTLHI : Minimum Test Limit (High Byte)
LMID_MINTLLO : Minimum Test Limit (Low Byte)
LMID_MAXTLHI : Maximum Test Limit (High Byte)
LMID_MAXTLLO : Maximum Test Limit (Low Byte)
]
Multiple Test IDs may be supported for a single OBD Monitor ID. In such case a LMID_DataRecord[] is
included in the response message for each Test ID supported by the OBD Monitor ID. Refer to
ISO/PAS 27145-3 for definition of the ReadDataByIdentifier service.
ISO/PAS 27145-2
Table 5 — Response message data parameter definition
Definition
LMID (Legacy Monitor Data Identifier (#1 - #3))
This parameter is an echo of the data parameter unifiedDataIdentifier from the request message.
LMID_DataRecord (#1 to #k)
This parameter is used by the ReadDataByDataIdentifier positive response message to provide the requested data
record values to the client. The content of the dataRecord is defined in ISO/PAS 27145-2.
LMID_SMTID (OBD Monitor Test ID)
The Standardized and Manufacturer Defined Test ID is a 1-byte parameter. Many OBD monitors have multiple tests that
are done in either a serial or parallel manner. If a monitor uses multiple OBD Monitor ID/Test ID combinations that may
not all complete 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”) that 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
current completed monitoring event.
In some cases, test results (or “Monitor ID/Test ID combinations”) will be displayed as being incomplete even though the
monitor (as indicated by PID 0x41) was successfully completed and either passed or failed. In other cases, some Test
IDs will show passing results while others will 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 re-test 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 would show a failing
result, while the small leak test and the very small leak test would 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 rpm increase. If the purge valve is activated and a large rich lambda shift occurs, the Test ID for the rich lambda
shift would show a passing result while the other two Test IDs would show incomplete. Since some Test IDs for a
completed monitor will show incomplete, LPID “Monitor status this driving cycle” must be used to determine monitor
completion status.
LMID_UASID (Unit and Scaling ID)
The Unit and Scaling ID is a one (1) byte identifier to reference 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 the
Annex of ISO/PAS 27145-2.
LMID_TV (#1 - #2) (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.
LMID_MINTL (#1 - #2) (Minimum Test Limit)
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 the Annex
of ISO/PAS 27145-2. 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 results in a “Fail” condition;
⎯ if the Test Value equals the Minimum Test Value results in a “Pass” condition;
if the Test Value is greater than the Minimum Test Value results in a “Pass” condition.
14 © ISO 2006 – All rights reserved

Table 5 — Response message data parameter definition (continued)
Definition
LMID_MAXTL (#1 - #2) (Maximum Test Limit)
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 the Annex
of ISO/PAS 27145-2. The Maximum Test Limit shall be the maximum value for the monitor identified by the On-Board
Diagnostic 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 results in a “Pass” condition;
⎯ if the Test Value equals the Maximum Test Value results in a “Pass” condition;
if the Test Value is greater than the Maximum Test Value results in a “Fail” condition.
7.1.3.4 Legacy InfoType ID data record structure
The data record structure definition is compatible with the definition in ISO 15031-5.
LITID_DataRecord[] = [ ; data record of InfoType
LITID_NODI ; Number of data items
LITID_DATA_#1 ; data #1
LITID_DATA_#2 ; data #2
:
LITID_DATA_#m ; data #m
]
Only one (1) LITID can be included in a ReadDataByIdentifier request message. Therefore a single
LITID_DataRecord[] is included in the response message if LITID is supported by the server. Refer to
ISO/PAS 27145-3 for definition of the R
...