Road vehicles — Unified diagnostic services (UDS) — Part 3: Unified diagnostic services on CAN implementation (UDSonCAN)

ISO 14229-3:2012 specifies the implementation of a common set of unified diagnostic services (UDS) on controller area networks (CAN) in road vehicles (UDSonCAN). It references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the diagnostic services to be used for diagnostic communication over CAN. It does not specify any requirement for the in-vehicle CAN bus architecture.

Véhicules routiers — Services de diagnostic unifiés (SDU) — Partie 3: SDU sur l'implémentation du gestionnaire de réseau de communication (SDUsurCAN)

General Information

Status
Withdrawn
Publication Date
29-Nov-2012
Current Stage
6060 - International Standard published
Start Date
23-Oct-2012
Completion Date
30-Nov-2012
Ref Project

RELATIONS

Buy Standard

Standard
ISO 14229-3:2012 - Road vehicles -- Unified diagnostic services (UDS)
English language
16 pages
sale 15% off
Preview
sale 15% off
Preview
Standard
ISO 14229-3:2012 - Road vehicles -- Unified diagnostic services (UDS)
English language
16 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO
STANDARD 14229-3
First edition
2012-12-01
Corrected version
2013-01-15
Road vehicles — Unified diagnostic
services (UDS) —
Part 3:
Unified diagnostic services on CAN
implementation (UDSonCAN)
Véhicules routiers — Services de diagnostic unifiés (SDU) —
Partie 3: SDU sur l’implémentation du gestionnaire de réseau de
communication (SDUsurCAN)
Reference number
ISO 14229-3:2012(E)
ISO 2012
---------------------- Page: 1 ----------------------
ISO 14229-3:2012(E)
COPYRIGHT PROTECTED DOCUMENT
© 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2012 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 14229-3:2012(E)
Contents Page

Foreword ........................................................................................................................................................................................................................................iv

Introduction ..................................................................................................................................................................................................................................v

1 Scope ................................................................................................................................................................................................................................. 1

2 Normative references ...................................................................................................................................................................................... 1

3 Terms, definitions and abbreviated terms ................................................................................................................................ 1

3.1 Terms and definitions ....................................................................................................................................................................... 1

3.2 Abbreviated terms ............................................................................................................................................................................... 1

4 Conventions ............................................................................................................................................................................................................... 2

5 Document overview........................................................................................................................................................................................... 2

6 Unified diagnostic services implementation on CAN ..................................................................................................... 4

6.1 General ........................................................................................................................................................................................................... 4

6.2 UDS on CAN services overview ................................................................................................................................................. 4

6.3 ResponseOnEvent (0x86) service DoCAN implementation requirements ......................................... 5

6.4 ReadDataByPeriodicIdentifier (0x2A) service ............................................................................................................ 7

7 Application layer requirements ........................................................................................................................................................13

7.1 Application layer services ..........................................................................................................................................................13

7.2 Application layer protocol ..........................................................................................................................................................13

7.3 Application layer timing...............................................................................................................................................................13

8 Presentation layer requirements .....................................................................................................................................................13

9 Session layer requirements ....................................................................................................................................................................13

10 Transport/Network layer interface adaptation ................................................................................................................13

10.1 General information ........................................................................................................................................................................13

10.2 DoCAN Transport/Network layer interface adaptation ...................................................................................14

11 Data link layer diagnostic implementation requirements ....................................................................................15

11.1 Usage of legislated 11-bit OBD CAN Identifiers for enhanced diagnostics ......................................15

11.2 Usage of legislated 29-bit OBD CAN Identifiers for enhanced diagnostics ......................................15

Bibliography

.............................................................................................................................................................................................................................16

