> 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/diane-rtdp/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 > DIANE**, under **Simulator Channel**.

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.

## Status connectable point

<table><thead><tr><th width="135">Connectable name</th><th width="325">Description</th><th width="135">Direction</th><th width="150">Exposure condition</th></tr></thead><tbody><tr><td><strong>HPF_10s</strong></td><td>Timestamp of the message with a resolution of <strong>10 seconds</strong>.</td><td>To model (Receiver)<br>From model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>HPF_ms</strong></td><td>Timestamp of the message with a resolution of <strong>milliseconds</strong>.</td><td>To model (Receiver)<br>From model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>HHR_us</strong></td><td>Timestamp of the message with a resolution of <strong>microseconds</strong>.</td><td>To model (Receiver)<br>From model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>Disable transmission</strong></td><td>Disables message transmission for this group when set to <code>1</code>. When set to <code>0</code>, transmission is enabled. <strong>Defaults to disabled transmission if not connected.</strong> If set to <code>1</code> during a timestep, the data for that timestep is not sent. This connectable can be used to reduce the effective transmission rate of a message group.</td><td>From model (Transmitter)</td><td>Always exposed.</td></tr></tbody></table>

## Box level connectable points

The following connectable points are exposed **for each configured box**.

<table><thead><tr><th width="150">Connectable name</th><th width="310">Description</th><th width="130">Direction</th><th width="155">Exposure condition</th></tr></thead><tbody><tr><td><strong>Time</strong></td><td>Timestamp associated with the DIANE datagram.</td><td>To model (Receiver)<br>From model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>Synchronized</strong></td><td>Indicates producer synchronization status:<br><code>0</code> – Producer is synchronized<br><code>1</code> – Producer is not synchronized.<br>This connectable corresponds to <strong>bit 0</strong> of the datagram status field.</td><td>To model (Receiver)<br>From model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>Saturated</strong></td><td>Indicates transmitter saturation state:<br><code>0</code> – Producer is saturated (risk of data loss)<br><code>1</code> – Producer is not saturated.<br>Increasing the <strong>Inter‑process FIFO depth</strong> for the transmitter may help mitigate saturation. This connectable corresponds to <strong>bit 1</strong> of the datagram status field.</td><td>To model (Receiver)<br>To model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>Timeout</strong></td><td>Indicates a transmission timeout condition:<br><code>0</code> – No timeout occurred<br><code>1</code> – Timeout occurred during data transmission.<br>This connectable corresponds to <strong>bit 6</strong> of the datagram status field.</td><td>To model (Receiver)<br>To model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>Sequence number</strong></td><td>Sequence number associated with the datagram block.</td><td>To model (Receiver)<br>From model (Transmitter)</td><td>Always exposed.</td></tr><tr><td><strong>Number of blocks sent</strong></td><td>Total number of times the datagram block has been transmitted.</td><td>To model (Transmitter)</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/diane-rtdp/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.
