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

# Select the HSCS Time Step

## Overview

The **Time Step** parameter defines the simulation step used by the **High Speed Converter Solver** block

The default value is **Auto**, which automatically selects the smallest compatible time step based on the HSCS circuit, the parent eHS circuit model, and other integrated solvers. Automatic time-step selection is recommended for most applications.

## Use automatic time-step selection

Automatic time-step selection:

* Chooses the smallest compatible HSCS time step
* Considers the parent eHS circuit and other FPGA solvers
* Is recommended for most applications

The selected time step is reported in the **Build Report** under the **HSCS Solver** section as **Effective Timestep (ns)**.

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

## Configure a manual time step

When manually specifying a time step:

* The value must be between **4 ns** and **4000 ns**
* The eHS time step must be an integer multiple of the HSCS time step
* The achievable minimum time step depends on the circuit complexity and solver settings

Although values as low as **4 ns** can be entered, the minimum achievable time step is currently **32 ns** for a circuit configured with **0 iterations**.

If the configured value is not compatible with the circuit or firmware, an error is generated when the model is loaded.

## Multi-circuit applications

When multiple HSCS circuits are used:

* All HSCS instances must use the same time step
* Each HSCS instance requires **4 ns** to initiate execution

As long as all circuit launches fit within the achievable time step of a single HSCS circuit, the time step does not increase.

For example:

* A circuit capable of running at **32 ns** can support up to **8 instances** without increasing the time step
* A ninth instance increases the minimum achievable time step to **36 ns**

## Recommendations

* Use **Auto** whenever possible
* Select the largest time step that satisfies the application requirements
* Verify the effective time step in the Build Report after every model change
* Reevaluate the time step when changing the number of HSCS instances


---

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