ETAS ISOLAR-EVE (ETAS Virtual ECU) tool environment comprises both the ETAS ISOLAR-EVE and ETAS RTPC-EVE software products. They serve for testing production ECU software in a virtual environment on the PC.

ISOLAR-EVE provides a realistic representation of an ECU (right) on a Windows PC (left).

With the help of ISOLAR-EVE, users are able to test AUTOSAR software, e.g. software of production ECUs, on their PCs. To that end, AUTOSAR configurations consisting of AUTOSAR-XML files and the ECU program code are imported into ISOLAR-EVE, where, they are configured for execution on the PC. In this process, only the hardware-related software components, that is MCAL (Microcontroller Abstraction Layer) and OS (Operating System, must be replaced. Afterwards, ISOLAR-EVE generates executable programs – virtual ECUs (VECU) – for the PC.

Non-real-time execution on a Windows PC

For the execution of virtual ECUs, two use cases apply:

Execution on a Windows PC

The virtual ECU is operated in an open-loop test environment or together with a plant model. Execution in non-real-time makes full use of the PC’s computing capacity and ensures fast results. Users can opt to manually adjust the speed of execution.

Execution on ETAS RTPC-EVE

Execution on a Real-Time PC and real components.

The virtual ECU is executed on a separate PC using the ETAS RTCP-EVE simulation software. RTPC-EVE supports not only purely virtual execution, but also integration of the virtual ECU into real hardware environments. This is why it supports hardware interfaces such as a CAN card or a digital/analog I/O card, enabling communication with other ECUs and tools.

Flexible choice of testing environment

ISOLAR-EVE not only generates virtual ECUs for execution on the PC – it also provides an integrated test framework. By means of open, flexible interfaces to simulation, test, and calibration tools such as Simulink®, CANoe, BUSMASTER, PikeTec TPT, INCA and others, virtual ECUs can be integrated easily in existing execution and test environments.

In this way e.g. a Simulink® S function interface can be generated for connection to a Simulink® environment or a Functional Mockup Unit (FMU) for use in FMI-compatible co-simulation tools (Functional Mockup Interface, FMI). Thus, virtual ECUs can be tested in a closed feedback loop.

The behavior of the virtual ECUs can be quickly and easily visualized in the ETAS Experiment Environment. What’s more, XCP-capable measurement and calibration tools, such as ETAS INCA, can be used for data recording, visualization, and calibration of the virtual ECU. In this way, users can also exchange parameter data sets between real and virtual ECUs and use them for executing tests on the PC.

To analyze the communication behavior of the virtual ECU, ISOLAR-EVE supports the connection with bus analysis tools, such as CANoe or BUSMASTER. This can be performed either via a real CAN bus or via virtual CAN communication on the Windows PC.


ISOLAR-EVE is open to other AUTOSAR conform authoring and behavior-modelling tools as well as to manually coded AUTOSAR software components. ISOLAR-EVE is of course compatible with other ETAS tools, in particular the ISOLAR-A AUTOSAR authoring tool and software development tools of the ASCET product family.