> 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/change-the-chassis-of-an-hypersim-ehs-model.md).

# Change the Chassis of an HYPERSIM eHS Model

Models containing [FPGA Based Circuit blocks](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-tools/fpga-based-circuit.md), including the example models delivered with HYPERSIM, are configured for a specific hardware chassis. The purpose of this document is to explain how to update a model so that it can run on a different chassis.

The procedure described in this guide can also be used when adapting an example model to run with a different firmware version.

## Update circuit in Schematic Editor

Double-click the FPGA based Circuit block to open the circuit in the **Schematic Editor**. Then open **Simulator Setup** by selecting **Simulate → Simulator Setup** from the menu. The dialog displays the simulator configuration currently associated with the model.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5bc384c117f943ab0e86f925d3ecd890e2a5b3a5%2Fchange-chassis-efpgasim-model-1.png?alt=media" alt=""><figcaption></figcaption></figure>

The simulator setup defines the firmware that will be used to generate the eHS configuration, as well as the hardware connections available to your circuit. A model can contain multiple simulator setups, allowing it to target different chassis and firmware configurations.

To create a new setup, click the **+** button and select the desired **chassis**, **eHS license class**, and **firmware version**. To choose a different firmware version, click the drop-down arrow as shown below:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-911d00ef4d7ad0b5128b8f8a164d9df0848a14bd%2Fchange-chassis-efpgasim-model-2.png?alt=media" alt=""><figcaption></figcaption></figure>

You can also rename a setup by clicking its name.

After creating the new setup:

1. Select the setup and update all required circuit connections.
2. Save the circuit and return to your HYPERSIM model.
3. Reload the circuit by right-clicking the **FPGA Based Circuit** block and selecting **eHS → Load Circuit**.

The FPGA block will then use the updated circuit configuration associated with the selected setup.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-56d3639259a079f42f4d6255e24cfa59456cbf93%2Fchange-chassis-efpgasim-model-3.png?alt=media" alt="" width="480"><figcaption></figcaption></figure>

Now the FPGA Based Circuit block is configured with the new Bitstream. Next step will be to configure the Opalboards interface.

## Update the I/O Interface

In the HYPERSIM ribbon, click the **I/O Interface** button to open the **I/O Interface** window.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-0c991a0b1230743407fa61468cccb31ea5c05e67%2Fchange-chassis-efpgasim-model-4.png?alt=media" alt=""><figcaption></figcaption></figure>

To update the configuration, perform the following steps:

1. Update the **chassis** selection.
2. *(Optional)* The **Standard Repository** corresponds to the firmware delivered with eFPGASIM. If you need to use a custom firmware, select **File System** instead.
3. Select the required **bitstream configuration file**. The bitstream name will automatically update to match the selected configuration. Ensure that it corresponds to the bitstream selected in the **Schematic Editor**.

**Important:** Changing the bitstream resets the current **I/O configuration**. As a result, any previously configured I/O channels must be reviewed and reconfigured as needed.

For example, in this model, the first eight channels of **Digital Slot 1A** were configured as **PWM output signals** before the bitstream was changed:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7c1e2deb307f6a739a444dbb46d9b4f60940d07b%2Fchange-chassis-efpgasim-model-5.png?alt=media" alt=""><figcaption></figcaption></figure>

The signals were also mapped to devices in the HYPERSIM model, as shown below. The view is taken from the **Sensor Summary** window:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d7840c964879b6de4581dc00167cdb4f261946d5%2Fchange-chassis-efpgasim-model-6.png?alt=media" alt=""><figcaption></figcaption></figure>

**Note:** If your model does not contain any configured I/O connections, you can skip this step.

When you change the **chassis** or the **bitstream**, the available I/O slots may differ from the original configuration. As a result, the I/O mapping may need to be updated.

When the new configuration is applied, a pop-up dialog prompts you to choose whether to preserve the existing connection assignments or reset them, as shown below:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4035cd500b83fc6d53af97e2a3ca8a8cb8da8c9b%2Fchange-chassis-efpgasim-model-7.png?alt=media" alt="" width="480"><figcaption></figcaption></figure>

HYPERSIM attempts to automatically remap all existing I/O connections to the new firmware configuration. However, if the new chassis or firmware uses a different hardware configuration, some connections may not be mapped correctly and must be updated manually.

For example, after switching to a new **OP5707** firmware, the available I/O configuration changed. As a result, some I/O assignments were no longer valid and had to be reconfigured to match the original setup:

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8cb3c74ed19012da6b402cda6695cf672981853d%2Fchange-chassis-efpgasim-model-8.png?alt=media" alt=""><figcaption></figcaption></figure>

The same applies to the **Sensor Summary**: some connections may need to be recreated.

To edit a connection, click the **Edit** button (highlighted in red below):

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7ba8473430db6847ae4ecd45a12c94279ac8afee%2Fchange-chassis-efpgasim-model-9.png?alt=media" alt=""><figcaption></figcaption></figure>

Once the **eHS Schematic Editor** circuit and the **Opal-Boards Driver Interface** have been configured for the new chassis, and any required I/O connections have been updated, the model is ready to run.

Before launching the simulation, verify that the correct **simulator setup** is selected in the **HYPERSIM Settings** menu.


---

# 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/change-the-chassis-of-an-hypersim-ehs-model.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.