© ISO 2012 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 14229-3:2012(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-3 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,

Electrical and electronic equipment.
This first edition of ISO 14229-3 cancels and replaces ISO 15765-3:2004.

This corrected version incorporates the above information regarding ISO 14229-3 cancelling and

replacing ISO 15765-3:2004.

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 parts are under preparation / are planned:

— Part 7: Unified diagnostic services on Local Interconnet Network implementation(UDSonLIN)

iv © ISO 2012 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 14229-3:2012(E)
Introduction

This part of ISO 14229 has been established in order to enable the implementation of unified diagnostic

services, as specified in ISO 14229-3, on Controller Area Networks (UDSonCAN).

To achieve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model specified in

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 14229 are divided into
— Application layer (layer 7):
— Vehicle manufacturer enhanced diagnostics: ISO 14229-1, ISO 14229-3,
— Legislated OBD: ISO 15031-5,
— Legislated WWH-OBD: ISO 14229-1 / ISO 27145-3;
— Presentation layer (layer 6):
— Vehicle manufacturer enhanced diagnostics: vehicle manufacturer specific,
— Legislated OBD: SAE J1930-DA, SAE J1979-DA, SAE J2012-DA,

— Legislated WWH-OBD: ISO 27145-2 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):
— Vehicle manufacturer enhanced diagnostics: ISO 14229-2,
— Legislated OBD: ISO 14229-2,
— Legislated WWH-OBD: ISO 14229-2;
— Transport layer services (layer 4):
— Vehicle manufacturer enhanced diagnostics: ISO 15765-2,
— Legislated OBD: ISO 15765-2, ISO 15765-4
— Legislated WWH-OBD: ISO 27145-4;
— Network layer services (layer 3):
— Vehicle manufacturer enhanced diagnostics: ISO 15765-2,
— Legislated OBD: ISO 15765-2, ISO 15765-4
— Legislated WWH-OBD: ISO 27145-4;
— Data link layer (layer 2):

— Vehicle manufacturer enhanced diagnostics: ISO 11898-1, ISO 11898-2, ISO 11898-3, ISO 11898-5,

— Legislated OBD: ISO 11898-1, ISO 11898-2, ISO 15765-4,
— Legislated WWH-OBD: ISO 27145-4;
— Physical layer (layer 3):

— Vehicle manufacturer enhanced diagnostics: ISO 11898-1, ISO 11898-2, ISO 11898-3, ISO 11898-5,

— Legislated OBD: ISO 11898-1, ISO 11898-2, ISO 15765-4,
© ISO 2012 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 14229-3:2012(E)
— Legislated WWH-OBD: ISO 27145-4;
in accordance with Table 1.

Table 1 — DoCAN enhanced diagnostics, legislated OBD and WWH-OBD specification reference

applicable to the OSI layers
Legislated
Vehicle manufac-
OBD Legislated WWH-OBD
Applicability OSI 7 layers turer enhanced
(On-Board (On-Board Diagnostics)
diagnostics
Diagnostics)
Application ISO 14229-1, ISO/
ISO 15031-5 ISO 14229-1, ISO 27145-3
(layer 7) FDIS 14229-3
ISO 27145-2 SAE J1930-DA,
SAE J1930-DA,
Presentation vehicle manufac- SAE J1939 Companion Spreadsheet (SPNs),
SAE J1979-DA,
(layer 6) turer specific SAE J1939 −73:2010, Appendix A (FMIs),
SAE J2012-DA
SAE J1979-DA, SAE J2012-DA
Seven layer Session
ISO 14229-2
according to (layer 5)
ISO/IEC 7498-1
Transport
and ISO/
(layer 4)
ISO 15765-2, ISO 15765-2,
IEC 10731
ISO 15765-2 ISO 13400-2
ISO 15765-4 ISO 15765-4
Network
(layer 3)
ISO 27145-4
Data link
ISO 11898-1,
ISO 11898-1, ISO 11898-1,
(layer 2)
ISO 11898-2, ISO 13400-3,
ISO 11898-2, ISO 11898-2,
ISO 11898-3, IEEE 802.3
Physical
ISO 15765-4 ISO 15765-4
ISO 11898-5
(layer 1)
vi © ISO 2012 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 14229-3:2012(E)
Road vehicles — Unified diagnostic services (UDS) —
Part 3:
Unified diagnostic services on CAN implementation
(UDSonCAN)
1 Scope

This part of ISO 14229 specifies the implementation of a common set of unified diagnostic services

