PLC vs. RTU: What's the Difference for Remote Monitoring?

· 14 min read
14 min read
Lucas Moreau
Lucas Moreau
OT/IT Network Engineer

In conversations between automation engineers and project managers, the terms PLC and RTU are often used interchangeably—or, conversely, presented as being radically opposed. The reality is more nuanced: PLCs and RTUs are two families of equipment designed to meet distinct needs, which have gradually converged with the advent of the IIoT but still retain fundamental differences that are critical to the choice of a remote monitoring architecture.

This guide clarifies the definitions, compares the two technologies based on the criteria that really matter, and explains how to monitor each one remotely in a modern SCADA or cloud architecture.

What is a PLC (Programmable Logic Controller)?​

A PLC (Programmable Logic Controller), known as an API (Automate Programmable Industriel) in French, is an industrial computer designed to execute a real-time control program for a local industrial process. Its primary role is to process inputs and outputs (sensors, actuators) at a high frequency and to execute sequencing or control logic.

How It Works​

The PLC operates in a cyclic loop: input acquisition, program execution, output update, and repeat. The cycle time is typically 1 to 100 ms, depending on the program’s complexity and the CPU’s processing power. The programming languages are standardized by the IEC 61131-3 standard: Ladder Diagram (LD), Function Block Diagram (FBD), Structured Text (ST), Instruction List (IL), and Sequential Function Chart (SFC).

Representative Examples​

  • Siemens: S7-1200, S7-1500, S7-300 (legacy)
  • Schneider Electric: Modicon M340, M580, M262
  • Allen-Bradley (Rockwell): ControlLogix, CompactLogix, MicroLogix
  • Omron: CX-Programmer, NX/NJ Series
  • Mitsubishi: MELSEC Q Series, iQ-R Series

Typical Areas of Application​

PLCs are found wherever complex logic needs to be executed locally: automotive production lines, packaging machines, robotic welding cells, multi-axis conveyors, food processing operations with recipe management, and multi-zone temperature control.

The key feature: the PLC is at the heart of a local process that cannot afford to wait for a command from the cloud to make a decision in a matter of milliseconds.

What is an RTU?​

An RTU (Remote Terminal Unit — Remote Terminal Unit) is a device designed to collect measurement data from a remote site, aggregate it, and transmit it to a central system (SCADA, monitoring center) via a communication network—historically radio or PSTN, but now GPRS/4G or fiber. Its local processing capacity is limited; its primary role is remote management: relaying information and, in some cases, executing simple commands received from the central system.

How It Works​

The RTU monitors its inputs (4–20 mA, on/off, meter pulses), stores the values in a buffer, and transmits them periodically or on an event-driven basis to the central SCADA system. In the event of a communication outage, it continues to store data locally (with embedded timestamps) and transmits the data at a later time once communication is restored. This timestamped data logging feature is critical in water, energy, and remote management applications.

Areas of Application​

  • Water Distribution and Sanitation: remote monitoring of pumping stations, reservoir monitoring, leak detection
  • Power Distribution: high-voltage (HV) and extra-high-voltage (EHV) substations, monitoring of transformer stations
  • Gas: monitoring of delivery stations, long-distance metering
  • Environment: weather stations, river flow measurement, air quality
  • Agriculture: automated irrigation, remote field sensors

The key feature: The RTU is a satellite device deployed at remote and often unattended sites, whose primary function is to report the system's status to a centralized control center.

Comparison Chart: PLC vs. RTU​

CriterionPLC (API)RTU
Processing PowerHigh — cycle times of 1 to 100 ms, complex logicLow to medium — simple processing, no multi-axis control
Field Interface (I/O)Modular, high-density digital and analog I/OAnalog I/O (4–20 mA), digital I/O, pulse counting, measurement
Native ProtocolsModbus TCP/RTU, OPC-UA, PROFIBUS, EtherNet/IP, PROFINETModbus RTU, DNP3, IEC 60870-5-101/104, IEC 61968
Power consumptionMedium to high (24 V DC power supply, several amps)Low (designed for possible solar/battery power)
Environmental robustnessIndustrial grade, but optimized for fixed installation inside a cabinetDesigned for unattended sites, extreme cold, heat, and humidity
Typical UseLocal automation, machinery, production linesRemote management, water/energy SCADA, remote sites
Price€500 to €10,000 depending on power and I/O€300 to €3,000 depending on I/O and protocols
ProgrammingIEC 61131-3 (LD, FBD, ST…) — automation engineerSimplified configuration or manufacturer-specific language — remote control technician
Remote CommunicationOPC-UA, Modbus TCP, via gatewayDNP3, IEC 104, Modbus RTU over 4G, native WAN
Redundancy / Offline BufferLimited — designed to remain connectedNative — time-stamped data storage in case of network outage

When Should You Choose a PLC?​

A PLC is the right choice when the following criteria are met:

Complex local logic. If your system requires multi-step sequencing, multi-loop PID control, recipe management, or multi-actuator coordination, only a PLC has the processing power and the appropriate development environment.

