ISO 13209-3:2012

INTERNATIONAL ISO
STANDARD 13209-3
First edition
2012-08-15

Road vehicles — Open Test sequence
eXchange format (OTX) —
Part 3:
Standard extensions and requirements
Véhicules routiers — Format public d'échange de séquence-tests
(OTX) —
Partie 3: Exigences et spécifications des extensions du standard




Reference number
ISO 13209-3:2012(E)
©
ISO 2012

---------------------- Page: 1 ----------------------
ISO 13209-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 13209-3:2012(E)
Contents Page
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 2
4 Requirements . 3
4.1 Basic principles for requirements definition . 3
4.2 Requirement priorities . 3
4.3 Requirement listing . 4
5 Extension overview . 7
5.1 General . 7
5.2 Dependencies . 7
5.3 Basic characteristics of the OTX extensions . 8
6 OTX DateTime extension . 10
6.1 Introduction . 10
6.2 Terms . 10
7 OTX DiagCom extension . 13
7.1 Introduction . 13
7.2 General considerations . 13
7.3 Data types. 21
7.4 Exceptions . 24
7.5 Variable access . 26
7.6 Actions. 27
7.7 Terms . 42
8 OTX DiagDataBrowsing extension . 67
8.1 Introduction . 67
8.2 Data types. 67
8.3 Variable access . 69
8.4 Terms . 69
9 OTX EventHandling extension . 74
9.1 Introduction . 74
9.2 Data types. 74
9.3 Variable access . 76
9.4 Actions. 76
9.5 Terms . 78
10 OTX Flash extension . 85
10.1 Introduction . 85
10.2 Data types. 86
10.3 Exceptions . 88
10.4 Variable access . 89
10.5 Actions. 89
10.6 Terms . 92
11 OTX HMI extension . 113
11.1 Introduction . 113
© ISO 2012 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 13209-3:2012(E)
11.2 Data types . 116
11.3 Exceptions . 118
11.4 Variable access . 119
11.5 Actions . 119
11.6 Terms . 130
11.7 Signatures . 134
12 OTX i18n extension. 137
12.1 Introduction . 137
12.2 Data types . 137
12.3 Exceptions . 138
12.4 Variable access . 139
12.5 Terms . 139
13 OTX Job extension . 147
13.1 Introduction . 147
13.2 Exceptions . 147
13.3 Actions . 148
13.4 Terms . 153
13.5 Standard signature definitions . 157
14 OTX Logging extension . 160
14.1 Introduction . 160
14.2 Data types . 161
14.3 Variable access . 162
14.4 Actions . 163
14.5 Terms . 165
15 OTX Math extension . 167
15.1 Introduction . 167
15.2 Terms . 167
16 OTX Measure extension . 170
16.1 Introduction . 170
16.2 Data types . 170
16.3 Exceptions . 171
16.4 Variable access . 172
16.5 Signatures . 172
16.6 Actions . 175
16.7 Terms . 177
17 OTX Quantities extension . 183
17.1 Introduction . 183
17.2 Data types . 185
17.3 Exceptions . 187
17.4 Variable access . 188
17.5 Terms . 188
18 OTX StringUtil extension . 196
18.1 Introduction . 196
18.2 Data types . 196
18.3 Exceptions . 197
18.4 Variable access . 198
18.5 Terms . 198
Annex A (normative) Comprehensive checker rule listing . 205
Annex B (normative) OTX DiagCom extension data type mappings . 208
Annex C (normative) OTX DiagMetaData auxiliary for the OTX DiagCom extension . 210
Annex D (normative) OTX standard signature documents . 214
Annex E (informative) Test sequence examples . 215
Annex F (informative) OTX DiagComRaw extension for resource-restrained systems . 218
iv © ISO 2012 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 13209-3:2012(E)
Annex G (normative) XML Schemas . 231
Bibliography . 278

© ISO 2012 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 13209-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 13209-3 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
ISO 13209 consists of the following parts, under the general title Road vehicles — Open Test sequence
eXchange format (OTX):
 Part 1: General information and use cases
 Part 2: Core data model specification and requirements
 Part 3: Standard extensions and requirements
vi © ISO 2012 – All rights reserved

