> 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.md).

# IEC 60870-5-104 Slave

## Introduction to IEC 60870‑5‑104

IEC 60870‑5‑104 (commonly “IEC 104”) is an international standard for telecontrol communication widely used in electrical transmission, distribution, and SCADA systems. It defines how a control station (master) exchanges process information with remote terminal units (RTUs), IEDs, and gateways over TCP/IP networks. IEC 104 extends the serial‑based IEC 60870‑5‑101 protocol to Ethernet, providing reliable, event‑driven monitoring and control capabilities suitable for utility and substation automation environments.

## Protocol characteristics <a href="#protocolcharacteristics" id="protocolcharacteristics"></a>

* **Master/Slave (Control Station / Controlled Station) architecture**\
  A control station (master) initiates supervisory commands, while a controlled station (slave) provides measurements, status information, and event notifications. Communication is bidirectional but role‑based: the slave sends spontaneous or cyclic updates, while the master issues interrogations, commands, and time synchronization messages.
* **ASDU‑based data model**\
  All information in IEC 60870‑5‑104 is carried in ASDUs, which package one or more Information Objects (the actual data points) and describe them using a Type Identifier for meaning, a Cause of Transmission explaining why the ASDU is sent, an ASDU address identifying the logical device, and an IOA pointing to the specific data item.
* **Function categories**\
  IEC 104 supports several classes of operations, ranging from monitoring functions, such as spontaneous events, cyclic updates, and interrogation responses, to control actions including single‑ or double‑command outputs and setpoints. It also handles counters, time synchronization, and optionally file transfer. Slaves interpret and respond to these operations based on the COT and TypeID, ensuring consistent and interoperable behavior.
* **Transport layer characteristics**\
  IEC 104 relies on TCP/IP to provide reliable and ordered transport and maintains a dedicated T‑connection between the master and the slave throughout the session. Communication is controlled through APCI frames, which include information frames, supervisory frames, and unnumbered frames that manage sequencing, acknowledgments, and link control. Error checking is handled entirely by TCP/IP, so the protocol itself does not include checksum fields.
* **Reliability & latency considerations**\
  Thanks to TCP support, IEC 104 ensures in‑order delivery and automatic retransmission.\
  However, like most SCADA protocols, it does **not guarantee deterministic latency**. Event‑driven communication and low overhead make it suitable for telecontrol applications with moderate real‑time requirements.
* **Security model (protocol‑agnostic)**\
  IEC 104 does not provide authentication or encryption within the protocol itself. Deployments therefore rely on external protections such as physically controlled networks, virtual private networks, encrypted tunnels using TLS, and security devices like firewalls and intrusion detection systems.

## How the protocol works <a href="#howtheprotocolworks" id="howtheprotocolworks"></a>

* **Addressing and configuration**\
  An IEC 104 slave defines a communication session with the master, along with its ASDU addresses, information object addresses, and transmission behavior. The master must be configured with the slave’s data types, addressing, and interpretation rules.
* **Monitoring and control cycle**\
  A typical exchange begins with connection establishment, followed by general interrogation, after which the slave reports its values. The slave then sends spontaneous updates as data changes, while the master issues commands and periodic time synchronization. Both sides maintain sequence counters and acknowledgments throughout the session.
* **Data encoding**\
  IEC 104 encodes information using standardized binary formats for indications, measurements, counters, commands, and time stamps. Larger or vendor‑specific values are represented using the appropriate Type Identifiers.

## Example applications <a href="#exampleapplications" id="exampleapplications"></a>

* **SCADA & Telecontrol**\
  Remote monitoring of equipment across the power system, including breaker states, electrical measurements from lines and transformers, accumulated energy values, and protection‑related events.
* **Electrical Transmission & Distribution**\
  Interfacing RTUs, gateways, and IEDs in substations and control centers.
* **Laboratory & HIL Systems**\
  Feeding simulated grid data to control systems or validating protection algorithms.
* **Industrial and Utility Automation**\
  Integrating distributed monitoring systems, power meters, and control units.
* **Legacy system integration**\
  Serving as a bridge between modern control platforms and older RTU/IED fleets.


---

# 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.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.
