> 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/constant-param-4-ph.md).

# Constant Param, 4-ph

## Description

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

The **Constant Parameter (CP) 4-ph Line** block, located in the **Network Lines and Cables** library, assumes that line parameters R, L, and C are independent of frequency and do not model skin-effect impacts on phase conductors or ground. The model treats L and C as distributed (ideal line) and lumps R at three locations (R/4 at each end and R/2 in the middle). The shunt conductance G is set to zero. While frequency-dependent (FD) line parameters are important for accurate waveforms and peak values, the CP model is robust, simple, and fast, and is suitable for first-approximation studies.

A transposed or untransposed CP line can be represented by either its sequence components or by its propagation modes with the transformation matrix (Ti) between mode currents and phase currents. Implementation details can be found in \[1].

## Mask parameters

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

| Parameter                                            | Description                                                                                                                                                 |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Description**                                      | Use this field to add information about the component.                                                                                                      |
| **EMTP (.pun) file for line parameters calculation** | Path to the EMTP .pun file containing the line parameters.                                                                                                  |
| **L-C units in EMTP (.pun) file**                    | <p>Select units read from the .pun file. Options:<br>- mH/km, uF/km (L, C) (0)<br>- Ohm/km, uS/km (Xl, 1/Xc) (1)</p>                                        |
| **Line Length**                                      | Length of the line (km), length \[0, 1e64].                                                                                                                 |
| **R**                                                | Per-unit-length resistance for each phase (mode) (Ω/km), R \[-1e64, 1e64].                                                                                  |
| **L**                                                | Per-unit-length inductance for each phase (mode) (H/km), L \[-1e64, 1e64].                                                                                  |
| **C**                                                | Per-unit-length capacitance for each phase (mode) (F/km), C \[-1e64, 1e64].                                                                                 |
| **Base power (perPhase)**                            | Base value for per-unit conversion (MVA) per phase, pBase \[1, 1e64].                                                                                       |
| **Base voltage (rmsLN)**                             | Base value for per-unit conversion (kV rms LN), vBase \[1, 1e64].                                                                                           |
| **Base frequency**                                   | Base value for per-unit conversion (Hz0, fBase \[1, 1e64].                                                                                                  |
| **Continuously transposed line**                     | <p>Transposition selection transp. Options:<br>0 — No (untransposed line);<br>1 — Yes (transposed line).</p>                                                |
| **Transformation matrix**                            | <p>Transformation matrix between mode current and phase current Ti \[-1e64, 1e64].<br>\[Iphase] = \[Ti] × \[Imode]);<br>not used for a transposed line.</p> |

## 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    |
| **net\_3\_1** | Network connection of phase 3 left (+) side |
| **net\_3\_2** | Network connection of phase 3 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(*****1,2,3*****)\_(*****1,2*****)**                  | Bus voltage (V) for each phase (1,2,3,4)                   |
| **I(1,2)\_Node(*****1,2*****)**                                | Current (A) for each phase (1,2,3,4)                       |
| **P(*****1,2*****)\_Node(*****1,2,3,4*****)\_(*****1,2*****)** | Active power (W) for each phase (1,2,3,4) on bus (1,2)     |
| **Q(*****1,2*****)\_Node(*****1,2,3,4*****)\_(*****1,2*****)** | Reactive power (VAR) for each phase (1,2,3,4) on bus (1,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. H. W. Dommel, "Digital computer solution of electromagnetic transients in single and multiphase networks," IEEE Trans. Power App. Syst., vol. pas-88, pp. 388-99, 04/ 1969.


---

# 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/constant-param-4-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.
