> 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-tools/load-flow-equivalent.md).

# Load Flow Equivalent

## Description

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

The **Load flow equivalent** block, located in the **Network Tools** library, is used when a component is not supported by the load flow algorithm. For example, when importing a Simulink model or developing a network-type UCM that affects the power-flow solution, place a Load flow equivalent next to that component and enter the values that the load flow algorithm must use to compute the network steady-state.

## Mask parameters

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

<table data-search="false"><thead><tr><th width="199.5999755859375">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Description</strong></td><td>Enter any relevant information about the component.</td></tr><tr><td><strong>Type</strong></td><td>Load flow model type. Three options:<br>Swing — Fixed V (PQ balance);<br>PV — Fixed P and V;<br>PQ — Fixed P and Q.</td></tr><tr><td><strong>Voltage</strong></td><td>Load flow constraint (pu).</td></tr><tr><td><strong>Angle</strong></td><td>Load flow constraint (deg).</td></tr><tr><td><strong>Qmin</strong></td><td>Minimum reactive power allowed in the load flow solution (var).</td></tr><tr><td><strong>Qmax</strong></td><td>Maximum reactive power allowed in the load flow solution (var).</td></tr><tr><td><strong>P</strong></td><td>Active power (W).</td></tr><tr><td><strong>Q</strong></td><td>Reactive power (var).</td></tr><tr><td><strong>R</strong></td><td>Internal resistance (ohm).</td></tr><tr><td><strong>L</strong></td><td>Internal inductance (H).</td></tr></tbody></table>

## Conservating ports

<table><thead><tr><th width="200.4000244140625">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>Net_1</strong></td><td>Network connection (supports only 3-phase connections).</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Signals available for monitoring and external I/O connections (via sensors form) <a href="#signals-available-for-monitoring-and-external-i-o-connections-via-sensors-form" id="signals-available-for-monitoring-and-external-i-o-connections-via-sensors-form"></a>

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.

<table><thead><tr><th width="240.4000244140625">Signal</th><th>Description</th></tr></thead><tbody><tr><td><strong>Angbus</strong></td><td>Angle at the connected bus (deg).</td></tr><tr><td><strong>Angint</strong></td><td>Angle before the internal impedance (deg).</td></tr><tr><td><strong>P</strong></td><td>Active power at the connected bus (MW).</td></tr><tr><td><strong>Q</strong></td><td>Reactive power at the connected bus (MVAr).</td></tr><tr><td><strong>Vbus</strong></td><td>Voltage at the connected bus (pu).</td></tr><tr><td><strong>Vint</strong></td><td>Voltage before the internal impedance (pu).</td></tr></tbody></table>


---

# 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-tools/load-flow-equivalent.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.
