> 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/ehs/3.7/first-steps/choose-the-ehs-firmware/introduction-to-standard-ehs-firmware/op4815-io/ehsx128-gen5-hscs-ioconfig1.md).

# Power Electronics HSCS IOConfig1

## Firmware specifications

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-23d4e4ba6ec49e0ff6954484b0879aaaeb8baccf%2FOP4815_eHS128_gen5_PMSM_ioconf1.png?alt=media" alt="" width="480"><figcaption></figcaption></figure>

* Compatible with Schematic Editor workflow
* Compatible with XG and XG2 platforms
* Solver eHS x128 Gen5
* 2 High Speed Converter Solvers x256
* SFP inter-FPGA link
* FPGA Scope

## FPGA ports mapping table

<details>

<summary><strong>I/O mapping details table</strong></summary>

| Port number | LoadIn                      | DataIn                        | DataOut                 |
| ----------- | --------------------------- | ----------------------------- | ----------------------- |
| 1           | Config eHS                  | Inputs eHS                    | eHS Averaged            |
| 2           | Scenario / Rst eHS = Status | TSDO 1 - eHS 0 to 7           | eHS DownSample          |
| 3           |                             | TSDO 2 - eHS 8 to 15          | Digital In 1 - 0 to 7   |
| 4           | PWM 1 - 0 to 7              | TSDO 3 - eHS 16 to 23         | Digital In 1 - 8 to 15  |
| 5           | PWM 1 - 8 to 15             | TSDO 4 - eHS 24 to 31         | Digital In 1 - 16 to 23 |
| 6           | PWM 1 - 16 to 23            | TSDO 5 - eHS 32 to 39         | Digital In 1 - 24 to 31 |
| 7           | PWM 1 - 24 to 31            | TSDO 6 - eHS 40 to 47         | Digital In 2 - 0 to 7   |
| 8           | PWM 2 - 0 to 7              | TSDO 7 - eHS 48 to 55         | Digital In 2 - 8 to 15  |
| 9           | PWM 2 - 8 to 15             | TSDO 8 - eHS 56 to 63         | Digital In 2 - 16 to 23 |
| 10          | PWM 2 - 16 to 23            |                               | Digital In 2 - 24 to 31 |
| 11          | PWM 2 - 24 to 31            | Digital Out 1A - SDO 0 to 7   | Analog In 1 - 0 to 7    |
| 12          | Config AOMR                 | Digital Out 1A - SDO 8 to 15  | Analog In 1 - 8 to 15   |
| 13          | eHS PWM 1 - eHS 0 to 7      | Digital Out 1A - SDO 16 to 23 | HSCS DataOut 1          |
| 14          | eHS PWM 2 - eHS 8 to 15     | Digital Out 1A - SDO 24 to 31 | HSCS Downsampled 1      |
| 15          | eHS PWM 3 - eHS 16 to 23    | Digital Out 2A - SDO 0 to 7   | HSCS DataOut 2          |
| 16          | eHS PWM 4 - eHS 24 to 31    | Digital Out 2A - SDO 8 to 15  | HSCS Downsampled 2      |
| 17          | Config AIR                  | Digital Out 2A - SDO 16 to 23 |                         |
| 18          | HSCS1 Config                | Digital Out 2A - SDO 24 to 31 |                         |
| 19          |                             | AOMR/Analog Out 1 - 0 to 7    |                         |
| 20          | HSCS2 Config                | Analog Out 1 - 8 to 15        |                         |
| 21          |                             | Analog Out 2 - 0 to 7         |                         |
| 22          | Config SFP1                 | Analog Out 2 - 8 to 15        |                         |
| 23          |                             | eHS PWM 1 - 0 to 7            |                         |
| 24          | Config SFP2                 | eHS PWM 2 - 8 to 15           |                         |
| 25          |                             | eHS PWM 3 - 16 to 23          |                         |
| 26          |                             | eHS PWM 4 - 24 to 31          |                         |
| 27          |                             | eHS SWG                       |                         |
| 28          | Reset HSCS1                 |                               |                         |
| 29          | PWM4 - 0 to 7               |                               |                         |
| 30          | PWM4 - 8 to 15              |                               |                         |
| 31          | PWM4 - 16 to 23             | SFP 4                         |                         |
| 32          | PWM4 - 24 to 31             |                               |                         |
| 33          | Reset HSCS2                 |                               |                         |
| 34          |                             |                               |                         |
| 35          |                             |                               |                         |
| 36          |                             |                               |                         |
| 37          |                             |                               |                         |
| 38          |                             |                               |                         |
| 39          |                             | SFP 5                         |                         |

