> 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/pe-add-on-opal-rt/model-in-schematic-editor/library-blocks-reference/system-blocks/high-speed-converter-solver.md).

# High Speed Converter Solver

## Description

The **High Speed Converter Solver (HSCS)** block allows to simulate small power-electronics circuits operating at very high switching frequencies with time steps as low as **32 ns**. It can be used to accelerate selected portions of an eHS Gen 5 circuit or an entire eHS circuit.

The circuit placed inside this block, referred to as the **HSCS circuit**, is simulated by the HSCS solver, while the surrounding **parent eHS circuit** continues to be simulated by the eHS solver.

Only blocks supported by HSCS are available inside the HSCS circuit.

See more details on how to [Improve performance with HSCS](https://www.opal-rt.com/docs/pe-add-on-opal-rt/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs.md) guide.

{% hint style="danger" %}
HSCS requires the parent eHS circuit **Solver Strategy** to be set to **High Performance – Lowest Latency**. As a result, the simulator license must include the **EHS\_HIGH\_PERFORMANCE\_TOKEN** feature with a sufficient number of tokens. The selected firmware must also support the **High Speed Converter Solver**. Verify compatibility in **Simulator Setup** or refer to the firmware documentation.
{% endhint %}

## Parameters

| Parameter                                           | Description                                                                           |
| --------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Time Step (T**<sub>**s**</sub>**)**               | Simulation time step used by HSCS. Set to **Auto** for automatic time-step selection. |
| **Integration method (I**<sub>**m**</sub>**)**      | Numerical integration method used by HSCS.                                            |
| **Number of iterations (It**<sub>**num**</sub>**)** | Additional diode and switch-state iterations performed at each HSCS time step.        |
| **Oversampling mode (Os**<sub>**m**</sub>**)**      | Improves switching-event resolution and converter linearity.                          |
| **Discretization method (D**<sub>**m**</sub>**)**   | Selects the HSCS discretization method.                                               |

## Conserving ports

The **High Speed Converter Solver** block exposes one conserving port for each **Power Port** defined inside the HSCS circuit. The number and configuration of these ports therefore depend on the HSCS circuit design.

When Power Ports are added, removed, or modified inside the HSCS circuit, the corresponding conserving ports on the HSCS block are updated automatically.


---

# 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/pe-add-on-opal-rt/model-in-schematic-editor/library-blocks-reference/system-blocks/high-speed-converter-solver.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.
