Aging, Displacement & Priority - UDS Diagnostics

DTC Aging: Self-Clearing After Healing

DTC Aging Lifecycle

  Fault confirmed (status byte: bit 3 set, bit 0 set)
       │
       ▼
  Fault heals: monitor passes; bit 0 cleared; bit 3 remains set
  Aging counter begins incrementing each drive cycle
       │
       ├── After N drive cycles (typically 40) with bit 0 not set:
       │   DTC removed from confirmed storage; aging counter reset
       └── If fault returns: bit 0 set again; aging counter reset; aging halted

  AUTOSAR DEM aging config:
  DemAgingCycleCounterThreshold = 40  (40 passing drive cycles)
  DemAgingCycleRef = DriveCycleMaster  (must match OBD drive cycle definition)

  Rationale: prevents workshop from having to clear DTCs for intermittent faults
  that self-heal (e.g., loose connector that re-seats; temporary sensor brownout)
  OBD-II mandates: confirmed emission-related DTC ages out after 40 warm-up cycles
  if no recurrence

DTC Displacement When Storage Is Full

Strategy	Behaviour	Risk
Priority-based	Lower-priority DTC displaced first; high-priority preserved	Critical fault might not be stored if configured with wrong priority
Oldest-first	DTC stored longest (by drive cycle) displaced first	Recent faults preserved; old faults may be lost
No displacement	Return E_DEM_NO_SUCH_ELEMENT; do not store new DTC	New fault missed entirely; workshop sees no evidence
OBD permanent first	Protect permanent DTC storage; primary storage can displace	OBD compliance maintained; OEM DTCs may be lost

DEM Priority Configuration

XMLDem_Priority.arxml




  DemEvent_BrakePressureSensor_Open
  1   
  /Dem/DTCs/DTC_C0040



  DemEvent_CabinTemp_Offset
  200  
  /Dem/DTCs/DTC_B1234




  50
  PRIORITY

Summary

Aging, displacement, and priority are the three DEM policies that determine what the workshop actually sees when they scan the vehicle months after a fault occurred. Aging prevents permanent DTC accumulation for self-healing faults; displacement policy ensures critical ASIL faults are never lost to storage overflow; and priority configuration matches business importance to technical severity. Always verify that ASIL C/D safety faults have priority 1 and test the displacement scenario in lab: fill DEM storage, then trigger a high-priority fault — confirm it displaces a low-priority DTC, not the other way around.

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