> 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-lab-library/opvirtualscope.md).

# OpVirtualScope

## Description

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

The **OpVirtualScope** block, located in the **RT-LAB/Miscellaneous** library, displays, logs, and manages multiple signals in the TestDrive application. It links the LabVIEW interface to the RT-Lab controller without using the OpComm acquisition tool. As a result, many LabVIEW GUI controls are not signals or parameters of the RT-Lab simulation model, which affects how the model must be built compared with other TestDrive modules.

## Mask parameters

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

<table><thead><tr><th width="249.7999267578125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>ID</strong></td><td><p>The Blob ID defined in the LabVIEW GUI uniquely binds the GUI to this block.</p><ul><li>If two acquisition cards are present on a carrier board, each card can have its own GUI. This requires two OpVirtualScope blocks with distinct Blob IDs.</li><li>You can link more than one card to a single OpVirtualScope (one GUI). In this case, all acquired data must have the same type and the same number of samples per step.</li><li>You can link more than one OpVirtualScope to a single card. The same constraint applies: identical data type and identical number of samples per step.</li></ul></td></tr><tr><td><strong>Maximum Buffer Size (Seconds)</strong></td><td>Defines the duration of all active traces that are continuously buffered. This is the maximum observable trace length. In triggered mode, it is also the maximum duration displayed before the trigger occurs. The buffer size can be as large as allowed by system RAM (and CPU speed) and as small as the step size. It is strongly recommended NOT to set the size to the step size.</td></tr><tr><td><strong>Maximum Scope Width</strong></td><td>Sets the maximum pixel width of the scope.</td></tr><tr><td><strong>Number of Traces</strong></td><td>Provides the C function with the number of channels so the code can demultiplex the signals correctly. Fewer channels generally improve communication speed because less data is sent over the network, which can help reduce data loss. However, other factors also affect communication speed, including data type, number of samples per step, scope width, and active channels. Limiting the number of traces might not produce a significant change by itself.</td></tr><tr><td><strong>Input Data Type</strong></td><td>Casts the incoming channel data to any Simulink type. This is useful when acquired data is encapsulated while being transferred from the acquisition card to the Simulink model (for example, two 16-bit integers into one 32-bit integer). This method is faster and uses less memory than the Simulink "conversion" block. Default value: auto (uses the Simulink type and does not cast).</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="251.39996337890625">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Channels</strong></td><td>Concatenation of all samples of all traces into a single 1-D vector. Samples are ordered by trace, where s<sub>ij</sub> denotes the jth sample of the ith trace.</td></tr></tbody></table>

## Outputs

This block has no outputs.

## Characteristics and limitations

<table><thead><tr><th width="241">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td>Maximum number of traces</td><td>One OpVirtualScope block can handle up to 32 traces, regardless of configuration (for example, 4 OP6228 modules with 8 traces each, or 1 OP5130 with 32 traces).</td></tr><tr><td>Performance note</td><td>A model with two 4-channel cards is slower than a model with a single 8-channel card.</td></tr></tbody></table>


---

# 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-lab-library/opvirtualscope.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.
