The automotive world is changing rapidly. Vehicles are shifting from mechanically defined systems to software-defined machines, where innovation happens in code. This shift brings incredible opportunities – but it also introduces a major challenge:
How can we validate increasingly complex electronic control unit (ECU) software early, efficiently, and at scale?
Why Early Virtual Validation Matters
Hardware-in-the-loop (HIL) testing remains essential for ECU validation. It provides real-time interaction between physical hardware and simulated environments and is critical for safety-related systems. While HIL testing is indispensable for final-stage validation, it also presents practical challenges:
- Hardware prototypes often arrive late.
- HIL test benches may need to be shared across multiple teams.
- Complex integrations can slow down or break test pipelines.
These limitations can delay integration and system-level testing. In addition, the reliance on physical setups limits scalability, making large-scale or parallel testing difficult. As vehicles become more software-centric, these bottlenecks become more pronounced. One structural solution is to introduce testing earlier in the V-cycle, without requiring the actual hardware.
What are V-ECUs?
Virtual electronic control units (V-ECUs) are software representations – or digital twins – of physical ECUs. They enable software-in-the-loop (SIL) testing long before hardware prototypes are available. With V-ECUs, developers can validate functionality, integration, and communication in PC- or cloud-based environments, helping teams accelerate development and bring software to maturity faster.
While hardware-in-the-loop (HIL) testing remains essential for final validation and real-world interaction, V-ECUs complement HIL by enabling front-loaded testing. This can reduce time pressure and give engineering teams greater control over their development process. For us at dSPACE and for our partners, V-ECUs are the key to enabling front-loaded testing, continuous integration, and cross-domain simulation workflows – ensuring robust systems that are ready for the next step.
Levels of V-ECUs
When simulating ECUs, realistic component behavior is essential for meaningful results. This includes replicating the characteristics of a real ECU, including:
- the operating system,
- the basic software (BSW),
- and the communication stacks.
To meet these requirements, virtual ECUs (V-ECUs) have been introduced as digital representations of physical ECUs, offering varying levels of accuracy to suit different testing objectives.
The concept of V-ECU levels emerged from the need to balance model fidelity with simulation efficiency across different stages of development. Early in the workflow, engineers focus on algorithm design and functional validation, where high levels of detail are unnecessary and would slow down iteration cycles. Later, during integration and compliance testing, more realism becomes essential. This led to the introduction of incremental levels, each adding complexity and realism to meet specific validation goals.
According to the official prostep white paper, five distinct V-ECU levels are defined:
Level |
Description |
Typical Use Cases |
|---|---|---|
|
0 – Controller Model |
Pure functional model for algorithm design and early validation |
Algorithm development and early design iterations |
|
1 – Application Level |
Application software without BSW; ideal for initial integration |
Algorithm development and early design iterations |
|
2 – Simulation BSW |
Adds simulated BSW for communication and timing analysis |
Integration testing and network simulation |
| 3 – Production BSW | Includes real BSW for realistic behavior and compliance testing | Integration testing and network simulation |
| 4 – Target Binary | Full ECU software including the operating system (OS) and drivers | Pre-HIL validation and full system simulation |
dSPACE Solutions for V-ECU Generation and SIL Testing
At dSPACE, we recognized early that virtual validation must be both practical and scalable. That’s why our tool chain enables end-to-end workflows, bridging the gap between model-based development and production software. As a result, engineers can validate functionality, communication, and integration long before hardware is available. This represents a significant shift from hardware-first testing to software-first validation, enabling more agile workflows and smoother integration.
Good to know: ASM runs in VEOS and SCALEXIO, our modular real-time platform for HIL applications, enabling reuse of model configurations and automated test routines across model-in-the-loop (MIL), SIL, and HIL thanks to standardized interfaces and ASAM‑compliant test automation support.
Which benefits do V-ECUs offer during development?
Modern vehicles include more than 100 ECUs, millions of lines of code, and highly sophisticated communication networks. Add autonomous driving, electrification, and connected services, and the need for fast, reliable, and scalable software validation becomes undeniable.
V-ECUs help development teams keep pace by enabling:
- Faster time-to-market: V-ECUs allow integration and functional testing months before hardware prototypes exist, reducing delays and helping teams move faster.
- Parallel development: Multiple teams can work concurrently on application software, basic software, and integration tasks, boosting collaboration and resource efficiency.
- Scalable CI/CT workflows: Automotive software increasingly follows agile and DevOps principles. As V‑ECUs can be executed entirely in the cloud without hardware dependencies, they fit naturally into continuous integration and continuous testing (CI/CT) pipelines, enabling scalable automated regression tests, rapid updates, and early defect detection.
- Reduced costs: Reduced reliance on prototypes and test benches lowers overall costs. Cloud-based testing reduces travel and logistics costs.
- Scaling for complex architectures: Modern electric/electronic (E/E) architectures include domain controllers, centralized computing, and service-oriented communication. V-ECUs allow the simulation of entire vehicle networks, including CAN, LIN, FlexRay, and Ethernet – without physical setups.
- Early safety and compliance assurance: Early validation of functional safety in accordance with ISO 26262, the automotive standard for safety-related systems, and cybersecurity requirements reduces late-stage risks and helps teams stay compliant right from the beginning.
How do SIL and HIL form a unified workflow?
A standout innovation from dSPACE is the seamless integration of SIL and HIL environments. This unified workflow allows developers to reuse models, test cases, and configurations in both domains, ensuring consistency, reducing duplication of effort, and improving development speed.
For example, a V-ECU tested in VEOS during early SIL stages can be effortlessly transferred to a real-time HIL setup using SCALEXIO, our modular hardware platform. This continuity improves traceability, increases test coverage, and supports incremental validation from MIL to full system integration.
The dSPACE tool chain also supports automated test migration, enabling teams to maintain a single source of truth for test artifacts across the development lifecycle. This is especially valuable in agile environments driven by continuous integration and continuous testing (CI/CT).
Standardization and FMI
As collaboration between OEMs and suppliers intensifies, standardization becomes essential. dSPACE is actively involved in advancing the Functional Mock-up Interface (FMI) standard.
With FMI 3.0, the standard supports more complex simulation scenarios, including:
- Clock variables for synchronized co-simulation.
- Grouped I/O terminals for better modularity and signal management.
- The Layered Standard for Network Communication (FMI-LS-BUS) extension for exchanging V-ECUs with embedded bus interfaces.
These advancements simplify the integration of V-ECUs into different tool chains, so that different teams and tools can work together smoothly. Our strong commitment to FMI ensures that dSPACE solutions remain open, interoperable, and future-ready.
What’s next for V-ECUs?
The future of V-ECUs is shaped by major trends that are changing the way we build and test embedded software:
- AI-assisted V-ECU generation: Automotive OEMs and Tier‑1 suppliers can create and update V-ECUs faster, with reduced manual effort. At CES 2026, dSPACE demonstrated a GitHub Copilot-based concept, that shows how developers could generate V-ECUs directly within their development environment. This approach highlights how AI can accelerate the integration of ECU code into CI/CT pipelines, enhancing the efficiency and scalability of SIL validation. It also illustrates the potential to accelerate development pipelines for software-over-the-air (SOTA) updates and the digital homologation of software-defined vehicles (SDVs).
- Cloud-based simulation: With platforms like AWS and dSPACE VEOS, teams can deploy scalable SIL environments in the cloud. This enables globally distributed teams to collaborate in real time, run massive test campaigns, and integrate simulation into DevOps pipelines.
- Autonomous & connected vehicles: As vehicles become more intelligent and interconnected, V-ECUs play a critical role in validating complex E/E architectures, AI-based control algorithms, and vehicle-to-everything (V2X) communication systems.
Additionally, the transition of V-ECUs into Functional Mock-up Units (FMUs) ensures compatibility with FMI-compliant simulators, enabling cross-platform validation and continuous integration workflows.
Conclusion
V-ECUs are no longer just tools; they are becoming the backbone of modern automotive development. At dSPACE, we are building a future where virtual validation is faster, smarter, and more globally connected. We are moving beyond isolated workflows to integrated ecosystems powered by AI, cloud platforms, and real-time collaboration – with safety and compliance built in from the start.
Let’s shape the next generation of mobility together. Whether you are an OEM, supplier, or technology partner, join us in creating a smarter way to develop and validate automotive software.
