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

Status
Withdrawn
Publication Date
14-Mar-2013
Withdrawal Date
14-Mar-2013
Current Stage
9599 - Withdrawal of International Standard
Start Date
07-Feb-2020
Completion Date
19-Apr-2025
Ref Project

Relations

Standard
ISO 14229-1:2013 - Road vehicles -- Unified diagnostic services (UDS)
English language
392 pages
sale 15% off
Preview
sale 15% off
Preview

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 2013
©  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

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
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 .
...

Questions, Comments and Discussion

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