> 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-loads/pq-load-with-load-flow.md).

# PQ Load with Load Flow

## Description

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

The **PQ Load with Load-Flow** block, located in the **Network Loads library**, models a three-phase load using equivalent RLC branches. Each phase can include an equivalent resistance (P → R), an equivalent inductance (Q > 0 → L), and an equivalent capacitance (Q < 0 → C) connected either in parallel or, when Q > 0, as an RL series. Two RLC connection types are supported: RLC parallel and RL series. The element operates in both load-flow and non-load-flow modes and is similar to the model available in EMTP-RV.

### Load model

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

The PQ load with load-flow consists of the parallel combination of equivalent R, L and C branches and the series combination of equivalent R and L branches. The following rules are applied:

* If P=0 and Q=0, the element becomes disconnected in all solution methods.
* The **RL series** inductance equivalent is calculated using $$L = \frac{V\_{\text{base}}^2 \cdot Q}{\omega \cdot (P^2 + Q^2)}$$ and the resistance value is $$R = \frac{V\_{\text{base}}^2 \cdot P}{P^2 + Q^2}$$
* The resistance value in the **parallel combination** is given by $$R = \frac{V\_{base}^2}{P}$$
  * When Q>0, the inductance value in the parallel combination becomes $$L(Q > 0) = \frac{V\_{\text{base}}^2}{\omega \cdot Q}$$
  * When Q<0, the capacitance value in the parallel combination becomes $$C(Q < 0) = \frac{|Q|}{\omega \cdot V^2}$$

### Load-flow model

The load-flow model equations of this load are given by:

$$
P\_{\text{constraint}} = P \left\[ \frac{V\_{\text{load-flow}}}{V\_{\text{base}}} \right]^{N\_P} \ Q\_{\text{constraint}} = Q \left\[ \frac{V\_{\text{load-flow}}}{V\_{\text{base}}} \right]^{N\_Q}
$$

The P<sub>constraint</sub> and Q<sub>constraint</sub> power become the load-flow constraints for the model. The V<sub>load-flow</sub> is the actual voltage magnitude solution on the load bus. The P and Q are the values specified in the mask as “Active Power (P)” and “Reactive Power (Q)”, respectively.

$$
R + j \cdot \omega \cdot L = \frac{V\_{\text{base}}^2}{P - j \cdot Q} \\
\text{therefore} \space R = \frac{V\_{\text{base}}^2 \cdot P}{P^2 + Q^2}\\
\text{and} \space  L = \frac{V\_{\text{base}}^2 \cdot Q}{\omega \cdot (P^2 + Q^2)}
$$

## Mask parameters

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

| Parameter               | Description                                                                                                            |
| ----------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **RLC connection type** | <ul><li>RLC Parallel: RL parallel (when Q > 0) or RC parallel (when Q < 0)</li><li>RL Series: RL series only</li></ul> |
| **Base voltage**        | Base value for PU conversion (kV)                                                                                      |
| **Base frequency**      | Base value for PU conversion (Hz)                                                                                      |
| **Active power (P)**    | 3-phase active power (MW)                                                                                              |
| **Reactive power (Q)**  | 3-phase reactive power (Mvar)                                                                                          |
| **Np**                  | Active power coefficient for load-flow constraints calculation                                                         |
| **Nq**                  | Reactive power coefficient for load-flow constraints calculation                                                       |

## Conserving ports

| Port       | Description                                                |
| ---------- | ---------------------------------------------------------- |
| **net\_1** | \*\*Network connection (supports only 3-phase connections) |

## 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                |
| ------------ | -------------------------- |
| **I(a,b,c)** | Current for each phase (A) |


---

# 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-loads/pq-load-with-load-flow.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.
