| Test Objective | Procedure | Pass Criterion |
|---|---|---|
| DTC set on fault | Inject fault; wait FHTI; read DTCs via UDS 0x19 | DTC present with status byte confirming "confirmed" bit set |
| DTC clear on recovery | Inject fault; wait; remove fault; drive cycle; verify cleared | DTC absent after OBD driving cycle (or ECU-specific clear cycle) |
| DTC debounce | Inject fault for duration shorter than debounce threshold; verify DTC NOT set | DTC absent for brief faults (< debounce_ms); present after sustained fault |
| DTC freeze frame | Inject fault; read freeze frame (UDS 0x19 04) | Freeze frame contains vehicle speed, RPM, and other snapshot data at fault time |
| DTC storage in NVM | Inject fault; power-cycle ECU; read DTCs on next power-on | DTC persists across power cycle (stored in non-volatile memory) |
| Confirmed DTC count | Inject fault; clear 10 times via UDS; verify counter reset | agingCounter and confirmedDTC status byte per UDS specification |
DTC Validation Testing
Safe State Transition Validation
#!/usr/bin/env python3
# Test: safe state transition timing after sensor fault injection
# Requirement: [ASIL-D] ECU shall reach safe state within FTTI = 200 ms
import time
class SafeStateTest:
FTTI_MS = 200 # Fault Tolerance Time Interval
FHTI_MS = 100 # Fault Handling Time Interval (FTTI / 2)
def run(self, hil, ecu_monitor):
results = []
for fault_type in ["SHORT_GND", "OPEN_CIRCUIT", "STUCK_HIGH"]:
print(f"Testing safe state for fault: {fault_type}")
# Establish nominal operating condition
hil.set("Plant/Speed_kph", 100.0)
hil.set("Plant/Motor/Torque_Nm", 50.0)
time.sleep(2)
# Record pre-fault actuator state
pre_torque = ecu_monitor.get("ECU/Motor/TorqueCmd_Nm")
assert abs(pre_torque - 50.0) < 5.0, "Pre-fault state wrong"
# Inject fault and start timer
t_fault = time.time()
hil.inject_fault("TorqueSensor_ChA", fault_type)
# Poll for safe state (motor torque = 0)
safe_reached = False
t_safe = None
while (time.time() - t_fault) * 1000 < self.FTTI_MS + 50:
torque = ecu_monitor.get("ECU/Motor/TorqueCmd_Nm")
if abs(torque) < 1.0: # safe state = 0 Nm
t_safe = (time.time() - t_fault) * 1000
safe_reached = True
break
time.sleep(0.005)
passed = safe_reached and t_safe <= self.FTTI_MS
print(f" {fault_type}: safe state at {t_safe:.1f} ms -- {"PASS" if passed else "FAIL"}")
results.append({"fault": fault_type, "pass": passed,
"time_ms": t_safe})
# Clear fault and recover
hil.clear_fault("TorqueSensor_ChA")
time.sleep(1)
return resultsSummary
Diagnostics validation on HIL is the quantitative evidence that safety mechanisms work as designed. The safe state transition test is particularly critical for ASIL-D systems: it measures the actual time from fault injection to safe actuator output in milliseconds and compares against the FTTI specified in the safety concept. If the measured transition time exceeds FTTI even once, it is a safety finding that must be resolved before production release. Automated test infrastructure that measures timing with millisecond precision (using hardware timestamps from the HIL platform, not OS sleep() calls) is essential for reliable FTTI measurements.
🔬 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.