Validation & Consistency Checks - ODX & Diagnostic Data

ODX Validation Levels

Level	What it Checks	Tool	When to Run
XML well-formed	Valid XML syntax; matching tags	xmllint	Every file save
Schema valid	ODX elements/attributes match XSD schema	xmllint --schema	Every commit
Reference valid	All ID-REF point to existing IDs	Custom script	Every commit
Semantic valid	DOP encoding consistent; byte positions non-overlapping	ODXStudio checker	Before delivery
Communication valid	CAN IDs unique per bus; timing params in range	Custom script	Before delivery
Coverage valid	Every DTC has a freeze frame; all services have DOPs	Custom script	Before release

XML Schema Validation Script

Bashvalidate_odx.sh

#!/bin/bash
# Validate ODX file against ISO 22901 XSD schema
# Requires: xmllint (libxml2-utils package)

ODX_FILE="$1"
XSD_FILE="odx_schema/ISO22901_ODX_2.2.0.xsd"

if [ -z "$ODX_FILE" ]; then
    echo "Usage: $0 <odx_file>"
    exit 1
fi

# Step 1: Well-formedness check
echo "Checking XML well-formedness..."
xmllint --noout "$ODX_FILE" 2>&1
if [ $? -ne 0 ]; then
    echo "FAIL: XML is not well-formed"
    exit 1
fi

# Step 2: Schema validation
echo "Validating against ODX 2.2.0 schema..."
xmllint --noout --schema "$XSD_FILE" "$ODX_FILE" 2>&1
if [ $? -ne 0 ]; then
    echo "FAIL: Schema validation failed"
    exit 1
fi

echo "PASS: ODX file is schema-valid"

# Step 3: ID reference check
echo "Checking ID references..."
python3 odx_manager.py validate-refs "$ODX_FILE"
echo "Validation complete"

Consistency Rule Checker

Pythonodx_consistency.py

"""ODX consistency checker: semantic rules beyond schema."""
import xml.etree.ElementTree as ET
from typing import List

def check_consistency(odx_path: str) -> List[str]:
    tree = ET.parse(odx_path)
    root = tree.getroot()
    issues = []

    # Rule 1: Every VALUE PARAM must have a valid DOP-REF
    dop_ids = {e.get("ID") for e in root.iter("DATA-OBJECT-PROP")}
    for param in root.iter("PARAM"):
        if param.get("{http://www.w3.org/2001/XMLSchema-instance}type") == "VALUE":
            dop_ref = param.findtext("DOP-REF/@ID-REF")
            ref_elem = param.find("DOP-REF")
            if ref_elem is not None:
                ref_id = ref_elem.get("ID-REF","")
                if ref_id not in dop_ids:
                    name = param.findtext("SHORT-NAME","")
                    issues.append(f"PARAM {name}: DOP-REF {ref_id} not found")

    # Rule 2: No overlapping BYTE-POSITION in same REQUEST
    for req in root.iter("REQUEST"):
        positions = {}
        for param in req.iter("PARAM"):
            bp = param.get("BYTE-POSITION")
            name = param.findtext("SHORT-NAME","")
            if bp:
                if bp in positions:
                    issues.append(
                        f"REQUEST: params {positions[bp]} and {name} both at byte {bp}")
                positions[bp] = name

    # Rule 3: Every DTC should have an ENV-INFO-REF (freeze frame)
    for dtc in root.iter("DIAG-TROUBLE-CODE-UDS"):
        name = dtc.findtext("SHORT-NAME","")
        if dtc.find("ENV-INFO-REF") is None:
            issues.append(f"DTC {name}: missing freeze frame (ENV-INFO-REF)")

    return issues

Summary

ODX consistency checking is the quality gate that prevents tool failures in the workshop. The three most common ODX quality issues found in automotive programmes are: broken ID-REF links (service references a DOP that was deleted or renamed), overlapping byte positions in request structures (two parameters assigned to the same byte, causing incorrect encoding), and missing freeze frame assignments on DTCs (the workshop tool cannot read freeze frame data for a DTC because the ODX does not define which parameters to read). All three are preventable with automated pre-delivery checks. The consistency checker running in the CI/CD pipeline transforms these issues from "discovered in tool integration testing after delivery" to "caught before the ODX file leaves the team" -- a significant improvement in programme efficiency.

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