---------------------- Page: 6 ----------------------
ISO 13209-3:2012(E)
Introduction
Diagnostic test sequences are utilized whenever automotive components or functions with diagnostic abilities
are being diagnosed, tested, reprogrammed or initialised by off-board test equipment. Test sequences define
the succession of interactions between the user (i.e. workshop or assembly line staff), the diagnostic
application (the test equipment) and the vehicle communication interface as well as any calculations and
decisions that have to be carried out. Test sequences provide a means to define interactive, guided
diagnostics or similar test logic.
Today, the automotive industry mainly relies on paper documentation and/or proprietary authoring environ-
ments to document and to implement such test sequences for a specific test application. An author who is
setting up engineering, assembly line or service diagnostic test applications needs to implement the required
test sequences manually, supported by non-uniform test sequence documentation, most likely using different
authoring applications and formats for each specific test application. This redundant effort can be greatly
reduced if processes and tools support the OTX concept.
ISO 13209 proposes an open and standardized format for the human- and machine-readable description of
diagnostic test sequences. The format supports the requirements of transferring diagnostic test sequence
logic uniformly between electronic system suppliers, vehicle manufacturers and service dealerships/repair
shops.
ISO 13209-2 represents the requirements and technical specification for the fundament of the OTX format,
namely the "OTX Core". The Core describes the basic structure underlying every OTX document. This
comprises detailed data model definitions of all required control structures by which test sequence logic is
described, but also definitions of the outer, enveloping document structure in which test sequence logic is
embedded. To achieve extensibility the core also contains well-defined extension points that allow a separate
definition of additional OTX features – without the need to change the core data model.
This part of ISO 13209 extends the Core by a set of additional features, using the extension mechanism rules
described in ISO 13209-2. The extensions defined herein comprise features which allow diagnostic
communication to a vehicle's diagnostic interface, flashing, executing diagnostic jobs, controlling
measurement equipment, internationalisation, working with physical units, accessing the environment,
communication via a human machine interface (HMI) and other utility extensions.

© ISO 2012 – All rights reserved vii

---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO 13209-3:2012(E)

Road vehicles — Open Test sequence eXchange format
(OTX) —
Part 3:
Standard extensions and requirements
1 Scope
This part of ISO 13209 defines the Open Test sequence eXchange (OTX) extension requirements and data
model specifications.
The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4.
The data model specification aims at an exhaustive definition of all features of the OTX extensions which have
been implemented to satisfy the requirements. This part of ISO 13209 establishes rules for the syntactical
entities of each extension. Each of these syntactical entities is accompanied by semantic rules which
determine how OTX documents containing extension features are to be interpreted. The syntax rules are
provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity
diagrams and prose definitions.
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/IEC 646:1991, Information technology — ISO 7-bit coded character set for information interchange
ISO 8601:2004, Data elements and interchange formats — Information interchange — Representation of
dates and times
ISO/IEC 8859-1:1998, Information technology — 8-bit single-byte coded graphic character sets — Part 1:
Latin alphabet No. 1
ISO/IEC 10646, Information technology — Universal Multiple-Octet Coded Character Set (UCS)
ISO/IEC 13209-1, Road vehicles — Open Test sequence eXchange format (OTX) — Part 1: General
information and use cases
ISO/IEC 13209-2, Road vehicles — Open Test sequence eXchange format (OTX) — Part 2: Core data model
specification and requirements
ISO/IEC 19501:2005, Information technology — Open Distributed Processing — Unified Modeling Language
(UML) Version 1.4.2
ISO 14229 (all parts), Road vehicles — Unified diagnostic services (UDS)
ISO 22900 (all parts), Road vehicles — Modular vehicle communication interface (MVCI)
© ISO 2012 – All rights reserved 1

