> 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/facts-and-hvdc/unified-power-flow-control-upfc.md).

# Unified Power Flow Control (UPFC)

## Description

The **UPFC** example, located in **File > Open an Example File > FACTS & HVDC**, demonstrates a UPFC composed of series and shunt converters with their controllers. Each converter uses four three-level inverters fed by four phase-shifting zig‑zag transformers. The shunt converter operates as a STATCOM, while the series converter regulates power flow. The UPFC is installed between buses B\_1 and B\_2 in a 500 kV transmission system. Each converter is rated 100 MVA and uses a 48‑pulse GTO-based topology. The shunt converter conduction angle (Sigma) is set to 172.5 degrees to move dominant harmonics to higher orders and achieve quasi‑sinusoidal bus voltage.

The objective is to control active and reactive power exchange between the two buses.

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

## Requirements

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

{% hint style="danger" %}
**The example does not work with the icc compiler on RedHat and CentOS**.
{% endhint %}

## Detailed explanation

Configuration summary:

* UPFC location: between buses B\_1 and B\_2 in a 500 kV system.
* Converter ratings: two 100 MVA, 48‑pulse GTO-based converters (series and shunt).
* Converter structure: each converter consists of four three-level inverters supplied through four phase‑shifting zig‑zag transformers.
* Operating roles: shunt converter as STATCOM; series converter in power flow control mode.
* Conduction angle: Sigma = 172.5 degrees on the shunt converter to improve waveform quality.

## Simulation and results

On the **Pref\_Qref\_Vref block**, make sure that for the active power the constant value is 6 pu, in the delay Td=0.5s, Ton=100s and the addition parameter has gain value of g1=-1, g2=1. Similarly, for the reactive power, make sure the constant value is -0.6 pu, in the delay Td=1s, Ton=100s and the additional parameter has gain value of g1=1.3, g2=1.

On the **UPFC block**, the “Shunt converter control” tab put the Sigma parameter with a value of 172.5 degrees. Also, set on the tab “General” the operation mode as Auto (Power Flow Control). By selecting those parameters the system will control the active and reactive power flowing between the two connected buses. The initial and final parameters correspond to a pu/100 MVA base.

**Run the simulation** and open the Scopeview template. Observe on the first page the results of the active and reactive power, compared with their references.

The acquisition parameters are set to run a run of 1.5 seconds. At the beginning P=600 MW, Q=-60 MVar. After 0.5 seconds P is set to 500 MW. At 1 second Q is ramped up to 70 MVar. The parameters of the “Series converter control” tab are set by default, for the rate limiter section, to “active power rising/falling slew rate” (10/-10), “reactive power rising/falling slew rate” (15/-15)

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-335f376e8b957d9e960f0d5ebbfa4451769fb74c%2Fimage%20(107).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-56394fae3a29a52810382e162dbb5ee38b94a54d%2Fimage%20(108).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-7ae8bd37ff332200b1d541b8dc58798db1680251%2Fimage%20(109).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-7c2058bf08e03958ad40cda37c4da0958c53d83c%2Fimage%20(110).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-e7ab45945fed5a1fc85f90da94b2feb5a8b6bd53%2Fimage%20(111).png?alt=media" alt=""><figcaption></figcaption></figure>

## Reference

OPAL-RT SMART POWER SIMUALTION - [Unified Power Flow Controller (UPFC)](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/example-models/power-transmission-and-distribution/unified-power-flow-controller-upfc.md) Example


---

# 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/facts-and-hvdc/unified-power-flow-control-upfc.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.
