> 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/get-started-with-ephasorsim.md).

# Get Started with ePHASORSIM

## Add ePHASORSIM to an existing model

{% stepper %}
{% step %}

### Add the ePHASORSIM Solver block to the Simulink model

Open the Simulink **Library Browser**, navigate to **RT-LAB > ePHASORSIM** and drag the **Solver** block into the model.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-388147a08259d08609d36c3c45ccb846a6e94264%2Frt-lab-ephasorsim-block.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
When more than one **ePHASORSIM Solver** block is present in the model, each **ePHASORSIM Solver** block must be assigned a unique **Name.**
{% endhint %}
{% endstep %}

{% step %}

### Open an Excel configuration template file

The power system model integrated into the **ePHASORSIM Solver** block exchanges signals with the surrounding Simulink model through ports defined in an Excel configuration file. This file is required for all workflows. Save a copy of the template file in your model directory.

1. Double-click the **ePHASORSIM Solver** block to open its mask.
2. Navigate to the **Network data** tab.
3. Click **Open** to open the Excel Template.
   * When **Excel** is selected as the **Input File Format**, the **Open** button is located under **Complete Network**.
   * When **PSS/e**, **PowerFactory**, or **CYME** is selected, the **Open** button is located next to **I/O pins file**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4ce875cf2e9fa30da7c6ba5c10be8a31e1e5c31d%2Feph-rtlab-solver-mask.png?alt=media" alt=""><figcaption></figcaption></figure>

4. Save a copy of the template file in the model directory. You may rename the file as needed.
   {% endstep %}
   {% endstepper %}

## Start from an example model

You may explore one of the included example models to become familiar with the ePHASORSIM workflow and adapt the example to your application.

From the menu bar, select **File > New > RT‑LAB Project**. Enter a name and location for your project, then click **Next**. From the available templates list, navigate to **ePHASORsim** and select one of the available example models, then click **Finish**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-9b4e56895e66b69bda179f06db33b4cebd2135fa%2Feph-rtlab-examples.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/get-started-with-ephasorsim.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.
