1、BS ISO22901-1:2008ICS 43.180NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBRITISH STANDARDRoad vehicles Open diagnostic dataexchange (ODX)Part 1: Data model specificationThis British Standardwas published underthe authority of theStandards Policy andStrategy Committee on 30No
2、vember 2008 BSI 2008ISBN 978 0 580 55358 5Amendments/corrigenda issued since publicationDate CommentsBS ISO 22901-1:2008National forewordThis British Standard is the UK implementation of ISO 22901-1:2008.The UK participation in its preparation was entrusted to TechnicalCommittee AUE/16, Electrical a
3、nd electronic equipment.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisionsof a contract. Users are responsible for its correct application.Compliance with a British Standard cannot
4、 confer immunityfrom legal obligations.BS ISO 22901-1:2008Reference numberISO 22901-1:2008(E)ISO 2008INTERNATIONAL STANDARD ISO22901-1First edition2008-11-15Road vehicles Open diagnostic data exchange (ODX) Part 1: Data model specification Vhicules routiers change de donnes de diagnostic ouvert (ODX
5、) Partie 1: Spcification de modle de donnes BS ISO 22901-1:2008ISO 22901-1:2008(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed
6、to and installed on the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the so
7、ftware products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it
8、 is found, please inform the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO 2008 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
9、and microfilm, without permission in writing from either ISO at the address below or ISOs 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 copyrightiso.org Web www.iso.org Published in Switzerland
10、ii ISO 2008 All rights reservedBS ISO 22901-1:2008ISO 22901-1:2008(E) ISO 2008 All rights reserved iiiContents Page Foreword .v Introductionvi 1 Scope1 2 Normative references1 3 Abbreviated terms .2 4 ODX use cases.3 4.1 General .3 4.2 Use case 1: ODX process chain.3 4.3 Use case 2: Cross vehicle pl
11、atform ECU diagnostic development4 4.4 Use case 3: Franchise and aftermarket service dealership diagnostic tool support.5 4.5 Architecture of a Modular VCI compliant D-server 6 4.6 ODX benefit examples.6 5 Specification release version information8 5.1 Specification release version location 8 5.2 Sp
12、ecification release version.8 6 Introduction to and use of Unified Modelling Language (UML)8 6.1 General aspects.8 6.2 Class diagrams 8 6.3 Mapping to XML.12 7 ODX data model.14 7.1 General modelling principles .14 7.2 ODX package .26 7.3 ODX data model for diagnostics29 7.4 Usage scenarios (diagnos
13、tic).183 7.5 ODX data model for ECU memory programming.229 7.6 ECU programming usage scenarios (flash)253 7.7 ECU variant coding usage scenarios 265 7.8 ODX data model for ECU configuration 266 7.9 Function dictionary .276 8 Data model implementation in XML.287 8.1 Classifier.287 8.2 Relationships .
14、295 9 Packaged ODX data (PDX)304 9.1 Overview.304 9.2 Structure of PDX package 305 9.3 Usage scenarios 308 Annex A (normative) Enumerations and pre-defined values .315 Annex B (normative) ODX checker rules326 Annex C (normative) XML schema345 Annex D (informative) User-defined formats for flashdata.
15、420 Annex E (informative) Coherent examples for diagnostic services 424 Annex F (informative) ECU-MEM example464 Annex G (informative) Session security example472 BS ISO 22901-1:2008ISO 22901-1:2008(E) iv ISO 2008 All rights reservedBibliography 485 BS ISO 22901-1:2008ISO 22901-1:2008(E) ISO 2008 Al
16、l rights reserved vForeword 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 su
17、bject 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 (
18、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 commi
19、ttees 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 b
20、e held responsible for identifying any or all such patent rights. ISO 22901-1 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3, Electrical and electronic equipment. ISO 22901 consists of the following parts, under the general title Road vehicles Open diagnostic data ex
21、change (ODX): Part 1: Data model specification The following parts are under preparation: Part 2: Emissions-related diagnostic dataBS ISO 22901-1:2008ISO 22901-1:2008(E) vi ISO 2008 All rights reservedIntroduction The purpose of this part of ISO 22901 is to define the data format for transferring El
22、ectronic Control Unit (ECU) diagnostic and programming data between the system supplier, vehicle manufacturer and service dealerships and diagnostic tools of different vendors. In todays automotive industry, an informal description is generally used to document the diagnostic data stream information
23、 of vehicle ECUs. Any user wishing to use the ECU diagnostic data stream documentation to set up development tools or service diagnostic test equipment needs a manual transformation of this documentation into a format readable by these tools. This effort will no longer be required if the diagnostic
24、data stream information is provided in Open Diagnostic Data Exchange (ODX) format and if those tools support the ODX format. This part of ISO 22901 includes the data model definition of ECU diagnostic and programming data and the related vehicle interface description in Unified Modelling Language (U
25、ML). This part of ISO 22901 also includes an implementation by Extensible Mark-up Language (XML) schema in Annex C. BS ISO 22901-1:2008INTERNATIONAL STANDARD ISO 22901-1:2008(E) ISO 2008 All rights reserved 1Road vehicles Open diagnostic data exchange (ODX) Part 1: Data model specification 1 Scope T
26、his part of ISO 22901 specifies the concept of using a new industry standard diagnostic format to make diagnostic data stream information available to diagnostic tool application manufacturers, in order to simplify the support of the aftermarket automotive service industry. The Open Diagnostic Data
27、Exchange (ODX) modelled diagnostic data are compatible with the software requirements of the Modular Vehicle Communication Interface (MVCI), as specified in ISO 22900-2 and ISO 22900-3. The ODX modelled diagnostic data will enable an MVCI device to communicate with the vehicle Electronic Control Uni
28、t(s) (ECU) and interpret the diagnostic data contained in the messages exchanged between the external test equipment and the ECU(s). For ODX compliant external test equipment, no software programming is necessary to convert diagnostic data into technician readable information to be displayed by the
29、tester. The ODX specification contains the data model to describe all diagnostic data of a vehicle and physical ECU, e.g. diagnostic trouble codes, data parameters, identification data, input/output parameters, ECU configuration (variant coding) data and communication parameters. ODX is described in
30、 Unified Modelling Language (UML) diagrams and the data exchange format uses Extensible Mark-up Language (XML). The ODX modelled diagnostic data describe: protocol specification for diagnostic communication of ECUs; communication parameters for different protocols and data link layers and for ECU so
31、ftware; ECU programming data (Flash); related vehicle interface description (connectors and pinout); functional description of diagnostic capabilities of a network of ECUs; ECU configuration data (variant coding). Figure 1 shows the usage of ODX in the ECU life cycle. The purpose of this part of ISO
32、 22901 is to ensure that diagnostic data from any vehicle manufacturer is independent of the testing hardware and protocol software supplied by any test equipment manufacturer. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated
33、 references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. BS ISO 22901-1:2008ISO 22901-1:2008(E) 2 ISO 2008 All rights reservedISO 8601, Data elements and interchange formats Information interchange Represen
34、tation of dates and times ISO/IEC 8859-1, Information technology 8-bit single-byte coded graphic character sets Part 1: Latin alphabet No. 1 ISO/IEC 8859-2, Information technology 8-bit single-byte coded graphic character sets Part 2: Latin alphabet No. 2 ISO/IEC 10646, Information technology Univer
35、sal Multiple-Octet Coded Character Set (UCS) ISO 22900-2, Road vehicles Modular vehicle communication interface (MVCI) Part 2: Diagnostic protocol data unit application programming interface (D-PDU API) ISO 22900-3, Road vehicles Modular vehicle communication interface (MVCI) Part 3: Diagnostic serv
36、er application programming interface (D-Server API) IEEE 754, Binary floating-point arithmetic XML Schema 2, XML Schema Part 2: Datatypes, 2nd Edition, W3C Recommendation, 2004-10-28 ASAM MCD 2, Harmonized Data Objects Version 1.0 3 Abbreviated terms API Application Programming Interface ASAM Associ
37、ation for Standardisation of Automation and Measuring Systems ASCII American Standard for Character Information Interchange DOP Data Object Property ECU Electronic Control Unit GMT Greenwich Mean Time MCD Measurement, Calibration and Diagnosis ODX Open Diagnostic Data Exchange OEM Original Equipment
38、 Manufacturer PDU Protocol Data Unit PDX Packaged ODX UML Unified Modelling Language UTC Coordinated Universal Time VMM Vehicle Message Matrix W3C World Wide Web Consortium XML Extensible Mark-up Language BS ISO 22901-1:2008ISO 22901-1:2008(E) ISO 2008 All rights reserved 34 ODX use cases 4.1 Genera
39、l Figure 1 Usage of ODX data in the ECU life cycle shows the usage of ODX in the ECU life cycle. Engineering, manufacturing, and service specify communication protocol and data to be implemented in the ECU. This information will be documented in a structured format utilizing the XML standard and by
40、an appropriate ODX authoring tool. There is potential to generate ECU software from the ODX file. Furthermore, the same ODX file is used to setup the diagnostic engineering tools to verify proper communication with the ECU and to perform functional verification and compliance testing. Once all quali
41、ty goals are met, the ODX file may be released to a diagnostic database. Diagnostic information is now available to manufacturing, service, OEM franchised dealers, and aftermarket service outlets via Intranet and Internet. Figure 1 Usage of ODX data in the ECU life cycle 4.2 Use case 1: ODX process
42、chain Figure 2 shows an example of how ODX data is used in a process chain consisting of three phases, as described below. a) Phase A of the development process between vehicle manufacturer and system supplier comprises the exchange of ODX data to support the development of the diagnostic implementa
43、tion in the ECU and the development tools. b) In phase B of the development process at the vehicle manufacturer, the engineering departments release the ODX data into a diagnostic database. The manufacturing and service departments use the ODX data as the basis to setup the End-Of-Line test equipmen
44、t and service application development tools and generate service documentation. c) Phase C of the development process supports the service dealership diagnostic and programming tools. The service department develops service tool application software based on the ODX data model. The diagnostic and pr
45、ogramming software is now available to all service dealerships. BS ISO 22901-1:2008ISO 22901-1:2008(E) 4 ISO 2008 All rights reservedThe ODX data is the base for all exchange of diagnostic and programming data. Figure 2 Example of ODX process chain 4.3 Use case 2: Cross vehicle platform ECU diagnost
46、ic development A vehicle manufacturer implements electronic systems into multiple new vehicle platforms. There is little variation in the electronic system across the different vehicle platforms. Utilizing the same ECU in many different vehicle platforms reduces redundant development effort. The maj
47、ority of design, normal operation, and diagnostic data of an electronic system can be reused in various vehicles. Large automotive manufacturer tend to have multiple engineering development centres. Diagnostic data exchange can be based on the ODX data format to reduce the amount of proofreading of
48、diagnostic data at different development sites. Establishing an ODX compliant tool chain will avoid re-authoring diagnostic data into various specific formats at different engineering sites. BS ISO 22901-1:2008ISO 22901-1:2008(E) ISO 2008 All rights reserved 5Figure 3 shows an example of cross vehic
49、le platform ECU diagnostic development between two engineering sites. Figure 3 Example of cross vehicle platform ECU diagnostic development 4.4 Use case 3: Franchise and aftermarket service dealership diagnostic tool support Figure 4 shows one of many scenarios a vehicle manufacturer may implement to support the service dealership, franchise and aftermarket. ODX files may be converted into an ODX runtime format for download to the dealership diagnostic system. IMPORTANT The