(UDS) on controller area networks (CAN) in road vehicles (UDSonCAN).

UDSonCAN references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the

diagnostic services to be used for diagnostic communication over CAN.

NOTE UDSonCAN does not specify any requirement for the in-vehicle CAN bus architecture.

This part of ISO 14229 does not include any redundant information of the documents as listed in the

Introduction. It focuses on

— additional requirements specific to the implementation of UDS on the CAN network, and

— specific restrictions in the implementation of UDS on the CAN network.
2 Normative references

The following documents, in whole or in part, are normatively referenced in this document and are

indispensable for its application. For dated references, only the edition cited applies. For undated

references, the latest edition of the referenced document (including any amendments) applies.

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 services

ISO 15765-1, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 1:

General information and use case definition

ISO 15765-2, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 2:

Transport protocol and network layer services

ISO 15765-4, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 4:

Requirements for emissions-related systems
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 14229-1, ISO 14229-2,

ISO 15765-1, ISO 15765-2 and ISO 15765-4 apply.
© ISO 2012 – All rights reserved 1
---------------------- Page: 7 ----------------------
ISO 14229-3:2012(E)
3.2 Abbreviated terms
CF consecutive frame
DA destination address
DLC data length code
FF first frame
FC flow control
ID identifier
NA network address
SA source address
SF single frame
SM subnet mask
SOM start of message
STRT serviceToRespondTo
TA target address
UDS unified diagnostic services
USDT unacknowledged segmented data transfer
UUDT unacknowledged unsegmented data transfer
4 Conventions

This part of ISO 14229 is based on the conventions discussed in the OSI Service Conventions

(ISO/IEC 10731:1994) as they apply for diagnostic services.
5 Document overview
Figure 1 illustrates the documents required to implement UDSonCAN.
2 © ISO 2012 – All rights reserved
---------------------- Page: 8 ----------------------
ISO 14229-3:2012(E)
Uniied Diagnostic Services (UDS)
subset
ISO 14229-1 UDS
ISO 14229-3 UDS
speciication and
OSI Layer 7
UDSonCAN
requirements
Application
vehicle manufacturer speciic
OSI Layer 6
Presentation
ISO 14229-2 UDS
OSI Layer 5
session layer services
Session
Standardized Service Primitive Interface
DoCAN
ISO 14229-3 UDS –
UDSonCAN
implementation
OSI Layer 4
Transport
ISO 15765-2 DoCAN
transport protocol
and
network
layer services
OSI Layer 3
Network
ISO 11898-1 CAN
data link layer and physical
OSI Layer 2
signalling
Data Link
ISO 11898 CAN
Part 2: High-speed medium access unit
Part 3: Low-speed, fault-tolerant, medium-
OSI Layer 1
dependent interface
Physical
Part 5: High-speed medium access unit
with low-power mode
Figure 1 — UDSonCAN document reference according to OSI model
© ISO 2012 – All rights reserved 3
---------------------- Page: 9 ----------------------
ISO 14229-3:2012(E)
6 Unified diagnostic services implementation on CAN
6.1 General

This clause defines how the diagnostic services as defined in ISO 14229-1 apply to DoCAN. For each

applicable service, the applicable sub-function and data parameters are defined.

NOTE The sub-function parameter definitions take into account that the most significant bit is used for the

suppressPosRspMsgIndicationBit parameter as defined in ISO 14229-1.
6.2 UDS on CAN services overview

The purpose of Table 2 is to reference all ISO 14229-1 and ISO 14229-2 services as they are applicable

for an implementation in ISO 14229-3, UDSonCAN. Table 2 contains the sum of all applicable services.

Certain applications using this part of ISO 14229 to implement UDSonCAN may restrict the number

of useable services and may categorize them in certain application areas/diagnostic sessions (default

session, programming session, etc.).

Services in Table 2 that are marked “No CAN specific requirements” shall be implemented as defined

in ISO 14229-1 and ISO 14229-2 with no additional restrictions. Services that are marked “CAN specific

requirements” shall be implemented as defined by the subclause listed in the Table 2 entry.

