Video: Get to Know vVIRTUALtarget in 2:30 Min. ... Just Click

Page navigation

Virtual Developing and Testing AUTOSAR Software

vVIRTUALtarget is a software that is used to generate virtual ECUs for all typical AUTOSAR projects. It supports function and software developers, software integrators and test engineers throughout the entire ECU development process.

With vVIRTUAltarget you create virtual Systems Under Test (SUTs) for both AUTOSAR Classic and AUTOSAR Adaptive:

AUTOSAR Classic has been the established standard for use in signal-based applications for many years.
AUTOSAR Adaptive, on the other hand, concentrates on the service-oriented architecture as it will be increasingly used in future projects.

Both architectures complement each other and are used depending on the application.

Advantages

vVIRTUALtarget runs on all typical Windows PCs
Execute your software either in or independently of real time
Set up and run tests of the entire ECU software even in the absence of the target hardware – from the application software, through the AUTOSAR Basic Software and on to the hardware drivers
Modify and simulate your configuration for the real hardware
Configurations of real and virtual hardware always remain consistent
Simple connection to other test tools

Gallery

All Images Videos

In this short video you will learn how to develop and test AUTOSAR ECU software faster and more relaxing - namely virtual - with vVIRTUALtarget. Join our two engineers and see yourself. (2:36 min)

Learn about the easy setup of a virtual ECU in an AUTOSAR environment. See how to use vVIRTUALtarget in a typical workflow together with the DaVinci Tool Suite and with CANoe (4:30 min).

System Description: Add AUTOSAR descriptions to a project

System Under Test: Setting the scope of the test

BSW Emulation: Setting options of the Basic Software emulation

Application Files: Managing the implementation files of the software components

Simulation Setup: Selection of ECU and network setups for the execution environment

Directories: Setting the locations of files belonging to the project

Applications Areas

Testing of functional software based on AUTOSAR 4 even during early phases
Supportive testing during design and implementation of the functional software
Testing and verification of software integration in a virtual environment
Verification of tests using virtual ECUs for re-use at physical ECUs

50 Seconds Elevator Pitch:

Senior Product Manager Roman Marktl introduces his product vVIRTUALtarget.

Highlights Version 4.0

Current AUTOSAR Adaptive and AUTOSAR Classic standards are supported
Automated generation of a System Under Test (SUT) supports continuous testing
The SUT can now also be build with the current version of Visual Studio 2019
It is also possible to generate the SUT with alternative build environments

Webinar Recording: Product Introduction and Highlights of Version 4.0

Users

Even at of a very early stage, Software Developers and System Integrators use the “pro” and “basic” variants for the virtual testing of functional software based on AUTOSAR 4. In the subsequent work steps, the virtual ECUs are integrated and used in test environments:

Typical user roles and software tools in a workflow with vVIRTUALtarget

Variants

Variant "pro"

You can start verifying your results with vVIRTUALtarget as early as the software component (SWC) design and development phases. The vVIRTUALtarget pro variant allows you to automate the connection of one or more SWCs to a runtime environment via your AUTOSAR interfaces. In this case, vVIRTUALtarget pro emulates the typical behavior of the AUTOSAR basic software so that you do not need to worry about configuring basic services – as in the case of ECU configuration – or about the implementation of these services – as in the case of a unit test. On the one hand, the tool delivers an automatically generated proposal for the typical management layer services while, on the other, also allowing you to determine these yourself. Thanks to this flexible approach, you can concentrate fully on the task of test implementation itself, which means, simulating the inputs to your software and observing the reactions at the outputs.

Variant "basic"

The next step is to test the entire ECU configuration as visualized in vVIRTUALtarget basic. This is done using an original target ECU configuration – again created using the designated tool DaVinci Configurator Pro – in order to obtain the greatest possible level of fidelity to detail. There is no need for any reconfiguration or new configuration work. The result is a binary file that you can use in your PC runtime environment, for example CANoe. In the same way as with physical ECUs, your test interfaces are network messages and I/Os.

The created virtual ECUs can be used in the cluster as well as with physical ECUs in order to test the entire system.

Coverage of the Variants for AUTOSAR Classic and AUTOSAR Adaptive

vVIRTUAltarget supports you in creating virtual Systems Under Test (SUT) for both AUTOSAR Classic and AUTOSAR Adaptive:

AUTOSAR Classic has been the established standard for many years for use in primarily signal based applications.
AUTOSAR Adaptive, on the other hand, concentrates on service-oriented architecture as it will be increasingly used in future projects.

Both architectures complement each other and are used depending on the use case.

Case Study

Efficient Creation and Testing of Virtual AUTOSAR ECUs

The Challenge

Testing efficient AUTOSAR ECU software for unavailable ECUs

The Solution

Virtualization needs no hardware!

Read the Case Study

Product Descriptions

Show previous

Show next

Documents Webinar Recording System Requirements Language Versions

Fact Sheet:

Short overview of fa cts (PDF)

Case Study:

"Efficient Creation and Testing of Virtual AUTOSAR ECUs" (PDF)

Use this know how from our specialists:

"Virtual Integration and Test of AUTOSAR Systems"
Duration: 58 min.

Watch Now!

Component	Recommendation	Minimum
Operation System	Windows 10/8.1/7 SP1 (64 Bit)
Processor	Intel Core i5 3.0 GHz	Intel Core 2 Duo 2.6 GHz
Memory (RAM)	4 GB	1 GB
Hard drive capacity	≥ 2,0 GB (depending on options used and necessary operating system components)
Screen resolution	1280 x 1024	1024 x 768