| Feature | Description |
|---|---|
| Full name | Virtual ECU Operating System |
| Purpose | Simulate complete ECU software including AUTOSAR BSW, OS, and application |
| Execution | x86-64 host; Windows or Linux; real-time capable via VEOS Player |
| Integration | SystemDesk (ARXML), TargetLink code, ControlDesk for signal monitoring |
| Python API | VEOS Python scripting for automated test execution |
| Coverage | Code coverage via gcov integration; ASPICE report export |
| Bus simulation | Virtual CAN, LIN, Ethernet via VEOS Network Models |
dSPACE VEOS Overview
VEOS Python Scripting
"""dSPACE VEOS automated test using Python API."""
import veos
import time
def run_speed_controller_test(speed_ref: float,
duration_s: float) -> dict:
"""Run one test case in VEOS and return result."""
# Start VEOS with the compiled vECU package
player = veos.Player("SpeedController_vECU.veos")
player.start()
# Set input signal via VEOS variable access
player.set_variable("SpeedController/SpeedRef_kmh", speed_ref)
# Run for specified duration
player.run(duration_s)
# Read output signals
pedal = player.get_variable("SpeedController/PedalRequest_pct")
fault = player.get_variable("SpeedController/FaultActive")
speed = player.get_variable("SpeedController/VehicleSpeed_kmh")
player.stop()
return {"pedal": pedal, "fault": fault, "speed": speed}
def test_nominal_cruise():
result = run_speed_controller_test(speed_ref=100.0,
duration_s=10.0)
assert abs(result["speed"] - 100.0) < 1.0, \
f"Speed error too large: {result['speed']}"
assert result["fault"] == 0
if __name__ == "__main__":
test_nominal_cruise()
print("VEOS test: PASS")Summary
dSPACE VEOS provides the most complete AUTOSAR SiL environment available, simulating not just the application code but the full AUTOSAR stack including OS task scheduling, COM signal routing, NvM management, and BSW module interactions. This level of fidelity catches integration defects that standalone SiL binaries miss: timing issues between OS tasks, NvM initialisation sequences, and COM gateway routing errors all require the full AUTOSAR stack to reproduce. The Python scripting API makes VEOS CI-friendly: tests are written as standard Python scripts, executed by any CI framework, and results parsed automatically. The main limitation is cost -- VEOS licensing is significant, making it most cost-effective for projects where AUTOSAR integration complexity justifies the investment.
🔬 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.