> 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/requirements.md).

# eHS Requirements

## Software requirements

eHS is **included by default with RT-LAB and HYPERSIM** and does not require any additional installation.

## Hardware requirements

To use the eHS solver, the simulator or expansion unit must be equipped with a compatible FPGA board.

<details>

<summary><strong>Compatible simulators</strong></summary>

* OP4510 V2, only if upgraded to OPAL-RTLinux (Kintex-7: TE0741\_3, TE0741\_4)
* OP4512 (Kintex-7: TE0741\_4)
* OP4610XG and OP4610XG2 (Kintex-7: TE0741\_4)
* OP5707XG and OP5707XG2 (Virtex-7: VC707\_2)

</details>

<details>

<summary><strong>Compatible expansion units</strong></summary>

* OP4300 (KRIA KV26)
* OP4520 (Kintex-7: TE0741\_3, TE0741\_4)
* OP4610-IO (Kintex-7: TE0741\_4)
* OP4810-IO (Versal)
* OP4815-IO (Versal)
* OP5607 (Virtex-7: VC707\_2)
* OP5707-IO (Virtex-7: VC707\_2)

</details>

## Firmware requirements

The eHS solver requires a compatible **FPGA firmware (bitstream)** to operate. The firmware determines:

* The **FPGA board**, simulator, or expansion unit it can run on
* The [**solver generation**](https://www.opal-rt.com/docs/ehs/overview/ehs-solver-generations.md) (e.g., Gen 4 or Gen 5)
* The **available features**, such as supported machine types, circuit capabilities, and advanced solver functions
* The **I/O configuration**, including the number, type, and location of inputs and outputs

In contrast, the **license** controls which of these capabilities are **enabled** during simulation.

{% hint style="info" %}
**Key distinction**: The firmware defines what is technically possible, while the license determines what is permitted.
{% endhint %}

## eHS license requirements <a href="#minimum-artemis-license-requirements" id="minimum-artemis-license-requirements"></a>

### Simulator license <a href="#simulator-license" id="simulator-license"></a>

Verify that an active license with the following features is installed on the simulator to execute eHS simulations on that simulator:

| Feature Name              | Required status      | Description                                                                                           |
| ------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------- |
| XSG\_EHS                  | enabled              | FPGA-based power electronics solver (eHS)                                                             |
| EHS\_CORE\_TOKEN          | 16 enabled (or more) | eHS [license class](https://www.opal-rt.com/docs/ehs/overview/requirements/get-a-licence.md) per core |
| EHS\_MACHINE\_CORE\_TOKEN | 1 enabled (or more)  | Number of machines allowed per model                                                                  |

{% hint style="danger" %}
Additional license features are required for specific applications, such as machine models, specialized line models, and decoupling blocks. See below **optional simulator features**.
{% endhint %}

#### Optional simulator features:

| Feature Name                  | Description                                                                                                                                                                                                                                                                                                  |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| EHS\_HIGH\_PERFORMANCE\_TOKEN | Defines the number of cores eligible for high-performance execution. Each eHSx32 core consumes 32 tokens. Total tokens can be distributed across cores (e.g., 128 tokens → 1× eHSx128, 2× eHSx64, or 4× eHSx32). Required for high-performance features such as decoupling blocks and certain switch models. |
| EHS\_HSCS\_CORE\_TOKEN        | Defines the number of HSCS cores and corresponding solver instances at a given performance level.                                                                                                                                                                                                            |
| EHS\_GEN5                     | Enables the use of Generation 5 eHS solver firmware                                                                                                                                                                                                                                                          |
| EHS\_PADE5                    | Enables the use of PADE5 discretization                                                                                                                                                                                                                                                                      |

{% hint style="info" %}
Some eHS-related features may still appear in the simulator license, but they are deprecated and have no impact on the simulation.
{% endhint %}

### Workstation license <a href="#workstation-license" id="workstation-license"></a>

**No additional license feature** is required on a workstation license to run simulations using the eHS solver.


---

# 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/requirements.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.
