> 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/examples/phasor-emt-co-simulation/ieee-9-bus-phasor-system-with-emt-feeder.md).

# IEEE 9-Bus Phasor System with EMT Feeder

## Description

The **IEEE 9-Bus Phasor System with EMT Feeder** model, located in **File > Open an Example File > Phasor-EMT Co-Simulation**, based on the IEEE 9-bus system, serves as an example of co-simulation implementation.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-86f3bcbe02d08cf155607caf1a501f60260237d9%2Fco-simulation-phasor-emt-example.png?alt=media" alt=""><figcaption></figcaption></figure>

## Detailed explanation

The system consists of three generators, each connected through a step-up transformer, three static loads, and six transmission lines. All transmission network components are modeled in ePHASORSIM, while a 5-node distribution feeder containing an induction machine is represented in the EMT domain. The distribution feeder is interconnected with the transmission network at Bus 6, as shown in the figures below.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-99b2b72817a55353f03aef460742b388a5e26ff2%2Fco-simulation-phasor-emt-system-connection.png?alt=media" alt=""><figcaption><p>IEEE 9-bus power system and feeder connected to the PHASOR/EMT co-simulation</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-7fa4102e6bd1e29a01508cce0f6a88c3755ac406%2Fco-simulation-distrib-feeder.png?alt=media" alt=""><figcaption><p>Distribution feeder connected on bus 6 of the transmission network</p></figcaption></figure>

In the HYPERSIM implementation, the coupling interface is established at Bus 6, where the positive-sequence phasor voltage magnitude and angle from the transmission-domain model are converted into a three-phase instantaneous voltage source that energizes the EMT distribution feeder. Voltage and current measurements obtained from the EMT domain are subsequently used to compute the active and reactive power exchanged at the interface. These power values are then fed back to the phasor-domain model as dynamic PQ load injections at Bus 6. The co-simulation is executed with a time step of 10 ms for the transmission network (phasor domain) and 20 μs for the distribution feeder (EMT domain). For more information on the methodology used in this example, refer to the \[Couple Phasor and EMT Models]\(../../model-and-simulation/co-simulation/Co-simulation-Phasor-EMT-systems-in-HYPERSIM/couple-phasor-emt-models) section.

## Simulation and Results

