dSPACE offers a comprehensive framework for a seamless transition between software-in-the-loop (SIL) and hardware-in-the-loop (HIL) platforms.
Shift-Left Testing
For continuous feedback
Holistic Test Strategy
Including SIL and HIL for high test coverage with as little effort as possible
Create Once − Use Twice
Easier start in SIL due to reusability of HIL
SIL, HIL, Hybrid – A Holistic Test Strategy
Effortlessly switch between simulation platforms:
- Use plant and environment models for software-in-the-loop (SIL) and hardware-in-the-loop (HIL) tests
- Use tests across platforms
- Use virtual ECUs (V-ECU) on SIL, but also HIL simulators
Hybrid Simulation (SIL-HIL Co-Simulation)
- Gradually replace virtual ECUs with real ECUs instead of hard switching
- Availability-driven testing: Combine SIL and HIL to test ECUs or V-ECUs − whichever is available
- Supplement component-level HIL with full-vehicle SIL
As a SIL user, how do I benefit from HIL?
HIL: Physical Fidelity, Safety, and Real-World Confidence
Hardware-in-the-loop (HIL) testing validates real ECUs within a realistic, simulated environment to ensure proper behavior under real-time conditions. HIL offers reproducible, fully automated tests for the hardware-software integration in a 24/7 lab execution. Critical corner cases can be safely tested without risk to the device or its surroundings, delivering physical fidelity and confidence before deployment.
Use Cases
- Perform reliable HW-SW integration checks before prototype vehicles.
- Ensure deterministic real-time behavior of ECUs and networks, including communication.
- Verify correct responses under electrical fault conditions.
Benefits
- Early feedback from software-hardware integration tests if the same test setup is used between SIL and HIL.
- Real hardware testing: Validate with actual ECUs and sensors.
- High fidelity: Realistic behavior for certification and approval.
- Find errors more efficiently: Reproduce tests between SIL and HIL
- Reuse: Leverage SIL models and test cases.
Workflow
- Define the interfaces between software and hardware (e.g., CAN, Ethernet, analog/digital I/O).
- Choose a HIL system that fully meets your test requirements.
- Prepare the test environment.
- Hardware setup: Connect ECUs, sensors, actuators, and communication interfaces.
- Simulation models: Reuse or adapt models from SIL (e.g., plant models, environment models).
- Real-time execution: Ensure models run in real time on the HIL system.
As a HIL user, how do I benefit from SIL?
SIL: Speed, Scalability, and Early Validation
Software-in-the-loop (SIL) testing simply means that software – regardless of its state – is executed in a simulated environment to thoroughly test its functionality and check the bits and bytes, without requiring physical ECU hardware. SIL can be accelerated beyond real time, enabling faster test execution, early error detection, agile iteration in virtual environments, and providing high availability and scalability for efficient development.
Use Cases
- Test applications or SW-SW integration before prototype hardware is available.
- Continuous testing with regression runs after each code change.
- Fast fault analysis during function development.
- Left shift of validation tasks.
Benefits
- Early testing: Debug at function and integration level (e.g., perception, sensor fusion, speed control).
- Cost efficiency: No need for physical hardware during early stages.
- Fast iteration: Quick turnaround for code changes and regression testing.
- Scalability: Run multiple simulations in parallel.
- Reuse: Models and test cases can be reused in HIL.
Workflow
- Identify software components to be tested (e.g., perception, control algorithms, sensor fusion).
- Clarify the interfaces and dependencies (e.g., inputs from sensors, outputs to actuators).
- Choose a SIL environment that fully meets your test requirements.
- Prepare the test environment:
- Use V-ECU with virtual interfaces.
- Reuse or adapt simulation models from HIL (e.g., plant models, environment models).
As a SIL/HIL user, how do I benefit from SIL-HIL continuity?
Hybrid: Flexibility, Continuity, and Seamless Transition
Hybrid testing combines the strengths of SIL and HIL by integrating simulated components with real hardware in one environment. This approach enables seamless transitions between virtual and physical testing, supports continuous validation across development stages, and maximizes test coverage. Hybrid setups allow early software verification while incorporating real-world hardware behavior—delivering flexibility, efficiency, and confidence throughout the entire development cycle.
Use Cases
- Ensure your software quality prior to hardware integration.
- Step-by-step integration and testing.
- Software has matured beyond initial SIL validation, but hardware is not fully available.
- Combine virtual components with real hardware for early integration validation.
- Continuous testing across SIL and HIL environments without waiting for full prototypes.
Benefits
- Early error detection: Fix software errors before hardware integration to avoid a big bang integration.
- Flexibility: Mix simulated and real components for optimal resource usage.
- Continuity: Seamlessly bridge SIL and HIL stages for uninterrupted validation.
- Cost reduction: Reduce dependency on complete prototypes and physical setups.
- Comprehensive coverage: Validate complex interactions under both realistic and virtual conditions.
- Faster time to market: Detect issues earlier and accelerate development cycles.
- Reuse: Use the same setup across SIL and HIL environments.
Workflow
- Identify components that remain virtual and those that will be replaced with real hardware.
- Define interfaces between virtual and physical components (e.g., signal routing, communication protocols).
- Choose a hybrid-capable test system that supports SIL and HIL integration.
- Prepare the test environment:
- Virtual components: Use V-ECUs, simulated sensors, and plant models from SIL.
- Physical components: Integrate real ECUs, sensors, or actuators as needed.
- Synchronization: Ensure time alignment and data consistency between virtual and physical domains.
