ISO 22901-1:2008
Current
The latest, up-to-date edition.
Road vehicles — Open diagnostic data exchange (ODX) — Part 1: Data model specification
PDF 1 User , PDF 3 Users , PDF 5 Users , PDF 9 Users
English
06-11-2008
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.
DevelopmentNote |
Supersedes ISO/DIS 22901-1. (11/2008)
|
DocumentType |
Standard
|
Pages |
486
|
PublisherName |
International Organization for Standardization
|
Status |
Current
|
Standards | Relationship |
BS ISO 22901-1:2008 | Identical |
15/30277952 DC : 0 | BS ISO 22901-3 - ROAD VEHICLES - OPEN DIAGNOSTIC DATA EXCHANGE (ODX) - PART 3: FAULT SYMPTOM EXCHANGE DESCRIPTION (FXD) |
ISO 14229-1:2013 | Road vehicles Unified diagnostic services (UDS) Part 1: Specification and requirements |
ISO 22900-2:2017 | Road vehicles Modular vehicle communication interface (MVCI) Part 2: Diagnostic protocol data unit (D-PDU API) |
BS ISO 14229-1:2013 | Road vehicles. Unified diagnostic services (UDS) Specification and requirements |
BS ISO 22900-2:2017 | Road vehicles. Modular vehicle communication interface (MVCI) Diagnostic protocol data unit (D-PDU API) |
BS ISO 22900-1:2008 | Road vehicles. Modular vehicle communication interface (MVCI) Hardware design requirements |
BS ISO 22900-3:2012 | Road vehicles. Modular vehicle communication interface (MVCI) Diagnostic server application programming interface (D-Server API) |
ISO 22900-3:2012 | Road vehicles — Modular vehicle communication interface (MVCI) — Part 3: Diagnostic server application programming interface (D-Server API) |
12/30227351 DC : 0 | BS ISO 11992-4 - ROAD VEHICLES - INTERCHANGE OF DIGITAL INFORMATION ON ELECTRICAL CONNECTIONS BETWEEN TOWING AND TOWED VEHICLES - PART 4: DIAGNOSTIC COMMUNICATION |
11/30227758 DC : 0 | BS ISO 22900-3 - ROAD VEHICLES - MODULAR VEHICLE COMMUNICATION INTERFACE (MVCI) - PART 3: DIAGNOSTIC SERVER APPLICATION PROGRAMMING INTERFACE (D-SERVER API) |
BS ISO 22901-2:2011 | Road vehicles. Open diagnostic data exchange (ODX) Emissions-related diagnostic data |
14/30291315 DC : 0 | BS ISO 22900-2 - ROAD VEHICLES - MODULAR VEHICLE COMMUNICATION INTERFACE (MVCI) - PART 2: DIAGNOSTIC PROTOCOL DATA UNIT (D-PDU API) |
BS ISO 11992-4:2014 | Road vehicles. Interchange of digital information on electrical connections between towing and towed vehicles Diagnostic communication |
ISO 22900-1:2008 | Road vehicles — Modular vehicle communication interface (MVCI) — Part 1: Hardware design requirements |
ISO 11992-4:2014 | Road vehicles — Interchange of digital information on electrical connections between towing and towed vehicles — Part 4: Diagnostic communication |
11/30218759 DC : 0 | BS ISO 14229-1 - ROAD VEHICLES - UNIFIED DIAGNOSTIC SERVICES (UDS) - PART 1: SPECIFICATION AND REQUIREMENTS |
ISO 22901-3:2018 | Road vehicles — Open diagnostic data exchange (ODX) — Part 3: Fault symptom exchange description (FXD) |
ISO 22901-2:2011 | Road vehicles Open diagnostic data exchange (ODX) Part 2: Emissions-related diagnostic data |
ISO 639-1:2002 | Codes for the representation of names of languages — Part 1: Alpha-2 code |
ISO/IEC 8859-1:1998 | Information technology 8-bit single-byte coded graphic character sets Part 1: Latin alphabet No. 1 |
SAE J 1708 : 2016 | SERIAL DATA COMMUNICATIONS BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY-DUTY VEHICLE APPLICATIONS |
ISO/IEC 10646:2014 | Information technology Universal Coded Character Set (UCS) |
ISO 14229-1:2013 | Road vehicles Unified diagnostic services (UDS) Part 1: Specification and requirements |
ISO 11898-2:2016 | Road vehicles — Controller area network (CAN) — Part 2: High-speed medium access unit |
SAE J 1587 : 2013 | JOINT SAE/TMC ELECTRONIC DATA INTERCHANGE BETWEEN MICROCOMPUTER SYSTEMS IN HEAVY-DUTY VEHICLE APPLICATIONS |
SAE J 2190 : 1993 | ENHANCED E/E DIAGNOSTIC TEST MODES |
ISO 11898-1:2015 | Road vehicles — Controller area network (CAN) — Part 1: Data link layer and physical signalling |
ISO 8601:2004 | Data elements and interchange formats Information interchange Representation of dates and times |
SAE J 2610 : 2015 | SERIAL DATA COMMUNICATION INTERFACE |
ISO 22900-2:2017 | Road vehicles Modular vehicle communication interface (MVCI) Part 2: Diagnostic protocol data unit (D-PDU API) |
ISO/IEC 11578:1996 | Information technology — Open Systems Interconnection — Remote Procedure Call (RPC) |
SAE J 1939 : 2013 | SERIAL CONTROL AND COMMUNICATIONS HEAVY DUTY VEHICLE NETWORK - TOP LEVEL DOCUMENT |
SAE J 2534/1 : 2015 | RECOMMENDED PRACTICE FOR PASS-THRU VEHICLE PROGRAMMING |
ISO/IEC 8859-2:1999 | Information technology 8-bit single-byte coded graphic character sets Part 2: Latin alphabet No. 2 |
ISO 11992-1:2003 | Road vehicles Interchange of digital information on electrical connections between towing and towed vehicles Part 1: Physical and data-link layers |
ISO 11898-3:2006 | Road vehicles Controller area network (CAN) Part 3: Low-speed, fault-tolerant, medium-dependent interface |
ISO 3166-1:2013 | Codes for the representation of names of countries and their subdivisions Part 1: Country codes |
ISO 15031-5:2015 | Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 5: Emissions-related diagnostic services |
ISO 22900-3:2012 | Road vehicles — Modular vehicle communication interface (MVCI) — Part 3: Diagnostic server application programming interface (D-Server API) |
IEEE 754-2008 REDLINE | IEEE Standard for Floating-Point Arithmetic |
ISO 15031-6:2015 | Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 6: Diagnostic trouble code definitions |
SAE J 1850 : 2015 | CLASS B DATA COMMUNICATIONS NETWORK INTERFACE |
Access your standards online with a subscription
Features
-
Simple online access to standards, technical information and regulations.
-
Critical updates of standards and customisable alerts and notifications.
-
Multi-user online standards collection: secure, flexible and cost effective.