> 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/ehs/model-in-schematic-editor/library-blocks-reference/line-blocks/fd-line-1-12-phases.md).

# FD Line (1-12) Phases

## Description

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-eb06fb3236e6a5f160f0dec3c0505b034c537bce%2FSE_FDline.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

The **FD Line (1-12 Phases)** blocks model a frequency-dependent transmission line with distributed parameters. The line resistance and inductance vary with frequency, enabling accurate representation of transmission line behavior over a wide frequency range.

{% hint style="info" %}
This block is only available in the eHS library.
{% endhint %}

## Parameters

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-254bfd3ff7cb35be90e820da6fca6f3234eb24b8%2FSE_DFlineparam.png?alt=media" alt=""><figcaption></figcaption></figure>

| Parameter                             | Description                            | Sets feature | I/O & monitoring |
| ------------------------------------- | -------------------------------------- | ------------ | ---------------- |
| **Line parameters L**<sub>**p**</sub> | Import `.pun` file for line parameters | No           | N/A              |

### Generate a `.pun` FD Line file

The .pun file is derived using the **HYPERSIM tool** called the "**Transmission line data calculation function**" which takes the line data in .lin format as input. The conductor data is modified by reducing the number of conductors (wires) from 6 to 3, using only the first three lines. Subsequently, by navigating to the "Save and Run this case" tab and changing the current case data file name to "line\_3ph\_rv," and selecting "Run this case to create a model data file for the selected line model," the line data calculation function will initiate the creation of new line data in .pun format for a three-phase transmission line.

The .pun is comprised of 3 main sections. The **line information** in red (number of phases, line length, etc), the **impedance and propagation function residues and poles** in blue and the **transformation matrix data** in gree&#x6E;**.**

<figure><img src="https://3212678799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FABuoXNYgvaoO7wIe3bfO%2Fuploads%2Fgit-blob-216922ba69b63406183ee1640acaaccd77cb0043%2FSE_DSline_ex.png?alt=media" alt=""><figcaption></figcaption></figure>

## Conserving ports

| Port            | Description                                                      |
| --------------- | ---------------------------------------------------------------- |
| **p1 to pN**    | Phase terminals on side 1 of the transmission line               |
| **pN+1 to p2N** | Corresponding phase terminals on side 2 of the transmission line |

***N** is the number of phases of the FD Line block.*

**For example, for the FD Line 2 Phases block:**

| Port   | Description              |
| ------ | ------------------------ |
| **p1** | Phase 1 terminal, side 1 |
| **p2** | Phase 2 terminal, side 1 |
| **p3** | Phase 1 terminal, side 2 |
| **p4** | Phase 2 terminal, side 2 |


---

# 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/ehs/model-in-schematic-editor/library-blocks-reference/line-blocks/fd-line-1-12-phases.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.
