> 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-rlc/shunt-inductor-l.md).

# Shunt Inductor (L)

## Description

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

The **Shunt Inductor (L)** block, located in the **Network RLC** library, models a shunt inductor connected to an electrical bus with configurable connection types and base quantities.

{% hint style="info" %}
By default, this block operates in single-phase mode. When it is connected to a three-phase bus signal, it automatically switches to three-phase operation.
{% endhint %}

## Mask parameters

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

<table><thead><tr><th width="225">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Connection Type</strong></td><td><p>For three-phase shunt elements, select one of the following connection types:</p><ul><li><strong>Ground Y</strong>: one end of the shunt RL element is connected to a bus and the other end to ground.</li><li><strong>Floating Y</strong>: one end of each RLC branch is connected to a phase at the end of the bus; the other ends are tied together but not grounded.</li><li><strong>Delta (triangle)</strong>: the three RL branches are delta-connected; each vertex is connected to a bus phase.</li></ul></td></tr><tr><td><strong>R</strong></td><td>Resistance value for each phase (</td></tr><tr><td><strong>L</strong></td><td>Inductor value for each phase (H)</td></tr><tr><td><strong>Base Power</strong></td><td>Total base power (MVA)</td></tr><tr><td><strong>Base Voltage</strong></td><td>Base voltage (rms). Use line-to-line (LL) if the shunt inductor is connected to a three-phase bus; use line-to-neutral (LN) if only one phase is connected (kV)</td></tr><tr><td><strong>Base Frequency</strong></td><td>Base frequency (Hz)</td></tr><tr><td><strong>Enable User Initial Value</strong></td><td></td></tr><tr><td><strong>Initial Current</strong></td><td>Initial current. This value cannot be modified while the simulation is running (A)</td></tr></tbody></table>

## Conserving ports

<table><thead><tr><th width="219">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>Net_+</strong></td><td>Positive network connection</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.


---

# 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-rlc/shunt-inductor-l.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.