Table 2 — Overview of applicable ISO 14229-1, Unified diagnostic services and data ranges

Diagnostic service name Comment Reference in this
(ISO 14229-1) document
Diagnostic and Communication Management Functional Unit
DiagnosticSessionControl No CAN specific requirements —
ECUReset No CAN specific requirements —
SecurityAccess No CAN specific requirements —
CommunicationControl No CAN specific requirements —
TesterPresent No CAN specific requirements —
SecuredData-Transmission No CAN specific requirements —
ControlDTCSetting No CAN specific requirements —
ResponseOnEvent CAN specific requirements see 6.3
LinkControl No CAN specific requirements —
Data Transmission Functional Unit
ReadDataByIdentifier No CAN specific requirements —
ReadMemoryByAddress No CAN specific requirements —
ReadScalingDataByIdentifier No CAN specific requirements —
ReadDataByPeriodicIdentifier CAN specific requirements see 6.4
DynamicallyDefineDataIdentifier No CAN specific requirements —
WriteDataByIdentifier No CAN specific requirements —
WriteMemoryByAddress No CAN specific requirements —
ReadDTCInformation No CAN specific requirements —
ClearDiagnosticInformation No CAN specific requirements —
Data Transmission Functional Unit
ReadDTCInformation No CAN specific requirements —
ClearDiagnosticInformation No CAN specific requirements —
4 © ISO 2012 – All rights reserved
---------------------- Page: 10 ----------------------
ISO 14229-3:2012(E)
Table 2 (continued)
Input/Output Control Functional Unit
InputOutputControlByIdentifier No CAN specific requirements —
Remote Activation Of Routine Functional Unit
RoutineControl No CAN specific requirements —
Upload/Download Functional Unit
RequestDownload No CAN specific requirements —
RequestUpload No CAN specific requirements —
TransferData No CAN specific requirements —
RequestTransferExit No CAN specific requirements —
RequestFileTransfer No CAN specific requirements —
6.3 ResponseOnEvent (0x86) service DoCAN implementation requirements

In addition to the generic implementation requirements stated in ISO 14229-1 the following additional

CAN specific implementation requirements shall apply.

While the ResponseOnEvent service is active, the server shall be able to process concurrent

diagnostic request and response messages accordingly. This should be accomplished with a different

serviceToRespondTo CAN Identifiers. If the same diagnostic request/response CAN Identifiers are used for

diagnostic communication and the serviceToRespondTo-responses, the following restrictions shall apply:

a) The server may ignore an incoming diagnostic request issued by the client that initiated the

event, after an event has occurred and the serviceToRespondTo-response is in progress, until the

serviceToRespondTo-response is completed. If another client issued the request, the server may or

may not ignore the request, depending on the server’s capabilities.

b) When the client receives any response after sending a diagnostic request, the response shall be

classified according to the possible serviceToRespondTo-responses and the expected diagnostic

responses to the previously sent request.

1) If the response is a serviceToRespondTo-response (one of the possible responses set up with

ResponseOnEvent-service), the client shall repeat the request after the serviceToRespondTo-

response has been received completely.

2) If the response is ambiguous (i.e. the response could originate from the serviceToRespondTo

initiated by an event or from the response to a diagnostic request), the client shall present

the response both as a serviceToRespondTo-response and as the response to the diagnostic

request. The client shall not repeat the request with the exception of NegativeResponseCode

busyRepeatRequest (0x21) (see the negative response code definitions in ISO 14229-1.

© ISO 2012 – All rights reserved 5
---------------------- Page: 11 ----------------------
ISO 14229-3:2012(E)
client server
SF-Diag-Request STRT-ResponseFF Event
server ignores request
STRT-FC
STRT-CF
STRT-CF
the STRT-response is completed
and the tester repeats the
diagnostic request, if the
response is a valid STRT-
SF-Diag-Request
response.
server responds to request
Response
Figure 2 — Concurrent request when the event occurs

c) When the specified event is detected, the server shall respond immediately with the appropriate

serviceToRespondTo-response message. The immediate serviceToRespondTo-response message

