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

# OpInput

## Description

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

The **OpInput** block, located in the **RT-LAB** library, creates a connection interface between the model and 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-7086dbb2ffe831f876ada761d13ae000228132d5%2FRTL_opinput_mask.png?alt=media" alt="" width="329"><figcaption></figcaption></figure>

<table><thead><tr><th width="221">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Identifier</strong></td><td>Specifies the name of the connection interface. Default is OpInput. All identifiers must be unique.</td></tr><tr><td><strong>Number of parent blocs in identifier</strong></td><td>Includes parent block names in the identifier to ensure uniqueness.</td></tr><tr><td><strong>Default Value</strong></td><td>Value output by the block when no I/O is connected.</td></tr><tr><td><strong>Default Values Type</strong></td><td>Data type used for the default value.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

<table><thead><tr><th width="221.79998779296875">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Data</strong></td><td>The data received from the entity connected to the block.</td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="221.00006103515625">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td>Signal dimensions limit</td><td>The signal dimensions for an OpInput block is limited by the minimum between PARAM_VECTOR_SIZE_LIMIT and SIGNAL_VECTOR_SIZE_LIMIT variables.</td></tr><tr><td>Parameter vector size limit</td><td>Parameter(s) with more than 1000 values will be disabled. Use PARAM_VECTOR_SIZE_LIMIT environment variable to modify this limit.</td></tr><tr><td>Signal vector size limit</td><td>Signal(s) with more than 1000 values will be disabled. Use SIGNALS_VECTOR_SIZE_LIMIT environment variable to modify this limit.</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>Yes</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/opinput.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.
