> 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/standard-workflow.md).

# Standard Workflow

## Power Electronics simulation workflow

The FPGA-based solvers included in the Power Electronics Add-On can be used independently or combined to simulate nearly any power electronics or machine drive circuit in real-time, while maintaining a sample time below 1µs.

The solution provides a simple workflow for users:

{% stepper %}
{% step %}
**Design a power electronics circuit** using the **Simulink Editor**
{% endstep %}

{% step %}
**Configure** the simulation parameters in VeriStand
{% endstep %}

{% step %}
**Deploy the real-time application**, which will in turn configure the OPAL-RT FPGA solvers.
{% endstep %}

{% step %}
**Connect a real or simulated controller** directly to the I/O of the selected NI hardware, provide stimuli, and acquire measurements.
{% 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/overview/standard-workflow.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.