shall not disrupt any other diagnostic request or response transmission already in progress (i.e. the

serviceToRespondTo-response shall be delayed until the current message transmission has been

completed, see Figure 3).
client server
SF Diag-Request
Diag-Resp. FF
Event
STRT-Response
is delayed
Diag.- Response is
completed
STRT-Resp. FF
and the server sends the
STRT-response.
STRT-CF
STRT-CF
Figure 3 — Event occurrence during a message in progress
6 © ISO 2012 – All rights reserved
---------------------- Page: 12 ----------------------
ISO 14229-3:2012(E)
6.4 ReadDataByPeriodicIdentifier (0x2A) service
6.4.1 Periodic transmission response message
The ReadDataByPeriodicIdentifier service allows the client to request the perio
...

DRAFT INTERNATIONAL STANDARD ISO/DIS14229-3
ISO/TC 22/SC 3 Secretariat: DIN
Voting begins on Voting terminates on
2011-07-01 2011-12-01

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION • МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ПО СТАНДАРТИЗАЦИИ • ORGANISATION INTERNATIONALE DE NORMALISATION

Road vehicles — Unified diagnostic services (UDS —
Part 3:
Unified diagnostic services on CAN implementation
(UDSonCAN)
Véhicules routiers — Services de diagnostic unifiés (SDU) —

Partie 3: SDU sur l'implémentation du gestionnaire de réseau de communication (SDUsurCAN)

ICS 43.180

In accordance with the provisions of Council Resolution 15/1993 this document is circulated in

the English language only.

Conformément aux dispositions de la Résolution du Conseil 15/1993, ce d ocument est

distribué en version anglaise seulement.

To expedite distribution, this document is circulated as r eceived from the committee

secretariat. ISO Central Secretariat work of editing and text composition will be undertaken at

publication stage.

Pour accélérer la distribution, le présent document est distribué tel qu'il est parvenu du

secrétariat du comité. Le travail de rédaction et de composition de texte sera effectué au

Secrétariat central de l'ISO au stade de publication.

THIS DOCUMENT IS A DRAFT CIRCULATED FOR COMMENT AND APPROVAL. IT IS THEREFORE SUBJECT TO CHANGE AND MAY NOT BE

REFERRED TO AS AN INTERNATIONAL STANDARD UNTIL PUBLISHED AS SUCH.

IN ADDITION TO THEIR EVALUATION AS BEING ACCEPTABLE FOR INDUSTRIAL, TECHNOLOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT

INTERNATIONAL STANDARDS MAY ON OCCASION HAVE TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL TO BECOME STANDARDS TO

WHICH REFERENCE MAY BE MADE IN NATIONAL REGULATIONS.

RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT, WITH THEIR COMMENTS, NOTIFICATION OF ANY RELEVANT PATENT RIGHTS OF WHICH

THEY ARE AWARE AND TO PROVIDE SUPPORTING DOCUMENTATION.
© International Organization for Standardization, 2011
---------------------- Page: 1 ----------------------
ISO/DIS 14229-3
Copyright notice

This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted

under the applicable laws of the user’s country, neither this ISO draft nor any extract from it may be

reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic,

photocopying, recording or otherwise, without prior written permission being secured.

Requests for permission to reproduce should be addressed to 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
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO 2011 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/DIS 14229-3
Contents Page

Foreword ............................................................................................................................................................ iv

Introduction ......................................................................................................................................................... v

1  Scope ...................................................................................................................................................... 1

2  Normative references ............................................................................................................................ 1

3  Terms, definitions, symbols and abbreviated terms ......................................................................... 2

3.1  Terms and definitions ........................................................................................................................... 2

3.2  Abbreviated terms ................................................................................................................................. 2

4  Conventions ........................................................................................................................................... 2

5  Document overview ............................................................................................................................... 3

6  Unified diagnostic services implementation on CAN ........................................................................ 4

6.1  General ................................................................................................................................................... 4

6.2  UDS on CAN services overview ........................................................................................................... 4

6.3  ResponseOnEvent (0x86) service DoCAN implementation requirements ...................................... 5

6.4  ReadDataByPeriodicIdentifier (0x2A) service DoCAN implementation requirements ................... 7

7  Application layer requirements .......................................................................................................... 13

7.1  Application layer services .................................................................................................................. 13

7.2  Application layer protocol .................................................................................................................. 13

7.3  Timing definition .................................................................................................................................. 13

8  Presentation layer requirements ....................................................................................................... 13

9  Session layer requirements ............................................................................................................... 13

10  Transport/Network layer interface adaptation .................................................................................. 14

10.1  General information ............................................................................................................................ 14

10.2  DoCAN Transport/Network layer interface adaptation .................................................................... 14

11  Data link layer diagnostic implementation requirements ............................................................... 16

11.1  Usage of legislated 11-bit OBD CAN Identifiers for enhanced diagnostics .................................. 16

11.2  Usage of legislated 29-bit OBD CAN Identifiers for enhanced diagnostics .................................. 16

Annex A (informative) UDSonCAN / LIN-Master gateway ............................................................................. 17

A.1  UDSonCAN to LIN gateway definition ............................................................................................... 17

A.2  UDSonCAN gateway / LIN-Master to LIN-Slave message example ................................................ 17

Bibliography ...................................................................................................................................................... 18

© ISO 2011 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/DIS 14229-3
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-3 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,

Electrical and electronic equipment.

This first edition cancels and replaces the first edition ISO 15765-3:2004, of 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)

