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

# OpAsyncRecv

## Description

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

The **OpAsyncRecv** block, located in the **RT-LAB/Communication/Asynchronous** library, receives data from the asynchronous process started by the associated controller. The block reads data from shared memory and makes it available in the model. If no new value is available, it outputs the most recent value stored in shared memory.

Refer to the RT-LAB Connectivity chapter, section **RT-LAB Asynchronous process**, in the **User Guide** for details.

## Mask parameters

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

<table><thead><tr><th width="275.81817626953125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Controller ID</strong></td><td>Specifies the controller ID that the OpAsyncRecv block will use.</td></tr><tr><td><strong>Receive ID</strong></td><td>Specifies the ID of this OpAsyncRecv block. The asynchronous program uses this ID as an identifier.</td></tr><tr><td><strong>Display parameters list</strong></td><td>Shows or hides the parameters listed below.</td></tr><tr><td><strong>Float parameter 1 .. 5</strong></td><td>Values entered here are available to the asynchronous application by calling the <code>OpalGetAsyncRecvParameters</code> function. These five values are placed in the <code>FloatParam</code> array of the <code>Opal_RecvAsyncParam</code> structure. Example:</td></tr></tbody></table>

## Inputs <a href="#inputs" id="inputs"></a>

<table><thead><tr><th width="169.45452880859375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Timeout</strong></td><td>Timeout value available to the asynchronous program via <em>OpalGetAsyncRecvIconTimeout</em>.</td></tr></tbody></table>

## Outputs <a href="#outputs" id="outputs"></a>

<table><thead><tr><th width="140.3636474609375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Error</strong></td><td>Reports error values set by the asynchronous program using <em>OpalSetAsyncSendIconError</em>.</td></tr><tr><td><strong>Status</strong></td><td>Indicates the reception status set by the asynchronous program using <em>OpalSetAsyncRecvIconStatus</em>.</td></tr><tr><td><strong>Data</strong></td><td>Contains values written to shared memory by the asynchronous program. Use a demux block to separate multiple received values.</td></tr></tbody></table>

## Characteristics and limitations <a href="#characteristics-and-limitations" id="characteristics-and-limitations"></a>

| Characteristic       | Value                  |
| -------------------- | ---------------------- |
| Direct Feedthrough   | N/A                    |
| Discrete sample time | No                     |
| XHP support          | Yes (Partial XHP only) |
| 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/opasyncrecv.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.