---------------------- Page: 8 ----------------------
ISO 13209-3:2012(E)
ISO 22901 (all parts), Road vehicles — Open diagnostic data exchange (ODX)
RFC 1866, Hypertext Markup Language - 2.0
SAE J1979, E/E Diagnostic Test Modes
W3C XPtr:2003, W3C Recommendation: XPointer Framework (all parts)
W3C XLink:2001, W3C Recommendation: XML Linking Language (XLink) Version 1.0
W3C XML:2008, W3C Recommendation: Extensible Markup Language (XML) 1.0 (Fifth Edition)
W3C XMLNS:2009, W3C Recommendation: Namespaces in XML 1.0 (Third Edition)
W3C XSD:2004, W3C Recommendation: XML Schema (all parts)
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 13209-1, ISO 13209-2 and the
following apply.
3.1.1
custom screen
screen with attributes and fields defined by a test sequence author
3.1.2
dialog
screen with predefined attributes and fields which can be set or read from an OTX sequence
3.1.3
ECOS measurement device
widely-used embedded system for testing electrical consumer's current and voltage curves
3.1.4
modal dialog
dialog which is blocking the flow execution until the user dismisses it
3.1.5
non-modal screen
asynchronous, non-blocking screen which is still displayed while the test sequence execution continues
3.1.6
tester
computer system attached to a vehicle via a Vehicle Communication Interface, running a diagnostic
application
3.1.7
text ID
string reference to a thesaurus data base entry containing localized string translations
3.2 Abbreviated terms
API Application Programming Interface
DTC Diagnostic Trouble Code
2 © ISO 2012 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 13209-3:2012(E)
ECOS Electric Check-Out System
ECU Electronic Control Unit
GUI Graphical User Interface
HMI Human Machine Interface
IFD Interface Definition (OTX extension)
NOP No Operation Performed
OEM Original Equipment Manufacturer
OTX Open Test sequence eXchange
PDU Protocol Data Unit
UI User Interface
UML Unified Modeling Language
VCI Vehicle Communication Interface
XML Extensible Markup Language
XSD XML Schema Definition

4 Requirements
4.1 Basic principles for requirements definition
Basic principles have been established as a guideline to define the OTX requirements:
a) OTX requirements specify the conditions that the OTX data model and format shall satisfy.
b) All stakeholders (System Suppliers, OEMs, Tool Suppliers), which offer diagnostic test procedures are
expected to implement and follow the requirements of this standard.
The content of OTX documents and the quality of the information is the responsibility of the originator.
4.2 Requirement priorities
Each of the following requirements carries a priority-attribute which can be set to SHALL or SHOULD.
 SHALL:
The requirement represents stakeholder-defined characteristics the absence of which will result in a
deficiency that cannot be compensated by other means.
 SHOULD:
If the requirement defined characteristic is not or not fully implemented in the data model, it does not
result in a deficiency, because other features in the data model can be used to circumvent this.
© ISO 2012 – All rights reserved 3

---------------------- Page: 10 ----------------------
ISO 13209-3:2012(E)
4.3 Requirement listing
Extensions_R01 – Read current date and time
Priority: SHALL
Rationale: It shall be possible to retrieve the current date and time.
Description: The current date and time shall be accessible in a way appropriate for calculating durations
between two dates but also for generating a human readable form of a date.
Extensions_R02 – Support but not require ODX
Priority: SHALL
Rationale: For communication with vehicle ECUs, the usage of ODX shall be supported but not forced.
Description: Any vehicle communication related extension data model shall match to a useful subset of the
functionality of ODX.
Extensions_R03 – Handle flash sessions
Priority: SHALL
Rationale: Functionality shall be provided to browse and select flash sessions.
Description: A extension for flashing shall provide the possibility to select by direction and name.
Extensions_R04 – Low level flash data access
Priority: SHALL
Rationale: Functionality shall be provided for browsing and selecting data from the flash environment
(download container).
Description: The data shall be clustered in blocks and segments. Security functions, used by modern data
formats like ODX Flash shall be supported.
Extensions _R05 – Flash data storage
Priority: SHALL
Rationale: Uploaded flash data shall be stored in local storage.
Description: For flash data upload, an OTX extension for flashing shall provide functionality to store in a
selected format.
Extensions _R06 – Enable developer to use OTX in place of ODX Java Jobs
Priority: SHALL
Rationale: Functionality shall be provided to emulate ODX Java Jobs by OTX sequences.
Description: A job extension shall enable developers to run OTX sequences as ODX Java Jobs.
SingelEcuJob, SecurityAccessJob and FlashJob shall be supported.
4 © ISO 2012 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 13209-3:2012(E)
Extensions _R07 – Provide means for diagnostic communication with vehicle ECUs
Priority: SHALL
Rationale: Functionality shall be provided for diagnostic communication with a vehicle's ECU systems.
Description: There shall be an OTX extension which allows configuring and executing diagnostic services of
vehicle ECUs. It shall be possible establish a communication channel to a particular ECU, to configure request
parameters of a diagnostic service which is sent to the ECU and to analyze the response parameters of the
ECU. The description of communication channels, diagnostic services and parameters shall happen in a
human-readable and symbolic way; any existing diagnostic symbolic-to-binary mapping (e.g. ODX) shall be
supported. The actual functionality for sending a diagnostic service and receiving shall be prov
...