> 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/get-started-with-sps/current-transformer-saturation.md).

# Current Transformer Saturation

This example shows the measurement distortion due to saturation of a current transformer (CT).

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

## Description

A current transformer (CT) is used to measure current in a shunt inductor connected on a 120 kV network. The CT is rated 2000 A / 5 A, 5 VA. The primary winding, which consists of a single turn passing through the CT toroidal core, is connected in series with the shunt inductor rated 69.3 Mvar, 69.3 kV (120 kV / sqrt(3)), 1 kA rms. The secondary winding consisting of 1 \* 2000/5 = 400 turns is short-circuited through a 1 ohm load resistance. A voltage sensor connected at the secondary reads a voltage which should be proportional to the primary current. In steady state, the current flowing in the secondary is 1000 \* 5 / 2000 = 2.5 A (2.5 Vrms or 3.54 Vpeak read by the voltage measurement block V2).

Open the CT dialog box and observe how the CT parameters are specified. The CT is assumed to saturate at 10 pu and a simple 2-segment saturation characteristic is used.

The primary current reflected on the secondary and the voltage developed across the 1 ohm resistance are sent to trace 1 of the Scope block. The CT flux, measured by the Multimeter block, is converted in pu and sent to trace 2. (1 pu flux = 0.0125 V \* sqrt(2) / (2 \* pi \* 50) = 5.63e-5 V.s)

The switch connected in series with the CT secondary is normally closed. This switch will be used later to illustrate overvoltages produced when the CT secondary is left open.

{% hint style="danger" %}
**Never leave a CT secondary open** while the primary is energized: the example demonstrates large overvoltages produced when the CT secondary is opened.
{% endhint %}

### Simulation

{% stepper %}
{% step %}

### Normal operation

In this test, the breaker is closed at a peak of source voltage (t = 1.25 cycle). This switching produces no current asymmetry. Start the simulation and observe the CT primary current and secondary voltage (first trace of Scope block). As expected the CT current and voltage are sinusoidal and the measurement error due to CT resistance and leakage reactances is not significant. The flux contains a DC component but it stays lower than the 10 pu saturation value.
{% endstep %}

{% step %}

### CT saturation due to current asymmetry

Change the breaker closing time to close at a voltage zero crossing. Use t = 1/50 s. This switching instant will produce full current asymmetry in the shunt reactor. Restart the simulation. Observe that for the first 3 cycles, the flux stays lower than the saturation knee point (10 pu) and the CT voltage output V2 follows the primary current. After 3 cycles, however, the flux asymmetry produced by the primary current causes CT saturation, producing large distortion of the CT secondary voltage.
{% endstep %}

{% step %}

### Overvoltage due to CT secondary opening

Reprogram the primary breaker closing time to t = 1.25/50 s (no flux asymmetry) and change the secondary switch opening time to t = 0.1 s. Restart the simulation and observe the large overvoltage produced when the CT secondary is opened. The flux has a square wave shape chopped at +10 and -10 pu. Large dφ/dt produced at flux inversion generates high voltage spikes (up to ≈250 V).
{% endstep %}
{% endstepper %}

## Command

Example model name: power\_ctsat

{% code lineNumbers="true" %}

```matlab
open('power_ctsat')
```

{% 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/get-started-with-sps/current-transformer-saturation.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.
