> 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.md).

# Phasor-Domain with ePHASORSIM

## Introduction to ePHASORSIM

ePHASORSIM is OPAL-RT's real-time **phasor-domain simulation** solver for large-scale power system studies. It enables the real-time execution of third-party applications such as **PSS®E**, **CYME**, and **PowerFactory**, while also supporting standalone simulation through a native component library.

Designed for transmission and distribution networks, ePHASORSIM can simulate **systems with over 100,000 nodes at millisecond-level time steps**. It calculates voltage and current magnitudes, phase angles, power flows, and machine dynamics directly in the phasor domain. Enabling efficient system-level analysis and validation of protection, control, monitoring, and energy management applications.

ePHASORSIM also provides a Python API for RT-LAB, enabling programmatic interaction with the solver, including parameter updates and result retrieval. Refer to [ePHASORSIM API](https://www.opal-rt.com/docs/rt-lab/automation-api-and-scripting/python-ephasorsim-api.md) for details.

## ePHASORSIM Solver block

To use **ePHASORSIM**, **the phasor-domain power system model is created separately from the Simulink model**. The network can be imported from a supported third-party software package or developed using the **ePHASORSIM native components library**.

The model is integrated into the simulation through the **ePHASORSIM Solver** block, which interfaces the power system model with the surrounding Simulink environment.

An Excel configuration file is used to define the I/O pins used to exchange signals with the surrounding model.

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

## Key applications

1. **HIL and WAMPAC Validation**\
   Perform Hardware-in-the-Loop (HIL) testing, validate EMS and SCADA interfaces, and develop Wide Area Monitoring, Protection and Control (WAMPAC) applications.
2. **Flexible I/O and Protocol Integration**\
   Connect external systems using industry-standard protocols such as C37.118 (PMU/PDC), Modbus, and DNP3, as well as custom analogue and digital I/O interfaces.
3. **Extensible Modelling with FMUs**\
   Integrate custom components through Functional Mock-up Units (FMUs), including Modelica-based models, to extend the native component library.
4. **EMS Application and Control Algorithm Testing**\
   Validate grid control applications, including Automatic Generation Control (AGC) and load-shedding strategies, in a real-time simulation environment.
5. **PMU Stream Generation and PDC Integration**\
   Generate realistic synchrophasor data streams and interface with Phasor Data Concentrators (PDCs) and monitoring platforms.
6. **Microgrid and Renewable Integration Studies**\
   Assess network behaviour under high penetration of distributed energy resources (DERs) and varying operating conditions.
7. **Controller Design and Validation**\
   Design, tune, and validate controllers such as Automatic Voltage Regulators (AVRs) and turbine governors within full network simulations.


---

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