BS ISO 22901-1:2008
$256.21
Road vehicles. Open diagnostic data exchange (ODX) – Data model specification
| Published By | Publication Date | Number of Pages |
| BSI | 2008 | 498 |
This 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 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).
Figure 1 shows the usage of ODX in the ECU life cycle.
The purpose of this part of ISO 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.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 9 | Scope Normative references |
| 10 | Abbreviated terms |
| 11 | ODX use cases General Use case 1: ODX process chain |
| 12 | Use case 2: Cross vehicle platform ECU diagnostic developmen |
| 13 | Use case 3: Franchise and aftermarket service dealership dia |
| 14 | Architecture of a Modular VCI compliant D-server ODX benefit examples ECU system supplier Vehicle manufacturer engineering |
| 15 | Vehicle manufacturer production Vehicle manufacturer service department and dealerships Test equipment manufacturer Franchise and aftermarket dealerships Legal authorities |
| 16 | Specification release version information Specification release version location Specification release version Introduction to and use of Unified Modelling Language (UML) General aspects Class diagrams Class |
| 17 | Inheritance relationships Aggregation and composition relationships |
| 18 | Association relationships |
| 19 | Association classes Interfaces |
| 20 | Constraints Mapping to XML |
| 22 | ODX data model General modelling principles Common members |
| 23 | Common objects Special data group |
| 25 | AUDIENCE and ADDITIONAL-AUDIENCE |
| 28 | Administrative information Overview |
| 29 | Location in ODX data model |
| 30 | Structure of ADMIN-DATA |
| 32 | Structure of COMPANY-DATA |
| 33 | Usage of ADMIN-DATA Revision information of ODX objects Updating the revision history of an ODX object |
| 34 | Versioning conflicts Value coding ODX package Overview |
| 36 | Package ODXStructure |
| 37 | ODX data model for diagnostics Overview |
| 38 | Diagnostic layer structure Overview |
| 39 | Diagnostic layer modelling |
| 40 | Diagnostic layer commonalities |
| 41 | Value inheritance Overview General |
| 45 | Elimination of inherited objects |
| 46 | Overriding of objects |
| 47 | Multiple inheritance Importing and referencing of objects |
| 48 | Value inheritance and referencing examples |
| 55 | Variant identification |
| 56 | Base variant identification Communication parameter |
| 60 | Inheritance of communication parameters |
| 63 | Datastream Overview |
| 64 | Diagnostic communication |
| 66 | Service |
| 69 | Parameter |
| 73 | Request |
| 75 | Response |
| 77 | Single ECU job |
| 80 | Library |
| 82 | Data parameter Overview |
| 86 | Simple data – DATA-OBJECT-PROP |
| 98 | Data extraction |
| 101 | Data packing |
| 105 | Value comparison Computational methods General |
| 110 | Identical Linear |
| 111 | Scale linear |
| 113 | Rational function |
| 114 | Scale rational function |
| 115 | Text table |
| 117 | Tab interpolated |
| 118 | Computational code |
| 121 | Units General |
| 123 | Unit groups |
| 124 | DTC data object property |
| 131 | Environment data description General |
| 136 | Rules for authoring Reuse of ENV-DATA objects |
| 137 | Complex data (complex data object property) Overview |
| 138 | Structure |
| 141 | Static field |
| 143 | Dynamic length field |
| 145 | Dynamic endmarker field |
| 146 | End of PDU – Field |
| 148 | Multiplexer |
| 150 | TABLE – compound data object |
| 159 | Cascading tables |
| 160 | Diagnostic variable General |
| 161 | Use cases |
| 162 | Structure of DIAG-VARIABLE |
| 168 | Inheritance of DIAG-VARIABLEs Dynamically defined messages |
| 169 | Session and security handling |
| 171 | Vehicle information Vehicle identification data |
| 172 | Vehicle topology |
| 174 | Runtime behaviour |
| 176 | Multiple ECU jobs |
| 178 | Data types References Overview |
| 179 | References via odxlink |
| 182 | References via short name path |
| 183 | Single-Param-Algorithm |
| 186 | Multiple-Param-Algorithm |
| 188 | References via SHORT-NAME Boundary for uniqueness of SHORT-NAME |
| 191 | Usage scenarios (diagnostic) Diagnostic service description |
| 194 | Dynamically defined messages General |
| 196 | Dynamic case |
| 199 | Static case |
| 200 | Variant identification |
| 204 | Base variant identification scenario Overview ODX data structures for BASE-VARIANT identification scenario |
| 205 | Sequence of events for BASE-VARIANT identification ODX example |
| 209 | Diagnostic trouble code description |
| 214 | Protocol communication parameter |
| 219 | Dynamic diagnostic response Example of DYNAMIC-LENGTH-FIELD |
| 220 | Example of DYNAMIC-ENDMARKER-FIELD |
| 221 | Example of END-OF-PDU-FIELD Example of MUX |
| 222 | Variable length parameter |
| 223 | Functional addressing Overview Communication on the vehicle bus |
| 225 | Data structures in ODX to define functional addressing |
| 227 | Sequence of events for functional addressing |
| 230 | ODX examples |
| 237 | ODX data model for ECU memory programming Overview ECU-MEM data model description Structure of ECU-MEM |
| 238 | Sessions |
| 241 | Datablocks General |
| 248 | Example |
| 252 | Flashdata |
| 254 | Physical memory |
| 256 | ECU-MEM-CONNECTOR data model description |
| 258 | The programming process as a whole |
| 260 | The upload process as a whole |
| 261 | ECU programming usage scenarios (flash) ECU model description |
| 262 | ECU-MEM flash instance description |
| 263 | Flash session #1 Flash session #2 |
| 264 | Flash session #3 |
| 265 | Flash session #4 |
| 266 | Finalization |
| 273 | ECU variant coding usage scenarios Overview General modelling concepts |
| 274 | ODX data model for ECU configuration Description of the ECU configuration data model Overview Describing blocks of binary data |
| 275 | Describing individual configuration items |
| 277 | Description of configuration values Combining binary data blocks with ECU functions Reading and writing configuration data from and to the ECU |
| 278 | ECU-CONFIG |
| 279 | Comprehensive UML model |
| 283 | Example |
| 284 | Function dictionary Terms and requirements |
| 285 | Functions and function groups in ODX |
| 286 | Function dictionary data model description |
| 288 | Function dictionary usage scenario |
| 291 | SUB-COMPONENT data model description |
| 293 | SUB-COMPONENT usage scenario |
| 295 | Data model implementation in XML Classifier Classes Default mapping Description UML example |
| 296 | Schema example ODX instance example Transparent mapping Description UML example Schema example |
| 297 | ODX instance example Interfaces Description UML example Schema example ODX instance example Enumerations Description |
| 298 | UML example Schema example ODX instance example Odxlink classes Description |
| 299 | UML example Schema example ODX instance example |
| 300 | Imported classes Description UML example Schema example ODX instance example Attributes Default mapping Description UML example |
| 301 | Schema example ODX instance example XML attribute mapping Description UML example Schema example ODX instance example |
| 302 | Transparent mapping Description UML example Schema example ODX instance example XML content mapping Description |
| 303 | UML example Schema example ODX instance example Relationships Generalizations Overview Parent generalization Description |
| 304 | UML example Schema example |
| 305 | ODX instance example Child generalization Description UML example Schema example |
| 306 | ODX instance example Associations Composition and aggregation Description |
| 307 | UML example XML schema example ODX instance example Wrapper elements Description |
| 308 | Wrapper element for child generalizations Description UML example XML schema example |
| 309 | ODX instance example Wrapper element for parent generalizations Description UML example XML schema example |
| 310 | ODX instance example No wrapper Description UML example XML schema Example |
| 311 | ODX instance example Single wrapper for different elements Description UML example XML schema example |
| 312 | ODX instance example Packaged ODX data (PDX) Overview General |
| 313 | PDX package/package catalogue use cases Structure of PDX package Structure of PDX package catalogue |
| 315 | Technical aspects of PDX package |
| 316 | Usage scenarios PDX package in the exchange process General |
| 317 | Full data exchange Incremental (partial) data exchange Configuration management and version control Overview Exchange of revision history |
| 318 | CMS-specific versioning |
| 319 | Using the UPD attribute for configuration management |
