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

# Connect the Hardware

## Connect devices using standard Ethernet cables

IEC 60870‑5‑104 communication operates over **Ethernet using TCP/IP** and relies on the simulator’s **built‑in LAN ports**. To establish communication between IEC 60870‑5‑104 slaves and a control station (master), connect the devices using **standard Ethernet cables**.

## Set IP addresses and subnets

For reliable IEC 60870‑5‑104‑over‑TCP operation, all devices must follow standard IP networking rules:

* The **master and all slaves must be reachable within the same IP subnet**, unless routing has been explicitly configured.
* Each **physical device on the network must use a unique IP address** to avoid conflicts.
* Multiple logical IEC 60870‑5‑104 slaves may share the same IP address **only if they are hosted on the same simulator**, in which case they are differentiated by unique TCP ports or ASDU addresses.

Example of valid subnet configuration:

* Master: `192.168.10.10 / 255.255.255.0`
* Slave 1: `192.168.10.20 / 255.255.255.0`
* Slave 2: `192.168.10.30 / 255.255.255.0`

## Set the TCP port

IEC 60870‑5‑104 uses **TCP port** **2404** by convention. This value can be changed if required by the application or network environment.

Multiple slaves can use the same TCP port as long as they have different IP addresses. When multiple slaves share the same IP address, each slave must be assigned a different TCP port.

If custom port configurations are used, ensure that:

* The selected TCP ports are not blocked by firewalls or network security policies.
* The master is configured to connect to the correct IP address and TCP port for each slave.


---

# 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/iec-60870-5-104-slave/connect-the-hardware.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.
