> 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/iec-60870-5-104-slave/configure-iec-60870-5-104-slave.md).

# Configure IEC 60870-5-104 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 IEC 60870-5-104 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 **IEC 60870-5-104 Slave** and select **Add**. Keep the default name or enter a custom one. If multiple **IEC 60870-5-104 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-857b3221e9b25383cea2fd47af092e2f593d98ef%2Fdr-hyp-iec104-add.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the general settings

Click the newly added **IEC 60870-5-104 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-97eaa25b3ce93a29886a5f2e2d64a22deab15503%2FDR-hyp-iec104-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> The driver reserves a dedicated real‑time CPU core for its communication tasks, allowing it to handle a larger number of slaves efficiently.<br><strong>Unchecked:</strong> The communication system runs on core 0 alongside the operating system.</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> Only standard log messages are shown.</td></tr><tr><td><strong>Enable virtual mode</strong></td><td><strong>Checked:</strong> Allows the model to execute even if the I/O interface does not match the hardware configuration. All connections are initialized, but the interface performs no communication. Useful for troubleshooting without hardware or preparing models for future systems.<br><strong>Unchecked:</strong> The interface operates normally and requires compatible hardware.</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-97eaa25b3ce93a29886a5f2e2d64a22deab15503%2FDR-hyp-iec104-gen.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 device that needs to be reached.

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

<table><thead><tr><th width="140">Parameter</th><th>Value (Description)</th></tr></thead><tbody><tr><td><strong>Mode</strong></td><td>Only <strong>TCP</strong> is available.or <strong>RTU</strong>.</td></tr><tr><td><strong>TCP port</strong></td><td>Specify the TCP port used for communication. When multiple IEC 60870‑5‑104 slaves are simulated on the same target IP address, each slave must use a different TCP port. Slaves may share the same TCP port only when IP aliasing is used. In all cases, each slave must have a unique ASDU address.</td></tr><tr><td><strong>Ethernet adapter</strong></td><td>Network interface name. Select the correct interface based on your <strong>System Description Document</strong> or Linux <code>ifconfig</code> command.</td></tr><tr><td><strong>IP address</strong></td><td>IP address of the slave. This can be set to <strong>AUTO</strong> or to the simulator IP address when a dedicated IP is not required. When multiple slaves share the same simulator IP address, each must use a different TCP port. If a specific IP address is provided, the driver creates an IP alias on the selected network interface and binds the slave to it, allowing multiple slaves to be accessed using distinct IP addresses. In all cases, each slave must have a unique ASDU address.</td></tr><tr><td><strong>ASDU address</strong></td><td>Application Service Data Unit address (1-255) of the slave. Must always be different from one slave device to another.</td></tr><tr><td><strong>COT size (byte)</strong></td><td>Number of octets of the COT field (1 or 2). The master has to select the same COT field size to communicate with the slave device.</td></tr><tr><td><strong>Thread delay (ms)</strong></td><td>Delay between iterations of the communication thread. This thread updates the IEC 60870‑5‑104 slave database by reading model outputs and handling event recording and timestamping, preventing non‑deterministic delays in the real‑time simulation. The delay controls the thread execution rate and is applied after each iteration. It may be set to zero if required, but since the thread runs on CPU core 0 by default, a minimum delay of 1 ms is recommended to allow other threads on the same core to execute.</td></tr><tr><td><strong>Cyclic message interval (ms)</strong></td><td>Cyclic group reporting interval. This defines how often the IEC 60870‑5‑104 slave transmits values for points assigned to the Cyclic group.</td></tr><tr><td><strong>Event scan (ms)</strong></td><td>Rate at which the slave database is scanned.</td></tr><tr><td><strong>Event buffer size</strong></td><td>Each data type uses an event buffer to record value changes. This setting defines the maximum number of stored events per data type; when the buffer is full, the oldest events are discarded.</td></tr><tr><td><strong>Single point event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of single point values are reported to the master.<br><strong>Unchecked:</strong> Single point value changes are not reported spontaneously</td></tr><tr><td><strong>Double point event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of double point values are reported to the master.<br><strong>Unchecked:</strong> Double point value changes are not reported spontaneously.</td></tr><tr><td><strong>Regulating step event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of regulating step values are reported to the master.<br><strong>Unchecked:</strong> Regulating step value changes are not reported spontaneously.</td></tr><tr><td><strong>Bitstring event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of bitstring values are reported to the master.<br><strong>Unchecked:</strong> Bitstring value changes are not reported spontaneously.</td></tr><tr><td><strong>Normalized event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of normalized values are reported to the master.<br><strong>Unchecked:</strong> Normalized value changes are not reported spontaneously.</td></tr><tr><td><strong>Scaled event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of scaled values are reported to the master.<br><strong>Unchecked:</strong> Scaled value changes are not reported spontaneously.</td></tr><tr><td><strong>Floating event scan</strong></td><td><strong>Checked:</strong> Spontaneous changes of floating‑point values are reported to the master.<br><strong>Unchecked:</strong> Floating‑point value changes are not reported spontaneously.</td></tr><tr><td><strong>Disable timestamp check</strong></td><td><strong>Checked:</strong> Time tag validation is bypassed and time‑tagged commands are always accepted and acknowledged.<br><strong>Unchecked:</strong> Time tag validation is enforced and outdated commands may be rejected.</td></tr><tr><td><strong>Maximum command age (ms)</strong></td><td>Maximum acceptable age of time‑tagged commands. Commands older than the simulator’s current time minus this value are discarded without acknowledgment.</td></tr></tbody></table>
{% endstep %}

