> 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/overview/ehs-solver-generations.md).

# eHS Solver Generations

## Overview

This version of the eHS supports **Generation 5 (Gen 5)** and **Generation 4 (Gen 4)**. Each generation introduces improvements in simulation accuracy, performance, and modeling capabilities.

* Gen 5: Current and actively developed generation
* Gen 4: Maintenance only (legacy support)

#### Generation and firmware compatibility

The eHS solver generation is **directly tied to the FPGA firmware** used during simulation. A given firmware is **built for a specific solver generation** (Gen 4 *or* Gen 5).

The solver generation can be identified directly from the **firmware file name**, which explicitly includes the generation (e.g. `eHSGen4` or `eHSGen5`). Additional details can be obtained from the firmware (IOConfig) or bitstream description.

## Generation 5

**Gen 5** introduces a new circuit analysis approach based on state-space equation solving, enabling faster and more accurate discretization.

**Gen 5** offers a High Speed Converter Solver (HSCS), which allows for faster simulation of high-frequency power electronics systems. This mode is particularly useful for simulating systems with switching frequencies above 100 kHz, such as resonant converters and dual active bridge converters. It also offers a simplified switch tuning only based on $R\_on$ and $R\_off$.

Gen 5 enables accurate simulation of frequency- and/or phase-controlled power electronics systems, including:

* **Resonant converters (CLLC and LLC topologies)**
* **Dual Active Bridge (DAB) converters operating above 200 kHz switching frequency**
* **SST topologies**

### Key characteristics

* Electrical system sample time: **70 ns to 4 µs** (depending on circuit complexity)
* Advanced discretization methods (including higher-order ART5)
* Improved switching accuracy via interpolation
* Support for complex and high-frequency power electronics applications
* Support for decoupling capability (requires High Performance license)
* Deprecation of LCA
* Capability to have up to 32 instances of the same HSCS cell or 2 different HSCS cells, each instantiated up to 16 times
* HSCS cell time-step as low as 32 ns

## Generation 4

**Gen 4** is a legacy generation now in maintenance mode. In this generation, switches are modeled using the Pejovic method, which avoids recomputing the conductance matrix during simulation. All required matrices are preloaded onto the FPGA at simulation startup, eliminating the need for application-specific firmware reconfiguration \[1].

### Key characteristics

* Electrical system sample time: **200 ns to 4 µs** (depending on circuit complexity)
* Simplified execution model with preloaded matrices
* Stable and proven for a wide range of applications
* Support for single-cycle model coupling (e.g., FD Line, saturable transformer)

### Limitations

The following components are **not supported**:

* Single-phase cycloconverter
* 3-level T-Type converter
* Decoupling blocks
* Bi-directional switches

## Reference

\[1] P. Pejovic and D. Maksimovic, “A new algorithm for simulation of power electronic systems using piecewise-linear device models," in IEEE Transactions on Power Electronics, vol. 10, no. 3, pp. 340-348, May 1995, doi: 10.1109/63.388000.


---

# 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/overview/ehs-solver-generations.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.
