> 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/3.7/model-in-schematic-editor/library-blocks-reference/line-blocks/pi-section-line.md).

# Pi Section Line

## Description

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-4c19771fc86dd66653f3937e8967fbaa6b4b3e89%2FSE_Pi_sectionline_block.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Pi Section Line** blocks models a single‑phase transmission line using lumped π‑sections. In a transmission line, resistance, inductance, and capacitance are assumed to be uniformly distributed along the line.

The operating frequency $$f$$ must remain below the maximum frequency range of the π‑section line model to ensure accurate results. An approximation of this maximum frequency is given by the following equation:

$$
f\_{max}=\frac{Nb \cdot v}{8 \cdot Length} \\\[8pt]
v=\frac{1}{\sqrt{LC}}
$$

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

## Parameters

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-791d4b88450b4f800373fa35e8b5032de59e733e%2FSE_pisection_param.png?alt=media" alt=""><figcaption></figcaption></figure>

| Parameter                      | Description                                                                | Sets feature | I/O & monitoring |
| ------------------------------ | -------------------------------------------------------------------------- | ------------ | ---------------- |
| **Number of PI sections (Nb)** | The number of PI sections.                                                 | Yes          | N/A              |
| **Frequency f (Hz)**           | Frequency at which per unit length *r*, *l*, *c* parameters are specified. | Yes          | N/A              |
| **Resistance (R)(Ω/km)**       | The resistance per unit length of the line.                                | Yes          | N/A              |
| **Inductance (L)(H/km)**       | The inductance per unit length of the line.                                | Yes          | N/A              |
| **Capacitance (C)(F/km)**      | The capacitance per unit length of the line.                               | Yes          | N/A              |
| **Line length (Length)(km)**   | Length of the line.                                                        | Yes          | N/A              |

## Conserving ports

| Port   | Description                              |
| ------ | ---------------------------------------- |
| **p1** | First terminal of the transmission line  |
| **p2** | Second terminal of the transmission line |
| **g1** | Ground reference terminal                |


---

# 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/3.7/model-in-schematic-editor/library-blocks-reference/line-blocks/pi-section-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.
