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

# License Requirements

To deploy a **VeriStand project with the Power Electronics Add-On**, a valid deployment license must be installed on the simulator.

A deployment license can be tied to one or more NI targets, identified by the **MAC address** of their primary network adapters (NIC). The Power Electronics Add-On can only be executed on the targets added to the deployment license.

### <mark style="background-color:$danger;">Requesting a License</mark>

## eHS License Class <a href="#ehs-license-class" id="ehs-license-class"></a>

The eHS solver comes in different core flavors depending on its performance:

* x16
* x32
* x64
* x128

Based on your OPAL-RT license, you are authorized to use a certain number of eHS solver cores.

```
License key: EHS_CORE_TOKEN
```

This value is the cumulative cost of all cores defined in your model.

| eHS License Class | Performance Cost |
| ----------------- | ---------------- |
| x128              | 128              |
| x64               | 64               |
| x32               | 32               |
| x16               | 16               |

While setting up your configuration, please indicate the type you wish to use to adequately fit the eHS solver to your [**firmware**](https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/default-hardware-configurations.md).


---

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