Use Case: TargetLink and VEOS

Early Simulation and Experimenting with TargetLink Code

TargetLink code can run not only in SIL/PIL simulations in the Simulink environment, but also on dSPACE’s PC-based simulator VEOS (figure below). This is done by wrapping code in an executable unit called a virtual ECU V-ECU, which is generated from TargetLink models. TargetLink code can then be executed along with other V-ECUs as well as plant models on VEOS. To capture signals and adjust or test parameters, A2L files exported from TargetLink are used with dSPACE ControlDesk, which provides access to VEOS. Thus, the standard dSPACE tools used for real-time simulation are also used for offline simulation and experimentation with TargetLink-generated code. This provides the following benefits for TargetLink users:

• Early simulation of TargetLink code in large systems consisting of multiple virtual ECUs and plant models, including buses if required
• Convenient experimentation and testing with ControlDesk and other dSPACE tools

AUTOSAR and Non-AUTOSAR Projects

The approach shown in the figure intended for TargetLink users who do not work on AUTOSAR projects. For AUTOSAR projects, it is recommended to exchange AUTOSAR software components between SystemDesk and TargetLink, and generate the V-ECU from SystemDesk.