> 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/hypersim/configure-ios/communication-protocol-ios/abb-ps935-driver/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **ABB PS935** driver is included by default with HYPERSIM and does not require any additional installation.

## Hardware requirements

The PS935 is a PCIe hardware device that interfaces with an OPAL‑RT simulator through a **MAGMA PCIe expansion chassis**, which hosts the board and provides the required PCIe connectivity. The board requires a **24 V power supply** for operation.

Communication between multiple PS935 devices is performed using **optical fiber links**, enabling distributed hardware configurations. No Ethernet connectivity is involved.

## License requirements

### Simulator license

[Verify that an active HYPERSIM license](https://www.opal-rt.com/docs/hypersim/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the ABB PS935 driver:

| Feature Name | Required Status | Description       |
| ------------ | --------------- | ----------------- |
| PS935        | enabled         | Enables ABB PS935 |

### Workstation license

**No additional feature is required** in the workstation license to run simulations in HYPERSIM using the ABB PS935 driver.

## Supported Features <a href="#supported-features" id="supported-features"></a>

* Configurable using the GUI of HYPERSIM but also using the .io file workflow; both methods yield the same results
* Supports 3 modes:
  * Software loopback
  * Hardware loopback
  * No loopback
* Use of PS935 hardware can be daisy chained
  * Done by connecting the OUT PCIe port of the n<sup>th</sup> PS935 device to the IN PCIe port of the N+1<sup>th</sup> device
  * The interconnection is seamless for the OPAL simulator
  * Each PS935 device is identified by its MAC address (an 8 numeral hexadecimal value)
  * One PS935 HYPERSIM interface is necessary per PS935 device
* Supports exchange of up to 256 floating point values per direction
* Supports exchange of up to 512 binary values per direction

## Limitations <a href="#limitations" id="limitations"></a>

* The board requires to be flashed each time the OPAL-RT simulator interfacing with it it is booted
* Flashing the firmware is only possible after a boot-up of the system i.e. cannot re-program a firmware or change it without having gone through a power-up sequence
* Firmware is not retro-compatible, the firmware used for the PS935 device needs to be compatible with the hardware
* If a problem occurs during the upload of the firmware, the device must be rebooted followed by rebooting the OPAL simulator before attempting the upload again


---

# 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/hypersim/configure-ios/communication-protocol-ios/abb-ps935-driver/requirements-features-and-limitations.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.
