> 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-two-area-kundur-system-with-thyristor-controlled-series-compensator-tcsc.md).

# Modified Two-Area Kundur System with Thyristor Controlled Series Compensator (TCSC)

## Description

The **Modified Two-Area Kundur System with Thyristor Controlled Series Compensator (TCSC)** 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 **phasor24\_Kundur2Area**, then click **Finish**.

This demo presents the application of Thyristor Controlled Series Compensator, TCSC, to damp tie-line power oscillations. For this reason a TCSC is installed on the tie-line located between buses 900 and 1200 of the two-area Kundur power system (Figure 1). This model also has four generation units including synchronous machines (GENROE type), exciter (EXAC4 type) and stabilizer (STAB1 type). The TCSC model is equivalent of Series Reactor Model in PSS/e library (CRANIT). The input to the CRANIT controller is the active power of the line measured from bus 900 and the output of the CRANIT is the reactance of the branch.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-78392671b7fe71b6eaf3dd6637ec1336b3b587c2%2FKundur2Area.png?alt=media" alt=""><figcaption><p>Figure 1. - Two-area Kundur system with CRANIT type TCSC on the line between buses 900 &#x26; 1200.</p></figcaption></figure>

The in-port and out-port configurations are given in **phasor24\_Kundur2Area.xlsx** file. Moreover the network data as well as dynamic data are given in phasor24\_Kundur2Area.raw and phasor24\_Kundur2Area.dyr files respectively.

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

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

<details>

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

* Vmag: Voltage magnitude of all the buses (p.u.)
* Vang: Voltage angle of all the buses (degree)
* slip: Speed deviation of all the machines (p.u.)
* Line\_pwr\_P0: CRANIT input signal (Measured active power of line\_900\_to\_1200\_1 (in p.u.) from the sending end, i.e. bus 900
* line\_X: CRANIT output (Reactance of line\_900\_to\_1200\_1 (p.u.)

</details>

<details>

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

* load: Active and Reactive power of the load located on bus 710 (MW, MVar)

</details>

## Requirements

* MATLAB R2019b and later

## Simulation and results

To show the effect of the TCSC a load change scenario is considered. In this way, at t = 1 second, load at bus 710 is increased by 50%. Figure 2 shows the simulation results with and without considering TCSC in the system. The results implies that TCSC was successful to damp the oscillations.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-0c19279f29ed9c2944c1f71ce95497a894518f81%2Fresults.png?alt=media" alt=""><figcaption><p>Figure 2. - Simulation results for the proposed scenario. (a) Active power from buses 900 and 1200. (b) Angular difference between buses 900 and 800. (c) Reactance of the line between buses 900 and 1200.</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/rt-lab/example-models/ephasorsim-example-models/modified-two-area-kundur-system-with-thyristor-controlled-series-compensator-tcsc.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.
