ISO 14229-1:2013
(Main)Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
Road vehicles — Unified diagnostic services (UDS) — Part 1: Specification and requirements
ISO 14229-1:2013 specifies data link independent requirements of diagnostic services, which allow a diagnostic tester (client) to control diagnostic functions in an on-vehicle Electronic Control Unit (ECU, server) such as an electronic fuel injection, automatic gear box, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle. It specifies generic services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic message transmission on the data link. ISO 14229-1:2013 does not apply to non-diagnostic message transmission on the vehicle's communication data link between two ECUs. However, it does not restrict an in-vehicle on-board tester (client) implementation in an ECU in order to utilize the diagnostic services on the vehicle's communication data link to perform bidirectional diagnostic data exchange. ISO 14229-1:2013 does not specify any implementation requirements.
Véhicules routiers — Services de diagnostic unifiés (SDU) — Partie 1: Spécification et exigences
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 14229-1
Second edition
2013-03-15
Road vehicles — Unified diagnostic
services (UDS) —
Part 1:
Specification and requirements
Véhicules routiers — Services de diagnostic unifiés (SDU) —
Partie 1: Spécification et exigences
Reference number
ISO 14229-1:2013(E)
©
ISO 2013
---------------------- Page: 1 ----------------------
ISO 14229-1:2013(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2013
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any
means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
Permission can be requested 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2013 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 14229-1:2013(E)
Contents Page
Foreword .vi
Introduction.vii
1 Scope.1
2 Normative references.1
3 Terms, definitions, symbols and abbreviated terms .1
3.1 Terms and definitions .1
3.2 Abbreviated terms .4
4 Conventions.5
5 Document overview.6
6 Application layer services .7
6.1 General .7
6.2 Format description of application layer services .9
6.3 Format description of service primitives.9
6.4 Service data unit specification.12
7 Application layer protocol .15
7.1 General definition .15
7.2 Protocol data unit specification.16
7.3 Application protocol control information .16
7.4 Negative response/confirmation service primitive .18
7.5 Server response implementation rules .18
8 Service description conventions .29
8.1 Service description .29
8.2 Request message .30
8.3 Positive response message .33
8.4 Supported negative response codes (NRC_) .34
8.5 Message flow examples.34
9 Diagnostic and Communication Management functional unit .35
9.1 Overview.35
9.2 DiagnosticSessionControl (0x10) service.36
9.3 ECUReset (0x11) service .43
9.4 SecurityAccess (0x27) service.47
9.5 CommunicationControl (0x28) service.53
9.6 TesterPresent (0x3E) service .58
9.7 AccessTimingParameter (0x83) service.61
9.8 SecuredDataTransmission (0x84) service .66
9.9 ControlDTCSetting (0x85) service .71
9.10 ResponseOnEvent (0x86) service.75
9.11 LinkControl (0x87) service.99
10 Data Transmission functional unit .106
10.1 Overview.106
10.2 ReadDataByIdentifier (0x22) service .106
10.3 ReadMemoryByAddress (0x23) service.113
10.4 ReadScalingDataByIdentifier (0x24) service .119
10.5 ReadDataByPeriodicIdentifier (0x2A) service .126
10.6 DynamicallyDefineDataIdentifier (0x2C) service.140
10.7 WriteDataByIdentifier (0x2E) service.162
10.8 WriteMemoryByAddress (0x3D) service .167
© ISO 2013 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 14229-1:2013(E)
11 Stored Data Transmission functional unit .174
11.1 Overview.174
11.2 ClearDiagnosticInformation (0x14) Service .175
11.3 ReadDTCInformation (0x19) Service.178
12 InputOutput Control functional unit.245
12.1 Overview.245
12.2 InputOutputControlByIdentifier (0x2F) service .245
13 Routine functional unit.259
13.1 Overview.259
13.2 RoutineControl (0x31) service.260
14 Upload Download functional unit.270
14.1 Overview.270
14.2 RequestDownload (0x34) service.270
14.3 RequestUpload (0x35) service.275
14.4 TransferData (0x36) service.280
14.5 RequestTransferExit (0x37) service.285
14.6 RequestFileTransfer (0x38) service .295
15 Non-volatile server memory programming process .303
15.1 General information.303
15.2 Detailed programming sequence.307
15.3 Server reprogramming requirements .315
15.4 Non-volatile server memory programming message flow examples.319
Annex A (normative) Global parameter definitions .325
A.1 Negative response codes .325
Annex B (normative) Diagnostic and communication management functional unit data-parameter
definitions.333
B.1 communicationType parameter definition .333
B.2 eventWindowTime parameter definition .334
B.3 linkControlModeIdentifier parameter definition .334
B.4 nodeIdentificationNumber parameter definition .335
Annex C (normative) Data transmission functional unit data-parameter definitions .337
C.1 DID parameter definitions .337
C.2 scalingByte parameter definitions.343
C.3 scalingByteExtension parameter definitions.345
C.4 transmissionMode parameter definitions .351
C.5 Coding of UDS version number .352
Annex D (normative) Stored data transmission functional unit data-parameter definitions .353
D.1 groupOfDTC parameter definition.353
D.2 DTCStatusMask and statusOfDTC bit definitions .353
D.3 DTC severity and class definition .366
D.4 DTCFormatIdentifier definition.369
D.5 FunctionalGroupIdentifier definition .369
D.6 DTCFaultDetectionCounter operation implementation example.371
D.7 DTCAgingCounter example .372
Annex E (normative) Input output control functional unit data-parameter definitions .374
E.1 InputOutputControlParameter definitions .374
Annex F (normative) Routine functional unit data-parameter definitions.375
F.1 RoutineIdentifier (RID) definition .375
Annex G (normative) Upload and download functional unit data-parameter .376
G.1 Definition of modeOfOperation values.376
Annex H (informative) Examples for addressAndLengthFormatIdentifier parameter values .377
H.1 addressAndLengthFormatIdentifier example values.377
Annex I (normative) Security access state chart .379
iv © ISO 2013 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 14229-1:2013(E)
I.1 General .379
I.2 Disjunctive normal form based state transition definitions.379
Annex J (informative) Recommended implementation for multiple client environments.385
J.1 Introduction.385
J.2 Implementation specific limitations .385
J.3 Use cases relevant for system design .386
J.4 Use Case Evaluation:.388
J.5 Multiple client server level implementation.389
Bibliography.391
© ISO 2013 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 14229-1:2013(E)
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 14229-1 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
This second edition cancels and replaces the first edition (ISO 14229-1:2006), which has been technically
revised.
ISO 14229 consists of the following parts, under the general title Road vehicles — Unified diagnostic services
(UDS):
⎯ Part 1: Specification and requirements
⎯ Part 2: Session layer services
⎯ Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)
⎯ Part 4: Unified diagnostic services on FlexRay implementation (UDSonFR)
⎯ Part 5: Unified diagnostic services on Internet Protocol implementation (UDSonIP)
⎯ Part 6: Unified diagnostic services on K-Line implementation (UDSonK-Line)
The following part is under preparation:
⎯ Part 7: Unified diagnostic services on Local Interconnect Network implementation (UDSonLIN)
The titles of future parts will be drafted as follows:
⎯ Part n: Unified diagnostic services on … implementation (UDSon…)
vi © ISO 2013 – All rights reserved
---------------------- Page: 6 ----------------------
ISO 14229-1:2013(E)
Introduction
ISO 14229 has been established in order to define common requirements for diagnostic systems, whatever
the serial data link is.
To achieve this, ISO 14229 is based on the Open Systems Interconnection (OSI) Basic Reference Model in
accordance with ISO 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers.
When mapped on this model, the services used by a diagnostic tester (client) and an Electronic Control Unit
(ECU, server) are broken into the following layers in accordance with Table 1:
⎯ Application layer (layer 7), unified diagnostic services specified in ISO 14229-1, ISO 14229-3
UDSonCAN, ISO 14229-4 UDSonFR, ISO 14229-5 UDSonIP, ISO 14229-6 UDSonK-Line, ISO 14229-7
UDSonLIN, further standards and ISO 27145-3 WWH-OBD.
⎯ Presentation layer (layer 6), vehicle manufacturer specific, ISO°27145-2 WWH-OBD.
⎯ Session layer services (layer 5) specified in ISO 14229-2.
⎯ Transport layer services (layer 4), specified in ISO 15765-2 DoCAN, ISO 10681-2 Communication on
FlexRay, ISO 13400-2 DoIP, ISO 17987-2 LIN, ISO 27145-4 WWH-OBD.
⎯ Network layer services (layer 3), specified in ISO 15765-2 DoCAN, ISO 10681-2 Communication on
FlexRay, ISO 13400-2 DoIP, ISO 17987-2 LIN, ISO 27145-4 WWH-OBD.
⎯ Data link layer (layer 2), specified in ISO 11898-1, ISO 11898-2, ISO 17458-2, ISO 13400-3, IEEE 802.3,
ISO 14230-2, ISO 17987-3 LIN and further standards, ISO 27145-4 WWH-OBD.
⎯ Physical layer (layer 1), specified in ISO 11898-1, ISO 11898-2, ISO 17458-4, ISO 13400-3, IEEE 802.3,
ISO 14230-1, ISO 17987-4 LIN and further standards, ISO 27145-4 WWH-OBD.
NOTE The diagnostic services in this standard are implemented in various applications e.g. Road vehicles –
Tachograph systems, Road vehicles – Interchange of digital information on electrical connections between towing and
towed vehicles, Road vehicles – Diagnostic systems, etc. It is required that future modifications to this standard provide
long-term backward compatibility with the implementation standards as described above.
Table 1 — Example of diagnostic/programming specifications applicable to the OSI layers
OSI seven WWH-
Applicability Enhanced diagnostics services
layer OBD
Application ISO 14229-1, ISO 14229-3 UDSonCAN, ISO 14229-4 UDSonFR, ISO 14229-5 ISO
(layer 7) UDSonIP, ISO 14229-6 UDSonK-Line, ISO 14229-7 UDSonLIN, further standards 27145-3
Presentation ISO
vehicle manufacturer specific
(layer 6) 27145-2
Session
ISO 14229-2
(layer 5)
Seven layer
according to
Transport further
ISO/IEC 7498-1
(layer 4) standards
ISO ISO ISO Not ISO
and
15765-2 10681-2 13400-2 applicable 17987-2
ISO/IEC 10731
Network further
(layer 3) standards
ISO
27145-4
Data link ISO ISO ISO further
ISO ISO
(layer 2) 17458-2 14230-2 17987-3 standards
11898-1, 13400-3,
ISO IEEE
Physical ISO ISO ISO further
11898-2 802.3
(layer 1) 17458-4 14230-1 17987-4 standards
© ISO 2013 – All rights reserved vii
---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO 14229-1:2013(E)
Road vehicles — Unified diagnostic services (UDS) —
Part 1:
Specifications and requirements
1 Scope
This part of ISO 14229 specifies data link independent requirements of diagnostic services, which allow a
diagnostic tester (client) to control diagnostic functions in an on-vehicle Electronic Control Unit (ECU, server)
such as an electronic fuel injection, automatic gear box, anti-lock braking system, etc. connected to a serial
data link embedded in a road vehicle.
It specifies generic services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic
message transmission on the data link.
This part of ISO 14229 does not apply to non-diagnostic message transmission on the vehicle's
communication data link between two Electronic Control Units. However, this part of ISO 14229 does not
restrict an in-vehicle on-board tester (client) implementation in an ECU in order to utilize the diagnostic
services on the vehicle's communication data link to perform bidirectional diagnostic data exchange.
This part of ISO 14229 does not specify any implementation requirements.
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 14229-2, Road vehicles — Unified diagnostic services (UDS) — Part 2: Session layer services
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
boot manager
part of the boot software that executes immediately after an ECU power on or reset whose primary purpose is
to check whether a valid application is available to execute as compared to transferring control to the
reprogramming software
NOTE The boot manager may also take into account other conditions for transitioning control to the reprogramming
software.
3.1.2
boot memory partition
area of the server memory in which the boot software is located
© ISO 2013 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO 14229-1:2013(E)
3.1.3
boot software
software which is executed in a special part of server memory which is used primarily to boot the ECU and
perform server programming
NOTE 1 This area of memory is not erased during a normal programming sequence and must execute when the server
application is missing or otherwise deemed invalid to always ensure the capability to reprogram the server.
NOTE 2 See also 3.1.1 and 3.1.17.
3.1.4
client
function that is part of the tester and that makes use of the diagnostic services
NOTE A tester normally makes use of other functions such as data base management, specific interpretation,
human-machine interface.
3.1.5
diagnostic data
data that is located in the memory of an electronic control unit which may be inspected and/or possibly
modified by the tester
NOTE 1 Diagnostic data includes analogue inputs and outputs, digital inputs and outputs, intermediate values and
various status information.
NOTE 2 Examples of diagnostic data are vehicle speed, throttle angle, mirror position, system status, etc. Three types
of values are defined for diagnostic data:
⎯ the current value: the value currently used by (or resulting from) the normal operation of the electronic control unit;
⎯ a stored value: an internal copy of the current value made at specific moments (e.g. when a malfunction occurs or
periodically); this copy is made under the control of the electronic control unit;
⎯ a static value: e.g. VIN.
The server is not obliged to keep internal copies of its data for diagnostic purposes, in which case the tester may only
request the current value.
NOTE 3 Defining a repair shop or development testing session selects different server functionality (e.g. access to all
memory locations may only be allowed in the development testing session).
3.1.6
diagnostic routine
routine that is embedded in an electronic control unit and that may be started by a server upon a request from
the client
NOTE It could either run instead of a normal operating program, or could be enabled in this mode and executed with
the normal operating program. In the first case, normal operation for the server is not possible. In the second case,
multiple diagnostic routines may be enabled that run while all other parts of the electronic control unit are functioning
normally.
3.1.7
diagnostic service
information exchange initiated by a client in order to require diagnostic information from a server or/and to
modify its behaviour for diagnostic purpose
3.1.8
diagnostic session
state within the server in which a specific set of diagnostic services and functionality is enabled
2 © ISO 2013 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 14229-1:2013(E)
3.1.9
diagnostic trouble code
DTC
numerical common identifier for a fault condition identified by the on-board diagnostic system
3.1.10
ECU
electronic control unit, containing at least one server
NOTE Systems considered as Electronic Control Units include Anti-lock Braking System (ABS) and Engine
Management System.
3.1.11
functional unit
set of functionally close or complementary diagnostic services
3.1.12
integer type
simple type with distinguished values which are the positive and the negative whole numbers, including zero
NOTE The range of type integer is not specified within this part of ISO 14229.
3.1.13
local client
client that is connected to the same local network as the server and is part of the same address space as the
server
3.1.14
local server
server that is connected to the same local network as the client and is part of the same address space as the
client
3.1.15
OSI
open systems interconnection
3.1.16
permanent DTC
diagnostic trouble code (DTC) that remains in non-volatile memory, even after a clear DTC request, until other
criteria (typically regulatory) are met (e.g. the appropriate monitors for each DTC have successfully passed)
NOTE Refer to the relevant legislation for all necessary requirements.
3.1.17
record
one or more diagnostic data elements that are referred to together by a single means of identification
NOTE A snapshot including various input/output data and trouble codes is an example of a record.
3.1.18
remote server
server that is not directly connected to the main diagnostic network
NOTE 1 A remote server is identified by means of a remote address. Remote addresses represent an own address
space that is independent from the addresses on the main network.
NOTE 2 A remote server is reached via a local server on the main network. Each local server on the main network can
act as a gate to one independent set of remote servers. A pair of addresses must therefore always identify a remote
server: one local address that identifies the gate to the remote network and one remote address identifying the remote
server itself.
© ISO 2013 – All rights reserved 3
---------------------- Page: 10 ----------------------
ISO 14229-1:2013(E)
3.1.19
remote client
client that is not directly connected to the main diagnostic network
NOTE 1 A remote client is identified by means of a remote address.
NOTE 2 Remote addresses represent an own address space that is independent from the addresses on the main
network.
3.1.20
reprogramming software
part of the boot software that allows for reprogramming of the electronic control unit
3.1.21
security
mechanism for protecting vehicle modules from "unauthorized" intrusion through a vehicle di
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.