> 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/configure-ios/communication-protocol-ios/c37.118-slave/map-model-signals-to-io-interface.md).

# Map Model Signals to I/O Interface

{% hint style="info" %}
Note that the communication‑protocol driver **connectable points** configured in the RT‑LAB **I/O Interfaces** are exposed as **Simulator Channels** in the **Dashboards** interface.
{% endhint %}

{% stepper %}
{% step %}

### Open Dashboards

In the RT-LAB Project Explorer, double-click **Dashboards** within your current project.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-33e4d7a7ee2b6c509e5c302468e3b292af0659f9%2FDR-open-dashboards.png?alt=media" alt="" width="183"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Review all exposed connectable points

In the **Dashboards** interface, navigate to **Interfaces** and select the communication‑protocol I/O interface created in RT‑LAB to view all exposed **connectable points**. These points are listed under **Simulator Channel**.

{% hint style="info" %}
The **Simulator Channel** list in **Dashboards** is automatically updated whenever changes are made to the Interface configuration in RT-LAB.
{% endhint %}
{% endstep %}

{% step %}

### Connect a model signal to a connectable point

To connect a model signal to a connectable point, click the **+** icon next to the desired connectable point and double-click the desired signal from the model. Use the search function to quickly find and select the desired model signal. Once connected, the link will appear at the bottom of the window and as a link icon under the **Connection** column. Repeat for all desired connections.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-db52dc361e07ae1f3f5587cf06d73d921f9e9374%2FDR-connection_driver.gif?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Connect a model’s signal vector to a connectable point vector

You can sometimes connect a model’s signal vector to a connectable point vector. To do this, click the **\[+]** icon next to the desired connectable point vector, then double-click the model’s signal vector. Use the search function to quickly find and select the desired signals.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-b24661d1897d11705bb289fc1322db532c27e7f4%2FDR-connection_driver_vector.gif?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Manage connections: view or delete <a href="#manage-connections-delete-deactivate-or-reactivate" id="manage-connections-delete-deactivate-or-reactivate"></a>

To **delete a connection**, hover over the connection until the **trash icon** appears, then click it.

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

To **view all existing connections**, click **Connections** in the navigation menu. This opens a complete list of connections for easy review and management. The list includes not only connections between model signals and channels, but also connections between model signals and Dashboard panel widgets.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-23a2893b30859e12f66240bd9dcb8147edaaac38%2FDR-dashboards-connections-1.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Load and execute the model

You can load and execute the model directly from **Dashboards**.

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

Alternatively, you can return to RT-LAB to load and execute the model.
{% endstep %}
{% endstepper %}


---

# 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/configure-ios/communication-protocol-ios/c37.118-slave/map-model-signals-to-io-interface.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.
