> 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/can/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.

{% if space.vars.RTLAB } Exposed connectable points appear in **Dashboards > Interfaces > CAN**, 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-3cd53a34863d6133583b0114e0df42d6d83861be%2FDR-rtlab-can-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

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

### Control and metric

<table><thead><tr><th width="140">Connectable name</th><th width="295">Description</th><th width="100">Direction</th><th width="210">Exposure condition</th></tr></thead><tbody><tr><td><strong>Empty Receive Buffer</strong></td><td>Empties the software reception buffer of the channel when set to <code>1</code></td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Empty Transmit Buffer</strong></td><td>Empties the software transmission buffer of the channel when set to <code>1</code></td><td>From model</td><td>Always exposed.</td></tr><tr><td><strong>Enable Transmission</strong></td><td>Enables transmission on channel 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>Exposed when <strong>Enable transmission control</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-channel-s-settings">CAN interface configuration</a>.</td></tr><tr><td><strong>Enable Reception</strong></td><td>Enables reception on channel 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>Exposed when <strong>Enable reception control</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-channel-s-settings">CAN interface configuration</a>.</td></tr><tr><td><strong>Bus Load</strong></td><td>CAN bus utilization (percentage)</td><td>To model</td><td>Exposed when <strong>Monitor bus load</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-channel-s-settings">CAN interface configuration</a>.</td></tr></tbody></table>

### Status

All status connectable points for a channel are exposed only when **Monitor channel flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-channel-s-settings) for that channel.

<table><thead><tr><th width="135">Connectable name</th><th width="285">Description</th><th width="120">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>API Fail</strong></td><td>Indicates a hardware API error related to the channel (<code>1</code> = error)</td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>Tx Buffer Overflow</strong></td><td>Indicates overflow of the hardware transmission buffer (<code>1</code> = overflow)</td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr></tbody></table>

### Flags

All flag connectable points for a channel are exposed only when **Monitor channel flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-channel-s-settings) for that channel.

<table><thead><tr><th width="215">Connectable name</th><th width="210">Description</th><th width="110">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>STAT_ERROR_PASSIVE</strong></td><td>Bus is in error‑passive state when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_BUS_OFF</strong></td><td>Bus is in bus‑off state when <code>1</code>; no further transmission possible</td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_ERROR_WARNING</strong></td><td>At least one error counter exceeded warning threshold when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_ERROR_ACTIVE</strong></td><td>Bus is in error‑active state when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_TX_PENDING</strong></td><td>Messages are pending transmission when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_RX_PENDING</strong></td><td>Messages are present in the receive buffer when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_TXERR</strong></td><td>At least one transmission error detected when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_RXERR</strong></td><td>At least one reception error detected when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_HW_OVERRUN</strong></td><td>Hardware buffer overflow detected when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>STAT_SW_OVERRUN</strong></td><td>Software buffer overflow detected when <code>1</code></td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr></tbody></table>

{% hint style="info" %}
Error thresholds depend on the platform. Software buffers are temporary buffers managed by the driver, while hardware buffers reside on the CAN interface card.
{% endhint %}

### Error counters

All error counter connectable points for a channel are exposed only when **Monitor channel flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-channel-s-settings) for that channel.

<table><thead><tr><th width="130">Connectable name</th><th width="275">Description</th><th width="120">Direction</th><th width="220">Exposure condition</th></tr></thead><tbody><tr><td><strong>Tx Errors</strong></td><td>Current value of the transmission error counter</td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>Rx Errors</strong></td><td>Current value of the reception error counter</td><td>To model</td><td>When monitoring is enabled for the channel.</td></tr><tr><td><strong>Overflow Errors</strong></td><td>Current value of the overflow error counter</td><td>To model</td><td>When monitoring is enabled for the channel.</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** [**CAN interface**](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-can-messages)**.**

<table><thead><tr><th width="150">Connectable name</th><th width="280">Description</th><th width="120">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;signal name></strong></td><td>Signal value forming part of the transmitted message payload.</td><td>From model</td><td>Exposed for each data field configured in the transmission message.</td></tr></tbody></table>

### Control and metric

<table><thead><tr><th width="135">Connectable name</th><th width="230">Description</th><th width="115">Direction</th><th width="270">Exposure condition</th></tr></thead><tbody><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>Exposed for non‑cyclic transmission messages. For cyclic transmission messages, this connectable is exposed only when <strong>Force enable message</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-can-messages">CAN interface configuration</a>.</td></tr><tr><td><strong>Total Sent</strong></td><td>Total number of frames sent</td><td>To model</td><td>Exposed when <strong>Monitor message flags, error counters and statuses</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings">CAN interface configuration</a>.</td></tr><tr><td><strong>ID</strong></td><td>CAN identifier of the transmitted message</td><td>To model</td><td>Exposed when <strong>Monitor message flags, error counters and statuses</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings">CAN interface configuration</a>.</td></tr><tr><td><strong>Queue Count</strong></td><td>Transmission buffer utilization (percentage)</td><td>To model</td><td>Exposed when <strong>Monitor message flags, error counters and statuses</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings">CAN interface configuration</a>.</td></tr></tbody></table>

