> 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/oltc-regulating-transformer.md).

# OLTC Regulating Transformer

This example shows a tap-changing transformer that regulates positive sequence voltage at a 25 kV bus.

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

## Description

The Three-Phase Tap-Changing Transformer (Two-Windings) block is used to model an On Load Tap Changer Transformer (OLTC) that regulates positive-sequence voltage at B2 25-kV bus. The reference voltage is set at 1.0 pu.

## Simulation

Observe OLTC reaction for the following 3 events:

* 1.1 pu over-voltage in 120 kV network at t= 2 sec.
* 0.95 pu under-voltage in 120 kV network at t= 10 sec.
* 0.2 sec single-phase fault at B2 bus at t= 20 sec. OLTC does not react because under-voltage duration is lower than specified Delay (0.4 sec).

{% hint style="info" %}
In order to reduce simulation time, the tap selection time (usually a value between 3 sec and 10 sec) has been shortened to 0.5 sec.
{% endhint %}

## Command

Example model name: power\_TapChangerTransformer

{% code lineNumbers="true" %}

```matlab
open('power_TapChangerTransformer')
```

{% endcode %}


---

# 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/oltc-regulating-transformer.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.
