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

# Orchestra\_External\_Subscribe

## Description

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

The **Orchestra External Subscribe** block, located in the **RT-LAB/Orchestra/ExternalComponents** library, subscribes to data items from an RT-LAB Orchestra framework within a specified DDF domain. Refer to the **RT-LAB Orchestra** page for more information.

## Mask parameters

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

<table><thead><tr><th width="249.79998779296875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Sample time</strong></td><td>Block sample time. Determines the data exchange rate between the model and the RT-LAB Orchestra framework.</td></tr><tr><td><strong>Domain name</strong></td><td>Domain name to use in the DDF.</td></tr><tr><td><strong>Item names(s)</strong></td><td>List of items to subscribe from the RT-LAB Orchestra framework in the specified domain. Click on the <em>Select</em> button to start the <strong>DDF Configurator</strong> and select the data items in the specified domain.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="251.39996337890625">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>ConnectOrder</strong></td><td>Connect this input to the output “ConnectOrder” of the Publish block to enforce the execution order between these blocks. In this case, the Publish block executes before the Subscribe block. No useful value is read from this input.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="249.79998779296875">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>Status of the connection with the RT-LAB Orchestra framework. The value is 0 if there is no External Component connected to the framework; otherwise, the value is 1. The number of outputs is dynamic. There is one output for each data item subscribed from the domain, as selected in the DDF.</td></tr></tbody></table>

## Characteristics and limitations

| Property             | Value                  |
| -------------------- | ---------------------- |
| Direct Feedthrough   | Yes                    |
| Discrete sample time | Yes                    |
| XHP support          | Yes (Partial XHP only) |
| Work offline         | Yes                    |


---

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