BS ISO 22901-1:2008

Foreword
Introduction
1 Scope
2 Normative references
3 Abbreviated terms
4 ODX use cases
  4.1 General
  4.2 Use case 1: ODX process chain
  4.3 Use case 2: Cross vehicle platform ECU diagnostic
      development
  4.4 Use case 3: Franchise and aftermarket service
      dealership diagnostic tool support
  4.5 Architecture of a Modular VCI compliant D-server
  4.6 ODX benefit examples
5 Specification release version information
  5.1 Specification release version location
  5.2 Specification release version
6 Introduction to and use of Unified Modelling Language (UML)
  6.1 General aspects
  6.2 Class diagrams
  6.3 Mapping to XML
7 ODX data model
  7.1 General modelling principles
  7.2 ODX package
  7.3 ODX data model for diagnostics
  7.4 Usage scenarios (diagnostic)
  7.5 ODX data model for ECU memory programming
  7.6 ECU programming usage scenarios (flash)
  7.7 ECU variant coding usage scenarios
  7.8 ODX data model for ECU configuration
  7.9 Function dictionary
8 Data model implementation in XML
  8.1 Classifier
  8.2 Relationships
9 Packaged ODX data (PDX)
  9.1 Overview
  9.2 Structure of PDX package
  9.3 Usage scenarios
Annex A (normative) - Enumerations and pre-defined values
Annex B (normative) - ODX checker rules
Annex C (normative) - XML schema
Annex D (informative) - User-defined formats for flashdata
Annex E (informative) - Coherent examples for diagnostic services
Annex F (informative) - ECU-MEM example
Annex G (informative) - Session security example
Bibliography

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

This part of ISO22901 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 ISO22900-2 and ISO22900-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).

Figure1 shows the usage of ODX in the ECU life cycle.

The purpose of this part of ISO22901 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.