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

# OpMonitoringStart

## Description

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

The **OpMonitoringStart** block, located in the **RT-LAB/Monitoring** library, enables monitoring of selected parts of a model. Use this block with a paired OpMonitoringStop block. Place an atomic subsystem between the two blocks so Simulink computes all blocks inside the subsystem before producing outputs. Then group the atomic subsystem and both monitoring blocks inside an atomic subsystem to preserve execution order (OpMonitoringStart executes before OpMonitoringStop at each computation step).

## Mask parameters

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

<table><thead><tr><th width="248.20001220703125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Event Name</strong></td><td>This field contains the name of the event to be registered. The same event name must be used in the corresponding OpMonitoringStop block.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

<table><thead><tr><th width="249.00006103515625">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Output</strong></td><td><p>Connect the output to an atomic subsystem.</p><p>Do not use the output value inside the model; the connection only enforces block execution order in the Simulink scheduler.</p></td></tr></tbody></table>

## Characteristics and limitations

| Characteristic       | Value |
| -------------------- | ----- |
| Direct Feedthrough   | No    |
| Discrete sample time | Yes   |
| XHP support          | Yes   |
| Work offline         | No    |


---

# 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/opmonitoringstart.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.
