> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-events-library/rte-scope.md).

# RTE Scope

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8a21a94cdb7c7b4ecff8d23e68a8e781216c590e%2FRTE_scope_block.png?alt=media" alt="" width="101"><figcaption></figcaption></figure>

The **RTE Scope** block, located in the **RT-EVENTS/Sink** library, displays signals generated during a simulation.

The block supports multiple axes (one per input). All axes share a common time range (x-axis) and have independent y-axes. You can adjust the displayed time span and value range, and you can move and resize the scope window.

Continuous signals are plotted point-to-point. Discrete signals are plotted as stair-step curves.

A trigger option pauses the display at the right edge and waits for a specified event before resuming from the left, resynchronizing the timebase to the input signal and preventing horizontal drift. Triggering supports both nonperiodic signals (for example, single pulses) and periodic signals (for example, sine and square waves).

Toolbar controls let you zoom, show all data received by the scope, preserve axis settings across simulations, limit displayed data, save data to the workspace, and select a specific time range. For details, see the Simulink Scope documentation.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-8e64d728fe3a03e537bc436e1f3a733c68119c1c%2FRTE_scope_acces_param.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-931944d772e7d52b3aa8a76ec68dfe83553a7f31%2FRTE_scope_mask.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Access the mask parameters by clicking the **Scope Parameters** button in the RTE Scope window.
{% endhint %}

<table><thead><tr><th width="172.39996337890625">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>External Trigger</strong></td><td>Select the trigger type. Choose None to disable triggering. A Double or an RTE Boolean signal can trigger the scope. With an RTE Boolean trigger, synchronization can occur anywhere within the calculation step.</td></tr><tr><td><strong>Number of Axes</strong></td><td>Set the number of y-axes (one per input), up to a maximum of 6. All axes share the same time base (x-axis) and have independent y-axes.</td></tr><tr><td><strong>Time Range</strong></td><td>Enter the x-axis span in seconds. Each screen displays that duration of data.</td></tr><tr><td><strong>Save Data to Workspace</strong></td><td>Enable to automatically save data collected by the block at the end of the simulation. This activates the Variable Name field.</td></tr><tr><td><strong>Variable Name</strong></td><td>Enter a unique workspace variable name. It must not conflict with other logging variables (other Scope blocks, To Workspace blocks, or simulation return variables such as time, states, and outputs).</td></tr><tr><td><strong>Format</strong></td><td>Data can be saved in only one format: Structure with time.</td></tr><tr><td><strong>Limits Data Points to Last Events</strong></td><td>Enable to limit saved data to the last N events, then enter N. The Scope uses its data history for zoom and autoscale. For example, if limited to 1,000 events and the simulation generates 2,000, only the last 1,000 are available for redisplay.</td></tr><tr><td><strong>Number of Points</strong></td><td>Number of data points to store in memory.</td></tr><tr><td><strong>Signal Name Format</strong></td><td>Choose none, short, or long signal labels.</td></tr><tr><td><strong>Discretization of Continuous Signals</strong></td><td>When enabled, display continuous signals as stair-step plots instead of point-to-point plots.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="250">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Inputs</strong></td><td>Signals to display.</td></tr><tr><td><strong>External Trigger</strong></td><td>External signal that triggers the scope.</td></tr></tbody></table>

## Outputs

This block has no outputs.

## Characteristics and limitations

| Characteristic     | Value |
| ------------------ | ----- |
| Direct Feedthrough | No    |
| Sample Time        | No    |
| Work Offline       | Yes   |
| Dimensionalized    | Yes   |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-events-library/rte-scope.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
