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.

Host Scope Usage

  • Simulink® Real-Time™ supports as many host scopes as the target computer resources can support. Each host scope can contain as many signals as the target computer resources can support.

  • To clarify your model functionality, consider adding signal labels. If you define signal labels, the host scope displays the labels, highlighted with pointed brackets, instead of the signal names. If you do not define signal labels, the host scope displays the short name of the signal.

  • Use host scopes to log signal data triggered by an event while your real-time application is running. The host scope acquires the first N samples into a buffer. You can retrieve this buffer into the scope object property sc.Data. The scope then stops. Restart the scope manually.

    The number of samples N to log after triggering an event is equal to the value that you entered in the Number of samples parameter.

    Select the type of trigger event in the Scope block dialog box by setting Trigger Mode to Signal Triggering, Software Triggering, or Scope Triggering.

  • The target computer transfers data to the development computer for display in the host scope viewer. Because of this latency, the host scope display lags a target scope display during real-time application execution.

Related Topics