SimulinkReal-Time Scope Usage

To monitor an output signal from a Constant block
by connecting it to a
Simulink®
Real-Time™Scope block, add
a test point for the Constant block output signal.

You can add a
Simulink
Real-TimeScope block
only to the topmost model, not to a referenced model. To log signals
from referenced models, use
Simulink
Real-Time Explorer scopes or
Simulink
Real-Time language
scope objects.

When you build and download the real-time application,
the
Simulink
Real-Time kernel creates a scope representing the real-time Scope block.
You can change the Scope parameters after building
the real-time application or while it is running. To change the parameters,
assign the scope to a MATLAB® variable using the target object
method SimulinkRealTime.target.getscope. You
can use SimulinkRealTime.target.getscope to remove
a scope created during the build and download process. The
Simulink
Real-Time kernel
recreates the scope when you restart the real-time application.

If the output of a Mux block is connected to the input of a
Simulink
Real-Time Scope block, the signal is not observable. To observe the signal, add a
unit gain block (a Gain block with a gain of 1)
between the Mux block and the
Simulink
Real-TimeScope block.

You can pass vector signals into a
Simulink
Real-TimeScope block.
The real-time application interprets the vector as a series of individual
signals. However, you cannot pass a matrix signal into a Scope block.
Doing so results in a build error. To display a matrix signal, pass
it to a Reshape block and pass the resulting vector
into the Scope block.

The real-time application can generate data faster
than the kernel can process it. Previous data can be overwritten,
causing gaps. If gaps occur in the data, consider increasing the value
of the Decimation property of the scope.