Critical response time. A conveyor that needs to detect a jam within 10 ms and shut down the line cannot rely on a decision coming from the cloud. The PLC makes the decision locally, in real time.

Controlled environment. The equipment is installed in a temperature-controlled workshop electrical cabinet with a stabilized power supply. Extreme environmental conditions (extreme outdoor cold, battery power, unguarded site) do not apply.

Practical examples:

  • Welding robot on an automotive production line: The PLC manages axis synchronization, the welding sequence, and safety interlocks.
  • Pharmaceutical packaging machine: The PLC manages product flow, weighing, labeling, and traceability in compliance with FDA 21 CFR Part 11.
  • Wastewater treatment plant with 6 tanks: The PLC manages the filling/draining sequences, pumps, and aerators using complex control logic.

When Should You Choose an RTU?​

The RTU is the right choice in the following situations:

Unmanned remote sites. A pumping station located 40 km from the monitoring center, powered by a generator with a backup battery, in a well or an un-air-conditioned room. The RTU is designed for this scenario.

A large number of measurement points. A water distribution network may include 200 pumping stations and 500 measurement points. Deploying PLCs at each location would be beyond budget and overkill. RTUs, which are more cost-effective and easier to configure, are the natural choice.

Native SCADA protocols. If your central SCADA system uses DNP3 or IEC 60870-5-104 (protocols designed for remote management with support for timestamping, event sequences, and intermittent communication), an RTU will support these protocols natively, whereas a PLC will require a gateway.

Battery backup during power outages. The RTU stores measurements locally with precise timestamps and transmits them in batches once communication is restored. This feature is required in many water and energy remote management specifications.

Specific examples:

  • Network of air quality monitoring stations: 80 stations transmitting PM2.5, NO2, and O3 readings every 15 minutes to the central server via 4G.
  • Gas delivery stations: RTUs with IEC 101 over a PSTN connection, followed by migration to IEC 104 over IP, monitored by the dispatch center.
  • Agricultural irrigation covering 500 ha: RTUs on each sector valve, controlled from the operations center via SCADA.

Monitoring a PLC Remotely​

Remote monitoring of a PLC involves retrieving process variables from the PLC and transmitting them to a centralized monitoring system or the cloud. Several methods are available, depending on the PLC generation and the available infrastructure.

OPC-UA: The Modern Approach (S7-1500, Modicon M580, ControlLogix)​

Modern PLCs (from around 2015 onward) include a built-in OPC-UA server. The IoT gateway or SCADA server connects as an OPC-UA client, subscribes to the relevant variables, and receives updates in real time or when a value changes. Security is built-in (encryption, certificates, authentication via username/password or client certificate).

Modbus TCP: The Universal Method​

Modbus TCP is supported by virtually all modern PLCs and many older PLCs via communication modules (CP for Siemens, NOE for Schneider). The IoT gateway polls the Modbus registers at fixed intervals and transmits the values to the cloud. Simple and universal, but without a native mechanism for change notifications.

Local IoT Gateway​

For PLCs without native network connectivity (S7-300 without an Ethernet CP, Modicon Quantum), an IoT gateway connects to the PLC’s RS-485 or RS-232 serial port via Modbus RTU and transmits data to the cloud. This approach is transparent to the PLC program.

Direct Access via VPN​

For maintenance and diagnostics, the engineer accesses the PLC from their workstation via a VPN tunnel. They see the PLC as if it were on the local network: TIA Portal for an S7, Unity Pro for a Modicon, Studio 5000 for a ControlLogix. No ports are open on the industrial site side.

Monitoring an RTU Remotely​

Remote monitoring is the primary purpose of the RTU. Its protocols and methods differ from those of PLCs because they were designed from the outset for communication over unstable WAN links.

DNP3: The Historic Utility Protocol​

DNP3 (Distributed Network Protocol 3) is the leading remote management protocol in North America for electric power grids and water distribution systems. It natively supports intermittent communication, event timestamping, exception reporting (reporting only when a value changes), and data classes (classes 0, 1, 2, and 3 to prioritize alarms).

A DNP3 RTU connects to the central SCADA master via TCP/IP (DNP3 over IP) or via a serial connection over radio. Over 4G, the RTU establishes a DNP3 TCP session with the master server.

IEC 60870-5-101 and IEC 60870-5-104​

These IEC standard protocols are the European equivalents of DNP3 and are widely used in power and water distribution networks in France and throughout Europe. IEC 101 is the serial variant (RS-232/485), while IEC 104 is the TCP/IP variant (the current choice for 4G and fiber deployments).

An IEC 104 RTU establishes a TCP connection to the SCADA master on port 2404. It transmits data in spontaneous mode (on change) or in response to general queries from the master.

Modbus RTU over 4G​

For simpler deployments or existing equipment fleets, an RTU can transmit its data via Modbus TCP encapsulated over 4G. The site’s 4G gateway creates a VPN tunnel to the central SCADA system; the SCADA system queries the RTU via Modbus TCP through this tunnel as if it were on the local network.

