> 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-39-bus-system-with-induction-generators.md).

# Modified IEEE 39-Bus System with Induction Generators

## Description

The **Modified IEEE 39-Bus System with Induction Generators** 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 **phasor22\_IEEE39\_IM**, then click **Finish**.

This demo shows transient stability simulation for the modified version of IEEE 39-bus power system in phasor01 in which the synchronous generator located at bus 38 is replaced with four induction generators, Im1, Im2, Im3 and Im4. Figure 1 shows single line diagram of this network.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-7300f7bb71e96c11e7c232184ac922b95f90509c%2Fphasor22_IEEE39_IM.png?alt=media" alt=""><figcaption><p>Modified IEEE 39-bus power system with induction generators.</p></figcaption></figure>

As shown in the figure, Im1 and Im2 are initially connected to the network while Im3 and Im4 are disconnected initially. Moreover, Im1 and Im3 are double cage while Im2 and Im4 are single cage type induction machines.

{% hint style="info" %}
**The type of induction machine, i.e. single or double cage, is determined by the value of two parameters T" or X"**. A zero value for any of these two parameters leads to a single cage induction machine. However, if both values are non-zero, the machine is defined as double cage.
{% endhint %}

## Requirements

* MATLAB R2019b and later

## Simulation and results

For the purpose of this demo, machine start-up scenario for the two induction generators Im3 and Im4 is considered. In this way, Im3 and Im4 get connected to the grid at t=1 second.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-0a9ddf758766fc50e415f3cdee8e8213aa01425d%2Fresults.png?alt=media" alt=""><figcaption><p>Simulation results for machine start-up scenario.</p></figcaption></figure>

Based on Figure (a) and Figure (b), right after connecting Im3 and Im4, the two machines act as induction motors and absorb active and reactive power from the grid (negative injection to the grid).

Due to the shortage of reactive power at the time of start-up, the voltage on bus-38 also decreases to below 0.7 p.u (Figure (b)). Meanwhile the energy from the grid gradually accelerates the two induction machines hence their frequency start increasing (Figure (a)). Around t=16.5 seconds however, the frequency of Im3 reaches the network frequency and the induction motor converts to induction generator thereafter. This is shown as sudden change of active power injection from negative to positive value for Im3. The same phenomena happens to Im4 later around t=25 seconds.

The network data as well as in-port and out-port configurations are given in **phasor22\_IEEE39\_IM.xlsx** file.

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

In the "Pins" page of the Excel file the following outgoing and incoming pins are assigned:

<details>

<summary>Outgoing pins (measurements)</summary>

* Vmag: Bus voltage magnitude (p.u.)
* Vang: Bus voltage angle (degrees)
* Pe: Machine's active power injection (p.u.)
* Qe: Machine's reactive power injection (p.u.)
* slip: Machine's frequency deviation (p.u.)
* status: Status of the induction machines

</details>

<details>

<summary>Incoming pin (control command)</summary>

* status: Status of Im3 and Im4

</details>


---

# 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-39-bus-system-with-induction-generators.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.
