> 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/readme.md).

# What's New in eHS 3.6!

### Version: 3.6

#### New features

* Support multi core High Speed Converter Solver in Schematic Editor workflow for OP48XX chassis
  * All of our official bitstreams featuring HSCS are now able to
  * Support up to **32 instances of the same HSCS circuits**.
  * Support up to **two different HSCS circuits**, each instantiated up to **16 times**.
* Support BLDC Motor type in PMSM Machine 3 phase Open-end Winding, PMSM Machine 6 phase and PMSM Machine 12 phase
* Support Scaling Transformer in SPS and Schematic Editor workflow

#### Improvements

* Support Versal Selected Edition in all official bitstreams
* Support Macronix chip for latest Versal shipped from Sep 2026

#### Bug fixes

* Fix the Phase parameter of the SineWave Generators that wasn't precise enough.
* Fix a problem in the SineWave Generator, that caused a long step at the 0-crossing value.
* Fix scenario from CPU feature in bitstream
  * OP4815 Power Electronics IOConfig 3 (6A-14)
  * OP4815 SST IOConfig 3 (ED-08)
  * OP4810 Machine Drive IOConfig 3 (7A-07)
* Fix bitstream F6-09 Versal Standard Edition flavor.

#### Known issues

* The scenario from CPU feature is not functional in OP48XX - Versal bitstreams not mentioned above.

{% hint style="info" %}
As of eFPGASIM 3.5, we do not deliver XSG eFPGASIM library by default. If you wish to generate custom bitstreams, please get in touch with the support team.
{% endhint %}


---

# 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/readme.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.
