> 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/benchmarks/kundur-4-machine-power-system.md).

# Kundur 4 Machine Power System

## Description

The **Kundur 4‑Machines** example, located in **File > Open an Example File > Benchmarks**, is based on the Kundur book example on page 813 \[1] and is designed to study low‑frequency electromechanical oscillations in large interconnected power systems. The model includes two symmetrical areas linked by two 230 kV, 220 km lines. To achieve a unity load‑voltage profile, 187 Mvar of shunt capacitance is added in each area, consistent with the Simscape setup \[2].

The objectives are to validate steady‑state operation, analyze inter‑area oscillations, and compare system responses with different power system stabilizer (PSS) configurations and disturbances.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-508f7fe8e4def83fab89f50290fd92d309921faf%2Fimage%20(1384).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

This example model does not require any additional hardware or licenses.

## Detailed explanation

Each area contains two identical round‑rotor synchronous machines rated 20 kV/900 MVA. Each machine is controlled by an SCRX exciter, a TGOV1 governor, and a selectable power system stabilizer (PSS1A or PSS4B). SM2 in area 1 is the slack machine, while the other machines operate as PV units. Each generator produces approximately 700 MW. Loads are modeled as constant impedances, with power split such that area 1 exports 413 MW to area 2. With SM2 as the slack machine, the reference load‑flow sets all generators to about 700 MW. Controller parameters are tuned for steady‑state stability.

The stabilizer selection is controlled by the constant “To\_select\_PSS” located at the bottom left of the schematic. The default value is 2. Options are:

<table><thead><tr><th width="158">Constant value</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>No power system stabilizer</td></tr><tr><td>1</td><td>Use PSS4B</td></tr><tr><td>2</td><td>Use PSS1A</td></tr></tbody></table>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2cea698025d8a6a3afc5fad7ed6aec83883de7fb%2Fimage%20(1385).png?alt=media" alt=""><figcaption><p>Subsystem contents showing the synchronous machine and its controllers.</p></figcaption></figure>

The following table lists the machine load‑flow results:

<table><thead><tr><th>Machine name</th><th width="90">Type</th><th width="119">Voltage (pu)</th><th>Angle (deg)</th><th>P (MW)</th><th width="104">Q(MW)</th></tr></thead><tbody><tr><td>SM1</td><td>PV</td><td>1.0</td><td>10.19</td><td>700</td><td>91.54</td></tr><tr><td>SM2</td><td>Swing</td><td>1.0</td><td>0.00</td><td>700.5</td><td>117.28</td></tr><tr><td>SM3</td><td>PV</td><td>1.0</td><td>-15.87</td><td>719</td><td>81.87</td></tr><tr><td>SM4</td><td>PV</td><td>1.0</td><td>-26.49</td><td>700</td><td>82.21</td></tr></tbody></table>

## Simulation and results

### Scenario 1: EFD perturbation

This scenario perturbs the exciter output that feeds the Efd\_i input of a selected synchronous machine. It provides a simple way to assess and tune machine controllers. By default, a gain of 1.1 is applied for 0.5 s starting at t = 5 s.

You can adjust these parameters inside the machine subsystem (Gain1 and DelayOn1). Select the target machine using the “Perturb\_selection” constant at the bottom left of the schematic (default = 1):

<table><thead><tr><th width="180">Constant value</th><th>Description</th></tr></thead><tbody><tr><td>0</td><td>No perturbation anywhere</td></tr><tr><td>1</td><td>Perturb EFD of SM1</td></tr><tr><td>2</td><td>Perturb EFD of SM2</td></tr><tr><td>3</td><td>Perturb EFD of SM3</td></tr><tr><td>4</td><td>Perturb EFD of SM4</td></tr></tbody></table>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a9066a4b65069f9593eec7a8096171e36bdeffd7%2Fimage%20(1386).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e37859ff19998a297680398b13e0869561ca5af9%2Fimage%20(1387).png?alt=media" alt=""><figcaption></figcaption></figure>

Comparing the SM1 terminal‑voltage response across stabilizer options shows: PSS4B provides the best settling time; PSS1A yields the least overshoot but the longest settling time. PSS1A can be further tuned to improve the response.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fef63ab03201f2f51365b1212743aaecf1658ae4%2Fimage%20(1388).png?alt=media" alt=""><figcaption></figcaption></figure>

### Scenario 2: Short‑circuit test

The model includes a short‑circuit test. Enable it by checking the trigger option in the associated ScopeView template (Trig is unchecked by default).

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f9c0a3c3921f202b854929e73c47aa42202cdf8f%2Fimage%20(1389).png?alt=media" alt=""><figcaption></figcaption></figure>

The default fault is a three‑phase‑to‑ground fault of 1e‑3 ohms applied at t = 5 s at bus 9 (mid‑intersection), followed by tripping Dline1 and Dline2 by opening breakers BR1 and BR2 at t = 5.1 s. At t = 25 s, the line breakers reclose to allow rerunning the scenario.

Before running this scenario, set Perturb\_selection to 0 to disable Scenario 1.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-3b122d5305e301f234816bd70dc6e4143bfaa808%2Fimage%20(1390).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-54940aff5ce1213081b82334b6aaacd4a05ad245%2Fimage%20(1391).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2cb85be88c32e19c682a2d1f174299608f1cff99%2Fimage%20(1392).png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9f640b311ec9dd57d5845a94b5eef2b557f5248d%2Fimage%20(1393).png?alt=media" alt=""><figcaption></figcaption></figure>

Without a power system stabilizer, the system becomes unstable; with PSS1A, the system remains stable but exhibits large voltage oscillations; with PSS4B, the system maintains voltage stability and settles well.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8e4fdf2e22c9a67cfeef07f2dd7260029301ba20%2Fimage%20(1394).png?alt=media" alt=""><figcaption></figcaption></figure>

## References

\[1] P. Kundur, Power system stability, and control, vol. 7. McGraw-hill New York, 1994, Example 12.6, p. 813.

\[2] I. Kamwa, Performance of Three PSS for Interarea Oscillations, SimPowerSystems Demo, Hydro-Québec.


---

# 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/benchmarks/kundur-4-machine-power-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.