The step-by-step development process of this example is described in the [Run a Phasor-EMT Co-Simulation Model](https://github.com/Opal-RT-Technologies/product-docs-hypersim/tree/release-2026.4/model-and-simulation/co-simulation/Co-simulation-Phasor-EMT-systems-in-HYPERSIM/run-phasor-emt-co-simulation-model/README.md). Then, to assess the dynamic performance and numerical stability of the co-simulation, the model is tested under one initialization scenario and two fault scenarios. The system first operates under steady-state conditions to verify that the EMT subsystem, the phasor subsystem, and the coupling interface are initialized correctly. After initialization, a three-phase-to-ground fault is applied at Bus 2 in the EMT subsystem from 1 s to 1.2 s. Once the system returns to steady state, a second three-phase-to-ground fault is applied at Bus 4 in the phasor subsystem from 5.8 s to 5.85 s.

| Scenario                        | Description                                                                   | Fault duration                 |
| ------------------------------- | ----------------------------------------------------------------------------- | ------------------------------ |
| **1: Initialization**           | The EMT subsystem, phasor subsystem, and coupling interface are initialized.  | Coupling established at 0.01 s |
| **2: Fault at the EMT side**    | A three-phase-to-ground fault is applied at BUS2 (69kV) within the EMT system | 1 s to 1.2 s                   |
| **3: Fault at the phasor side** | A three-phase-to-ground fault is applied at BUS4 within the phasor subsystem. | 5.8 s to 5.85 s                |

The results present the dynamic response of both the EMT and phasor domains under each simulated event. Key variables are monitored, including the coupling bus voltage, the active and reactive power (P–Q) exchanged at the interface, the instantaneous waveforms on the EMT side, and the voltage magnitudes in the phasor domain.

It is observed that disturbances introduced in one subsystem propagate through the coupling interface and are reflected in the corresponding variables of the other subsystem. For instance, transient events occurring in the EMT domain are captured in the phasor-domain responses through variations in voltage and power exchange, while disturbances originating in the phasor domain influence the EMT-side waveforms. This bidirectional interaction confirms that the coupling mechanism operates in a closed-loop manner, effectively transferring dynamic information between both domains and preserving the overall physical behavior of the system. Although the example considered is relatively simple, this initial demonstration highlights the potential of the methodology to be extended to more complex and large-scale power systems, where detailed EMT modeling can be selectively combined with phasor-domain simulations to achieve both high accuracy and computational efficiency.

### Scenario 1: Initialization

This model is prepared to be initialized from load flow solution. Then, before analyzing the dynamic response of the co-simulation, the initialization of the EMT subsystem cab be verified by recording data using Data Logger. The following figure illustrates the initial instantaneous voltages at each bus within the EMT subsystem. It can be observed that the system starts from steady-state conditions, and the connection between the EMT and phasor subsystems, established at 0.01 s, occurs smoothly. As shown in the figure, the initialization is satisfactory.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-749fe113e7e2ec4a7bed4083da823ad2d0458188%2Fco-simulation-phasor-emt-results1.png?alt=media" alt=""><figcaption><p>Initial instantaneous voltages at each bus within the EMT subsystem</p></figcaption></figure>

### Scenario 2: Fault at the EMT side

In this scenario, a three-phase-to-ground fault is applied at Bus 2 in the EMT subsystem from 1 s to 1.2 s. The EMT-domain results show the expected fault current and voltage sag near the faulted bus. The disturbance is also reflected in the phasor-domain subsystem through the active and reactive power quantities exchanged at the coupling interface.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-74c2a402af043c9a9c9da84be7c7efe8b6815231%2Fco-simulation-phasor-emt-results2.png?alt=media" alt=""><figcaption><p>Fault current within the EMT subsystem</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-d85e5150c5c9b1ec7ec8b0a11ccc6c8a4add7456%2Fco-simulation-phasor-emt-results3.png?alt=media" alt=""><figcaption><p>Instantaneous voltage magnitude on BUS 04 within the EMT subsystem</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a8c5abca7fe345b9d3cd6e45cea5d75850a3c604%2Fco-simulation-phasor-emt-results4.png?alt=media" alt=""><figcaption><p>Phasor and EMT voltages at boundary BUS 6</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-719ac8f7d4f8d64afa76fd7657542f3844a51bd0%2Fco-simulation-phasor-emt-results5.png?alt=media" alt=""><figcaption><p>PHASOR subsystem inputs, PQ quantities, during fault in EMT system from 1 - 1.2s</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-6525aed4357b63750e66fc19f288cd967577d5b9%2Fco-simulation-phasor-emt-results6.png?alt=media" alt=""><figcaption><p>PHASOR Subsystem phasor bus voltages during fault in EMT system from 1 - 1.2s</p></figcaption></figure>

### Scenario 3: Fault at the phasor side

In this scenario, a three-phase-to-ground fault is applied at Bus 4 in the phasor subsystem from 5.8 s to 5.85 s. The phasor-domain disturbance produces a voltage variation at the coupling bus, which is converted into an instantaneous three-phase source for the EMT subsystem. The EMT feeder response is observed through the instantaneous branch current, EMT bus voltages, and PQ quantities at the interface.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c808ddff694fdca9848e3d37090c44da135c83d8%2Fco-simulation-phasor-emt-results7.png?alt=media" alt=""><figcaption><p>Boundary bus voltages at boundary BUS 6 during fault at PHASOR subsystem from 5.8 – 5.85s</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-c165deca064c013af332bc2bd7329685f3a5b79f%2Fco-simulation-phasor-emt-results8.png?alt=media" alt=""><figcaption><p>Instantaneous current at RL branch and instantaneous voltage at BUS 04 within the EMT subsystem during fault at PHASOR subsystem from 5.8 – 5.85s</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-307a6e3af064a9227d15ade73d096f0b0be3dafe%2Fco-simulation-phasor-emt-results9.png?alt=media" alt=""><figcaption><p>PHASOR subsystem inputs, PQ quantities during fault at PHASOR subsystem from 5.8 – 5.85s</p></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-ea9115d9f638b00c7dd832f905bbb4f55896facc%2Fco-simulation-phasor-emt-results10.png?alt=media" alt=""><figcaption><p>PHASOR Bus phasor voltages during fault at PHASOR subsystem from 5.8 – 5.85s</p></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/hypersim/examples/phasor-emt-co-simulation/ieee-9-bus-phasor-system-with-emt-feeder.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.
