> 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/cmde-add-on/hardware-configurations-reference/hardware-configuration-manager.md).

# Hardware Configuration Manager

The Hardware Configuration Manager (HCM) is a tool used to edit, build, and distribute **Hardware Configurations**. It can be accessed from the main page of the CMDE Add-On via the **Launch HCM** toolbar button shown below.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FoGjT8vhnKrp5aXKmhoYb%2Fimage.png?alt=media&amp;token=ec5adaf9-d68a-4881-85e9-3b8d55f8a01e" alt=""><figcaption></figcaption></figure>

## Parameters and buttons

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FpYyFvCYqGGoP3x9Pkhkd%2Fimage.png?alt=media&amp;token=4bf6e98b-668f-40c7-a973-3d8222423513" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="201.55560302734375">Parameter / Button</th><th>Description</th></tr></thead><tbody><tr><td><strong>Installed Hardware Configurations Table</strong></td><td>Lists the hardware configurations currently installed to the host machine and available for use by the user. By clicking on the hardware configuration, the description of the selected configuration is made available below the table.</td></tr><tr><td><strong>Import...</strong></td><td>Imports a hardware configuration file (.opbitx) and installs it to the host computer. </td></tr><tr><td><strong>Export...</strong></td><td>Exports the selected hardware configuration file to a .opbitx file. </td></tr><tr><td><strong>Delete</strong></td><td>Deletes the selected hardware configuration. This operation is permanent.</td></tr><tr><td><strong>>></strong></td><td>Adds the bitfiles of an installed hardware configuration to the Selected Bitfiles table, allowing the user to build a new Custom Hardware Configuration from an existing one.</td></tr><tr><td><strong>&#x3C;&#x3C;</strong></td><td>Removes the bitfiles of the last selected hardware configuration from the Selected Bitfiles table.</td></tr><tr><td><strong>Selected Bitfiles Table</strong></td><td>Lists the bitfiles that have been selected to build a new hardware configuration and the targets they will be assigned to. The target names are automatically assigned and cannot be modified.</td></tr><tr><td><strong>New Hardware Configuration Name</strong></td><td>The name of the new Custom Hardware Configuration that will be created when clicking on the <strong>Create New Hardware Configuration</strong> button. This will be the name visible to the user in the Installed Hardware Configurations table and drop-down on the Main Page of the Power Electronics Add-On.</td></tr><tr><td><strong>New Hardware Configuration Description</strong></td><td>The description of the new Custom Hardware Configuration that will be created when clicking on the <strong>Create New Hardware Configuration</strong> button. This description will be visible to the user in the Installed Hardware Configurations table and on the Main Page of the Power Electronics Add-On.</td></tr><tr><td><strong>Create New Hardware Configuration</strong></td><td>Creates a new Custom Hardware Configuration using the selected bitfiles, the <strong>New Hardware Configuration Name</strong>, and the <strong>New Hardware Configuration Description</strong>. Clicking this button will generate a new entry in the <strong>Installed Hardware Configurations Table</strong> and will populate a new entry in the Configurations drop-down on the Main Page of the Power Electronics Add-On.</td></tr></tbody></table>

## Duplicate an existing hardware configuration

For example, consider a case where a user would like to simulate two rings of LTC6810 devices on two different PXIe-7820R boards. To achieve this, we can create a new hardware configuration by duplicating an existing one containing a single LTC6810 Ring, e.g. the **1xRing\_16xLTC6810\_7820R**. This will allow the simulation of double the resources on two separate PXIe-7820R FPGAs.

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2F8xRFgMOgPSX7wEUC4DH0%2Fimage.png?alt=media&amp;token=ec76db0f-ff2e-4c20-927e-dfb79348f3a2" alt=""><figcaption></figcaption></figure>

In the HCM interface,&#x20;

* Select the **1xRing\_16xLTC6810\_7820R** configuration from the Installed Configurations list.
* Click the **>>** button twice to populate the Selected Bitfiles list with the duplicate configuration. Note that this process also auto-assigns the FPGA Identifier.
* Enter a **New Hardware Configuration Name** and **Description** into the provided text boxes, and then click **Create New Hardware Configuration**.&#x20;

<figure><img src="https://2869406741-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fgtd2gZ5PvjsRaV45Czvu%2Fuploads%2FWcqvItJ6u5HlW3nqaRu0%2Fimage.png?alt=media&amp;token=46c001aa-bb03-4e44-975c-5081a517bad9" alt=""><figcaption></figcaption></figure>

The newly created Hardware Configuration will now be available for selection on the Power Electronics Add-On Main Page drop-down.


---

# 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/cmde-add-on/hardware-configurations-reference/hardware-configuration-manager.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.
