Diagnostic Extraction (DEXT) & ODX Mapping - AUTOSAR Classic BSW

DEXT: Diagnostic Extract Template

DEXT Workflow

  AUTOSAR ARXML (DcmDspDid + DemEventClass definitions)
       │ DEXT Export (DaVinci Configurator / ISOLAR)
       ▼
  DEXT ARXML file (diagnostic description subset)
       │ ODX conversion tool (CANdelaStudio / Vector ODX Editor)
       ▼
  ODX file (.pdx / .odx)
       │ CDD/CDDx import (CANoe, CANalyzer, Vector DIVA)
       ▼
  Diagnostic tester / CAPL scripts with decoded DIDs and DTCs

DID Definitions in ARXML

XMLDEXT_DIDs.arxml

<DIAGNOSTIC-DATA-IDENTIFIER>
  <SHORT-NAME>DID_ECU_Serial_Number</SHORT-NAME>
  <IDENTIFIER>0xF18C</IDENTIFIER>
  <DATAS>
    <DATA-ELEMENT-VALUE>
      <SHORT-NAME>SerialNumber</SHORT-NAME>
      <DATA-ELEMENT-LENGTH>10</DATA-ELEMENT-LENGTH>
    </DATA-ELEMENT-VALUE>
  </DATAS>
  <READ-BY-IDENTIFIER-CONDITION>
    <SESSION-REF>/Dcm/Sessions/DefaultSession</SESSION-REF>
  </READ-BY-IDENTIFIER-CONDITION>
</DIAGNOSTIC-DATA-IDENTIFIER>

ODX/CDD Generation for Tester Tools

Tool	Input	Output	Use
CANdelaStudio	AUTOSAR DEXT ARXML	CDD file (CANoe compatible)	CANoe diagnostic window + CAPL
Vector ODX Editor	DEXT ARXML	ODX .pdx package	DIVA, VehicleSpy, ECU-Test
ISOLAR ODX Export	ISOLAR project ARXML	ODX container	EB tresos-based project teams

Keeping DEXT in Sync

Symptom	Root Cause
Tester reports NRC 0x31 for a known DID	DID ID changed in ARXML without DEXT update
Tester decodes garbage data for a DID	Data element length changed in ARXML; DEXT not regenerated
DTC in ECU $19 but not in CDD	New DemEventClass added; DEXT export not updated

Summary

DEXT is the contractual diagnostic description between ECU software and test/service tools. It must be regenerated and version-controlled alongside every DCM/DEM ARXML change. Automate DEXT export in the CI pipeline to prevent stale CDD files reaching the test 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.