Supported test environments
The test execution is based on a virtual machine (TPT-VM) that is equal for all test environments.
To integrate a TPT-VM in different test environments, platform adapters are available. The modeling of a test is independent from its execution. By using the same virtual machine (TPT-VM) in every test environment, it’s ensured that test cases alike for Model-in-the-Loop (MiL), Software-in-the-Loop (SiL), and Hardware-in-the-Loop (HiL) without the need of adapting them.
TPT test are reactive and can react on the system’s behavior during the test execution if necessary.
Integrations exist for MATLAB/Simulink, TargetLink, and ASCET.
C-code can directly be tested with TPT. This way, AUTOSAR software components can be tested with TPT just as C-code that was automatically generated from Simulink, TargetLink, or ASCET models.
PiL-tests can be performed on different architectures by coupling TPT close to the Universal Debug Engine (UDE) by PLS or via Simulink.
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.
TPT-tests can be run directly inside a vehicle. Driving directions to the driver and communication via CAN or application tools like INCA or CANape are possible.
TPT supports manual and automatic testing. Manual testing can be done interactively via Dashboards built 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.
TPT enables you to test code directly on a target processor. For PiL-testing, TPT is connected to the Universal Debug Engine (UDE) by PLS via an interface.
To execute tests automatically, TPT takes over remote control from UDE.
Alternatively PiL testing is possible using Simulink or TargetLink. In this case MATLAB handles the communication between PC and 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 variables on target
(symbolic and address based)
- Access to local variables of functions
- Access to individual bits and registers
- Support of multidimensional arrays,
structures, maps, and curves
Control Flow features
- Synchronization with TPT at breakpoints
- Testing of isolated functions and code
- Direct access to control flow
- Invocation and use of UDE macros
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-individual 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 LABCAR are run on a Windows-control-PC and 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 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.
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.
Testing in vehicles (Driver-in-the-Loop)
TPT can be used directly for vehicle testing. These are tests where TPT communicates with the driver by driving commands, and at the same time with the vehicle itself by sending signals and parameters. The measurement data from these tests are assessed automatically. The data management is also automatic.
Observe the test progression
Which of the test steps is currently active during the test execution, is marked in colors inside the step list itself.
TPT communicates with driver via acoustic messages, screen dialogs, or via the TPT-Dashboard.
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 co-simulations with other so-called FUSION nodes and rest-bus simulations.
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.