> 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/overview/software-compatibilities.md).

# Software Compatibilities

<details>

<summary><strong>Use eHS in RT-LAB (Schematic Editor Workflow)</strong></summary>

Required software:

* S-Function driver: RT-LAB 2024.1 or later
* OpalBoards driver: RT-LAB 2025.1.3 or later
* Schematic Editor 3.8.2
* Unified Database 4.10.1

</details>

<details>

<summary><strong>Use eHS in RT-LAB (SPS Workflow)</strong></summary>

Required software:

* RT-LAB 2024.1 or later
* MATLAB 2018b, 2019b, or 2021a–2024b

Notes:

* Schematic Editor and Unified Database are not required when using the SPS workflow.

</details>

<details>

<summary><strong>Use eHS in HYPERSIM</strong></summary>

Required software:

* HYPERSIM 2025.2 and later
* Schematic Editor 3.8.0
* Unified Database 4.10.0

</details>

<details>

<summary><strong>Generate an eHS Firmware</strong></summary>

Required software:

* RT-XSG 3.13.1
* MATLAB 2018b to 2025b
* Xilinx Vivado Suite System Generator 2018.1–2023.1 or 2024.1

Notes:

* Firmware generation requires RT-XSG and the Xilinx toolchain.
* These tools are not required to run existing eHS firmware.

</details>


---

# 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/overview/software-compatibilities.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.
