> 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/smart-power-simulation-software-sps/blocks-functions-tools/basics/passives/three-phase-parallel-rlc-branch.md).

# Three-Phase Parallel RLC Branch

## Description

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-96fdd41194ed52ca2253ad0dccd72fdc89ac7a42%2F3P_parallel_RLC_branch_block.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Three-Phase Parallel RLC Branch** block, located in the **OPAL-RT SPS Software/Passives** library, implements three balanced branches consisting each of a resistor, an inductor, a capacitor, or a parallel combination of these. Use the **Branch type** parameter to select elements you want to include in each branch.

Negative values are allowed for resistance, inductance, and capacitance.

## Parameters

<table><thead><tr><th width="150">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Branch type</strong></td><td>Select the elements you want to include in the branch. The <strong>R</strong> letter defines the resistor, the <strong>L</strong> letter defines the inductor, and the <strong>C</strong> letter defines the capacitor. Select <strong>Open circuit</strong> to define an open circuit (R=inf, L=inf, C=0). Only existing elements are displayed in the block icon. Default is <code>RLC</code>.</td></tr><tr><td><strong>Resistance R</strong></td><td>The branch resistances, in ohms (Ω). Default is 1.</td></tr><tr><td><strong>Inductance L</strong></td><td>The branch inductances, in henries (H). Default is 1e-3.</td></tr><tr><td><strong>Capacitance C</strong></td><td>The branch capacitances, in farads (F). Default is 1e-6.</td></tr><tr><td><strong>Measurements</strong></td><td>Select Branch voltages to measure the three voltages across the Three-Phase Parallel RLC Branch block terminals.<br>Select Branch currents to measure the three total currents (sum of R, L, C currents) flowing through the Three-Phase Parallel RLC Branch block. Select Branch voltages and currents to measure the three voltages and the three currents of the Three-Phase Parallel RLC Branch block.<br>Default is None.<br>Place a Multimeter block in your model to display the selected measurements during the simulation. In the <strong>Available Measurements</strong> list box of the Multimeter block, the measurements are identified by a label followed by the block name.</td></tr></tbody></table>

### Measurement labels

| Measurement     | Label |
| --------------- | ----- |
| Branch voltages | Ua:   |
| Branch currents | Ia:   |


---

# 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/smart-power-simulation-software-sps/blocks-functions-tools/basics/passives/three-phase-parallel-rlc-branch.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.
