> 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/blocks-functions-tools/power-transmission-and-distribution/lines/distributed-parameters-line-frequency-dependent.md).

# Distributed Parameters Line (Frequency-Dependent)

## Description

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

The **Distributed Parameters Line (Frequency-Dependent)** block, located in the **OPAL-RT SPS Software/Power Grid Elements** library, implements a multiphase distributed parameter line model with high-fidelity frequency-dependent parameters. It performs accurate transient response simulations for a wide frequency range (typically from DC to 100 kHz or more).

The geometry of the line and the frequency-dependent model parameters are defined in a MAT-file that is associated with the block. The MAT-file must be edited with the **Power Line Parameters** app, which computes the RLC line parameters for a defined range of frequencies and applies a fitting algorithm that converts the line parameters into a rational model. Rational fitting for this model is performed by using the vector fitting (VF) procedure. For more information on the phase domain line model and the state-space analysis, see \[1].

## Ports

### Conserving

<table data-header-hidden><thead><tr><th width="250.08892822265625">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>Cons 1</strong> — Electric terminal<br>SPS electrical</td><td>SPS electrical conserving port associated with terminal 1 on the sending end of the line.</td></tr><tr><td><strong>Cons 2</strong> — Electric terminal<br>SPS electrical</td><td>SPS electrical conserving port associated with terminal 2 on the sending end of the line.</td></tr><tr><td><strong>Cons 3</strong> — Electric terminal<br>SPS electrical</td><td>SPS electrical conserving port associated with terminal 3 on the sending end of the line.</td></tr><tr><td><strong>Cons 4</strong> — Electric terminal<br>SPS electrical</td><td>SPS electrical conserving port associated with terminal 1 on the receiving end of the line.</td></tr><tr><td><strong>Cons 5</strong> — Electric terminal<br>SPS electrical</td><td>SPS electrical conserving port associated with terminal 2 on the receiving end of the line.</td></tr><tr><td><strong>Cons 6</strong> — Electric terminal<br>SPS electrical</td><td>SPS electrical conserving port associated with terminal 3 on the receiving end of the line.</td></tr></tbody></table>

## Parameters

<table data-header-hidden><thead><tr><th width="249.77783203125">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Edit geometry parameters</strong> — Opens MAT file<br>(default)</td><td>Opens the Power Line Parameters app for the specified MAT file that contains geometrical parameters of an overhead line. Opens the Power Cable Parameters app for the specified MAT file that contains geometrical parameters of a cable arrangement.</td></tr><tr><td><strong>File name</strong> — Name of MAT file<br>Line_735kV.mat (default) | string</td><td>Name of a MAT file that defines the geometry of the line or cable and the frequency-dependent model parameters. If the MAT file is not on the MATLAB® path, specify the full path name of the file.</td></tr><tr><td><strong>Browse</strong> — Browse for file<br>(default)</td><td>Select a MAT file from the directory browser.</td></tr><tr><td><strong>Line length (km)</strong> — Line or cable length<br>100 (default) | positive scalar</td><td>This read-only parameter is the value of the DATA.LineLength variable saved in the specified MAT file. This parameter is the length of the line, in km.</td></tr><tr><td><strong>Number of phases</strong> — Number of phases defined for line or cable<br>3 (default) | positive integer</td><td>This read-only parameter is the value of the DATA.Phases variable saved in the specified MAT file. This parameter is the number of phases defined for the line.</td></tr><tr><td><strong>Frequency range</strong> — Frequency range of line or cable parameters<br>1.00e-02 Hz to 1.00e+05 Hz, 141 points. (default)</td><td>This read-only parameter is the value of the DATA.FrequencyRange variable saved in the specified MAT file. This parameter is a detailed description of the frequency range of the internal model.</td></tr><tr><td><strong>Comments</strong> — Complementary information<br>example of a 735 KV three-phase line... (default)</td><td>This read-only parameter displays the contents of the GUI.Comments variable saved in the specified MAT file. This text provides complementary information about the line geometry and the type of conductors.</td></tr><tr><td><strong>Measurements</strong> — Measure voltages<br>None (default) | Phase-to-ground voltages</td><td>Select None to make no measurements. Select Phase-to-ground voltages to measure the sending end and receiving end voltages for each phase of the line model. Place a Multimeter block in your model to display the selected measurements during simulation. In the <strong>Available Measurements</strong> list box of the Multimeter block, the measurement is identified by a label followed by the block name:</td></tr></tbody></table>

Measurements table:

| Measurement                             | Label      |
| --------------------------------------- | ---------- |
| Phase-to-ground voltages, sending end   | Us ph1 gnd |
| Phase-to-ground voltages, receiving end | Ur ph1 gnd |


---

# 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/blocks-functions-tools/power-transmission-and-distribution/lines/distributed-parameters-line-frequency-dependent.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.
