> 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-opal-rt/hardware-configurations-reference/op4815/power-electronics-ioconfig3.md).

# Power Electronics - IOConfig3

## Specifications

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FfnwePPVMVtck8S7PWqfV%2Fimage.png?alt=media&amp;token=2b490564-9227-4d56-8132-e239d821cfe1" alt="" width="475"><figcaption></figcaption></figure>

### Bitstream signature <a href="#bitstream-signature" id="bitstream-signature"></a>

OP5145\_2-XXX-eHSx128\_Gen5\_PowerElectronics\_IOConfig3-XX-XX.pdi

## I/O capabilities

This configuration requires [**OP4815-IO**](https://www.opal-rt.com/docs/op4815-io) **FPGA boards**.

<figure><img src="https://1300141755-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCyfrFRdgX5VC5iwM13Zm%2Fuploads%2FrSEqAvqEbsG9zNdhrxVP%2Fimage.png?alt=media&amp;token=205c0d33-bc31-47a1-afb0-11ae76385249" alt=""><figcaption></figcaption></figure>

The configuration is equipped with two [**OP48H30 I/O modules**](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h30-description).

### Encoder output - PMSM solvers

Encoder outputs are sent to:

* Digital Out - RS422
* Digital Out - Slot 1 Connector P2

|       | Encoder 1  | Encoder 2  | Encoder 3                | Encoder 4                |
| ----- | ---------- | ---------- | ------------------------ | ------------------------ |
| **A** | RS422 Ch00 | RS422 Ch03 | Slot 1 Connector P2 Ch08 | Slot 1 Connector P2 Ch12 |
| **B** | RS422 Ch01 | RS422 Ch04 | Slot 1 Connector P2 Ch09 | Slot 1 Connector P2 Ch13 |
| **Z** | RS422 Ch02 | RS422 Ch05 | Slot 1 Connector P2 Ch10 | Slot 1 Connector P2 Ch14 |

### Encoder output - IM|SM solvers

Encoder outputs are sent to:

* Digital Out - Slot 1 Connector P2

|       | Encoder 1                | Encoder 2                | Encoder 3                | Encoder 4                |
| ----- | ------------------------ | ------------------------ | ------------------------ | ------------------------ |
| **A** | Slot 1 Connector P2 Ch16 | Slot 1 Connector P2 Ch20 | Slot 1 Connector P2 Ch24 | Slot 1 Connector P2 Ch28 |
| **B** | Slot 1 Connector P2 Ch17 | Slot 1 Connector P2 Ch21 | Slot 1 Connector P2 Ch25 | Slot 1 Connector P2 Ch29 |
| **Z** | Slot 1 Connector P2 Ch18 | Slot 1 Connector P2 Ch22 | Slot 1 Connector P2 Ch26 | Slot 1 Connector P2 Ch30 |

## Modeling capabilities

This configuration includes a pre-compiled firmware/bitfile which contains the following features:

* 1x eHSx128 GEN5 Solver
* 4x PMSM VDQ Solver
* 4x SCIM|DFIM|SPSM|RRSM Solver
* 64x Variable RL/RC
* 32x Sinewave Generators
* 32x PWM Generators

### PWM Generator Interface

| Names           | LoadIn Port Number | DataIn Port Number |
| --------------- | ------------------ | ------------------ |
| **PWM 00 - 07** | 11                 | 22                 |
| **PWM 08 - 15** | 12                 | 23                 |
| **PWM 16 - 23** | 13                 | 24                 |
| **PWM 24 - 31** | 14                 | 25                 |


---

# 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-opal-rt/hardware-configurations-reference/op4815/power-electronics-ioconfig3.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.
