ODX Data Model & Layer Structure - ODX & Diagnostic Data

ODX Layer Model

ODX Layer Hierarchy

  ODX File (DIAG-LAYER-CONTAINER)
  |
  +-- BASE-VARIANT              (shared content; inherited by all)
  |   +-- Services (ReadDTCInfo, ECUReset, ...)
  |   +-- Data Types (uint8, uint16, ...)
  |   +-- Communication Params (baudrate, timing)
  |
  +-- ECU-SHARED-DATA           (shared across ECU variants)
  |   +-- Variant-independent services
  |   +-- Common DTCs
  |
  +-- ECU-VARIANT               (one per ECU hardware/SW variant)
  |   +-- Variant-specific services
  |   +-- Variant coding parameters
  |
  +-- FUNCTIONAL-GROUP          (cross-ECU functional grouping)
      +-- Services that span multiple ECUs (e.g., all ABS ECUs)
      +-- Used for functional addressing (broadcast)

DIAG-LAYER-CONTAINER XML Structure

XMLecu_diag.odx

<?xml version="1.0" encoding="UTF-8"?>
<ODX MODEL-VERSION="2.2.0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <DIAG-LAYER-CONTAINER>

    <!-- Base variant: shared services all ECU variants inherit -->
    <BASE-VARIANTS>
      <BASE-VARIANT ID="BV_ISO14229_BASE">
        <SHORT-NAME>ISO14229_BaseServices</SHORT-NAME>
        <LONG-NAME>ISO 14229 UDS Base Service Set</LONG-NAME>
        <DIAG-COMMS><!-- ECUReset, ReadDTCInfo, etc. --></DIAG-COMMS>
        <DATA-OBJECT-PROPS><!-- Common data types --></DATA-OBJECT-PROPS>
        <UNIT-SPEC><!-- Physical units: km/h, bar, degC --></UNIT-SPEC>
      </BASE-VARIANT>
    </BASE-VARIANTS>

    <!-- ECU variant: this is the deliverable for a specific ECU build -->
    <ECU-VARIANTS>
      <ECU-VARIANT ID="EV_ABS_ECU_V4_2">
        <SHORT-NAME>ABS_ECU_HW2_SW4_2</SHORT-NAME>
        <PARENT-REFS>
          <BASE-VARIANT-REF ID-REF="BV_ISO14229_BASE"/>
        </PARENT-REFS>
        <DIAG-COMMS><!-- ABS-specific services --></DIAG-COMMS>
      </ECU-VARIANT>
    </ECU-VARIANTS>

  </DIAG-LAYER-CONTAINER>
</ODX>

Layer Inheritance Mechanism

How ODX Inheritance Works

ODX layers form an inheritance hierarchy similar to object-oriented programming. A child layer (ECU-VARIANT) inherits all services, data types, and communication parameters from its parent layers (BASE-VARIANT, ECU-SHARED-DATA). The child can:

Use inherited items directly -- no redefinition needed
Override inherited items -- redefine a service with the same SHORT-NAME to change behaviour for this variant
Add new items -- define services unique to this ECU variant

This inheritance model is critical for managing multiple ECU variants: the base layer contains the 80% of services common to all variants, and each ECU variant only describes its 20% of unique content.

Summary

The ODX layer model is the architectural decision that makes ODX manageable at scale. A real vehicle programme has 50-150 ECUs, each with 3-5 software variants (market regions, feature levels, powertrain options), resulting in potentially 500+ ECU variants. Without layer inheritance, each variant would require a complete copy of all 200+ diagnostic services -- a maintenance nightmare where changing a service definition requires updating hundreds of files. With layer inheritance, the base services are defined once in a BASE-VARIANT, inherited by all ECU variants, and only the variant-specific overrides are written in each ECU-VARIANT layer. This structure also mirrors the organisational structure of an automotive programme: the base layer is owned by the platform team, ECU-specific layers are owned by the ECU teams, and functional groups are owned by the system team.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.