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

# OpDelay

## Description

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

The **OpDelay** block, located in the **RT-LAB/Monitoring** library, simulates computation time by adding a delay in the model. It helps determine how much calculation time can be added without causing overruns.

## Mask parameters

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

<table><thead><tr><th width="220.99993896484375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Synchronize</strong></td><td>Forces the block to be executed at the beginning of each calculation step in the model.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="221">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Delay</strong></td><td>Delay in microseconds to be simulated by the block.</td></tr><tr><td><strong>Inputs</strong></td><td>Data input copied to the block outputs. Use this signal to position the OpDelay block in a specific execution order in the model. If the OpDelay block has no dependencies with other blocks, it can execute in any order. If its output is connected to another block (for example, a Gain), the OpDelay block should execute before that calculation.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="220.99993896484375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Outputs</strong></td><td>Copies the data received on Inputs. See Inputs for details.</td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="221.800048828125">Characteristic</th><th>Value</th></tr></thead><tbody><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/opdelay.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.