The following parts are under preparation / are planned:
⎯ Part 6: Unified diagnostic services on K-Line implementation (UDSonK-Line)
iv © ISO 2011 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/DIS 14229-3
Introduction

This part of ISO 14229 has been established in order to enable the implementation of unified diagnostic

services, as specified in ISO 14229-1, on Controller Area Networks (UDS on CAN).

To achieve this, it is based on the Open Systems Interconnection (OSI) Basic Reference Model specified in

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 14229 are divided into
⎯ Application layer (layer 7), specified in ISO 14229-1, ISO/DIS 14229-3;
⎯ Presentation layer (layer 6), vehicle manufacturer specific;
⎯ Session layer services (layer 5), specified in ISO 14229-2;
⎯ Transport layer services (layer 4), specified in ISO 15765-2, ISO 15765-4;
⎯ Network layer services (layer 3), specified in ISO 15765-2, ISO 15765-4;

⎯ Data link layer (layer 2), specified in ISO 11898-1, ISO 11898-2, ISO 11898-3, ISO 11898-5;

⎯ Physical layer (layer 1), specified in ISO 11898-1, ISO 11898-2, ISO 11898-3, ISO 11898-5;

in accordance with Table 1.

Table 1 — DoCAN enhanced diagnostics, legislated OBD and WWH-OBD specification reference

