This is machine translation

Translated by Microsoft
Mouseover text to see original. Click the button below to return to the English version of the page.

Note: This page has been translated by MathWorks. Click here to see
To view all translated materials including this page, select Country from the country navigator on the bottom of this page.

Troubleshoot Signals Not Accessible by Name

I cannot monitor, trace, or log some signal types in the real-time application.

What This Issue Means

You cannot monitor, trace, or log by name these types of signals in the real-time application:

  • Virtual or bus signals (including signals from bus creator blocks and virtual blocks). For example, assume that you connect the output of a Mux block (a virtual block) to a real-time Scope block. The Scope block displays the names of the Mux input signals rather than the names of the Mux output signals.

  • Signals that Simulink® optimizes away after you set the Signal storage reuse or Block reduction configuration parameters.

    The output of a block that was optimized away is replaced with the corresponding input signal to the block. To access these signals, make them test points.

  • Blocks that buffer their input signals to make them contiguous. Examples include the To Workspace block and some S-function blocks. Such blocks generate a signal name associated with the generated block.

    If you connect a signal to the input port of such a block and to a real-time Scope block, the Scope block cannot access the signal. To access the signal, add a unit Gain block (a Gain block with gain 1) before the model input to the Scope block.

  • Signals of complex or multiword data types.

  • If a block name consists only of spaces, Simulink Real-Time™ Explorer does not display a node for signals from that block. To reference such a block:

    • Provide an alphanumeric name for the block.

    • Rebuild and download the model to the target computer.

    • Reconnect the MATLAB® session to the target computer.

Try This Workaround

Check the signal types for the issues described in What This Issue Means.

See Also

Related Topics