> 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/arinc429/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 > ARINC429**, 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-e66358857fbe3407284a0f22aa1f97e2581c15d1%2FDR-rtlab-arinc-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.

## Channel‑level connectable points

### Tx channels

These connectable points apply to an entire **Tx channel** and provide status and diagnostic information related to channel operation.

<table><thead><tr><th width="140">Connectable name</th><th width="330">Description</th><th width="120">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Buffer Count</strong></td><td>Number of buffered items currently available in the board’s physical buffer for the channel.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Tx Buffer Overflow</strong></td><td>Indicates a buffer overflow condition for the channel.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Tx Errors</strong></td><td>Number of errors flagged by the channel.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Enable</strong></td><td>Enables channel transmission when set to <code>1</code> and disables it when set to <code>0</code>. <strong>Defaults to <code>1</code> when not connected.</strong></td><td>From model</td><td>Always exposed.</td></tr></tbody></table>

### Rx channels

These connectable points apply to an entire **Rx channel** and provide status and diagnostic information related to channel operation.

<table><thead><tr><th width="135">Connectable name</th><th width="345">Description</th><th width="115">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Bad Message Count</strong></td><td>Counter indicating the number of badly formed messages received on the channel.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Buffer Count</strong></td><td>Number of buffered items currently available in the board’s physical buffer for the channel.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Rx Buffer Overflow</strong></td><td>Indicates a buffer overflow condition for the channel.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Rx Errors</strong></td><td>Number of errors flagged by the channel.</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

## Message‑level connectable points

### Transmission messages

### Data signals

The number and names of data signal connectable points for a transmission message depend on the message configuration. **Each configured data signal is exposed as a separate connectable point, using the signal name defined in the** [**ARINC429 interface**](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md#configure-messages)**.**

<table><thead><tr><th width="135">Connectable name</th><th width="280">Description</th><th width="115">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;signal name></strong></td><td>Data field value associated with the transmission message.</td><td>From model</td><td>Exposed for each data field configured in the transmission message.</td></tr></tbody></table>

### Control and monitoring

These connectable points apply to individual transmission messages and allow the model to control message transmission and monitor transmission status.

<table><thead><tr><th width="130">Connectable name</th><th width="275">Description</th><th width="125">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Total Sent</strong></td><td>Total number of messages of this type that have been sent.</td><td>To model</td><td>Exposed only for <strong>non‑cyclic</strong> transmission messages.</td></tr><tr><td><strong>Enable Message</strong></td><td>Enables message transmission when set to <code>1</code> and disables it when set to <code>0</code>. <strong>Defaults to <code>0</code> when not connected.</strong></td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Raw ARINC Word</strong></td><td>Raw ARINC Word used for the message.</td><td>From model</td><td>Exposed when <strong>Enable raw data</strong> is <strong>checked</strong> for the message in <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md">ARINC429 interface configuration</a>.</td></tr><tr><td><strong>SDI</strong></td><td>SDI value used for message transmission.</td><td>From model</td><td>Exposed when <strong>Enable dynamic SDI</strong> is <strong>checked</strong> for the message in <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md">ARINC429 interface configuration</a>.</td></tr><tr><td><strong>SSM</strong></td><td>SSM value used for message transmission.</td><td>From model</td><td>Exposed when <strong>Enable dynamic SSM</strong> is <strong>checked</strong> for the message in <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md">ARINC429 interface configuration</a>.</td></tr></tbody></table>

### Reception messages

### Data signals

The number and names of data signal connectable points for a reception message depend on the message configuration. **Each configured data signal is exposed as a separate connectable point, using the signal name defined in the** [**ARINC429 interface**](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md#configure-messages)**.**

<table><thead><tr><th width="145">Connectable name</th><th width="285">Description</th><th width="110">Direction</th><th width="200">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;signal name></strong></td><td>Data field value extracted from the received message.</td><td>To model</td><td>Exposed for each data field configured in the reception message.</td></tr></tbody></table>

### Status and information

These connectable points apply to individual **reception messages** and provide extra status and timing information.

<table><thead><tr><th width="140">Connectable name</th><th width="290">Description</th><th width="110">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Total Received</strong></td><td>Total number of messages of this type that have been received.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Timestamp</strong></td><td>Timestamp associated with the received message.</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Message Timeout</strong></td><td>Shows <code>1</code> when the timeout threshold between two consecutive messages is exceeded.</td><td>To model</td><td>Exposed when <strong>Enable timeout monitoring</strong> is <strong>checked</strong> for the message in <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md">ARINC429 interface configuration</a>.</td></tr><tr><td><strong>Raw ARINC Word</strong></td><td>Raw ARINC Word received.</td><td>To model</td><td>Exposed when <strong>Enable raw data</strong> is <strong>checked</strong> for the message in <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/arinc429/configure-arinc429.md">ARINC429 interface configuration</a>.</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/arinc429/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.
