Testpoint¶
Simulink signals connect Simulink blocks with each other and transfer data between such blocks. Simulink signals can be made visible in PMP by marking them as a testpoint (see the properties dialog of a signal). For every Simulink signal marked as a testpoint a corresponding Signal instance is created in PMP. Signals marked as testpoint which are connected to inports and outports are not converted to PMP signals. Instead, the corresponding inport or outport values can be traced. Furthermore, the availability of testpoint data in PMP is limited by the set of data that Simulink generates.
The name of this signal instance corresponds with the name of the signal as discussed under Naming conventions and restrictions. PMP signals derived from testpoints are read-only. PMP signal properties can be set in the same way as for outports.
Note that the user is responsible for creating test-points with unique names.
The package property of a Simulink signal may not be set for a Simulink signal to be exported to PMP. Signals marked as testpoints which are connected directly to inports are not exported by Simulink and can therefore not be made visible in PMP as PMP signals.
In contrast to output signals, the testpoint data is immediately visible in the main loop if the model is executed asynchronously. This is illustrated in Overview of an asynchronously processed sample where a testpoint is written during the execution of the model. In dark blue is the writing of the testpoint and the arrow above indicates the data is immediately visible in the main loop.
Overview of an asynchronously processed sample where a testpoint is written during the execution of the model¶