> 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/pe-add-on-simulink/hardware-configurations-reference/pxie-7868r/ehsx32_dual_pmsm_vdq_io_32do_7868r/pin-assignment.md).

# Pin Assignment

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FycOlIhDLJdbKzDuvZC1E%2Fimage.png?alt=media&amp;token=1e3daa44-d22d-421a-9ac0-242fd1e33fc1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: The I/O channel names in this Hardware Configuration were updated in version 1.15.0 of the Power Electronics Add-On.
{% endhint %}

## Digital Inputs

| VeriStand Name | Pin Name   |
| -------------- | ---------- |
| Conn1.DIO0     | RDIO DIO0  |
| Conn1.DIO1     | RDIO DIO1  |
| Conn1.DIO2     | RDIO DIO2  |
| Conn1.DIO3     | RDIO DIO3  |
| Conn1.DIO4     | RDIO DIO4  |
| Conn1.DIO5     | RDIO DIO5  |
| Conn1.DIO6     | RDIO DIO6  |
| Conn1.DIO7     | RDIO DIO7  |
| Conn1.DIO8     | RDIO DIO8  |
| Conn1.DIO9     | RDIO DIO9  |
| Conn1.DIO10    | RDIO DIO10 |
| Conn1.DIO11    | RDIO DIO11 |
| Conn1.DIO12    | RDIO DIO12 |
| Conn1.DIO13    | RDIO DIO13 |
| Conn1.DIO14    | RDIO DIO14 |
| Conn1.DIO15    | RDIO DIO15 |

## Digital Outputs

| VeriStand Name | Pin Name   |
| -------------- | ---------- |
| Conn0.DIO0     | RMIO DIO0  |
| Conn0.DIO1     | RMIO DIO1  |
| Conn0.DIO2     | RMIO DIO2  |
| Conn0.DIO3     | RMIO DIO3  |
| Conn0.DIO4     | RMIO DIO4  |
| Conn0.DIO5     | RMIO DIO5  |
| Conn0.DIO6     | RMIO DIO6  |
| Conn0.DIO7     | RMIO DIO7  |
| Conn0.DIO8     | RMIO DIO8  |
| Conn0.DIO9     | RMIO DIO9  |
| Conn0.DIO10    | RMIO DIO10 |
| Conn0.DIO11    | RMIO DIO11 |
| Conn0.DIO12    | RMIO DIO12 |
| Conn0.DIO13    | RMIO DIO13 |
| Conn0.DIO14    | RMIO DIO14 |
| Conn0.DIO15    | RMIO DIO15 |
| Conn1.DIO16    | RDIO DIO16 |
| Conn1.DIO17    | RDIO DIO17 |
| Conn1.DIO18    | RDIO DIO18 |
| Conn1.DIO19    | RDIO DIO19 |
| Conn1.DIO20    | RDIO DIO20 |
| Conn1.DIO21    | RDIO DIO21 |
| Conn1.DIO22    | RDIO DIO22 |
| Conn1.DIO23    | RDIO DIO23 |
| Conn1.DIO24    | RDIO DIO24 |
| Conn1.DIO25    | RDIO DIO25 |
| Conn1.DIO26    | RDIO DIO26 |
| Conn1.DIO27    | RDIO DIO27 |
| Conn1.DIO28    | RDIO DIO28 |
| Conn1.DIO29    | RDIO DIO29 |
| Conn1.DIO30    | RDIO DIO30 |
| Conn1.DIO31    | RDIO DIO31 |

## Analog Inputs

| VeriStand Name | Pin Name |
| -------------- | -------- |
| Conn0.AI0      | RMIO AI0 |
| Conn0.AI1      | RMIO AI1 |
| Conn0.AI2      | RMIO AI2 |
| Conn0.AI3      | RMIO AI3 |
| Conn0.AI4      | RMIO AI4 |
| Conn0.AI5      | RMIO AI5 |

## Analog Outputs

| VeriStand Name | Pin Name |
| -------------- | -------- |
| Conn0.AO0      | RMIO AO0 |
| Conn0.AO1      | RMIO AO1 |
| Conn0.AO2      | RMIO AO2 |
| Conn0.AO3      | RMIO AO3 |
| Conn0.AO4      | RMIO AO4 |
| Conn0.AO5      | RMIO AO5 |
| Conn0.AO6      | RMIO AO6 |
| Conn0.AO7      | RMIO AO7 |
| Conn2.AO8      | RAO AO8  |
| Conn2.AO9      | RAO AO9  |
| Conn2.AO10     | RAO AO10 |
| Conn2.AO11     | RAO AO11 |
| Conn2.AO12     | RAO AO12 |
| Conn2.AO13     | RAO AO13 |
| Conn2.AO14     | RAO AO14 |
| Conn2.AO15     | RAO AO15 |
| Conn2.AO16     | RAO AO16 |
| Conn2.AO17     | RAO AO17 |


---

# 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/pe-add-on-simulink/hardware-configurations-reference/pxie-7868r/ehsx32_dual_pmsm_vdq_io_32do_7868r/pin-assignment.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.
