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

# Configure DNP3 Slave

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 slave I/O interface

{% stepper %}
{% step %}

### Add a new I/O interface

1. In the **HYPERSIM** tab, click **I/O Interface** in the **Sensors & I/Os** section to open the **I/O Interface Configuration** window.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-881ca3164b1b5fa2d589ecb145163b15e7af8f64%2FDR-hyp-io-interface.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Right‑click **DNP3 Slave** and select **Add**. Keep the default name or enter a custom one. If multiple **DNP3 Slave** are added, each one must have a unique name.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f13cf01ff2df436ff821fe5612962a3ff0b928dd%2Fdr-hyp-dnp3slave-add.jpg?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the general settings

Click the newly added **DNP3 Slave** in the **I/O Interface Configuration** window and configure the general settings.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-f03c60b02a4450b08277f94fd43c1ee2fdf672f9%2FDR-hyp-dnp3sl-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>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://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4476ae575e018dd578bcbc96af9d2905b9cd276a%2FDR-hyp-dnp3sl-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 simulated.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-e094b13b28d053dc88449bdbf5e20a6caea4ed7b%2FDR-hyp-dnp3sl-settings.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-4b1992fbd062c65e34253bc923c4baea579b0205%2FDR-hyp-dnp3sl-settings2.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>ID</strong></td><td>Unique numeric identifier for each DNP3 slave (range: 1–65534).</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>Protocol</strong></td><td>Communication protocol used by the master to reach the slave. <strong>Currently supported:</strong> <code>TCP</code> only.</td></tr><tr><td><strong>TCP port</strong></td><td>TCP port on which the DNP3 slave listens for connections from the master.</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 used to reach the slave’s communication interface. Each slave must use a distinct IP address unless multiple slaves are hosted on the same device, in which case each must use a different TCP port. Can be set to <strong>any</strong> to select the first available IP on the simulator.<br>For local testing on the same simulator, use <strong>127.0.0.1</strong>.</td></tr><tr><td><strong>Slave 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>Master link address</strong></td><td>Identity of the master at the <strong>DNP3 link layer</strong> expected to communicate with the simulated slave.</td></tr><tr><td><strong>Link status period</strong></td><td>Interval at which the slave sends link status requests when no DNP3 frames have been received (keep-alive).</td></tr><tr><td><strong>Validate source address</strong></td><td>Enables validation of the source link address in received frames. If set to 0, only the destination address is validated. If set to 1, both source and destination must match this session.</td></tr><tr><td><strong>Enable self address</strong></td><td>Enables self-addressing per DNP Technical Bulletin 2003‑003. The slave responds to address <strong>0xFFFC</strong> so that the master can automatically discover its address.</td></tr><tr><td><strong>Allow multiple fragment response</strong></td><td>Allows the application to send responses spanning multiple fragments.</td></tr><tr><td><strong>Confirm multiple fragment</strong></td><td>Requests application-layer confirmations for non-final fragments of multi-fragment responses. Confirmations are always required for event responses.</td></tr><tr><td><strong>Send qualifier 7 for activate config response</strong></td><td>Uses qualifier 7 instead of 5B for “activate configuration” responses for backward compatibility with older implementations.</td></tr><tr><td><strong>Set need time in response</strong></td><td>Determines whether the slave sets the Need Time IIN bit at startup and after the clock validity period expires. This prompts the master to perform time synchronization.</td></tr><tr><td><strong>Application confirm timeout (ms)</strong></td><td>Time the slave waits for an application-layer confirmation from the master before retrying unsolicited responses.</td></tr><tr><td><strong>Delete oldest event</strong></td><td>If set to 1, the oldest event is discarded when the event queue is full and a new event arrives.</td></tr><tr><td><strong>Select timeout (ms)</strong></td><td>Maximum permitted time between a Select and the corresponding Operate request before the Select becomes invalid.</td></tr><tr><td><strong>Warm restart delay (ms)</strong></td><td>Time the master must wait after receiving a warm restart response (encoded using a time-delay-fine object, max 65535 ms).</td></tr><tr><td><strong>Cold restart delay (ms)</strong></td><td>Time the master must wait after receiving a cold restart response (encoded using a time-delay-fine object, max 65535 ms).</td></tr><tr><td><strong>Allow unsolicited responses</strong></td><td>Enables or disables unsolicited responses (only for Class 1, 2, and 3 data).</td></tr><tr><td><strong>Send unsolicited responses when online</strong></td><td>Sends unsolicited responses immediately when the session becomes active.</td></tr><tr><td><strong>Unsolicited class mask</strong></td><td>Specifies which data classes are included when unsolicited responses are sent at startup.</td></tr><tr><td><strong>Default variation for type 30 objects</strong></td><td>Default DNP3 variation for type 30 objects (<em>refer to DNP3 documentation for details</em>).</td></tr><tr><td><strong>Default variation for type 32 objects</strong></td><td>Default DNP3 variation for type 32 objects (<em>refer to DNP3 documentation for details</em>).</td></tr><tr><td><strong>Default variation for type 40 objects</strong></td><td>Default DNP3 variation for type 40 objects (<em>refer to DNP3 documentation for details</em>).</td></tr><tr><td><strong>Default variation for type 42 objects</strong></td><td>Default DNP3 variation for type 42 objects (<em>refer to DNP3 documentation for details</em>).</td></tr><tr><td><strong>Event mode for analog inputs</strong></td><td>Event reporting mode for analog inputs: <strong>MOST_RECENT</strong> or <strong>SOE</strong> (sequence of events).</td></tr><tr><td><strong>Event mode for binary inputs</strong></td><td>Event reporting mode for binary inputs: <strong>MOST_RECENT</strong> or <strong>SOE</strong> (sequence of events).</td></tr><tr><td><strong>Maximum number of analog inputs</strong></td><td>Maximum number of analog input events that may accumulate between two polling operations. Determines analog input event buffer size.</td></tr><tr><td><strong>Maximum number of binary inputs</strong></td><td>Maximum number of binary input events that may accumulate between two polling operations. Determines binary input event buffer size.</td></tr><tr><td><strong>Analog inputs scan period (ms)</strong></td><td>Rate at which the slave scans analog inputs for changes. Recommended value: ~10× the fastest expected input variation.</td></tr><tr><td><strong>Binary inputs scan period (ms)</strong></td><td>Rate at which the slave scans binary inputs for changes. Recommended value: ~10× the fastest expected input variation.</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://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-2ee9415b28da7778c20ca8f78080b02fb4463b7d%2FDR-hyp-dnp3sl-data.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Click a data point type (**Analog inputs**, **Binary inputs**, **Double bit binary inputs**, **Analog outputs**, or **Binary outputs**) 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. Configure each data point **Point class** and any parameters specific to that type.