applicable to the OSI layers
Legislated OBD
Vehicle manufacturer Legislated WWH-OBD
Applicability OSI 7 layers (On-Board
enhanced diagnostics (On-Board Diagnostics)
Diagnostics)
ISO 14229-1,
Application (layer 7) ISO 15031-5 ISO 14229-1, ISO 27145-3
ISO/DIS 14229-3
SAE J1930-DA, SAE J1930-DA, SAE J1979 DA,
vehicle manufacturer
Presentation (layer 6) SAE J1979-DA, SAE J2012-DA, SAE J1939 Appendix C
specific
SAE J2012-DA (SPNs), SAE J1939-73 Appendix A (FMIs)
Seven layer
according to
Session (layer 5) ISO 14229-2
ISO 7498-1
and
Transport (layer 4)
ISO15765-4, ISO15765-4,
ISO/IEC
ISO 15765-2 ISO 13400-2
ISO15765-2 ISO15765-2
10731
Network (layer 3)
ISO
Data link (layer 2) ISO 11898-1,
27145-4
ISO 15765-4, ISO 15765-4,
ISO 11898-2, ISO 13400-3,
ISO 11898-1, ISO 11898-1,
ISO 11898-3, IEEE 802.3
Physical (layer 1)
ISO 11898-2 ISO 11898-2
ISO 11898-5
© ISO 2011 – All rights reserved v
---------------------- Page: 5 ----------------------
DRAFT INTERNATIONAL STANDARD ISO/DIS 14229-3
Road vehicles — Unified diagnostic services (UDS —
Part 3:
Unified diagnostic services on CAN implementation
(UDSonCAN)
1 Scope

This part of ISO 14229 specifies the implementation of a common set of unified diagnostic services (UDS) on

controller area networks (CAN) in road vehicles (UDSonCAN).

UDSonCAN references Part°1 and Part°2 of ISO 14229 and specifies implementation requirements of the

diagnostic services to be used for diagnostic communication over CAN.

NOTE UDSonCAN does not specify any requirement for the in-vehicle CAN bus architecture.

This part of ISO 14229 does not include any redundant information of the documents as listed in the

Introduction. It focuses on

⎯ additional requirements specific to the implementation of UDS on the CAN network, and

⎯ specific restrictions in the implementation of UDS on the CAN network.
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 11898-1, Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical

signalling

ISO 11898-2, Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit

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 services

ISO 15765-1, Road vehicles — Diagnostic communication over controller area network (DoCAN) — Part 1:

General information and use case definition

ISO 15765-2, Road vehicles — Diagnostic communication over controller area network (DoCAN) — Part 2:

Transport protocol and Network layer services

ISO 15765-4, Road vehicles — Diagnostic communication over controller area network (DoCAN) — Part 4:

Requirements for emissions-related systems
© ISO 2011 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/DIS 14229-3
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 14229-1, ISO 14229-2,

ISO 15765-1, ISO 15765-2 and ISO 15765-4 apply.
3.2 Abbreviated terms
CF consecutive frame
DA destination address
DLC data length code
FF first frame
FC flow control
ID identifier
NA network address
SA source address
SF single frame
SM subnet mask
SOM start of message
STRT serviceToRespondTo
TA target address
UDS unified diagnostic services
USDT unacknowledged segmented data transfer
UUDT unacknowledged unsegmented data transfer
4 Conventions

This part of ISO 14229 is based on the conventions discussed in the OSI Service Conventions

(ISO/IEC 10731:1994) as they apply for diagnostic services.
2 © ISO 2011 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/DIS 14229-3
5 Document overview
Figure 1 illustrates the documents required to implement UDSonCAN.
Figure 1 — UDSonCAN document reference according to OSI model
© ISO 2011 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/DIS 14229-3
6 Unified diagnostic services implementation on CAN
6.1 General

This clause defines how the diagnostic services as defined in ISO 14229-1 apply to DoCAN. For each

applicable service, the applicable subfunction and data parameters are defined.

NOTE The subfunction parameter definitions take into account that the most significant bit is used for the

suppressPosRspMsgIndicationBit parameter as defined in ISO 14229-1.
6.2 UDS on CAN services overview

The purpose of Table 2 is to reference all ISO 14229-1 and ISO 14229-2 services as they are applicable for

an implementation in ISO 14229-3 UDSonCAN. Table 2 contains the sum of all applicable services. Certain

applications using this part of ISO 14229 to implement UDSonCAN may restrict the number of useable

services and may categorize them in certain application areas/diagnostic sessions (default session,

programming session, etc.).

Services in Table 2 that are marked "No CAN specific requirements" shall be implemented as defined in

ISO 14229-1 and ISO 14229-2 with no additional restrictions. Services that are marked "CAN specific

requirements" shall be implemented as defined by the subclause listed in the Table 2 entry.

Table 2 — Overview of applicable ISO 14229-1 Unified diagnostic services and data ranges

Diagnostic service name Reference in this
Comment
(ISO 14229-1) document
Diagnostic and Communication Management Functional Unit
DiagnosticSessionControl No CAN specific requirements ---
ECUReset No CAN specific requirements ---
SecurityAccess No CAN specific requirements ---
CommunicationControl No CAN specific requirements ---
TesterPresent No CAN specific requirements ---
SecuredData-Transmission No CAN specific requirements ---
ControlDTCSetting No CAN specific requirements ---
ResponseOnEvent CAN specific requirements see 6.3
LinkControl No CAN specific requirements ---
Data Transmission Functional Unit
ReadDataByIdentifier No CAN specific requirements ---
ReadMemoryByAddress No CAN specific requirements ---
ReadScalingDataByIdentifier No CAN specific requirements ---
ReadDataByPeriodicIdentifier CAN specific requirements see 6.4
DynamicallyDefineDataIdentifier CAN specific requirements ---
WriteDataByIdentifier No CAN specific requirements ---
WriteMemoryByAddress No CAN specific requirements ---
4 © ISO 2011 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/DIS 14229-3
Table 2 — (continued)
Data Transmission Functional Unit
ReadDTCInformation No CAN specific requirements ---
ClearDiagnosticInformation No CAN specific requirements ---
Input/Output Control Functional Unit
InputOutputControlByIdentifier No CAN specific requirements ---
Remote Activation Of Routine Functional Unit
RoutineControl No CAN specific requirements ---
Upload/Download Functional Unit
RequestDownload No CAN specific requirements ---
RequestUpload No CAN specific requirements ---
TransferData No CAN specific requirements ---
RequestTransferExit No CAN specific requirements ---
6.3 ResponseOnEvent (0x86) service DoCAN implementation requirements

In addition to the generic implementation requirements stated in ISO 14229-1 the following additional CAN

specific implementation requirements shall apply:

a) While the ResponseOnEvent service is active, the server shall be able to process concurrent diagnostic

