Create test cases independently from the test method

You can model your tests in TPT independently from the test environment because the test execution 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.

That is, you do not need to bother 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.
Thus, once created test cases can be run effortlessly in Model-in-the-Loop (MIL), Software-in-the-Loop (SIL), and Hardware-in-the-Loop (HIL). The following test methods are supported by TPT:


Model-in-the-Loop

Model-in-the-Loop (MIL)

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


Software-in-the-Loop

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

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. PIL-tests via Simulink are also possible.

Hardware-in-the-Loop

Hardware-in-the-Loop (HIL)

TPT is connectable to dSPACE HIL, Simulink Realtime, Concurrent iHawk, NI Veristand, 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.




Driver-in-the-Loop

Automotive testing

It is possible to establish a communication between TPT and a vehicle via CAN or application tools like INCA and CANape. It is also possible to set textual call to actions in TPT for the tester.



Manual and automatic tests

Automatic and manual testing

TPT supports manual and automatic testing. Manual testing can be done interactively via the Dashboard by PikeTec that is set up by the user. Automatic test execution is done directly from the user interface, in batch-mode, or by using a continuous-integration-server
like Jenkins.

Processor-in-the-loop testing with TPT

For PIL-testing, TPT is connected via an interface to the Universal Debug Engine (UDE) by PLS.
TPT can take over remote control from UDE to execute the tests created with TPT automatically.
Alternatively PIL testing is possible using Simulink or TargetLink.
In this case it is MATLAB that handles the communication between PC and the PIL board.


Supported processor architectures

Via UDE, testing and debugging is possible of AURIX,
TriCore, Power Architecture, Cortex, ARM, XE166/XC2000, XScale, SH-2A, C166, XilinX SoCs, Freescale MPC family, and many more microcontrollers, and also
of multi-core-targets.

Variables and data support

  • Access to symbolic and address based variables
  • Access to local variables of functions
  • Access to individual bits and registers
  • Support of multidimensional arrays, structures, and lookup-tables

Control Flow features

  • Synchronization with TPT at breakpoints for debugging purposes
  • Testing isolated functions and code
  • Direct access to the control flow
  • Invocation and use of UDE macros

Hardware-in-the-loop testing with TPT

TPT-tests can be executed in several HIL test environments.
Solutions exist for dSPACE HIL systems, and TPT can be coupled to ETAS LABCAR, Concurrent iHawk, Simulink Realtime, and NI Veristand. Further customized proprietary HIL solutions are available and in use. Depending on the HIL architecture, the TPT-VM is integrated on the control-PC or on the real-time side of the HIL. The communication with the HIL is realised via ASAM HIL (XiL) API or using HIL-specific communication protocols.


Real-time HIL testing

Real-time capable and reactive execution of TPT-tests on HIL systems can be performed with cycle periods smaller than 100µs.

Tests in real-time are possible on HILs by dSPACE, Concurrent, Nationals Instruments, and Mathworks.

PC-controlled HIL testing

TPT-tests on the test environment LABCAR are run on a Windows-control-PC; the control signals are exchanged with the HIL. This way, a simple communication is possible with application tools like INCA or CANape. While controlling the HIL system, you can use TPT to run the Dashboard by PikeTec or directly control a CAN bus.

Virtual HIL using Synopsys Virtualizer

The Synopsys Virtualizer emulates HIL or PIL systems. TPT tests can be executed on the virtual hardware of the Synopsys Virtualizer.

  • TPT interacting with the Synopsys Virtualizer

Additional HIL features

  • Interface import of model values and controller signals
  • Automatic access to measurements and application parameters
  • Fault simulation

Customized HIL integration

Often HIL systems are solution-oriented and therefore unique. TPT can easily be connected also to such unique HILs. PikeTec can assist you with this task.

Test execution in vehicles (Driver-in-the-loop)

You can use TPT for tests in vehicles while driving. These are tests where TPT communicates with the vehicle via signals and parameters and where the driver receives driving commands and other calls to action at the same time.
The measurement data from the tests are assessed automatically by TPT.


TPT can communicate with the driver by sending driving command and with the vehicle by sending signals and parameters

Observe the test progression

Which of the test steps is currently active whilst testing, is highlighted with colors inside the step list.




Driving commands

TPT communicates with driver via acoustic messages, screen dialogs, or via the Dashboard by PikeTec.



Communication with the vehicle

TPT can access in-vehicle signals via interfaces like CAN, LIN, or via application tools. These interfaces can easily be extended by using more of the so-called FUSION nodes.

CAN and LIN

To execute tests directly via CAN and LIN busses, a Vector CAN card, a CAN case,
or a PCAN usb adapter by Peak is needed to connect to the hardware.

Test cases are run in quasi real-time (PC real-time). Signals in TPT are mapped to CAN/LIN messages and are transmitted to the control unit via the corresponding hardware connection. The configuration of the messages are done by using appropriate DBC or LDF files. The test is executed on the TPT-FUSION platform. It is possible to run restbus simulations and also co-simulations with other so-called FUSION nodes.


Integration with ETAS INCA

TPT can run INCA remotely. It’s possible to initiate measurements and alter application parameters. Besides scalar parameters, also structured application values like arrays, maps, and curves can be used. The results can be observed on the real system and afterwards assessed automatically.

Integration with CANape

TPT communicates with CANape via interfaces like MCD-3. Access to application parameters and online measurements during the test run are supported. The data can be observed and is used afterwards by TPT for automatic assessment.


Integration with CANoe

TPT can execute its test cases via CANoe. CANoe is run remote-controlled by TPT. In just a few steps, TPT can be integrated into each CANoe configuration as C-library. CANoe signals and system variables can automatically be accessed.


Follow us