> 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/modbus-master/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

The **Modbus master** driver is included by default with <code class="expression">space.vars.Software</code> and does not require any additional installation.

## Hardware requirements

The Modbus protocol communicates over Ethernet (TCP/IP) using the simulator’s built-in LAN ports, **eliminating the need for additional hardware**. Standard Ethernet cables are required to establish these connections. For systems requiring extra network interfaces, Modbus can also operate over additional Ethernet ports provided by supported PCIe network cards. Modbus is equally capable of operating in RTU mode using either the motherboard’s RS‑232 connector or dedicated RS‑232/422/485 PCIe cards. Refer to your system’s hardware modularity documentation to determine which external PCIe network and serial cards are supported.

## 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 Modbus master protocol:

| Feature Name       | Required Status      | Description                                                                    |
| ------------------ | -------------------- | ------------------------------------------------------------------------------ |
| DP\_MODBUS\_MASTER | enabled              | Enables Modbus Master                                                          |
| DP\_TOTAL\_NUMBER  | 50 enabled (or more) | Number of activated I/O data points for Ethernet-based communication protocols |

{% hint style="info" %}
A **data point** represents any individual value exchanged with the simulator, such as a boolean, integer, analog value, status, coil, register, phasor, quality bit, timestamp, or event. For Ethernet‑based communication protocols, OPAL‑RT licensing counts each **transmitted or received data value** as **one data point**.

**Example for Modbus:**\
10 holding registers + 8 coils + 6 discrete inputs = **24 data points**
{% endhint %}

### Workstation license

**No additional feature is required** in the workstation license to run simulations in HYPERSIM using the Modbus master protocol.

## Supported features

* Standard registers:
  * Coils
  * Discrete inputs
  * Input registers: The supported data types are UINT16, INT16, UINT32, INT32 and FLOAT32.
  * Holding registers: The supported data types are UINT16, INT16, UINT32, INT32 and FLOAT32.
* TCP and RTU modes.
* Allows multiple slaves instantiation.
* Configurable TCP port when operating over TCP mode.
* Configurable serial port parameters when operating over RTU mode.
* Supports reconnection with master device(s) if a connection is lost.
* Supports triggered read/write for non-cyclic operations.

## Limitations

* Modbus ASCII is not supported
* An OP3310 RS-232/422/485 PCIe serial card is needed in case it is required to communicate with multiple slaves on the same physical bus in RTU mode.


---

# 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/modbus-master/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.
