• ODX main components
• Packaged ODX (PDX)
• Minimal structure of an ODX-parameterization

ODX main components

Now we want to see what the structure of an ODX description of the various major components look more closely. The so-called ODX-categories are simply data containers, ie, groups of professionals who have met together a specific function. The whole thing is organized hierarchically. The light green shown here contains the so-called main-level categories. There you will see grayed elements, the parts of the Diag-layer container, the container of the most complex ODX description are.

ODX main components

Let's start with the group VEHICLE-INFO-SPEC, COMPARAM-SPEC, COMPARAM SUBSET. This group is responsible for the description of the vehicle and the diagnostic interface itself will find in the VEHICLE-INFO-SPEC get information about which vehicle is and how this vehicle is available for the diagnosis. The COMPARAM-SPEC and the corresponding COMPARAM SUBSET describe the protocol, the diagnostic interface works and what parameters are relevant for this protocol. The most important part of the diagnostic description consists of the DIAG-LAYER CONTAINER and the MULTIPLE ECU JOB SPECIFICATION. These parts of the information are responsible for diagnostic services and diagnostic procedures. The actual diagnostic services as they relate to a single control unit, are located in a DIAG-LAYER CONTAINER. Functions and services across multiple control units perform certain diagnostic functions to be defined within the Multiple ECU Job container. The ODX-FLASH container, ECU-CONFIG, and finally the FUNCTION DICTIONARY have specific tasks. FLASH in the section the information is specified for the End-Of-Line and Flash programming of a controller are relevant. The category ECU-CONFIG contains the data that are relevant to the model coding of ECUs and the FUNCTION DICTIONARY finally is a kind of library suitable

The gray recordset we investigate if we look at the details of the DIAG-LAYER CONTAINERS detail.

ODX-base structure - container elements

Packaged ODX (PDX)

Each party to this ODX container is on a separate XML file, while most manufacturers use listed in the table file name extensions for these files. In order for the exchange of ODX data sets do not handle this many individual files must ASAM has in addition to the actual ODX data format also known as package defines ODX data format that is nothing more than a Zip archive in which all a are project files with the entire folder structure and grabbed a package catalog (index.xml), a type of contents, references. Also included in the PDX format and the necessary revision and configuration information.

ODX file extensions

Minimal structure of an ODX-parameterization

The very brief overview of the basic structure of ODX sure not to leave the false impression that ODX is a relatively complex data format. Fortunately, you need the simplest case, by far not all of these elements. Three of the main elements meet. It starts with the VEHICLE-INFO-SPEC, the vehicle topology, the physical access to the vehicle, so pin assignments and describes the like. Then you need a COMPARAM-SPEC section in which the bus protocol is defined, in particular things like the baud rate, CAN identifier and the like. Third, you need the DIAG-LAYER CONTAINER with the sub-sections and PROTOCOL BASE VARIANT.

The VEHICLE-INFO-SPEC refers to the basic variant. The standard model describes a particular control device and its diagnostic services. The protocol section is connected to the BASE VARIANT by reference, refers in turn to the related COMPARAM-SPEC, so we describe the vehicle in VEHICLE-INFO-SPEC, the description of the bus system in the COMPARAM-SPEC and description have the diagnostic services in the BASE VARIANT section of the DIAG-LAYER CONTAINERS.

Minimal structure of an ODX-parameterization