> 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/pickering-driver/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 > Pickering**, 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-7af397a6c6bb0ad428cdfd0db377115b5c253b1e%2FDR-rtlab-pickering-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.

The set of available connectable points depends on the **card type selected**, as described in the following sections.

## Resistive card connectable points

| Connectable name | Description                                 | Direction  | Exposure condition |
| ---------------- | ------------------------------------------- | ---------- | ------------------ |
| **Channel**      | Resistive value programmed for the channel. | From model | Always exposed.    |
| **Status**       | Status of the resistive channel.            | To model   | Always exposed.    |

## FIU card connectable points

| Connectable name | Description                                                    | Direction  | Exposure condition                            |
| ---------------- | -------------------------------------------------------------- | ---------- | --------------------------------------------- |
| **Channel**      | FIU value when the channel type is **Channel**.                | From model | Exposed when channel **Type** is **Channel**. |
| **Fault**        | FIU value when the channel type is **Fault**.                  | From model | Exposed when channel **Type** is **Fault**.   |
| **Monitor**      | FIU value when the channel type is **Monitor**.                | From model | Exposed when channel **Type** is **Monitor**. |
| **Enable**       | Enables channel updates when set to `1`. Default value is `0`. | From model | Always exposed.                               |
| **Reset**        | Resets all channels to `0` when set to `1`.                    | From model | Always exposed.                               |
| **Status**       | Status of the FIU card.                                        | To model   | Always exposed.                               |

{% hint style="info" %}
Depending on how channels and faults are wired, enabling two faults on separate fault buses may result in a **short circuit between fault buses**. In this case, a *“Short Fault Bus”* action is applied to every enabled fault for each affected channel.
{% endhint %}

## Relay card connectable points

| Connectable name | Description                        | Direction  | Exposure condition |
| ---------------- | ---------------------------------- | ---------- | ------------------ |
| **Channel**      | Relay channel value (open/closed). | From model | Always exposed.    |
| **Status**       | Status of the relay card.          | To model   | Always exposed.    |

## Battery simulator card connectable points

| Connectable name     | Description                                                                      | Direction  | Exposure condition |
| -------------------- | -------------------------------------------------------------------------------- | ---------- | ------------------ |
| **Voltage**          | Voltage value programmed for the channel.                                        | From model | Always exposed.    |
| **Current**          | Current value programmed for the channel.                                        | From model | Always exposed.    |
| **Enable**           | Enables channel updates when set to `1`. Default value is `0`.                   | From model | Always exposed.    |
| **Error**            | Channel‑level error code. See the **battery simulator error codes** table below. | To model   | Always exposed.    |
| **Board error**      | Error reported at the board level.                                               | To model   | Always exposed.    |
| **Interlock status** | Interlock status (`0` = success; non‑zero = error code).                         | To model   | Always exposed.    |

### Battery simulator error codes

<table><thead><tr><th width="155">Error code</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>OK</td></tr><tr><td>1</td><td>No Pickering card has the specified card number</td></tr><tr><td>2</td><td>Cannot obtain information for the card</td></tr><tr><td>3</td><td>Card is disabled</td></tr><tr><td>4</td><td>Subunit value out of range for card</td></tr><tr><td>5</td><td>Bit number out of range for target sub‑unit</td></tr><tr><td>6</td><td>Target sub‑unit has no calibration data to read/write</td></tr><tr><td>7</td><td>SafeArray type, shape, or size is incorrect</td></tr><tr><td>8</td><td>Non‑zero write data value is illegal for MUX subunit</td></tr><tr><td>9</td><td>Execution would cause the closure limit to be exceeded</td></tr><tr><td>10</td><td>One or more specified channels cannot be masked</td></tr><tr><td>11</td><td>Cannot activate an output that is masked</td></tr><tr><td>12</td><td>Cannot open a Pickering card at the specified location</td></tr><tr><td>13</td><td>Failed to read from hardware</td></tr><tr><td>14</td><td>Failed to write to hardware</td></tr><tr><td>15</td><td>Hardware driver failure</td></tr><tr><td>16</td><td>Incompatible hardware driver version</td></tr><tr><td>17</td><td>Function call incompatible with sub‑unit type or capabilities</td></tr><tr><td>18</td><td>Matrix row value out of range</td></tr><tr><td>19</td><td>Matrix column value out of range</td></tr><tr><td>20</td><td>Attenuation value out of range</td></tr><tr><td>21</td><td>Voltage value out of range</td></tr><tr><td>22</td><td>Calibration index value out of range</td></tr><tr><td>23</td><td>Segment number out of range</td></tr><tr><td>24</td><td>Function code value out of range</td></tr><tr><td>25</td><td>Sub‑switch value out of range</td></tr><tr><td>26</td><td>Action code out of range</td></tr><tr><td>27</td><td>Cannot execute due to corrupt subunit state</td></tr><tr><td>28</td><td>Unrecognized attribute code</td></tr><tr><td>29</td><td>Timeout writing to EEPROM</td></tr><tr><td>30</td><td>Operation illegal in current subunit state</td></tr><tr><td>31</td><td>Unrecognized port number requested</td></tr><tr><td>32</td><td>Invalid write pattern for MATRIXR sub‑unit</td></tr><tr><td>33</td><td>Attempted operation on non‑existent channel</td></tr><tr><td>34</td><td>Card cannot be accessed (failed, removed, or unpowered)</td></tr><tr><td>35</td><td>Unsupported internal floating‑point format</td></tr><tr><td>36</td><td>Subunit not calibrated</td></tr><tr><td>37</td><td>Unobtainable resistance value</td></tr><tr><td>38</td><td>Invalid calibration store number</td></tr><tr><td>39</td><td>Invalid mode value</td></tr><tr><td>40</td><td>Conflicting device settings</td></tr><tr><td>41</td><td>Function call incompatible with card type or capabilities</td></tr><tr><td>42</td><td>Switch pole value out of range</td></tr><tr><td>43</td><td>Attempted activation of a non‑existent capability</td></tr><tr><td>44</td><td>Operation requires hardware that is not present</td></tr><tr><td>45</td><td>Faulty hardware</td></tr><tr><td>46</td><td>Failed to execute due to hardware condition</td></tr><tr><td>47</td><td>Current value out of range</td></tr><tr><td>48</td><td>Invalid range value</td></tr><tr><td>49</td><td>Attribute not supported</td></tr><tr><td>50</td><td>Register number out of range</td></tr><tr><td>51</td><td>Invalid channel closure or write pattern for MATRIXP sub‑unit</td></tr><tr><td>52</td><td>Data buffer too small</td></tr><tr><td>53</td><td>Inconsistent shared access mode</td></tr></tbody></table>

{% hint style="info" %}
Not all error codes apply to the **Pickering 41‑752 Battery Simulator** card.
{% endhint %}


---

# 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/pickering-driver/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.
