Signals with Test Points :: Signal Considerations (Real-Time Workshop®)

Signals with Test Points

A test point is a signal that is stored in a unique location no other signals share or reuse. See Working with Test Points in the Simulink documentation for information about including test points in your model.

When you generate code for models that include test points, the Real-Time Workshop build process allocates a separate memory buffer for each test point. Test points are stored as members of the model_B structure.

Declaring a signal as a test point disables the following options for that signal. This can lead to increased code and data size. You do not lose the benefits of optimized storage for any other signals in your model.

Signal storage reuse
Enable local block outputs
Reuse block outputs
Eliminate superfluous local variables (Expression folding)
Minimize data copies between local and global variables

For an example of storage declarations and code generated for a test point, see Summary of Signal Storage Class Options.

If you have a Real-Time Workshop Embedded Coder license, you can specify that the Real-Time Workshop build process ignore all test points in the model, allowing optimal buffer allocation, using the Ignore test point signals parameter. Ignoring test points facilitates transitioning from prototyping to deployment and avoids accidental degradation of generated code due to workflow artifacts. For more information, see Ignore test point signals in the Real-Time Workshop Reference.

Signals with Auto Storage Class

Interfacing Signals to External Code

Related Products & Applications

Get Simulink trial software

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

Get this Simulink Kit