request and response messages accordingly. This should be accomplished with a different

serviceToRespondTo CAN Identifiers. If the same diagnostic request/response CAN Identifiers are used

for diagnostic communication and the serviceToRespondTo-responses, the following restrictions shall

apply, see Figure 2:

1) The server may ignore an incoming diagnostic request issued by the client that initiated the event,

after an event has occurred and the serviceToRespondTo-response is in progress, until the

serviceToRespondTo-response is completed. If another client issued the request, the server may or

may not ignore the request, depending on the server’s capabilities.

2) When the client receives any response after sending a diagnostic request, the response shall be

classified according to the possible serviceToRespondTo-responses and the expected diagnostic

responses to the previously sent request.

i) If the response is a serviceToRespondTo-response (one of the possible responses set up with

ResponseOnEvent-service), the client shall repeat the request after the serviceToRespondTo-

response has been received completely.

ii) If the response is ambiguous (i.e. the response could originate from the serviceToRespondTo

initiated by an event or from the response to a diagnostic request), the client shall present the

response both as a serviceToRespondTo-response and as the response to the diagnostic

request. The client shall not repeat the request with the exception of NegativeResponseCode

busyRepeatRequest (0x21) (see the negative response code definitions in ISO 14229-1).

© ISO 2011 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/DIS 14229-3
client server
STRT-ResponseFF
SF-Diag-Request Event
server ignores request
STRT-FC
STRT-CF
STRT-CF
the STRT-response is completed
and the tester repeats the
diagnostic request, if the
response is a valid STRT-
SF-Diag-Request
response.
server responds to request
Response
Figure 2 — Concurrent request when the event occurs

b) When the specified event is detected, the server shall respond immediately with the appropriate

serviceToRespondTo-response message. The immediate serviceToRespondTo-response message shall

not disrupt any other diagnostic request or response transmission already in progress (i.e. the

serviceToRespondTo-response shall be delayed until the current message transmission has been

completed — see Figure 3.
Figure 3 — Event occurrence during a message in progress
6 © ISO 2011 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/DIS 14229-3

6.4 ReadDataByPeriodicIdentifier (0x2A) service DoCAN implementation requirements

6.4.1 Response Message Type - UUDT

The ReadDataByPeriodicIdentifier service allows the client to request the periodic transmission of data record

values from the server identified by one or more periodicDataIdentifiers. For service 0x2A implementation on

DoCAN, the response message type #2 (UUDT) format shall be supported according to ISO 14229-1.

Response message type #2 (UUDT) is mapped onto a UUDT message, using a different CAN identifier as

used for the USDT response message. The UUDT message for a single periodicDataIdent

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.