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

# OpOutput

## Description

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

The **OpOutput** block, located in the **RT-LAB** library, creates a connection interface between the model and an external entity such as an I/O module.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-9a2790dbaeb3d39af991d58187a3053c5fa706e0%2FRTL_opoutput_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>Identifier</strong></td><td>Specifies a name for the connection interface. Default is OpOutput. All identifiers must be unique.</td></tr><tr><td><strong>Number of parent blocs in identifier</strong></td><td>Includes the parent block names in the identifier to make it unique.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="251.39996337890625">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Data</strong></td><td>The data sent to the entity connected to the block.</td></tr></tbody></table>

## Outputs

This block has no outputs.

## Characteristics and limitations

<table><thead><tr><th width="213.99993896484375">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>Yes</td></tr><tr><td>Signal dimension limit</td><td>The signal dimension of an OpOutput block is limited by the SIGNAL_VECTOR_SIZE_LIMIT variable.</td></tr><tr><td>Vector size limit</td><td>Signals with more than 1000 values are disabled. Use the SIGNALS_VECTOR_SIZE_LIMIT environment variable to modify this limit.</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/opoutput.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.
