> 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/default-hardware-configurations.md).

# Default Hardware Configurations

The **Power Electronics Add-On** must be configured to use a specific hardware configuration before a simulation can be deployed. This configuration determines the **type of FPGA board(s)** being targeted and the **features available in the FPGA firmware**.

## eHS Solver

The OPAL-RT electric Hardware Solver (eHS) is a floating-point solver that enables the simulation of an electric circuit on an FPGA without having to write the mathematical equations. It combines the simplicity of building electric circuit models using circuit editing software with the strength of FPGA-based simulators to solve for the circuit currents and voltages in real-time, with a sample time below 1µs.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FkIVPEwORdBGfN9SQx4K9%2Fimage.png?alt=media&amp;token=fd4401f9-73af-4503-9788-128a933d9ef9" alt="" width="417"><figcaption></figcaption></figure>

The **eHS Solver** uses [**Modified Nodal Analysis**](http://www.swarthmore.edu/NatSci/echeeve1/Ref/mna/MNA2.html) to generate a conductance matrix that, when solved, returns the voltage at each node of the circuit and the current in each branch. The conductance matrix of the circuit is generated independently from the state of the switches, and therefore does not need to be recomputed when a switch is opened or closed during the simulation. This is achieved through the implementation of the Pejovic method, which represents each **Switch** block as an impedance–a conducting switch is represented as an inductor and an open switch is represented as a capacitor.

The components within the electric circuit model can be classified into four different types: **sources, switches, measurements** and **passive elements.**

### eHS Form Factors <a href="#inlineextension-ehs-form-factors" id="inlineextension-ehs-form-factors"></a>

The eHS solver is available in various form factors. Each form factor provides different capabilities for the number of Sources, Switches, Measurements, and Passive Elements that can be simulated.

<table><thead><tr><th width="214.666748046875">Features</th><th>eHSx16</th><th>eHSx32</th><th>eHSx64</th><th>eHSx128</th></tr></thead><tbody><tr><td><strong>Number of Sources</strong></td><td>16</td><td>32</td><td>64</td><td>128</td></tr><tr><td><strong>Number of Switches</strong></td><td>12</td><td>48</td><td>72</td><td>144</td></tr><tr><td><strong>Number of Measurements</strong></td><td>16</td><td>32</td><td>64</td><td>128</td></tr><tr><td><strong>Number of Resistors</strong></td><td>Unlimited</td><td>Unlimited</td><td>Unlimited</td><td>Unlimited</td></tr><tr><td><strong>LCA Capability*</strong></td><td>Yes</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td><strong>Estimated Maximum Number of States**</strong></td><td>84</td><td>112</td><td>168</td><td>344</td></tr><tr><td><strong>Supported Switch Types</strong></td><td>IGBT/Diode, Diode, Breaker, Thyristor, Ideal Switch</td><td>IGBT/Diode, Diode, Breaker, Thyristor, Ideal Switch</td><td>IGBT/Diode, Diode, Breaker, Thyristor, Ideal Switch</td><td>IGBT/Diode, Diode, Breaker, Thyristor, Ideal Switch</td></tr><tr><td><strong>Supported Non-Switching Devices</strong></td><td>Resistor, Inductor, Capacitor, Ideal Transformer, Mutual inductance, PI Line</td><td>Resistor, Inductor, Capacitor, Ideal Transformer, Mutual inductance, PI Line</td><td>Resistor, Inductor, Capacitor, Ideal Transformer, Mutual inductance, PI Line</td><td>Resistor, Inductor, Capacitor, Ideal Transformer, Mutual inductance, PI Line</td></tr><tr><td><strong>Calculation Power (GFLOPS)</strong></td><td>6.4</td><td>12.8</td><td>25.6</td><td>51.2</td></tr><tr><td><strong>Maximum Number of Scenarios</strong></td><td>Up to 512. Limit depends on circuit complexity.</td><td>Up to 512. Limit depends on circuit complexity.</td><td>Up to 512. Limit depends on circuit complexity.</td><td>Up to 512. Limit depends on circuit complexity.</td></tr></tbody></table>

\*LCA, or Loss Compensation Algorithm, optimizes losses for standard topologies such as 2-level converter and NPC 3-level converter arms.

\*\* The maximum number of states also depends on the number of inputs and outputs. There is no hard coded limit.

## Hardware configuration list

The following hardware configurations are available in the **Power Electronics Add-On** by default for **PXIe-7868R** and **PXIe-7891**, and existing configurations can be combined and manipulated using the [Hardware Configuration Manager](https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/hardware-configuration-manager.md) tool.

<details>

<summary><strong>PXIe-7868R</strong></summary>

* eHSx64\_Quad\_IM\_SM\_IO\_7868R
* eHSx32\_Dual\_PMSM\_SH\_IO\_7868R
* eHSx32\_6\_Ph\_PMSM\_VDQ\_IO\_32DO\_7868R
* eHSx64\_Dual\_PMSM\_VDQ\_IO\_7868R
* eHSx32\_Dual\_PMSM\_VDQ\_IO\_32DO\_7868R
* eHSx64\_Quad\_IM\_Saturation\_IO\_7868R

</details>

<details>

<summary><strong>PXIe-7891</strong></summary>

* eHSx64\_Dual\_6\_Ph\_PMSM\_VDQ\_IO\_7891
* eHSx64\_Dual\_PMSM\_VDQ\_Quad\_IM\_SM\_IO\_7891
* eHSx64\_Quad\_PMSM\_SH\_IO\_7891
* eHSx64\_Quad\_PMSM\_VDQ\_IO\_7891

</details>


---

# 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/default-hardware-configurations.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.
