> 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/time-and-frequency-domain-testing-of-a-single-phase-line.md).

# Time and Frequency Domain Testing of a Single Phase Line

This example shows time domain and frequency domain performance of a distributed parameter line model and a PI section line model.

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

## Description

A 200 km line is connected to a 1 kV, 60 Hz infinite source. The line is deenergized and then reenergized after 2 cycles. The simulation is performed simultaneously with two different line models:

* Distributed parameter line
* PI section line consisting of two 100 km sections

Currents at the sending end and voltages at the receiving end are compared for the two line models. Impedance Measurement blocks are connected at the open end of both lines in order to compare their frequency responses.

## Simulation

{% stepper %}
{% step %}

### Steady-state

Open the Powergui block and select **Steady-State Voltages and Currents** to display the voltage and current phasors. Observe that the values obtained with the two models are the same.
{% endstep %}

{% step %}

### Time domain comparison

Open the two scopes and start the simulation. Observe the difference in current and voltage waveforms at breaker opening and reclosing. Note the sharp edges of the distributed parameter model. These voltage and current steps, which are due to travelling wave reflections at line ends, are filtered by the PI model.
{% endstep %}

{% step %}

### Frequency domain comparison

Open the Powergui block and select **Impedance vs Frequency Measurement**. A new window appears, listing the two Impedance Measurement blocks Z\_Dist and Z\_PI connected to your circuit. Note that parameters are set to compute impedance in the 0:2000 Hz frequency range by steps of 2 Hz. Using the Ctrl key, select both Z\_Dist and Z\_PI in the upper right window. Then, click on the Display button. The two impedances are computed and displayed on the same graph.

The distributed parameter line shows a succession of poles and zeros equally spaced every 486 Hz. The first pole occurs at 243 Hz, corresponding to frequency f = 1 / (4\*T), where:

{% code overflow="wrap" lineNumbers="true" %}

```
T = travelling time = length * sqrt(L*C) = 200 * sqrt(2.137e-3 * 12.37e-9) = 1.028 ms
```

{% endcode %}

The PI section line only shows two poles because it consists of two PI sections. Impedance comparison shows that a two-PI line gives a good approximation of the distributed line for the 0–350 Hz frequency range.
{% endstep %}
{% endstepper %}

## Command

Example model name: power\_monophaseline

{% code lineNumbers="true" %}

```matlab
open('power_monophaseline')
```

{% 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/time-and-frequency-domain-testing-of-a-single-phase-line.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.
