That’s why ISOLAR-EVE development is consistently going into the direction of more openness and integration possibilities. For this we’re using a unique technology, which can be seen as the wiring harness of the Virtual ECU: the Virtual Devices. I wrote more about this in a previous blogpost. Thanks to this technology, an ETAS Virtual ECU generated by ISOLAR-EVE can be integrated in potentially all testing environments.
With the development of ISOLAR-EVE V3, released in December 2015, we improved further the “cabling” possibilities of the Virtual Object-under-test. Many options were available already with the V2.2, like the connection to Simulink, the FMU V1 generation, or the coupling to CANoe.
Following consistently the same development plan, we now provide:
- An integrated interface to the model-based testing tool RT2. Test scenarios developed with ETAS-RT2 can then directly be applied to the ETAS Virtual ECU, without further manual configuration
- The possibility to use the CANoe connection between 2 different PCs. Thanks to this, it is no longer required to have EVE and CANoe licenses available on the same PC to connect the Virtual ECU to a Virtual ECU network
- The support of FMI V2.
Furthermore, testing activities are part of the development process and should be possible in an integrated environment whenever the user needs. For instance, it shall be possible to test a software architecture easily as soon as possible. For this, we are now integrating ISOLAR-EVE with the ETAS Authoring Tool ISOLAR-A.It is therefore now possible to generate a Virtual ECU and test it at any time during the software design phase, assuming the internal behavior of the Software Components is available, e.g. ETAS ASCET or Simulink models, or directly as C-Code.