> 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/get-started/install-the-power-electronics-add-on/upgrade-or-uninstall-the-power-electronics-add-on.md).

# Upgrade or Uninstall the Power Electronics Add-On

Follow the steps below to upgrade the Power Electronics Add-On to a new version, or to uninstall it completely.

{% stepper %}
{% step %}

## Launch NI Package Manager

Navigate to the **INSTALLED** tab and filter for *OPAL-RT Technologies* under the **Maintainer** dropdown menu.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FWmKElINkL8oZiwxZMrA4%2Fimage.png?alt=media&amp;token=fb11b531-c26a-4d0e-85bc-c8dbaa70ab05" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

## Select the Power Electronics Add-On and related products

Select the *OPAL-RT Power Electronics Add-On for VeriStand*, as well as the following products:

* *OPAL-RT Advanced Electric Machine Simulation Runtime*
* *OPAL-RT eHS Runtime*
* *OPAL-RT Hardware Configuration Manager*
* *OPAL-RT License Manager*

{% hint style="danger" %}

## Shared Dependencies

Be cautious not to remove dependencies of other OPAL-RT software when managing installations. The **Hardware Configuration Manager** and the **License Manager**, both required by the **OPAL-RT CMDE Add-On** for NI VeriStand, may have multiple versions installed concurrently.\
The **Hardware Configuration Manager**, the **eHS runtime** and the **License Manager**, are required by the **Power Electronics (OPAL-RT Circuit) Add-On** for NI VeriStand.

Refer to the **NI Packages** section of the Release Notes of the installed software to confirm the required packages and versions for each product.
{% endhint %}
{% endstep %}

{% step %}

## Remove the selected packages

Click **Remove** and follow the uninstallation prompts.

**Reboot** the computer if prompted.
{% endstep %}

{% step %}

## (Optional) Install a new version

If desired, install a new version of the Power Electronics Add-On.

{% hint style="info" %}
It is not recommended to install different versions of the Power Electronics Add-On concurrently on the same computer.
{% endhint %}
{% endstep %}

{% step %}

## Migrate existing VeriStand projects

To upgrade any existing VeriStand projects to the newer version of the Power Electronics Add-On, follow the instructions in the [Project Migration Procedure](https://www.opal-rt.com/docs/pe-add-on-simulink/appendix/project-migration-procedure.md).
{% endstep %}
{% endstepper %}


---

# 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/get-started/install-the-power-electronics-add-on/upgrade-or-uninstall-the-power-electronics-add-on.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.
