Build & Validate Adaptive AUTOSAR Diagnostics Faster
- Automobiltechnik
- Entwicklung von Serienssoftware
06:39min
Übersicht
Accelerate your Adaptive AUTOSAR Diagnostics development with a model based workflow in TargetLink. In this hands on walkthrough, Ralf Turzer shows how to import diagnostic interface configurations, connect them to your model, and automatically generate the right API calls - so you can focus on functional logic, not a 450 page spec. You’ll also see SIL validation to catch issues early and avoid runtime surprises on the ECU.
Demo highlight:
We implement diagnostic behavior alongside a rain sensor and wiper actuator example: read sensor lifetime every 1s, rewrite max wiper speed at 10s, and call a diagnostic routine at 15s - then validate outputs in simulation.
Gastgeber
Ralf Turzer
Project Engineer, Engineering Services & Predevelopment, dSPACE
FAQ
Q1: Why is diagnostics functionality important in automotive ECUs?
A1: Diagnostics enable the collection and analysis of data throughout a vehicle’s lifespan, support maintenance and troubleshooting, allow reading and writing of configurations, and facilitate software updates, making them essential for vehicle reliability and serviceability.
Q2: What makes adaptive AUTOSAR diagnostics challenging to develop?
A2: The challenges stem from the complex specification, which includes over 50 diagnostic interfaces and a detailed 450-page API description, as well as dependencies on other functional clusters and runtime integration complexities that can cause unexpected errors.
Q3: How does TargetLink simplify the development of adaptive AUTOSAR diagnostics?
A3: TargetLink uses a model-based development approach that abstracts the specification details, allows importing diagnostic interface configurations, enables automatic API generation, and supports simulation and validation to catch errors early.
Q4: What diagnostic interfaces does TargetLink currently support?
A4: TargetLink supports the diagnostic data identifier interface for reading and writing data, and the diagnostic routine interface for starting, stopping, and requesting results of diagnostic routines.
Q5: How can developers validate their diagnostic implementations in TargetLink?
A5: Developers can use Model-in-the-Loop (MIL) and Software-in-the-Loop (SIL) simulation modes to test and validate both the model and the generated code before deploying it to the actual ECU, ensuring correctness and reducing runtime errors.
