> 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/rt-lab/configure-ios/communication-protocol-ios/dnp3-slave/requirements-features-and-limitations.md).

# Requirements, Features & Limitations

## Software requirements

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

## Hardware requirements

The DNP3 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, DNP3 can also operate over additional Ethernet ports provided by supported PCIe network cards. Check your hardware modularity options to determine which external PCIe network cards are supported.

## License requirements

### Simulator license

[Verify that an active RT-LAB license](https://www.opal-rt.com/docs/rt-lab/licensing-reference/simulator-license.md) with the following features is installed on the simulator to run simulations using the DNP3 slave protocol:

| Feature Name      | Required Status      | Description                                                                    |
| ----------------- | -------------------- | ------------------------------------------------------------------------------ |
| DP\_DNP3\_SLAVE   | enabled              | Enables DNP3 Slave                                                             |
| 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 DNP3:**\
10 analog inputs + 5 binary inputs + 2 double‑bit binary inputs = **17 data points**.
{% endhint %}

### Workstation license

A workstation license is **not** required to run simulations in RT-LAB using the DNP3 slave protocol.

## Supported features

* Read and write analog data points
* Read and write binary data points
* Read double-bit binary data points
* Read data points in polling mode or unsolicited responses mode
* Connect to multiple slaves
* Operate over TCP/IP
* Configurable network interface
* Configurable DNP3 link addresses
* Configurable read (polling) and write rates

## Limitations

* Only the DNP3 slave endpoint is supported.
* Data point indexes follow the order of definition in the configuration, starting at index 0.
* A maximum of 10 analog outputs and 10 binary outputs are supported per slave.
* RS‑232, RS‑422, RS‑485, and UDP communication links are not supported (TCP/IP only).
* Supported data types are analog inputs, analog outputs, binary inputs, binary outputs, and double‑bit binary inputs.
* Double‑bit binary inputs only support values 0, 1, 2, and 3, which are the only values reported to the DNP3 master.
* CROB command parameters **Clear** and **Queue** are not supported.


---

# 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/rt-lab/configure-ios/communication-protocol-ios/dnp3-slave/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.
