> 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/optimize-the-ehs-circuit/improve-performance-with-hscs.md).

# Improve Performance with HSCS

## Overview

The **High Speed Converter Solver (HSCS)** is an FPGA-based solver designed to simulate small power-electronics circuits at very high switching frequencies.

HSCS operates alongside the **eHS Gen 5** solver and can be used to accelerate simulation by:

* Simulating an entire eHS circuit with HSCS
* Simulating a selected portion of an eHS circuit with HSCS while the remaining circuitry is simulated by eHS (up to two distinct HSCS circuits)
* Simulate multiple instances of one or two HSCS circuits while the remaining circuitry is simulated by eHS

To use HSCS, place the portion of the circuit to be accelerated inside a **High Speed Converter Solver** block. The circuit inside the block is simulated by the **HSCS solver** and configured using its own solver settings, while the rest of the circuit remains simulated by the parent **eHS solver**.

## Requirements

HSCS requires a simulator license with the **EHS\_HIGH\_PERFORMANCE\_TOKEN** and **EHS\_HSCS\_CORE\_TOKEN** features. The selected firmware must also support the **High Speed Converter Solver**. Verify compatibility in **Simulator Setup** or refer to the firmware documentation.

{% hint style="info" %}
HSCS support is currently limited to selected firmware for the **OP4815** platform.
{% endhint %}

## Use HSCS in an eHS circuit

{% stepper %}
{% step %}

### Configure a Simulator Setup

Configure a **Simulator Setup** that uses firmware supporting the **High Speed Converter Solver (HSCS)**.
{% endstep %}

{% step %}

### Define the Solver Settings

HSCS requires the **Solver Strategy** to be set to **High Performance – Lowest Latency**.
{% endstep %}

{% step %}

### Add an HSCS block

Open the **Library Browser**, navigate to **System**, and drag a [High Speed Converter Solver](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) block into the **Work Area.**
{% endstep %}

{% step %}

### Configure the HSCS block

Select the **High Speed Converter Solver** block and configure its parameters.
{% endstep %}

{% step %}

### Build the HSCS circuit

The circuit inside the block, referred to as the **HSCS circuit**, is simulated by the HSCS solver using its own solver settings, while the surrounding **parent eHS circuit** (if any) continues to be simulated by the eHS solver.

When editing an HSCS circuit:

* Only HSCS-supported blocks are available
* Some blocks may use parameters that differ from their eHS counterparts
  {% endstep %}

{% step %}

### Connect the HSCS circuit to the parent eHS circuit

When only a portion of an eHS circuit is simulated by HSCS, interface **power ports** and **decoupling blocks** are required to exchange electrical signals between the independently solved eHS and HSCS circuits.

To create the interfaces:

1. Double-click the **High Speed Converter Solver** block to open the HSCS circuit.
2. Open the **Library Browser** and navigate to **Decoupling**.
3. Add the required decoupling blocks into the HSCS circuit work area. For guidance on selecting and tuning them, refer to [Optimize the Time Step with Decoupling](https://www.opal-rt.com/docs/pe-add-on-opal-rt/model-in-schematic-editor/optimize-the-ehs-circuit/optimize-the-time-step-with-decoupling.md).
4. Open the **Library Browser** and navigate to **System**.
5. Drag **Power Port** blocks into the HSCS circuit, connect them to the decoupling blocks, and configure the **Location** parameter:
   * **Left** for HSCS inputs
   * **Right** for HSCS outputs
6. Return to the parent eHS circuit. The **Power Ports** are automatically mapped to input and output ports on the **High Speed Converter Solver** block.

{% hint style="info" %}
If the entire eHS circuit run inside HSCS:

* No parent eHS circuit is required
* No interface ports are required
* No decoupling blocks are required

The **High Speed Converter Solver** block can be used directly at the top level of the eHS circuit model.

However, all eHS circuit models must contain at least one measurement block at the top level. Therefore, create a small dummy circuit containing a measurement block to satisfy this requirement.
{% endhint %}
{% endstep %}

{% step %}

### Save and validate the model

In Schematic Editor, go to **File** and select **Save**. Then reload the model from <code class="expression">space.vars.cpu\_model\_veristand</code>.

If the circuit exceeds HSCS limits, an error is generated during loading.
{% endstep %}
{% endstepper %}

## Use two HSCS circuits in an eHS circuit

Up to **two distinct HSCS circuits** can be used within a single eHS circuit, allowing selected portions of the circuit to be simulated by HSCS while the remaining circuitry continues to be simulated by eHS.

To add a second HSCS circuit, follow the same procedure described for a single HSCS circuit:

1. Add a second **High Speed Converter Solver** block to the parent eHS circuit.
2. Configure the HSCS block parameters.
3. Build the HSCS circuit inside the block.
4. Create the required interfaces using **Decoupling** and **Power Port** blocks.
5. Connect the HSCS circuit to the parent eHS circuit via these interfaces.
6. Configure and validate the circuit as usual.

Each HSCS circuit has its own solver settings and is simulated independently from the parent eHS circuit and the other HSCS circuit.

## Use multiple instances of HSCS circuits

Although only **two distinct HSCS circuits** can be used within a single eHS circuit, each HSCS circuit can be instantiated multiple times. Up to **16 instances** of the same HSCS circuit can be used in a single eHS circuit.

### Create additional HSCS instances

1. In the top-level schematic, select the **High Speed Converter Solver** block.
2. Copy and paste the block once for each additional circuit instance to be simulated.

Each copied HSCS block:

* Shares the same HSCS circuit definition as the original block.
* Uses the same background color as the original block.
* Is read-only, except for its I/O connections.
* Displays the name and contents of the parent HSCS circuit.
* Automatically reflects changes made to the parent HSCS circuit.

Only the I/O connections can differ between instances.

### Configure instance-specific I/O interfaces

Although all instances share the same circuit topology and parameters, they can use different I/O interfaces for **sources**, **measurements**, and **switch gate signals**.

To configure instance-specific I/O interfaces:

1. Double-click the HSCS instance to open the HSCS circuit.
2. Select a source, measurement, or switch block.
3. Click the arrow next to an I/O parameter to open the **Deep Panel**.
4. Configure the available I/O-connectable parameters as required.

All other parameters are inherited from the original HSCS block and are read-only. Only I/O connections can be configured independently for each instance.

Active I/O connections for each instance can be reviewed and configured from the **I/O** tab.


---

# 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/optimize-the-ehs-circuit/improve-performance-with-hscs.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.
