ISO/TC 22/SC 31/WG 5 - Test equipment/Data eXchange Formats

This document defines the Open Test sequence eXchange (OTX) additional 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 document 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.

ISO 22901-3:2018 specifies machine-readable descriptions of all fault symptom algorithms which are implemented as diagnostic software in an electronic control unit (ECU). The main use case is the standardized data exchange from a function & software supplier to a vehicle manufacturer (VM) in order to enable a tool-based information processing. Based on the FXD content and associated calibration values, several end user documents can be generated such as the "summary sheet" needed as part of the vehicle type approval documentation package or the "repair and maintenance information" (RMI). The expected main benefits of the FXD approach are an overall efficiency improvement as well as an independency of supplier- and VM-specific format handling.

ISO 22900-2:2017 specifies the diagnostic protocol data unit application programming interface (D-PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. ISO 22900-2:2017 covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI module description files accompany this document. The purpose of ISO 22900-2:2017 is to ensure that diagnostic and reprogramming applications from any vehicle or tool manufacturer can operate on a common software interface and can easily exchange MVCI protocol module implementations.

ISO 27145-6:2015 defines the requirements for the external test equipment as listed: - a means of establishing communications between a WWH-OBD-equipped vehicle and external test equipment; - a set of diagnostic services, including addressing methods, to be provided by the external test equipment in order to exercise the services defined in ISO 27145‑3. ISO 27145-6:2015 describes the minimum capabilities or functions in the external test equipment. Additional functionality, e.g. non WWH-OBD protocols or retrieval of repair and maintenance information, can be integrated into the external test equipment according to the test equipment manufacturer needs. The external test equipment designer ensures that no such capability or function can adversely affect either a WWH-OBD-equipped vehicle connected to the equipment, or the equipment itself. When the external test equipment implements functionality, which is not covered by ISO 27145‑3, this functionality is not linked to the timing requirements defined in this International Standard.

ISO 22900-3:2012 focuses on the description of an object-oriented programming interface. The objective is the ability to implement server applications, used during the design, production and maintenance phase of a vehicle communication system, compatible to each other and thus exchangeable. From a user's perspective, access and integration of on-board control units is provided by a corresponding application, the communication server and a VCI module for diagnostics. The user is granted access for the handling of control units (ECUs) in vehicles for the diagnostic services.

The Open Test sequence eXchange (OTX) Core, defined in ISO 13209-2, describes the basic structure underlying every OTX document. ISO 13209-3:2012 extends the Core by a set of additional features, using the extension mechanism rules described in ISO 13209-2. The extensions defined in ISO 13209-3:2012 comprise features which allow diagnostic communication to a vehicle's diagnostic interface, flashing, executing diagnostic jobs, controlling measurement equipment, internationalization, working with physical units, accessing the environment, communication via a human machine interface (HMI) and other utility extensions. ISO 13209-3:2012 defines the OTX extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. ISO 13209-3:2012 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.

ISO 13209-2:2012 defines the OTX Core requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in the requirements section that composes the first major part of ISO 13209-2:2012. The data model specification aims at an exhaustive definition of all OTX Core features implemented to satisfy the Core requirements. Since OTX is designed for describing test sequences, which themselves represent a kind of program, the Core data model follows the basic concepts common to most programming languages. ISO 13209-2:2012 establishes rules for syntactical entities like parameterised procedures, constant and variable declarations, data types, basic arithmetic, logic and string operations, flow control statements like loop, branch or return, simple statements like assignment or procedure call as well as exception handling mechanisms. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents 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. With respect to documentation use cases, special attention is paid to defining a specification/realisation concept (which allows for "hybrid" test sequences: human readable test sequences that are at the same time machine-readable) and so called floating comments (which can refer to more than one node of the sequence). The Core data model does NOT define any statements, expressions or data types that are dependent on a specific area of application.

1 Scope This part of ISO 13209 specifies a standardized, tester-independent, XML-based data exchange format for the documentation and formal description of diagnostic test sequences. The format serves to support the requirements of transferring diagnostic-test-sequence logic between electronic system suppliers, vehicle manufacturers and service dealerships/repair shops. This part of ISO 13209 provides an introduction to the rationale behind ISO 13209. It gives an overview of the document set and structure along with the use case definitions and a common set of resources (definitions, references) for use by all subsequent parts.

ISO 22901-2:2011 is intended to ensure that diagnostic data stream information is available to diagnostic tool application manufacturers to simplify the support of the aftermarket automotive service industry. The ODX modelled diagnostic data are compatible with the software requirements of the Modular Vehicle Communication Interface (ISO 22900-2 and ISO 22900-3). The ODX modelled diagnostic data can enable an MVCI device to communicate with the vehicle [ECU(s)] 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 for display by the external test equipment. ISO 22901-2:2011 contains emissions-related OBD data examples described in ODX. The data examples derive from ISO 15031 (all parts). The emissions-related OBD ODX modelled diagnostic data describe the protocol specification from diagnostic communication of emissions-related ECUs; the communication parameters for the emissions-related OBD protocols and data link layers and for emissions-related ECU software; the related vehicle interface description (connectors and pin-out); and the functional description of diagnostic capabilities of a network of ECUs. ISO 22901-2:2011 is based on emissions-related diagnostic data derived and formatted according to the ISO 15765-4 DoCAN protocol. The definitions and XML representation is exemplary for all other protocols that are referenced in ISO 15031-5.

ISO 22901-1:2008 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 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 Unit(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 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 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 software; 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). The purpose of ISO 22901-1:2008 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.

ISO 22900-1:2008 provides the framework to allow diagnostic and reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle communication interfaces (VCI) from multiple tool suppliers. This system enables each vehicle manufacturer to support all vehicle communication interfaces to perform diagnostics and to control the programming sequence for electronic control units (ECUs) in their vehicles. ISO 22900-1:2008 describes the applicable use cases to justify the benefits of ISO 22900. It also specifies the design requirements to be followed by diagnostic and programming vehicle communication interface designers. The design requirements are categorized into different levels of conformance classes to provide: “software compliance”, a set of requirements for existing VCIs, which are software but not hardware compliant; “electrical compliance”, defining all signals and electrical interfaces that allow a system integrator to connect more than one VCI Protocol Module to the vehicle diagnostic connector and the host system; “mechanical compliance”, defining standard connectors on the VCI Protocol Module to interface to the vehicle Data Link Connector (DLC) and the host system, as well as defining a cabling concept to support interfacing more than one VCI Protocol Module. The technical requirements specified in ISO 22900-1:2008 have been influenced by the requirements of legal authority with regard to “vehicle OBD and programming”. The Modular Vehicle Communication Interface hardware design requirements will provide appropriate development guidance for vehicle communication interface manufacturers to meet legal authority and automotive manufacturer demands with regard to inter-vendor operability.

ISO 17356-6:2006 describes the OSEK Implementation Language (OIL) concept for the description for ISO 17356 real-time systems, capable of multitasking and communications, which can be used for motor vehicles. It is not a product description that relates to a specific implementation.

ISO 17356-5:2006 defines a set of services for node monitoring (NM). NM consists of the following: interface to interact with the Application Programming Interface(API); algorithm for node monitoring; internal interfaces (NM COM, etc.); algorithm for transition into sleep mode; and NM protocol data unit (NMPDU).

ISO 17356-3:2005 describes the concept of a real-time operating system, capable of multitasking, which can be used for motor vehicles. It is not a product description which relates to a specific implementation. It also specifies the operating system Application Program Interface (API). General conventions, explanations of terms and abbreviations have been compiled in ISO 17356-1. ISO 17356-6 discusses implementation and system generation aspects. The specification of the OS represents a uniform environment which supports efficient utilisation of resources for automotive control unit application software. The OS is a single processor operating system meant for distributed embedded control units.

ISO 17356-4:2005 (COM) specifies a uniform communication environment for automotive control unit (ECU) application software. In ISO 17356-4:2005 , the specification increases the portability of application software modules by defining common software communication interfaces and behaviours for internal communication (communication within an ECU) and external communication (communication between networked vehicle nodes), which is independent of the used communication protocol.

ISO 17356-2:2005 gives the OSEK/VDX specifications for binding the OS (operating system), COM (communications) and NM (network management) of the open interface for embedded automotive applications. It specifies the variables (error codes, status types, etc.) programmable by the user to ensure that implementation of OS, COM and NM are coherent between each other.

ISO 17356-1:2005 outlines the general structure of, and defines terms and abbreviations used in relation to, the specification of the software open interface for embedded automotive applications given by the other parts of ISO 17356.

ISO 22900-2:2009 specifies the diagnostic protocol data unit application programming interface (D-PDU API) as a modular vehicle communication interface (MVCI) protocol module software interface and common basis for diagnostic and reprogramming software applications. ISO 22900-2:2009 covers the descriptions of the application programming interface (API) functions and the abstraction of diagnostic protocols, as well as the handling and description of MVCI protocol module features. Sample MVCI module description files accompany ISO 22900-2:2009. Migration from and to the existing standards SAE J2534-1 and RP1210a is addressed. ISO 22900-2:2009 contains a description of how to convert between the APIs. Corresponding wrapper APIs accompany ISO 22900-2:2009. The purpose of ISO 22900-2:2009 is to ensure that diagnostic and reprogramming applications from any vehicle or tool manufacturer can operate on a common software interface, and can easily exchange MVCI protocol module implementations.

Defines diagnostic provisions applicable to electronic systems in road vehicles. Applies to electronic systems including electronic modules, associated input sensors, output actuators and indicators. The measurement ranges specified exclude certain devices for which specific test equipment is required. Does not apply to those systems which have built-in diagnostic capabilities and do not require compatibility with off-board equipment.