> 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/overview/introduction-to-ehs.md).

# Introduction to eHS

## Welcome 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 is installed automatically in the following **OPAL-RT software platforms**:

* **RT-LAB**
* **HYPERSIM**

And available as an add-on for [NI Veristand](https://www.opal-rt.com/docs/pe-add-on-opal-rt).

To use the eHS solver, **the electrical circuit schematic is created separately from the main model**. eHS provides a **built-in Schematic Editor** dedicated to electrical circuit design, enabling simulation on FPGA without requiring VHDL programming or complex mathematical modeling.

The circuit developed in the **Schematic Editor** interacts with the main model and/or an external device under test (DUT) through its **sources**, **measurements**, and **switch gate signals**.

Throughout this documentation, the main simulation model running on the CPU (e.g., Simulink or HYPERSIM) is referred to as the **CPU model**, while the electrical circuit created in the Schematic Editor and executed on the FPGA using the eHS solver is referred to as the **eHS circuit model**.

### Example in RT-LAB

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-29623d559862fd1c080a787727740c475b68038a%2FeHS-in-rtlab-example.png?alt=media" alt=""><figcaption></figcaption></figure>

### Example in HYPERSIM

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-48bad9b8d5c59cdbefde5cfa6a9e0241b86a7e10%2Fehs-in-hypersim-example.png?alt=media" alt=""><figcaption></figcaption></figure>

## Typical application

Using OPAL-RT’s **eHS solver**, the simulator models the electrical machine, power electronics (converters and inverters), and mechanical load on the machine shaft. The device under test (DUT) interacts with the simulated system through analog, digital, or communication interfaces, forming a closed-loop system between controller and plant.

This setup enables accurate real-time emulation of single or multiple machine drives coupled with mechanical systems, such as hybrid powertrains or full vehicle configurations.

A typical test bench consists of:

* **Real-time simulator**: Implements the machine drive and power electronics models using eHS
* **External DUT**: The controller under test, connected via configurable I/O and communication protocols

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

This architecture enables high-fidelity hardware-in-the-loop (HIL) simulation for electric machine drives and a wide range of power electronics applications.


---

# 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/overview/introduction-to-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.
