Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer — Amendment 1

Véhicules routiers — Services de diagnostic unifiés (SDU) — Partie 1: Couche application — Amendement 1

General Information

Status
Published
Publication Date
24-Oct-2022
Current Stage
6060 - International Standard published
Start Date
25-Oct-2022
Due Date
29-Jun-2023
Completion Date
25-Oct-2022
Ref Project

Relations

Buy Standard

Standard
ISO 14229-1:2020/Amd 1:2022 - Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer — Amendment 1 Released:25. 10. 2022
English language
10 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 14229-1
Third edition
2020-02
AMENDMENT 1
2022-10
Road vehicles — Unified diagnostic
services (UDS) —
Part 1:
Application layer
AMENDMENT 1
Véhicules routiers — Services de diagnostic unifiés (SDU) —
Partie 1: Couche application
AMENDEMENT 1
Reference number
ISO 14229-1:2020/Amd.1:2022(E)
© ISO 2022

---------------------- Page: 1 ----------------------
ISO 14229-1:2020/Amd.1:2022(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
  © ISO 2022 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 14229-1:2020/Amd.1:2022(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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
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. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,
Data communication.
A list of all parts in the ISO 14229 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iii
© ISO 2022 – All rights reserved

---------------------- Page: 3 ----------------------
ISO 14229-1:2020/Amd.1:2022(E)
Road vehicles — Unified diagnostic services (UDS) —
Part 1:
Application layer
AMENDMENT 1

8.4, Table 2
Replace “80 to 82 ” with “80 to 83 ”.
16 16 16 16
Replace “83 to 88 ” with “84 to 88 ”.
16 16 16 16

11.6.2.3, Table 240, entry “memorySize”
Replace
“The memorySize shall be greater than 1.”
with
"The memorySize shall be greater than 0000 .".
16

12.2.2.1, Table 296, entry “#5”
Replace “Memory Selection” with “MemorySelection”.

12.2.4, Table 299, entry “31 ”
16
Replace
“This NRC shall be returned if the specified groupOfDTC parameter is not supported.”
with
“This NRC shall be returned if the specified groupOfDTC or MemorySelection parameter is not
supported.”.

12.3.1.1, last paragraph
Replace
“When using paged-buffer-handling to read DTCs (especially for SubFunction = reportDTCByStatusMask),
it is possible that the number of DTCs can decrease while creating the response. In such a case the
response shall be filled up with DTC 000000 and DTC status 00 . The client shall treat these DTCs as
16 16
not present in the response message.”
with
1
© ISO 2022 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 14229-1:2020/Amd.1:2022(E)
“The service ReadDTCInformation can result in responses that contain information
from many DTCs (such as reportDTCByStatusMask, reportDTCSnapshotIdentification,
reportDTCExtDataRecordByRecordNumber, …). With paged-buffer-handling to read DTCs it is possible
that:
— the DTC status is changing and thus the number of DTCs matching the filter is decreased; or
— the DTC is removed due to fault memory overflow and thus no more data to read is available.
In this case the response shall be filled up with DTC 000000 and statusOfDTC 00 . In case of
16 16
SubFunction reportDTCExtDataRecordByRecordNumber the DTCExtDataRecord data bytes shall be
also filled up with 00 .
16

12.3.1.19
Replace all occurrences of “DTCExtDataRecordNumber” with “UserDefDTCExtDataRecordNumber” in
12.3.1.19.

12.3.2.1, Table 312, entry #6

12.3.2.2, Table 317
12.3.2.3, Table 318
12.3.3.2, Table 335
12.3.5.17, heading
12.3.5.17.1
12.3.5.17.3, Table 388 (2 occurrences)
12.3.5.17.3, Table 389 (2 occurrences)
Replace
“reportDTCExtendedDataRecordIdentification”
with
“reportDTCExtDataRecordByRecordNumber”.

12.3.2.3, Table 318
Replace the table cell “UserDefDTCSnapshotRecordNumber” with the following two table cells:
DTCSnapshotRecordNumber
DTCSnapshotRecordNumber is a 1-Byte value indicating the number of the specific DTCSnapshot data
record requested for a client defined DTCMaskRecord via the reportDTCSnapshotByDTCNumber Sub-
Function.
DTCSnapshot data record number 00 and F0 shall be reserved for legislated purposes (e.g. VOBD).
16 16
DTCSnapshot records in the range of 01 through EF and F1 through FE shall be available for ve-
16 16 16 16
hicle manufacturer specific usage. A value of FF requests the server to report all stored DTCSnapshot
16
data records at once.
2
  © ISO 2022 – All rights reserved

---------------------- Page: 5 ----------------------
ISO 14229-1:2020/Amd.1:2022(E)
UserDefDTCSnapshotRecordNumber
UserDefDTCSnapshotRecordNumber is a 1-Byte value indicating the number of the specific DTCSnapshot
data record requested for a client defined DTCMaskRecord via the reportUserDefMemoryDTCSnapsho-
tRecordByDTCNumber SubFunction.
UserDefDTCSnapshot records in the range of 00 through FE shall be available for vehicle manufac-
16 16
turer specific usage. A value of FF requests the server to report all stored UserDefDTCSnapshot data
16
records at once.

12.3.2.3, Table 318, entry for DTCReadinessGroupIdentifier
Replace
“specifies the reference to the the DTC readiness group and associated”
with
“specifies the reference to the DTC readiness group and associated”.

12.3.2.3,
...

Questions, Comments and Discussion

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