> 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/hypersim/model-and-simulation/power-electronics-and-electric-machines-with-ehs.md).

# Power Electronics & Electric Machines with eHS

This version of HYPERSIM includes [FPGA-Based Power Electronics (eHS) version 3.5](https://www.opal-rt.com/docs/ehs/3.5/overview/software-compatibilities).

## Introduction to eHS

Real-time simulation of power electronics and electric machines requires **nanosecond-level timesteps**. OPAL-RT’s **eHS (electric Hardware Solver)** is a high-speed FPGA-based solver that meets this demand, enabling accurate simulation of converters, motors, and inverters without physical hardware. It is widely used in automotive, aerospace, and energy applications, including EV powertrains, battery management systems, and on-board chargers.

eHS allows users to simulate electric circuits on FPGA without VHDL programming or complex mathematical modeling.

To use the eHS solver, **the electric circuit schematic is created separately from the HYPERSIM model**. It is created using OPAL‑RT’s built-in **Schematic Editor** and then integrated into the main model via an [**FPGA-based circuit block**](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-tools/fpga-based-circuit.md).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9f21aedaadfdf9b16f85ffcbd2c528b865ff31f4%2Fimage%20(1)%20(1)%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

## Run an electric circuit with eHS on FPGA

{% stepper %}
{% step %}

### Add the FPGA Based Circuit block to the model

Go to the **Network Tools** library and drag the [FPGA Based Circuit](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-tools/fpga-based-circuit.md) block into the HYPERSIM model.
{% endstep %}

{% step %}

### Set the bitstream and design the electric circuit

This step requires knowledge of eHS bitstreams, supported circuit blocks, and available features. Refer to the [full eHS documentation](broken://spaces/nVlkMVXjY5bWbFGd9Gyz/pages/aBK8ZFLlzCBwUYs6t8ws) before proceeding.
{% endstep %}

{% step %}

### Prepare the hardware setup

Refer to the **Connect Analog & Digital I/Os** section of your simulator and/or expansion unit documentation for detailed instructions on connecting external hardware or a DUT through its I/O modules.
{% endstep %}

{% step %}

### Start the simulation

​In the **HYPERSIM** tab, click **Start**. Once the simulation is running, the **Start** button becomes grayed out, and the **Stop** button becomes active, allowing you to halt execution if required.
{% endstep %}
{% endstepper %}


---

# 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/hypersim/model-and-simulation/power-electronics-and-electric-machines-with-ehs.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.
