> 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/example-models/ephasorsim-example-models/modified-ieee-123-node-system.md).

# Modified IEEE 123 Node System

## Description

The **Modified IEEE 123 Node System** example can be created by starting a new RT‑LAB project. 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 **phasor10\_IEEE123**, then click **Finish**.

In this example the CYME input file of the IEEE 123-node network \[1] is used with the following modifications:

* The delta-delta connection transformer between bus 61 and 610 is replaced by a wye-wye connection transformer.
* The voltage regulator located on the line between node 25 and 26 as well as the other voltage regulator located on the line between node 9 and 14 are taken away. The rest of the two regulators are substituted by the wye-wye transformer.
* All loads are changed to Yg connection.

Figure below shows the diagram of the network.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-24fb7442c7bb8b5ed7d3b9faf5cd01e63623ec65%2Fphasor10_IEEE123.png?alt=media" alt=""><figcaption><p>IEEE 123-bus network diagram.</p></figcaption></figure>

The in-port and out-port pins are given in **phasor10\_IEEE123.xlsx** file, e.g. the pin for power loss on line between node 35 and 36 is given.

{% file src="/files/2qtyOSFKLzRBjVlL7xDe" %}

{% hint style="info" %}
This model is configured to assign core number 2 for the dynamic simulation on a target. The `EPHASOR_THREADS` environment variable can be revised in the Variables tab of RT-LAB GUI to modify this configuration.
{% endhint %}

## Requirements

* MATLAB R2019b and later

## Simulation and results

The simulation begins from steady state and three disturbances happen in the system as described below:

* At t = 2s: Taps of transformer between buses 160 and 670 are changed from 0 to 8 on three phases.
* At t = 4s: Active and reactive power of load 71 are changed to be equal on phase A.
* At t = 6s: Switch between nodes 197 and 97 will be opened and switch between nodes 151 and 300 will be closed.

There are three types of load in the system: constant power, constant impedance, and constant current loads. The bandwidth of these loads are set to 0.2, which means if the voltage is over 1.2 p.u. or under 0.8 p.u., then the load will change to a constant impedance type.

## Reference

{% file src="/files/TPbLGFkbE4m79S406fSI" %}


---

# 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/example-models/ephasorsim-example-models/modified-ieee-123-node-system.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.
