> 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/library-blocks-reference/network-lines-and-cables/frequency-dependent-2-ph.md).

# Frequency Dependent, 2-ph

## Description

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

The **Frequency Dependent line 2-ph** block, located in the **Network Lines and Cables** library, represents transmission lines with frequency-dependent distributed parameters. The details regarding the model implementation can be found in \[1].

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9230c4e6367b6a10bcb8535ae164edd06e0594d8%2Fimage%20(400).png?alt=media" alt="" width="432"><figcaption><p>Equivalent circuit</p></figcaption></figure>

### Data of a 2-phase FD Line Model <a href="#frequencydependent-2-ph-thedataofa2-phasefdlinemodel" id="frequencydependent-2-ph-thedataofa2-phasefdlinemodel"></a>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-010e6b6d89ede5215d5b5c53265656a41463216d%2Fimage%20(1111).png?alt=media" alt="" width="290"><figcaption><p>Geometrical data of a DC transmission line example</p></figcaption></figure>

The calculation of the electrical parameters of a line from its geometrical parameters can be done with the [Line Data](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/network-lines-and-cables/line-data.md) auxiliary module. The resulting EMTP output file (\*.pun) contains the electrical line parameters required by HYPERSIM. You can enter values manually, but it is recommended to load the .pun file into the data form.

<details>

<summary>Calculation of the parameters for the FD line model example</summary>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-177196d5adf1a5b89ebd168261f4365a3da9a6ab%2Fimage%20(1112).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-5ea4dd2c81b264b930c4eb53ea70c70ced83821b%2Fimage%20(1113).png?alt=media" alt=""><figcaption></figcaption></figure>

</details>

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-33c68fc07e0df9d32d1da9fc927d0c0c0a958aaa%2FFD2.jpg?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="General" %}

| Parameter                                          | Description                                                                                                                       |
| -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Description**                                    | Component description.                                                                                                            |
| **EMTP (.pun) file for line parameters**           | The location (path) of the EMTP file (.pun) containing the line parameters.                                                       |
| **Transformation matrix**                          | Transformation matrix (6 × 6), Ti \[-1e64, 1e64].                                                                                 |
| **Line Length**                                    | The length of the line (km), length \[0, 1e64].                                                                                   |
| **Number of poles for the weighting function**     | Number of poles for each phase (mode) of the propagation function, nA \[0, 1, ..., 39, 40].                                       |
| **Number of poles for the impedance function**     | Number of poles for each phase (mode) of the characteristic impedance function, nZ \[0, 1, ..., 39, 40].                          |
| **First coefficient for characteristic impedance** | First coefficient for each phase (mode) of the characteristic impedance (resistance at infinite frequency) (Ω) Ro \[-1e64, 1e64]. |
| **Propagation delay**                              | Propagation delay for each phase (s) To \[-1e64, 1e64].                                                                           |
| {% endtab %}                                       |                                                                                                                                   |

{% tab title="Impedenace" %}
|Parameter | Description | |-----------------|----------------------||**Impedance function coefficients**|Residues of the impedance function for each phase, KZ \[-1e64, 1e64].| |**Impedance function poles**|Poles of the impedance function for each phase PZ \[-1e64, 1e64].|
{% endtab %}

{% tab title="Weighting" %}
|Parameter | Description | |-----------------|----------------------||**Weighting function coefficients**|Residues of the weighting (propagation) function for each phase, KA \[-1e64, 1e64].| |**Weighting function poles**|Poles of the weighting (propagation) function for each phase, PA \[-1e64, 1e64].|
{% endtab %}
{% endtabs %}

## Conserving ports

|Port | Description | |-----------------|----------------------||**net\_1\_1**|Network connection of phase 1 **left (+)** side| |**net\_1\_2**|Network connection of phase 1 **right** side| |**net\_2\_1**|Network connection of phase 2 **left (+)** side| |**net\_2\_2**|Network connection of phase 2 **right** side|

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.

Additional signals are also available and are listed below with their descriptions.

| Signal                                                                           | Description                                       |
| -------------------------------------------------------------------------------- | ------------------------------------------------- |
| **V\_Node(phase&#x20;*****1, phase 2*****)\_(*****1,2*****)**                    | Bus voltage (V) for each phase (phase 1, phase 2) |
| **I(phase 1*****, phase 2*****)*****Node(phase 1, phase 2)*****(*****1,2*****)** | Current (A) for each phase (phase 1, phase 2)     |

{% hint style="info" %}
(1,2) indicates the bus name at each end of the line (1 for the left (+) side and 2 for the right side).
{% endhint %}

## References

1. J. R. Marti, "Accurate modelling of frequency-dependent transmission lines in electromagnetic transient simulations," IEEE Trans. Power App. Syst., vol. PAS-101, pp. 147-55, 01/1982.


---

# 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/library-blocks-reference/network-lines-and-cables/frequency-dependent-2-ph.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.
