> 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/switches-blocks/h-bridge-converter.md).

# H-Bridge Converter

## Description

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-0bb34a5bd47c02170ac018e35f87c11c6f9187b8%2Fse-h-bridge-converter-block.png?alt=media" alt=""><figcaption></figcaption></figure>

The **H-Bridge Converter** block models an H-bridge topology composed of two half-bridge legs.

The integrated implementation of both half-bridges within the HSCS solver enables FPGA resource optimizations. These optimizations rely on the assumption that a shoot-through condition in any leg produces an equivalent effect to a shoot-through condition in any other leg.

{% hint style="info" %}
This block is supported **only** by the High-Speed Converter Solver (HSCS).
{% endhint %}

{% hint style="danger" %}
This block **cannot be used in eHS-only circuits**.
{% endhint %}

## Parameters

<figure><img src="https://521571437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo99Izmvvw5eHT4ldzI4g%2Fuploads%2Fgit-blob-e006c9d8d6f3bd388ed4150f9a704c5bfd15ed47%2Fse-h-bridge-converter-parameters-hscs.png?alt=media" alt=""><figcaption></figcaption></figure>

| Parameter                                             | Description                                                               | Sets feature | I/O & Monitoring                                                                                   |
| ----------------------------------------------------- | ------------------------------------------------------------------------- | ------------ | -------------------------------------------------------------------------------------------------- |
| **Internal on resistance (R**<sub>**on**</sub>**)**   | The switch internal on resistance, in ohms (Ω).                           | Yes          | N/A                                                                                                |
| **Internal off Resistance (R**<sub>**off**</sub>**)** | The switch internal off resistance, in ohms (Ω).                          | Yes          | N/A                                                                                                |
| **Gate control signal (g**<sub>**1**</sub>**)**       | The signal to control on/off state of the upper switch of the first arm.  | No           | <p>From <code class="expression">space.vars.cpu\_model\_veristand</code><br>From Digital Input</p> |
| **Gate control signal (g**<sub>**2**</sub>**)**       | The signal to control on/off state of the lower switch of the first arm.  | No           | <p>From <code class="expression">space.vars.cpu\_model\_veristand</code><br>From Digital Input</p> |
| **Gate control signal (g**<sub>**3**</sub>**)**       | The signal to control on/off state of the upper switch of the second arm. | No           | <p>From <code class="expression">space.vars.cpu\_model\_veristand</code><br>From Digital Input</p> |
| **Gate control signal (g**<sub>**4**</sub>**)**       | The signal to control on/off state of the lower switch of the second arm. | No           | <p>From <code class="expression">space.vars.cpu\_model\_veristand</code><br>From Digital Input</p> |

## Conserving ports

| Port   | Description    |
| ------ | -------------- |
| **p1** | Positive port  |
| **p2** | First AC port  |
| **p3** | Second AC port |
| **n1** | 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/switches-blocks/h-bridge-converter.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.
