What Is Modbus TCP? Its Use in Energy Monitoring

What Is Modbus TCP?

Modbus TCP is one of the most widely used communication protocols in industrial automation. It is the version of the Modbus protocol—developed by Modicon in 1979—that runs over Ethernet/IP. Because it operates over TCP/IP, devices can be accessed through existing LAN infrastructure, and long-distance and multi-master connections are handled seamlessly.

How Does Modbus TCP Work?

Modbus TCP uses a client-server (master-slave) architecture. The master device (Field Agent or PLC) establishes a TCP connection to the slave device (energy analyzer, UPS, transformer relay) and performs register read/write operations via Function Codes:

• FC 01 — Read Coil (bit)
• FC 03 — Read Holding Register (most common: measurement values)
• FC 04 — Read Input Register
• FC 06 — Write Single Register
• FC 16 — Write Multiple Registers

Each transaction is wrapped in an MBAP (Modbus Application Protocol) header. The default port is 502/TCP. The response time is typically between 10-50 ms.

The Difference Between Modbus TCP and Modbus RTU

Modbus RTU runs over an RS-485 two-wire serial line. The cable distance is limited to 1200 m, and 247 devices are supported per segment. The baud rate is configured between 9600-115200 bps. The vast majority of legacy devices support only RTU.

Modbus TCP, on the other hand, runs over any Ethernet infrastructure; there is no distance limit, and it can also be used over fiber optic or wireless networks. Because there are no collision issues, the polling rate is higher.

Using Modbus TCP in Energy Monitoring

Modbus TCP forms the backbone of the data-acquisition layer in energy management systems. Energy analyzers such as the Schneider PM5350 or Siemens PAC3200 installed in a substation transmit the following data from their Modbus TCP registers:

• L1/L2/L3 phase voltage and current values
• Total active power (kW), reactive power (kVAr), apparent power (kVA)
• Power factor (cos φ)
• Cumulative energy consumption (kWh) and reactive energy (kVArh)
• Total harmonic distortion (THD)
• Phase imbalance and frequency

Modbus TCP Integration in Argus EMS

The Argus EMS Field Agent runs as a Windows-based service on the on-site PC. An IP address, TCP port and Slave ID are defined for each device. The default poll interval is 15 minutes (aligned with EPDK reporting granularity) and can be reduced to as little as 1 minute.

In the event of a connection loss, the Field Agent writes its data to a local SQLite queue and synchronizes automatically once the internet is re-established. Up to 30 days of data is buffered—data loss is zero.

Security Notes

Modbus TCP has no built-in authentication mechanism; therefore:

• Place Modbus devices on a separate VLAN
• Apply a firewall rule between the Field Agent and the device
• Do not expose port 502 to the internet
• Access the Argus EMS backend using HTTPS and JWT authentication