> 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-master/configure-dnp3-master.md).

# Configure DNP3 Master

When working with communication protocols, it is recommended to begin by configuring the protocol through the **I/O Interfaces** section in <code class="expression">space.vars.Software</code> before proceeding with other steps.

## Configure the DNP3 master I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

In RT-LAB Project Explorer, right-click **I/O Interfaces**, select **New I/O Interface**, and choose **DNP3 Master**. Double-click the newly created interface to begin configuration.
{% endstep %}

{% step %}

### Configure the general settings

In the **Folders** list, click **General** and configure the general settings.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-2ef478bc58d6464be727bcd70db7b331aa79c3fa%2FDR-rtlab-dnp3m-gen.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="165">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Use an RT core for asynchronous computation</strong></td><td><strong>Checked:</strong> Reserves a dedicated real-time CPU core for communication, allowing more slaves, phasors, analog, and digital signals.<br><strong>Unchecked:</strong> Defaults to core 0.</td></tr><tr><td><strong>Enable verbose mode</strong></td><td><strong>Checked:</strong> Displays the full configuration during model loading for debugging.<br><strong>Unchecked:</strong> Suppresses detailed output.</td></tr><tr><td><strong>Protocol</strong></td><td>Communication protocol used by the DNP3 master. <strong>Currently supported:</strong> <code>TCP</code> only.</td></tr><tr><td><strong>Link address</strong></td><td>Identity of the master at the <strong>DNP3 link layer</strong>. Must be distinct from all slaves, and slaves must be configured with this master address as their expected destination when replying.</td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> Allows the model to run even if the I/O interface is not compatible with the hardware configuration. Connections are initialized, but the interface performs no actions.<br><strong>Unchecked:</strong> Troubleshoot without hardware or prepare a model for a future hardware platform.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Manage slaves: add, remove, rename, or reorder

Click **Slaves** and use:

* **+** icon to add slaves
* **–** icon to remove slaves
* **Arrow** icons to reorder slaves

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-c0946768b6d2ed7c5f2bd36a277d5b485b2cc917%2FDR-rtlab-dnp3m-slave.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the slave(s) settings

Click a slave under the **Slaves** folder to configure its settings. Repeat this step for each additional slave that needs to be reached.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-1f9bf72f656d02ff2cf259de615c4ea9b1e6d7a4%2FDR-rtlab-dnp3m-settings.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="160">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Link address</strong></td><td>Identity of the slave at the <strong>DNP3 link layer</strong>. Must be unique for each slave.</td></tr><tr><td><strong>Channel name</strong></td><td>Name assigned to the DNP3 channel. Used only for logging and debugging purposes.</td></tr><tr><td><strong>NIC name</strong></td><td>Network interface name. Select the correct interface based on your <strong>System Description Document</strong> or Linux <code>ifconfig</code> command. Network interface name. For local testing on the same simulator, use the loopback interface <strong>lo</strong>.</td></tr><tr><td><strong>IP address</strong></td><td>IP address of the DNP3 slave to be reached by the master. This IP address must not conflict with the simulator’s IP address or any other device on the network. Each physical device must have a unique IP address. Multiple logical slaves may share the same IP address if they are hosted on the same device. For local testing on the same simulator, use <strong>127.0.0.1</strong>.</td></tr><tr><td><strong>TCP port</strong></td><td>TCP port on which the DNP3 slave is listening for a connection.</td></tr><tr><td><strong>Read mode</strong></td><td>Defines how the master reads data points from the slave:<br>• <strong>Event polling</strong> or <strong>Integrity polling</strong>: Master requests data at the rate specified by <strong>Polling rate (ms)</strong>.<br>• <strong>Unsolicited responses</strong>: Slave sends updates when values change, reducing bandwidth usage. Use polling if the slave does not support unsolicited responses.</td></tr><tr><td><strong>Analog write rate (ms)</strong></td><td>Interval (in milliseconds) at which the master sends analog point values to the slave.</td></tr><tr><td><strong>Binary write rate (ms)</strong></td><td>Interval (in milliseconds) at which the master sends binary point values to the slave.</td></tr><tr><td><strong>Polling rate (ms)</strong></td><td>Interval (in milliseconds) at which the master requests analog and binary point values from the slave. Used only if <strong>Read mode</strong> is set to polling and at least one data point is configured for reading.</td></tr><tr><td><strong>Promiscuous</strong></td><td>Indicates if the slave interacts with other DNP3 masters:<br>• <strong>True</strong>: Slave interacts with other masters; master uses <strong>select-and-operate</strong> method.<br>• <strong>False</strong>: Slave interacts only with this master; master uses <strong>direct-operate</strong> method.<br>• <strong>Unknown</strong>: No info; master defaults to <strong>select-and-operate</strong> for safety.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Configure the slave(s) data points

1. Expand a slave to reveal it's data point types.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-e63115a01fdb9ed4514730975d13914d83eb48d0%2FDR-rtlab-dnp3m-data.png?alt=media" alt="" width="480"><figcaption></figcaption></figure>

2. Click a data point type (**Analog inputs**, **Binary inputs**, **Analog outputs**, **Binary outputs**, or **Double bit binary inputs**) and use:

* **+** icon to add data points
* **–** icon to remove data points
* **Arrow** icons to reorder data points

{% hint style="info" %}
Inputs and outputs are defined from the master’s perspective. For example, analog input data points represent values received from the slave by the master.
{% endhint %}

3. Assign a **unique address** to each data point. Optionally, set a **Default value** (if omitted, the initial value defaults to 0).
   {% endstep %}

{% step %}

### Save the configuration

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-44bd03ce3c41f8ba5c990b61c29b38c9b80ae5f2%2FDR-rtlab-save.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

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