> 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/ehs/3.7/model-in-schematic-editor/library-blocks-reference/decoupling-blocks/two-phase-inductive-de-coupling.md).

# Two Phase Inductive Decoupling

## Description

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-729375e89e4f5644e072016ab91a500744f8471d%2Fse-decoupling-2phase-block.png?alt=media" alt="" width="194"><figcaption></figcaption></figure>

The **Single Phase Inductive Decoupling** block separates the circuit into two subcircuits and provides an interface between them equivalent to a series inductor.

{% hint style="info" %}
This block is only available in the eHS library.
{% endhint %}

### Decoupling model <a href="#decoupling-model" id="decoupling-model"></a>

The decoupling block implements a Transmission Line Model (TLM) equivalent of a linking inductor, represented using the Bergeron line model with separate Thévenin circuits on each side.

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-f4e3e28319d96b47be92702a1d9bbdea20acd053%2Fse-decoupling-tlm%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

$$
\begin{aligned}
I\_{\mathrm{right}}\[k] &= G,V\_{\mathrm{left}}\[k-1] + I\_{\mathrm{left}}\[k-1] \\
I\_{\mathrm{left}}\[k] &= G,V\_{\mathrm{right}}\[k-1] + I\_{\mathrm{right}}\[k-1] \\
G &= \frac{T}{L}
\end{aligned}
$$

where **L** is the inductance value and **T** is the circuit time step.

## Parameters <a href="#decoupling-model" id="decoupling-model"></a>

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-867eac030d3e81826a6b15dc6a4c7866119a4f82%2Fse-decoupling-2phase-paramters.png?alt=media" alt="" width="320"><figcaption></figcaption></figure>

| Parameter                                                 | Description                            | Sets feature | I/O & Monitoring |
| --------------------------------------------------------- | -------------------------------------- | ------------ | ---------------- |
| **De-coupling inductance value (L**<sub>**s**</sub>**a)** | Equivalent series inductance value (H) | Yes          | N/A              |
| **De-coupling inductance value (L**<sub>**s**</sub>**b)** | Equivalent series inductance value (H) | Yes          | N/A              |

## Conserving ports <a href="#conserving-ports" id="conserving-ports"></a>

| Port  | Description         |
| ----- | ------------------- |
| **A** | Left positive port  |
| **B** | Left negative port  |
| **Y** | Right positive port |
| **Z** | Right negative port |


---

# 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/ehs/3.7/model-in-schematic-editor/library-blocks-reference/decoupling-blocks/two-phase-inductive-de-coupling.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.
