> 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-12-ph.md).

# Constant Param, 12-ph

## Description

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

The **Constant parameter (CP) line (12-phase)** block, located in the **Network Lines and Cables** library, assumes that line parameters R, L, and C are independent of frequency (no skin effect on phase conductors or ground). The model treats L and C as distributed (ideal line) and R as lumped at three locations (R/4 at each end and R/2 in the middle). The shunt conductance G is zero. Although frequency dependence (as in the FD model) is important for accurate waveforms and peaks, the CP model is robust, simple, and fast, making it suitable for first-approximation studies.

A transposed or untransposed CP line is represented by either a) its sequences, or b) its propagation modes and the transformation matrix (Ti) between mode currents and phase currents. See \[1] for implementation details.

The 12-phase CP model simulates a quadruple-circuit line or four lines sharing the same right of way. Its parameters are the same as for 3-phase lines, except that the modal transformation matrix for double transmission lines is 12x12 because each conductor bundle is modeled as a separate phase.

The propagation delay is calculated as follows:

$$
Propagation\_delay=length\_of\_line \times \sqrt{L\[i] \times C\[i]}
$$

where i denotes each phase, and L and C are the per-unit-length inductance and capacitance.

{% hint style="danger" %}
When the propagation delay is smaller than the time step, the Constant Param block is automatically replaced by an equivalent PI line.
{% endhint %}

If the **Transposed parameter is set to yes**, the following warning appears in the console:

{% code overflow="wrap" %}

```
WARNING in line: : The propagation delay ( X ) is less than the sample time ( Y ). A PI line is automatically used.
```

{% endcode %}

If the Transposed parameter is set to no, a similar error message appears.

## Mask parameters

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

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

| Parameter                                            | Description                                                                                                                                                               |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Description**                                      | Use this field to add information about the component.                                                                                                                    |
| **EMTP (.pun) file for line parameters calculation** | The path to the EMTP file (pun file) containing the line parameters.                                                                                                      |
| **L-C units in EMTP (.pun) file**                    | <p>Select units from :<br>- mH/km, uF/km (0) — Inductance (L) and capacitance (C)<br>- Ohm/km, uS/km (1) — Inductive reactance (Xl) and capacitive susceptance (1/Xc)</p> |
| **Line Length**                                      | The 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 (per phase)**                           | Base value for PU conversion \[MVA total], pBase \[1, 1e64]                                                                                                               |
| **Base voltage (rmsLN)**                             | Base value for PU conversion \[kV rms LN], vBase \[1, 1e64]                                                                                                               |
| **Base frequency**                                   | Base value for PU conversion \[Hz], fBase \[1, 1e64]                                                                                                                      |
| **Continuously transposed line**                     | <p>Transposition transp<br>- No (0): Untransposed line<br>- Yes (1) : 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>                 |
| {% endtab %}                                         |                                                                                                                                                                           |

{% tab title="Line generator" %}
The electrical parameters of CP lines can be calculated using the Line Generator.\
For more information see [Line Generator](https://www.opal-rt.com/docs/hypersim/model-and-simulation/optimize-the-model/use-parameter-generators/line-parameters.md).
{% endtab %}
{% endtabs %}

## Conserving ports

| Port                 | Description                                                             |
| -------------------- | ----------------------------------------------------------------------- |
| **net\_1\_1(a,b,c)** | Network connection of phases (a,b,c) of the **left (+)** side of line 1 |
| **net\_1\_2(a,b,c)** | Network connection of phases (a,b,c) of the **right** side of line 1    |
| **net\_2\_1(a,b,c)** | Network connection of phases (a,b,c) of the **left (+)** side of line 2 |
| **net\_2\_2(a,b,c)** | Network connection of phases (a,b,c) of the **right** side of line 2    |
| **net\_3\_1(a,b,c)** | Network connection of phases (a,b,c) of the **left (+)** side of line 3 |
| **net\_3\_2(a,b,c)** | Network connection of phases (a,b,c) of the **right** side of line 3    |
| **net\_4\_1(a,b,c)** | Network connection of phases (a,b,c) of the **left (+)** side of line 4 |
| **net\_4\_2(a,b,c)** | Network connection of phases (a,b,c) of the **right** side of line 4    |

## 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(a,b,c)1\_Node1\_(1,2)** | Bus voltage for each phase (a,b,c) of line 1 (V) |
| **V(a,b,c)2\_Node2\_(1,2)** | Bus voltage for each phase (a,b,c) of line 2 (V) |
| **V(a,b,c)3\_Node3\_(1,2)** | Bus voltage for each phase (a,b,c) of line 3 (V) |
| **V(a,b,c)4\_Node4\_(1,2)** | Bus voltage for each phase (a,b,c) of line 4 (V) |
| **I(a,b,c)1Node1(1,2)**     | Current for each phase (a,b,c) of line 1 (A)     |
| **I(a,b,c)2\_Node2\_(1,2)** | Current for each phase (a,b,c) of line 2 (A)     |
| **I(a,b,c)3\_Node3\_(1,2)** | Current for each phase (a,b,c) of line 3 (A)     |
| **I(a,b,c)4\_Node4\_(1,2)** | Current for each phase (a,b,c) of line 4 (A)     |

{% hint style="info" %}
(1,2) indicates the bus 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-12-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.
