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

# Orchestra\_Proxy\_C

## Description

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

The **Orchestra\_Proxy\_C** block, located in the **RT-LAB/Orchestra/Proxy** library, allows data exchange between the RT-LAB Orchestra framework and C External Components. It acts as a bridge between the current model and External Components. Refer to the **RT-LAB Orchestra** page for more information.

{% hint style="info" %}
To synchronize multiple domains within the framework, you can use the ConnectionCount output of Proxy blocks with a NAND gate to control the wait-to-go input.
{% endhint %}

## 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>XML file</strong></td><td>Name of the file used to read data information. Click <em>Configure</em> to start the <strong>DDF Configurator</strong>.</td></tr><tr><td><strong>Sample time</strong></td><td>Block sample time. Determines the rate used to exchange data with the External Components.</td></tr><tr><td><strong>Domain name</strong></td><td>Domain name to use in the DDF.</td></tr><tr><td><strong>Work in Simulink mode</strong></td><td>Enables or disables the connection to the RT-LAB Orchestra framework when running the model outside an RT-LAB Orchestra co-simulation.</td></tr><tr><td><strong>Create Goto/From subsystems</strong></td><td>Creates the ‘Goto’ and ‘From’ blocks for all items described in the XML file under the FRAMEWORK_TO_CLIENT and CLIENT_TO_FRAMEWORK sections of the selected domain.</td></tr></tbody></table>

## Inputs

<table><thead><tr><th width="250.5999755859375">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Wait-to-go</strong></td><td>- Holds the start of publish/subscribe for the External Component until a falling edge.<br>- If the input is 1, the client is blocked; when it transitions to 0, it is unblocked.<br>- Leaving the input unconnected or set to a constant 0 starts publishing and subscribing upon connection (default behavior).<br>- Designed for synchronous mode, considering the domain name, to synchronize multiple domains to start together.</td></tr></tbody></table>

{% hint style="info" %}
If the wait-to-go input is used to synchronize RT-LAB based clients, disable the watchdog for the client models to prevent undesired simulation failures.
{% endhint %}

## Outputs

| Output                 | Description                                                                                                                                                                                                                                                                   |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ConnectionCount**    | <p>Number of External Components connected to the framework. In synchronous use, this output increments before blocking while waiting for the wait-to-go input.</p><p>Note: ConnectionCount is neither the number of active connections nor the number of attempted ones.</p> |
| **ConnectionIsActive** | Status of the connection with an External Component. The value is 0 if no External Component is connected to the framework; otherwise, the value is 1.                                                                                                                        |

## Characteristics and limitations

| Characteristic                  | Value                                                                                        |
| ------------------------------- | -------------------------------------------------------------------------------------------- |
| Direct Feedthrough              | Yes                                                                                          |
| Discrete sample time            | Yes                                                                                          |
| XHP support                     | Yes (Partial XHP only)                                                                       |
| Work offline                    | Yes                                                                                          |
| Synchronous mode considerations | Using the wait-to-go feature in synchronous mode may block the framework and cause overruns. |


---

# 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_proxy_c.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.
