> 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_controller.md).

# Orchestra\_External\_Controller

## Description

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

The **Orchestra External Controller** block, located in the **RT-LAB/Orchestra/ExternalComponents** library, configures the connection between the current model and an RT-LAB Orchestra framework. This block is required in any Simulink model that exchanges data with an RT-LAB framework. Refer to the **RT-LAB Orchestra** chapter of the RT-LAB user guide 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-3d643bee7b284b9ece253d313760a6394f8cfd16%2FRTL_orchestra_ext_control_mask.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

<table><thead><tr><th width="250.5999755859375">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 current model and an RT-LAB framework.</td></tr><tr><td><strong>XML file</strong></td><td>Name of the file that describes the signals exchanged during the Orchestra co-simulation. Click <em>Configure</em> to start the <strong>DDF configurator</strong>.</td></tr><tr><td><strong>Domain name</strong></td><td>Domain name to use in the DDF.</td></tr><tr><td><strong>Connection type</strong></td><td>Select a local connection or an external connection using Reflective Memory cards.</td></tr><tr><td><strong>PCI Index</strong></td><td>Used with Reflective Memory cards only. If multiple identical cards are installed, select the PCI index of the card to use.</td></tr><tr><td><strong>Work in Simulink mode</strong></td><td>Enable or disable the connection to the RT-LAB Orchestra framework when running the model outside an RT-LAB Orchestra co-simulation.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="250.5999755859375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>State</strong></td><td>Connect (1) or disconnect (0) the model from the RT-LAB Orchestra framework.</td></tr></tbody></table>

## Outputs

<table><thead><tr><th width="250.5999755859375">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>Connection status with the RT-LAB Orchestra framework. The value is 0 if no External Component is connected to the framework; otherwise, the value is 1.</td></tr></tbody></table>

## Characteristics and limitations

| Characteristic       | 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_controller.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.
