> 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/smart-power-simulation-software-sps/example-models/power-transmission-and-distribution/thyristor-controlled-series-capacitor-tcsc.md).

# Thyristor Controlled Series Capacitor (TCSC)

This example shows the Thyristor Controlled Series Capacitor (TCSC) test system.

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-a1b2a3a30acea95cf19744dd0e918f7f919ed00e%2Ftyristor_control_seri_capa_example.png?alt=media" alt=""><figcaption></figcaption></figure>

## Description

A TCSC is placed on a 500kV, long transmission line, to improve power transfer. Without the TCSC the power transfer is around 110MW, as seen during the first 0.5s of the simulation when the TCSC is bypassed. The TCSC consists of a fixed capacitor and a parallel Thyristor Controlled Reactor (TCR) in each phase. The nominal compensation is 75%, i.e. using only the capacitors (firing angle of 90deg). The natural oscillatory frequency of the TCSC is 163Hz, which is 2.7 times the fundamental frequency. The test system is described in \[1].

The TCSC can operate in capacitive or inductive mode, although the latter is rarely used in practice. Since the resonance for this TCSC is around 58deg firing angle, the operation is prohibited in firing angle range 49deg - 69deg. Note that the resonance for the overall system (when the line impedance is included) is around 67deg. The capacitive mode is achieved with firing angles 69-90deg. The impedance is lowest at 90deg, and therefore power transfer increases as the firing angle is reduced. In capacitive mode the range for impedance values is approximately 120-136 Ohm. This range corresponds to approximately 490-830MW power transfer range (100%-110% compensation). Comparing with the power transfer of 110 MW with an uncompensated line, TCSC enables significant improvement in power transfer level.

To change the operating mode (inductive/capacitive/manual) use the toggle switch in the control block dialog. The inductive mode corresponds to the firing angles 0-49deg, and the lowest impedance is at 0deg. In the inductive operating mode, the range of impedances is 19-60 Ohm, which corresponds to 100-85 MW range of power transfer level. The inductive mode reduces power transfer over the line. A constant firing angle can also be applied and the same limits will apply as above.

### TCSC Control

When TCSC operates in the constant impedance mode it uses voltage and current feedback for calculating the TCSC impedance. The reference impedance indirectly determines the power level, although an automatic power control mode could also be introduced.

A separate PI controller is used in each operating mode. The capacitive mode also employs a phase lead compensator. Each controller further includes an adaptive control loop to improve performance over a wide operating range. The controller gain scheduling compensates for the gain changes in the system, caused by the variations in the impedance.

The firing circuit uses three single-phase PLL units for synchronization with the line current. Line current is used for synchronization, rather than line voltage, since the TCSC voltage can vary widely during the operation.

## Simulation

Run the simulation and observe waveforms on the main variables scope block. The TCSC is in the capacitive impedance control mode and the reference impedance is set to 128 Ohm. For the first 0.5s, the TCSC is bypassed using the circuit breaker, and the power transfer is 110 MW. At 0.5s TCSC begins to regulate the impedance to 128 Ohm and this increases power transfer to 610MW. Note that the TCSC starts with alpha at 90deg to enable lowest switching disturbance on the line.

### Dynamic Response

At 2.5s a 5% change in the reference impedance is applied. The response indicates that TCSC enables tracking of the reference impedance and the settling time is around 500ms. At 3.3s a 4% reduction in the source voltage is applied, followed by the return to 1p.u. at 3.8s. It is seen that the TCSC controller compensates for these disturbances and the TCSC impedance stays constant. The TCSC response time is 200ms-300ms.

Note: Using the Simulink® Accelerator™ can speed up the execution of this model by approximately 9 times.

## Command

Example model name: power\_tcsc

{% code lineNumbers="true" %}

```matlab
open('power_tcsc')
```

{% endcode %}

## Reference

\[1] D.Jovcic, G.N.Pillai "Analytical Modelling of TCSC Dynamics" IEEE® Transactions on Power Delivery, vol 20, Issue 2, April 2005, pp. 1097-1104


---

# 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/smart-power-simulation-software-sps/example-models/power-transmission-and-distribution/thyristor-controlled-series-capacitor-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.