{% step %}

### Configure the slave(s) data points

1. Expand a slave to reveal its 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-df6660bbd7c39ff95c678577079328b449f19d60%2FDR-hyp-iec104-data.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Click a data point type (**Single points**, **Double points**, **Regulating steps**, **Bitstrings**, **Normalized points**, **Scaled points**, or **Floating points**) and use:

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

3. Change parameters as desired:

{% tabs %}
{% tab title="Common" %}
Here are the common parameters for **all data points**:

<table data-header-hidden><thead><tr><th width="140"></th><th></th></tr></thead><tbody><tr><td><strong>Direction</strong></td><td>Defines whether the data point is an <strong>input</strong> or an <strong>output</strong>. Inputs are written by the master and used by the simulation model. Outputs are produced by the simulation and transmitted to the master.</td></tr><tr><td><strong>Name</strong></td><td>Logical name of the data point, used to bind the configured point to a sensor in the model. This name appears in the sensor view and must be unique and meaningful.</td></tr><tr><td><strong>Data address</strong></td><td>Information object address used by the master to read or write the value of this data point.</td></tr><tr><td><strong>Data group</strong></td><td>Interrogation group assignment. Use <strong>0</strong> to attach the point to the General group only, <strong>C</strong> to attach it to the Cyclic group, or a value from <strong>1 to 16</strong> to assign it to a specific interrogation group.</td></tr><tr><td><strong>Data value</strong></td><td>Initial value of the data point. For inputs, this value is applied before the master connects or sends a command. For outputs, this field is ignored, as the value is driven by the assigned sensor in the simulation.</td></tr></tbody></table>
{% endtab %}

{% tab title="Normalized points Extra" %}
Here are the additional parameters for **Normalized points**:

<table data-header-hidden><thead><tr><th width="160"></th><th></th></tr></thead><tbody><tr><td><strong>Threshold address</strong></td><td>Address of the threshold parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Threshold value</strong></td><td>Initial threshold value. When event scanning is enabled, a change is reported if the threshold is crossed between consecutive values.</td></tr><tr><td><strong>Smoothing address</strong></td><td>Address of the smoothing parameter. This parameter can be updated dynamically by the master using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Smoothing value</strong></td><td>Initial smoothing value applied to the data point.</td></tr><tr><td><strong>Low limit address</strong></td><td>Address of the low limit parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Low limit value</strong></td><td>Initial low limit value. When event scanning is enabled, a change is reported if the value falls below this limit.</td></tr><tr><td><strong>High limit address</strong></td><td>Address of the high limit parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>High limit value</strong></td><td>Initial high limit value. When event scanning is enabled, a change is reported if the value exceeds this limit.</td></tr></tbody></table>
{% endtab %}

{% tab title="Scaled points Extra" %}
Here are the additional parameters for **Scaled points**:

<table data-header-hidden><thead><tr><th width="160"></th><th></th></tr></thead><tbody><tr><td><strong>Threshold address</strong></td><td>Address of the threshold parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Threshold value</strong></td><td>Initial threshold value. When event scanning is enabled, a change is reported if the threshold is crossed between consecutive values.</td></tr><tr><td><strong>Smoothing address</strong></td><td>Address of the smoothing parameter. This parameter can be updated dynamically by the master using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Smoothing value</strong></td><td>Initial smoothing value applied to the data point.</td></tr><tr><td><strong>Low limit address</strong></td><td>Address of the low limit parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Low limit value</strong></td><td>Initial low limit value. When event scanning is enabled, a change is reported if the value falls below this limit.</td></tr><tr><td><strong>High limit address</strong></td><td>Address of the high limit parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>High limit value</strong></td><td>Initial high limit value. When event scanning is enabled, a change is reported if the value exceeds this limit.</td></tr></tbody></table>
{% endtab %}

{% tab title="Floating points Extra" %}
Here are the additional parameters for **Floating points**:

<table data-header-hidden><thead><tr><th width="160"></th><th></th></tr></thead><tbody><tr><td><strong>Threshold address</strong></td><td>Address of the threshold parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Threshold value</strong></td><td>Initial threshold value. When event scanning is enabled, a change is reported if the threshold is crossed between consecutive values.</td></tr><tr><td><strong>Smoothing address</strong></td><td>Address of the smoothing parameter. This parameter can be updated dynamically by the master using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Smoothing value</strong></td><td>Initial smoothing value applied to the data point.</td></tr><tr><td><strong>Low limit address</strong></td><td>Address of the low limit parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>Low limit value</strong></td><td>Initial low limit value. When event scanning is enabled, a change is reported if the value falls below this limit.</td></tr><tr><td><strong>High limit address</strong></td><td>Address of the high limit parameter. The master can modify this value dynamically using a <strong>Parameter control command</strong>.</td></tr><tr><td><strong>High limit value</strong></td><td>Initial high limit value. When event scanning is enabled, a change is reported if the value exceeds this limit.</td></tr><tr><td><strong>Enable RMS computation</strong></td><td><strong>Checked:</strong> RMS is computed over the configured number of samples and reported to the master.<br><strong>Unchecked:</strong> The raw floating‑point value is reported without RMS computation.</td></tr><tr><td><strong>RMS gain</strong></td><td>Gain applied to each sample before RMS computation.</td></tr><tr><td><strong>RMS sample size</strong></td><td>Number of consecutive samples used to compute the RMS value before reporting it to the master.</td></tr></tbody></table>
{% endtab %}
{% endtabs %}
{% 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/iec-60870-5-104-slave/configure-iec-60870-5-104-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.
