> 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/tcp-and-udp/review-the-driver-connectable-points.md).

# Review the Driver Connectable Points

The driver’s connectable points enable the driver to exchange data with the model. **Once** the driver is configured, these connectable points are exposed.

Exposed connectable points appear in **Dashboards > Interfaces > TCP-UDP**, under **Simulator Channel:**

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

Depending on the **connectable point** data **direction**, channels can be mapped to:

* an **OpOutput** block, to **send** data **from the model** to the driver during execution, or
* an **OpInput** block, to **receive and monitor** data from the driver **into the model** during execution

The Simulink model must then be adapted to create matching model connectable points. These points are then connected together using the **Dashboards** interface.

## Endpoints connection (TCP only)

When the stream is configured to use **TCP**, an additional **Connected** connectable point becomes available.

<table><thead><tr><th width="135">Connectable name</th><th>Description</th><th width="115">Direction</th><th width="210">Exposure condition</th></tr></thead><tbody><tr><td><strong>Connected</strong></td><td>Indicates whether the local endpoint is currently connected to the remote endpoint.<br><code>0</code> = Not connected<br><code>1</code> = Connected</td><td>To model<br></td><td>Exposed when <strong>protoco</strong>l is set to <strong>TCP</strong> in the <strong>TCP-UDP interface</strong> configuration.</td></tr></tbody></table>

## Data signals

The number and names of data signal connectable points depend on the streams configuration. **Each configured data signal is exposed as a separate connectable point, using the signal name defined in the TCP-UDP interface.**

<table><thead><tr><th width="175">Connectable name</th><th>Description</th><th>Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;Signal name></strong></td><td>Data for the configured signal; type and size depend on the configuration.</td><td>To model (receive)<br>From model (transmit)</td><td>Always exposed.</td></tr></tbody></table>

## Control and metric

<table><thead><tr><th width="135">Connectable name</th><th width="295">Description</th><th width="125">Direction</th><th width="200">Exposure condition</th></tr></thead><tbody><tr><td><strong>Reception enable</strong></td><td>Enables the endpoint to forward received data to the model or panel when set to <code>1</code>, and disables forwarding when set to <code>0</code>. <strong>Defaults to <code>0</code> when not connected.</strong></td><td>From model</td><td>Exposed when <strong>Enable reception control</strong> is <strong>checked</strong> in the <strong>TCP-UDP interface</strong> configuration.</td></tr><tr><td><strong>Transmission enable</strong></td><td>Enables the endpoint to transmit data to its socket when set to <code>1</code>, and disables transmission when set to <code>0</code>. <strong>Defaults to <code>0</code> when not connected.</strong></td><td>From model</td><td>Exposed when <strong>Enable transmission control</strong> is <strong>checked</strong> in the <strong>TCP-UDP interface</strong> configuration.</td></tr><tr><td><strong>Transmitted bytes</strong></td><td>A stream-level counter indicating the cumulative number of bytes transmitted through the socket by this stream.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Received bytes</strong></td><td>A stream-level counter indicating the cumulative number of bytes received through the socket by this stream.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>


---

# 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/tcp-and-udp/review-the-driver-connectable-points.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.
