> 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/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs/configure-hscs-oversampling.md).

# Configure HSCS Oversampling

## Overview

**Oversampling Mode** increases the resolution used to evaluate gate-signal transitions.

Rather than evaluating switching events only at HSCS time-step boundaries, HSCS evaluates them at a finer internal resolution.

## Benefits

Oversampling improves:

* Converter linearity
* Duty-cycle resolution
* Switching-frequency resolution
* Dead-time representation

It is particularly beneficial for:

* Resonant converters
* Dual Active Bridge (DAB) converters
* High-frequency power-electronics applications

## Limitations

Oversampling uses FPGA resources that remain available after the primary HSCS computation has completed.

As circuit complexity increases, the available oversampling capability decreases.

Applications containing multiple HSCS instances may therefore obtain less benefit from Oversampling Mode.

The effective oversampling rate can be reviewed in the **Build Report**.

## Recommendations

Enable **Oversampling Mode** when:

* Small duty-cycle variations are important
* Dead-time accuracy is important
* Converter switching frequencies are very high

For most conventional converter applications, leave **Oversampling Mode** disabled unless additional accuracy is required.


---

# 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/model-in-schematic-editor/optimize-the-ehs-circuit/improve-performance-with-hscs/configure-hscs-oversampling.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.
