> 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/run-an-example-project.md).

# Run an Example Project

To demonstrate how to use the **Power Electronics Add-On** in VeriStand to run simulations on a real‑time PXI system, we will walk through a complete build project. This project includes a [**SCIM local control**](https://www.opal-rt.com/docs/pe-add-on-simulink/examples/scim-local-control.md) circuit that uses the **eHS Solver** to simulate a two‑level inverter circuit driving a **squirrel‑cage induction machine** model on the FPGA. An **open‑loop controller** runs on the system’s real‑time CPU to generate the gating commands for the inverter, which are transmitted to the FPGA through PWM signal generators.

The project can be deployed on either a **PXIe‑7868R** or **PXIe‑7891** FPGA card.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2Fcjif2cXuHDgRxw54d1Gk%2Fimage.png?alt=media&amp;token=9363105c-a1e0-4656-aaa9-2c2da56f4847" alt=""><figcaption></figcaption></figure>

## Confirm target configuration

* Open the [**NI Measurement and Automation Explorer**](https://www.ni.com/docs/en-US/bundle/max/page/mxhelp/mxhelp.html) (NI MAX) and in the configuration tree, expand **Remote Systems** and locate your real-time PXI target to confirm that it is properly connected.
* Click the target and make note of its **IP Address**. Confirm that the **Operating System** is *NI Linux Real-Time*.
* Expand the **Software** section under the target and confirm that the **NI VeriStand Engine** and **FlexRIO** is installed. The version of VeriStand installed on the target must match the version installed on the development machine.

{% hint style="info" %}
For more information about connecting and installing software to a target, refer to the NI documentation for [**Linux systems**](https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x2jQCAQ\&l=en-CA)**.**
{% endhint %}

* Expand **Devices and Interfaces** and locate the **NI PXIe-7868R** or the **NI PXIe-7891** card under the PXIe chassis. Confirm that the card to be used is named *FPGA0*.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FWAzCoKrHHH5JW7eaJtwO%2Fimage.png?alt=media&amp;token=42e8bed8-e626-4315-925d-27eef91174ac" alt=""><figcaption></figcaption></figure>

## Open and run the project example

During installation of the demo package, **the files are copied into the folder** C:\Users\Public\Documents\National Instruments\NI VeriStand 2024\Examples\OPAL-RT\Power Electronics Add-On. To avoid modifying the original example, make a local copy of the **Example Directory** shown above. More information are available [here](https://www.opal-rt.com/docs/pe-add-on-simulink/examples/open-and-run-an-example.md).

{% stepper %}
{% step %}

### Open the example in VeriStand

Open VeriStand and **Browse** to the copied directory, then continue browsing to the **Project Path** and select the VeriStand Project **SCIM Local Control.nivsprj** file in the **SCIM Local Control/Project/PXIe-xxx** folder.
{% endstep %}

{% step %}

### Configure the project

* In the tab for the **SCIM Local Control.nivssdf** System Definition file, click **Configure...** to launch the System Explorer and navigate to the **Controller** section of the tree.
* Configure the **IP Address** field with the information obtained in Step 1.3.\
  If permissions are configured on your Real Time target, enter the credentials in the **Username** and **Password** fields. National Instruments targets are programmed with the following credentials by default:\
  **Username**: *admin* **Password**: *\<blank>*
* Click **Save** and close the System Explorer.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FPErqtkNvzsjW2bvwQhM7%2Fimage.png?alt=media&amp;token=634e34c7-7ce5-4433-be33-22d3449a2240" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Deploy the System Definition

* In the VeriStand Editor, select **Idle >> Deploy** and wait until the connection.
* Navigate to **Main.nivsscr** file to view the main user interface.
* Experiment with the UI controls to monitor the simulation results.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2F45EoJ5jlwPWOrBd5wEHr%2Fimage.png?alt=media&amp;token=0f0008db-c687-4ad6-a4b3-58160ddced04" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Stop the simulation

In the VeriStand Editor, select **Connected >> Undeploy** to stop the simulation.
{% 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/run-an-example-project.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.