{% hint style="info" %}
In DNP3, **point classes** are used to categorize and prioritize how data points are reported from a slave to a master. Each point is assigned a class that determines when it is polled or included in unsolicited event reporting. **Class 0** represents static or current values returned during full integrity polls. **Class 1** contains high‑priority events for time‑critical or fast‑changing data, **Class 2** holds medium‑priority events often used for periodic updates, and **Class 3** contains low‑priority events representing less urgent or slow‑changing data. Classes 1, 2, and 3 are all eligible for unsolicited responses when enabled.

The **Deadband** (Analog input only) defines the minimum change required for an analog input value to generate a new event. The slave reports the value only if it differs from the last reported value by more than the deadband, preventing small or insignificant variations from triggering events.

The **Default value** (Analog output) is optional (if omitted, the initial value defaults to 0).

When **Operate as trip/close pair** (Binary output only) is **checked**, the **Binary output trip** and the **Binary output close** connectable points are exposed to provide separate *trip* and *close* control points. When **Default value** is **unchecked**, the command uses the **on‑time**. When it is **checked**, the command uses the **off‑time**.
{% endhint %}
{% endstep %}

{% step %}

### Save the configuration

Click **Ok** or **Apply** to save the configuration.
{% 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/hypersim/configure-ios/communication-protocol-ios/dnp3-slave/configure-dnp3-slave.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.
