Real-Time Workshop

Signals: Storage, Optimization, and Interfacing

Real-Time Workshop offers a number of options that let you control how signals in your model are stored and represented in the generated code. This section discusses how you can use these options to:

• Control whether signal storage is declared in global memory space, or locally in functions (i.e., in stack variables).
• Control the allocation of stack space when using local storage.
• Ensure that particular signals are stored in unique memory locations by declaring them as test points.
• Reduce memory usage by instructing Real-Time Workshop to store signals in reusable buffers.
• Control whether or not signals declared in generated code are interfaceable (visible) to externally written code. You can also specify that signals are to be stored in locations declared by externally written code.
• Preserve the symbolic names of signals in generated code by using signal labels.

The discussion in the following sections refers to code generated from Signals_examp, the model shown in the figure below.

Figure 5-4: Signals_examp Model

Parameter Configuration Quick Reference Diagram

Signal Storage Concepts