</details>

## Supported I/O modules

### IOConfig1

| I/O section | Slot 1                                                                                                                               | Slot 2                                                                                                                               |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Module**  | <p><a href="https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description">OP48H10</a><br>Fast I/O type H Module</p> | <p><a href="https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description">OP48H10</a><br>Fast I/O type H Module</p> |
| **P1**      | 16 DIO                                                                                                                               | 32 DIO                                                                                                                               |
| **P2**      | 16 DIO                                                                                                                               | 32 DIO                                                                                                                               |
| **P3**      | 16 AO                                                                                                                                | 16 AO                                                                                                                                |
| **P4**      | 16 AI                                                                                                                                | 16 AI - N/A in eHS                                                                                                                   |

The configuration includes **6 TX and 6 RX RS‑422 digital I/O channels** accessible via **DB9 connectors**. These are mapped to **Slot 3**, managed by the [OP5969‑1 RS‑422 I/O module.](https://www.opal-rt.com/docs/pcie-cards-and-connector-kits/connector-kits/op5969-1-rs-422-i-o-module)

## I/O module mapping and configuration (RT-LAB)

This section applies when using the **recommended S‑Function workflow** in **RT‑LAB**.

For I/O module mapping and configuration when using the **OPAL‑RT Board workflow**, refer to **I/O module mapping and configuration (HYPERSIM)**. The information provided there is also applicable when working with RT‑LAB.

### OpCtrl block configuration

Reference: [**OpCtrl**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/opctrl) block in RT-LAB

| Parameter                      | Value                                                                               |
| ------------------------------ | ----------------------------------------------------------------------------------- |
| **Primary Bitstream FileName** | OP5145\_2-EX-0001-3\_13\_1\_36-eHSx128Gen5\_HSCS\_PowerElectronics\_IOConfig1-FD-11 |
| **Board Type**                 | OP48xx                                                                              |

### Slot 1 and Slot 2 - Digital inputs/outputs

Refer to [OP48H10 pin assignment](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description/db37f-pin-assignment) for hardware connections.

Each **OP48H10** includes a **32‑channel digital I/O** module divided into four **8‑channel subsections**, each of which can be independently configured as either a digital input or a digital output.

#### **Schematic Editor digital inputs/outputs configuration**

Electric circuit **switch blocks** are directly mapped to the module’s **digital inputs** in Schematic Editor by selecting the block and assigning the desired module channel(s) as gate signal source(s).

Electric circuit **machine blocks** can have their **encoder outputs** mapped to the module's **digital outputs** in the Schematic Editor. However, the user does not select specific module channels; instead, encoder must be enabled for the machine, after which the encoder signals are automatically mapped to either **Slot 1A** or **RS422 Slot 3**. Open the **eHS Build Report** to determine the slot used.

#### Mezzanine Option block configuration

To configure a subsection for digital output on one OP48H10 - Fast I/O type H module, utilize the [**Mezzanine Option**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/mezzanine-option) block and set set the subsection direction to **Output**. When set to Output, the **Voltage** parameter becomes available for that subsection and can be set to **3.3 V** or **5 V**. To configure a subsection for digital input, set the subsection direction to **Input**.

**Mezzanine Option block for slot 1**

| Parameter          | Value          |
| ------------------ | -------------- |
| **Mezzanine type** | OP48H10 - Fast |
| **Chassis slot**   | Slot 1         |

**Mezzanine Option block for slot 2**

| Parameter          | Value          |
| ------------------ | -------------- |
| **Mezzanine type** | OP48H10 - Fast |
| **Chassis slot**   | Slot 2         |

#### Digital Input blocks configuration

When using [**Digital In**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/digital-in), [**PWM In**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/pwm-in), or [**Event Detector**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/event-detector) blocks in the RT-LAB model, ensure you assign the correct **DataOut port number** to the channel group.

| Parameter                                                              | CH00-07 | CH08-15 | CH16-23 | CH24-31 |
| ---------------------------------------------------------------------- | :-----: | :-----: | :-----: | :-----: |
| <p><strong>Slot 1</strong><br><strong>DataOut port number</strong></p> |    3    |    4    |    5    |    6    |
| <p><strong>Slot 2</strong><br><strong>DataOut port number</strong></p> |    7    |    8    |    9    |    10   |

#### Digital Output block configuration

When using [**Digital Out**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/digital-out), [**PWM Out**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/pwm-out), or [**Event Generator**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/event-generator) blocks in the RT-LAB model, ensure you assign the correct **DataIn** **port number** to the channel group.

| Parameter                                                             | CH00-07 | CH08-15 | CH16-23 | CH24-31 |
| --------------------------------------------------------------------- | :-----: | :-----: | :-----: | :-----: |
| <p><strong>Slot 1</strong><br><strong>DataIn port number</strong></p> |    11   |    12   |    13   |    14   |
| <p><strong>Slot 2</strong><br><strong>DataIn port number</strong></p> |    15   |    16   |    17   |    18   |
| <p><strong>Slot 1</strong><br><strong>LoadIn port number</strong></p> |    4    |    5    |    6    |    7    |
| <p><strong>Slot 2</strong><br><strong>DataIn port number</strong></p> |    8    |    9    |    10   |    11   |

### Slot 1 and Slot 2- Analog outputs

Refer to [OP48H10 pin assignment](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description/db37f-pin-assignment) for hardware connections.

#### Schematic Editor analog outputs configuration

Electric circuit **measurement blocks** are directly mapped to the module's **analog outputs** in the Schematic Editor by selecting the block and assigning the desired module channel as the destination.

#### Analog Out block configuration

When using [**Analog Out**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/analog-out) blocks in the RT-LAB model, ensure you assign the correct **DataIn port number** to the channel group.

{% hint style="danger" %}
Mapping a single electric circuit measurement block to an analog output in Schematic Editor reserves all 16 channels for eHS, disabling Analog Out blocks in the RT‑LAB model.
{% endhint %}

| Parameter                                                             | CH00-07 | CH08-15 |
| --------------------------------------------------------------------- | ------- | ------- |
| <p><strong>Slot 1</strong><br><strong>DataIn Port Number</strong></p> | 19      | 20      |
| <p><strong>Slot 2</strong><br><strong>DataIn Port Number</strong></p> | 21      | 22      |

### Slot 1 and Slot 2- Analog inputs

Refer to [OP48H10 pin assignment](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description/db37f-pin-assignment) for hardware connections.

#### Schematic Editor analog inputs configuration

Electric circuit **sources blocks** are directly mapped to the module's **analog inputs** in the Schematic Editor by selecting the block and assigning the desired module channel as the source.

Electric circuit **machine blocks** can also have their **resolver excitation source** mapped to the module's **analog inputs** in the Schematic Editor by enabling the resolver for the machine block and assigning the desired module channel as the excitation source.

#### Analog In block configuration

When using [**Analog In**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/analog-in) blocks in the RT-LAB model, ensure you assign the correct **DataOut port number** to the channel group.​

| Parameter                                                              | CH00-07 | CH08-15 |
| ---------------------------------------------------------------------- | ------- | ------- |
| <p><strong>Slot 1</strong><br><strong>DataOut Port Number</strong></p> | 11      | 12      |
| <p><strong>Slot 2</strong><br><strong>DataOut Port Number</strong></p> | 18      | 19      |

### SFP module

#### Schematic Editor SFP configuration

Electric circuit **sources blocks** can be mapped to the module's **SFP CH04** **input** in the Schematic Editor by selecting the block and assigning the desired **SFP input signal** as the source. All SFP input signals are carried through a **single SFP channel (CH04)**, which provides **32 input signals**. All other SFP channels are disabled in this firmware.

Electric circuit **measurement blocks** can be mapped to the module's **SFP CH04** **output** in the Schematic Editor by selecting the block and assigning the desired **SFP output signal** as the destination. All SFP output signals are carried through a **single SFP channel (CH04)**, which provides **32 output signals**. All other SFP channels are disabled in this firmware.

#### DataIn Send block configuration

Signals from the RT‑LAB model can be sent to the SFP CH00 output a [**DataIn Send**](https://www.opal-rt.com/docs/rt-lab/simulink-blocks-reference/rt-lab-i-o-library/datain-send) block. Ensure you assign the correct **DataIn port number**.

{% hint style="danger" %}
Mapping a single electric circuit measurement block to an SFP output signal in Schematic Editor reserves all SFP output signals for eHS, disabling SFP output in the RT‑LAB model.
{% endhint %}

| Parameter              | SFP CH04 |
| ---------------------- | -------- |
| **DataIn Port Number** | 42       |
| **LoadIn Port Number** | 22       |

## I/O module mapping and configuration (HYPERSIM)

### OPAL-RT Board configuration

| Parameter                            | Value                                                                               |
| ------------------------------------ | ----------------------------------------------------------------------------------- |
| **Chassis type**                     | OP48xx                                                                              |
| **Bitstream configuration location** | Standard repositories                                                               |
| **Bitstream configuration file**     | OP5145\_2-EX-0001-3\_13\_1\_36-eHSx128Gen5\_HSCS\_PowerElectronics\_IOConfig1-FD-11 |

### Slot 1 and Slot 2 - Digital inputs/outputs

Refer to [OP48H10 pin assignment](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description/db37f-pin-assignment) for hardware connections.

Each **OP48H10** includes a **32‑channel digital I/O** module divided into four **8‑channel subsections**, each of which can be independently configured as either a digital input or a digital output.

Electric circuit **switch blocks** are directly mapped to the module’s **digital inputs** in Schematic Editor by selecting the block and assigning the desired module channel(s) as gate signal source(s).

Electric circuit **machine blocks** can have their **encoder outputs** mapped to the module's **digital outputs** in the Schematic Editor. However, the user does not select specific module channels; instead, encoder must be enabled for the machine, after which the encoder signals are automatically mapped to either **Slot 1A** or **RS422 Slot 3**. Open the **eHS Build Report** to determine the I/O group used.

Mapping **HYPERSIM model signals** to the module's **digital inputs/outputs** follows the standard OPAL‑RT board workflow.

### Slot 1 and Slot 2- Analog outputs

Refer to [OP48H10 pin assignment](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description/db37f-pin-assignment) for hardware connections.

Electric circuit **measurement blocks** are directly mapped to the module's **analog outputs** in the Schematic Editor by selecting the block and assigning the desired module channel as the destination.

Mapping **HYPERSIM model signals** to the module's **analog outputs** follows the standard OPAL‑RT board workflow.

{% hint style="danger" %}
Mapping a single electric circuit measurement block to an analog output in Schematic Editor reserves all 16 channels for eHS, disabling analog output mapping in the HYPERSIM model.
{% endhint %}

### Slot 1 and Slot 2- Analog inputs

Refer to [OP48H10 pin assignment](https://www.opal-rt.com/docs/op48hxx/input-output-modules/op48h10-description/db37f-pin-assignment) for hardware connections.

Electric circuit **sources blocks** are directly mapped to the module's **analog inputs** in the Schematic Editor by selecting the block and assigning the desired module channel as the source.

Electric circuit **machine blocks** can also have their **resolver excitation source** mapped to the module's **analog inputs** in the Schematic Editor by enabling the resolver for the machine block and assigning the desired module channel as the excitation source.

Mapping **HYPERSIM model signals** to the module's **analog inputs** follows the standard OPAL‑RT board workflow.

### SFP module

Electric circuit **sources blocks** can be mapped to the module's **SFP CH04** **input** in the Schematic Editor by selecting the block and assigning the desired **SFP input signal** as the source. All SFP input signals are carried through a **single SFP channel (CH04)**, which provides **32 input signals**. All other SFP channels are disabled in this firmware.

Electric circuit **measurement blocks** can be mapped to the module's **SFP CH04** **output** in the Schematic Editor by selecting the block and assigning the desired **SFP output signal** as the destination. All SFP output signals are carried through a **single SFP channel (CH04)**, which provides **32 output signals**. All other SFP channels are disabled in this firmware.

Mapping **HYPERSIM model signals** to the **SFP module** follows the standard OPAL‑RT board workflow.

{% hint style="danger" %}
Mapping a single electric circuit measurement block to an SFP output signal in Schematic Editor reserves all SFP output signals for eHS, disabling SFP output mapping in the HYPERSIM model.
{% 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/ehs/3.7/first-steps/choose-the-ehs-firmware/introduction-to-standard-ehs-firmware/op4815-io/ehsx128-gen5-hscs-ioconfig1.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.
