scope:

This part of Road vehicles - Open diagnostic data exchange (ODX) - specifies the concept of utilizing a new industry standard diagnostic format to make diagnostic data stream information available to diagnostic tool application manufacturer to simplify the support of the aftermarket automotive service industry. The ODX modelled diagnostic data are compatible to the software requirements of the Modular Vehicle Communication Interface (ISO 22900-2 and -3). The ODX modelled diagnostic data will enable a 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 an 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 present specification contains emissions-related OBD data examples described in ODX. The data examples derive from the ISO 15031 (all parts) standard. Examples are: diagnostic trouble codes, data parameters, identification data and communication parameters. The emissions-related OBD ODX modelled diagnostic data describe . Protocol specification from diagnostic communication of emissions-related ECUs, . Communication parameters for the emissions-related OBD protocols and data link layers and for emissions-related ECU software, . Related vehicle interface description (connectors and pin-out), . Functional description of diagnostic capabilities of a network of ECUs; 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 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 quality 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.