> 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/hypersim/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 Interface block to the HYPERSIM model

Go to the **Network Tools** library and drag the **ePHASORSIM Interface** block into the HYPERSIM model.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-5aac2459bd27e5900e40188250866c0cbfcf8a7c%2Feph-hyp-ephasorsim-interface-block.png?alt=media" alt=""><figcaption></figcaption></figure>

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

{% step %}

### Open an Excel configuration template file

The power system model integrated into the **ePHASORSIM Interface** block exchanges signals with the surrounding HYPERSIM model through ports defined in an Excel configuration file. This file is required for all workflows.

Use the Excel configuration file included with the **ePHASORSIM\_CO\_SIMULATION** example model as a template and save a copy in your model directory.

1. In HYPERSIM, go to **File > Options**. Under **Open an Example File**, navigate to **How To**, select the **ePHASORSIM\_CO\_SIMULATION.ecf** example model and then click **Open Example**.
2. Choose the folder in which to save a copy of the example model. Once the file is saved, the main modeling interface appears.
3. Double-click the **ePHASORSIM Interface** block and then click **db://phasor26\_PHASOR\_EMT.xlsx**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a5bb4c9cb482d28642b6f28dfe7d37ff47a25b64%2Feph-hyp-xlsx.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Save a copy the phasor **phasor26\_PHASOR\_EMT.xlsx** file to your HYPERSIM 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.

In HYPERSIM, go to **File > Options**. Under **Open an Example File**, navigate to **How To**, select the **ePHASORSIM\_CO\_SIMULATION.ecf** example model and then click **Open Example**.


---

# 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/hypersim/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.
