Close

Testing in MiL, SiL, PiL, HiL and vehicle with TPT

TPT is independent of the tool environment in which the software is going to be tested. That means you can use the test cases created with TPT in MIL, SIL, HIL, and also in a vehicle. If you want to use a test environment not supported in TPT yet, we will find an individual integration solution for you.
 
 
The test execution with TPT is based on a virtual machine (TPT-VM) – that is the same for all test environments supported by TPT.

 

Several platform adapters are available to integrate the TPT-VM in different test environments.

 

With that, you do not need to think about adapting the test cases when switching to another test environment. Just create your test cases, change them according to the ongoing development process, and select the desired test environment in TPT. The following test methods are supported by TPT:

Model-in-the-loop (MiL)

MIL-tests in TPT can be
executed on MATLAB/Simulink,
TargetLink, and ASCET.

Software-in-the-loop (SiL)

C-code can directly be tested
with TPT. Also AUTOSAR software components can be tested with
TPT as well as C-code that has automatically been generated from Simulink, TargetLink, or ASCET models.

Processor-in-the-loop (PiL)

PIL-tests can be performed with TPT on different architectures by coupling TPT closely to the Universal Debug Engine (UDE) by PLS, or Trace32 by Lauterbach. PIL-tests via Simulink are also possible.

Hardware-in-the-loop (HiL)

TPT is connectable to dSPACE HIL, Simulink Realtime, Concurrent iHawk, NI Veristand, CANoe or LABCAR HIL.
Dependent on the HIL, the TPT-VM runs on a control-PC and communication via ASAM HIL API or on real-time capable hardware.

Vehicle-in-the-loop (ViL)

It is possible to establish a communication between TPT and a vehicle. Parallel driver interaction is possible via acoustic message or graphical display.