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

# Orchestra\_External\_Publish

## Description

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

The **Orchestra External Publish** block, located in the **RT-LAB/Orchestra/ExternalComponents** library, publishes signals to an RT-LAB Orchestra framework as data items in a DDF domain. This block configures the list of items to publish. Refer to the **RT-LAB Orchestra** page 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-f58422f7796f069c5ab6d026304b6f4baaad8ce3%2Fimage.png?alt=media" alt="" width="299"><figcaption></figcaption></figure>

<table><thead><tr><th width="250.60003662109375">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>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 data items to publish to the RT-LAB Orchestra framework in the specified domain. Click <em>Select</em> 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="248.99993896484375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Published data items</strong></td><td>The number of inputs is dynamic. There is an input for each published data item.</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.</td></tr><tr><td><strong>ConnectOrder</strong></td><td>Connect this output to the input “ConnectOrder” of the Subscribe block to force the execution order between these blocks. In this case, the Publish block is executed before the Subscribe block. No useful value is set on this output.</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_publish.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.