### Status

All status connectable points for all messages are exposed only when **Monitor message flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings).

<table><thead><tr><th width="135">Connectable name</th><th width="255">Description</th><th width="115">Direction</th><th width="245">Exposure condition</th></tr></thead><tbody><tr><td><strong>FIFO Full</strong></td><td>Software transmission buffer is full when <code>1</code></td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>API Fail</strong></td><td>Hardware API error related to the message when <code>1</code></td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>Tx Buffer Overflow</strong></td><td>Hardware transmission buffer overflow when <code>1</code></td><td>To model</td><td>When monitoring is enabled.</td></tr></tbody></table>

### Flags

All flag connectable points for all messages are exposed only when **Monitor message flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings).

<table><thead><tr><th width="135">Connectable name</th><th width="255">Description</th><th width="115">Direction</th><th width="235">Exposure condition</th></tr></thead><tbody><tr><td><strong>MSG_RTR</strong></td><td>Transmitted message is a Remote Transmission Request when set to <code>1</code></td><td>From model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_STD</strong></td><td>Forces the message ID to standard format when set to <code>1</code></td><td>From model</td><td>When monitoring is enabled.</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** [**CAN interface**](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-can-messages)**.**

<table><thead><tr><th width="150">Connectable name</th><th width="280">Description</th><th width="120">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>&#x3C;signal name></strong></td><td>Signal values forming part of the received message payload.</td><td>To model</td><td>Exposed for each data field configured in the reception message.</td></tr></tbody></table>

### Control and metrics

<table><thead><tr><th width="140">Connectable name</th><th width="215">Description</th><th width="115">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Enable Message</strong></td><td>Enables message reception 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>Valid Frame Count</strong></td><td>Number of valid frames received in the current time step</td><td>To model</td><td>Exposed when <strong>Monitor message flags, error counters and statuses</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings">CAN interface configuration</a>.</td></tr><tr><td><strong>Total Received</strong></td><td>Total number of frames received</td><td>To model</td><td>Exposed when <strong>Monitor message flags, error counters and statuses</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings">CAN interface configuration</a>.</td></tr><tr><td><strong>Queue Count</strong></td><td>Reception buffer utilization (percentage)</td><td>To model</td><td>Exposed when <strong>Monitor message flags, error counters and statuses</strong> is <strong>checked</strong> in the <a href="https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings">CAN interface configuration</a>.</td></tr></tbody></table>

### Buffered frame

*(Available for each buffered frame)*

<table><thead><tr><th width="150">Connectable name</th><th width="295">Description</th><th width="110">Direction</th><th width="190">Exposure condition</th></tr></thead><tbody><tr><td><strong>ID</strong></td><td>CAN identifier of the received frame</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Number of Bytes Received</strong></td><td>Number of bytes in the received frame</td><td>To model</td><td>Always exposed.</td></tr><tr><td><strong>Timestamp</strong></td><td>Reception timestamp in microseconds</td><td>To model</td><td>Always exposed.</td></tr></tbody></table>

### Status

All status connectable points for all messages are exposed only when **Monitor message flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings).

<table><thead><tr><th width="140">Connectable name</th><th width="245">Description</th><th width="115">Direction</th><th width="240">Exposure condition</th></tr></thead><tbody><tr><td><strong>FIFO Full</strong></td><td>Software reception buffer is full</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>API Fail</strong></td><td>Hardware API error related to the message</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>No Message</strong></td><td>No message received during the time step</td><td>To model</td><td>When monitoring is enabled.</td></tr></tbody></table>

### Flags

All flag connectable points for all messages are exposed only when **Monitor message flags, error counters and statuses** is **checked** in the [CAN interface configuration](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/can/configure-can.md#configure-the-general-settings).

<table><thead><tr><th width="220">Connectable name</th><th width="255">Description</th><th width="110">Direction</th><th width="160">Exposure condition</th></tr></thead><tbody><tr><td><strong>MSG_RTR</strong></td><td>Received frame is a Remote Transmission Request</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_STD</strong></td><td>Received frame uses a standard ID</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_EXT</strong></td><td>Received frame uses an extended ID</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_WAKEUP</strong></td><td>Frame received in wakeup mode</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_NERR</strong></td><td>Bus wiring fault detected</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_ERROR_FRAME</strong></td><td>Received frame is an error frame</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_TXACK</strong></td><td>Frame is a transmit acknowledge</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_TXRQ</strong></td><td>Frame is a transmit request</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSG_DELAY_MSG</strong></td><td>Transmission delayed; frame not sent</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_HW_OVERRUN</strong></td><td>Hardware buffer overrun detected</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_SW_OVERRUN</strong></td><td>Software buffer overrun detected</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_STUFF</strong></td><td>Bit stuffing error detected</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_FORM</strong></td><td>Frame format error detected</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_CRC</strong></td><td>CRC error detected</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_BIT0</strong></td><td>Dominant bit transmission error</td><td>To model</td><td>When monitoring is enabled.</td></tr><tr><td><strong>MSGERR_BIT1</strong></td><td>Recessive bit transmission error</td><td>To model</td><td>When monitoring is enabled.</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/can/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.
