> 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/opmonitor.md).

# OpMonitor

## Description

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

The **OpMonitor** block, located in the **RT-LAB/Monitoring** library, provides monitoring information for the subsystem where it is inserted.

Outputs appear in the same order as the corresponding parameters selected in the block mask. Information applies only to the subsystem containing the block. Time values are in microseconds.

{% hint style="info" %}
This block replaces the deprecated OpSimulationInfo block.
{% endhint %}

## Mask parameters

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

<table><thead><tr><th width="252.199951171875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Computation time (computing only)</strong></td><td>When selected, the corresponding output returns the time spent in calculation (excluding communication overhead) during the previous time step.</td></tr><tr><td><strong>Real Step Size (computing+overhead+synchronization)</strong></td><td>When selected, the corresponding output returns the total duration of the previous time step, including communication time and, if applicable, synchronization.</td></tr><tr><td><strong>Idle time</strong></td><td>When selected, the corresponding output returns the idle time during the previous time step.</td></tr><tr><td><strong>Number of overruns</strong></td><td>When selected, the corresponding output returns the number of overruns detected during execution of the subsystem where this block is inserted, unless this number was reset to 0 by sending a 1 on the Rst Overrun(s) input.</td></tr><tr><td><strong>User time</strong></td><td>When selected, the corresponding output returns the value of the specified user event time.</td></tr><tr><td><strong>User event name</strong></td><td>Enabled when User time is selected. Multiple events can be specified, separated by commas. User events are registered using the OpMonitoringStart and OpMonitoringStop blocks.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="249.800048828125">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Rst Overrun(s)</strong></td><td>Available when the Number of overruns parameter is selected. Toggle the input from 0 to 1 to reset the number of overruns to 0.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="249.79998779296875">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Monitoring outputs</strong></td><td>One output per selected checkbox in the block mask. See Mask parameters for the description of each output value. Outputs appear in the same order as the mask parameters.</td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="249.7999267578125">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td>Special characteristics</td><td>None</td></tr><tr><td>Direct feedthrough</td><td>No</td></tr><tr><td>Discrete sample time</td><td>Yes</td></tr><tr><td>XHP support</td><td>Yes</td></tr><tr><td>Work offline</td><td>No</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/opmonitor.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.