Example of a Water RTU Deployment​

A water district monitors 45 pumping stations via a central SCADA system. Each station has an RTU with:

  • 8 analog inputs (4–20 mA) (flow, pressure, level)
  • 16 digital inputs (pump status, alarms)
  • 4 digital outputs (pump controls)
  • IEC 104 communication over 4G LTE with failover to a secondary SIM card

The SCADA system polls each RTU every 5 minutes (general poll) and receives alarms in spontaneous mode. If a threshold is exceeded, the alarm is transmitted in less than 10 seconds.

PLC/RTU Convergence in the IIoT​

The lines between PLCs and RTUs have been blurring over the past decade, driven by the IIoT and the demand for cloud-based monitoring:

Modern PLCs include RTU functions. The Modicon M262, Siemens S7-1500T, and CompactLogix 5380 feature native cloud connectors (MQTT, OPC-UA), local storage capabilities, and remote management protocols. An S7-1500 with an IoT gateway can serve as a high-performance RTU.

Modern RTUs incorporate PLC logic. Devices such as the Schneider Electric SCADAPack 470 or the Wago 750-8207 offer processing power and an IEC 61131-3 programming environment comparable to compact PLCs, while retaining native remote management protocols (DNP3, IEC 104).

Edge computing is blurring the lines. The trend is toward versatile devices capable of advanced local processing (machine learning on sensor data, vibration analysis, anomaly detection), multiprotocol communication, and simultaneous cloud monitoring. These “edge controllers” offer the best of both worlds.

Practical Recommendation. For new installations, the PLC/RTU distinction is becoming less and less relevant. The real question is: Do you need local real-time logic (→ PLC), remote management via utility protocols (→ RTU), or both (→ edge controller with both capabilities)? In any case, remote monitoring today relies on an IoT gateway that abstracts the field protocol and exposes a standard cloud API.

Architecture Example: Monitoring PLCs and RTUs from a Single Platform​

In actual installed systems, PLCs and RTUs coexist: a control room operated by S7-1200s, remote stations equipped with legacy RTUs, and a few control cabinets with simple Modbus sensors. Rather than piling on monitoring tools, the unified architecture relies on the gateway:

PLC (Modbus TCP, S7, OPC-UA) + RTU (Modbus RTU, DNP3) + RS-485 sensors → Eziwan gateway → 4G M2M SIM card or Ethernet → outbound VPN tunnel → Eziwan cloud → unified monitoring, alerts, and remote access by device.

The gateway abstracts the field protocol: from the platform’s perspective, an RTU register from the 2000s and an OPC-UA variable from a new S7-1500 are monitored in exactly the same way. This is what makes it possible to modernize monitoring without waiting for the equipment to be replaced.

Modernization Costs: Replace or Connect?​

Before replacing an aging RTU with a modern PLC, compare the two scenarios:

ScenarioTypical Cost per SiteTimeframeRisk
Complete replacement of the RTU with a communication-enabled PLC€5,000 to €15,000 (hardware + engineering + rewiring + testing)Several weeks, site shutdownFunctional regression testing, re-certification
Addition of a 4G gateway to the existing systemA few hundred euros + subscriptionLess than a day, no downtimeVirtually none (read-only mode possible)

In most cases, the gateway meets actual needs—cloud monitoring, alerts, remote access—at a fraction of the cost, and allows hardware replacement to be planned smoothly over several years.

FAQ​

Can an RTU be replaced with a PLC in a water remote management application? Technically, yes, but there are some caveats. If your central SCADA system uses DNP3 or IEC 104, a PLC without a dedicated communication module cannot natively support these protocols. You’ll need a DNP3/IEC 104 → Modbus or OPC-UA gateway. Furthermore, PLCs generally consume more power and are less suited for battery or solar power sources. The RTU remains the optimal choice for water and energy remote management systems.

Can an RTU replace a PLC on a production line? No, for two reasons: its processing power is insufficient for complex sequencing and control logic, and RTUs are not designed for cycle times shorter than 100 ms. However, an RTU can monitor simple equipment on a production line (level sensors, manual valve statuses) as a supplement to a main PLC.

How can I monitor an older RTU whose protocol isn't supported by my cloud-based SCADA system? A protocol gateway (Moxa, Advantech, Eziwan) can convert a legacy field protocol (DNP3, IEC 101, BSAP) to MQTT or OPC-UA, which a modern cloud-based SCADA system can understand. This is often more cost-effective than replacing RTUs across fleets of hundreds of devices.

What is the difference between an RTU and a data logger? A data logger passively records measurements in its memory for later retrieval (often via USB or SD card). An RTU actively transmits data to a central system in near real time or on an event-driven basis. Some modern devices combine both functions (data logger with 4G transmission), but the functional distinction remains relevant.

Further Reading​

Do you oversee a fleet of PLCs or RTUs and want to centralize remote monitoring? Discover Eziwan's solutions for remote access to PLCs.

Additional Resources​