How to Connect Modbus TCP and RTU Gateways to Web SCADA Cloud

Industrial facilities frequently rely on Modbus RTU serial meters and Modbus TCP controllers that were never built for the modern web. Connecting these legacy field devices to a centralised Cloud SCADA Platform used to require complex VPN tunnels, static public IP addresses, and vulnerable open firewall ports.

With modern industrial edge IoT gateways and SCADA Cloud, bridging the gap between factory floor Modbus networks and browser-based dashboards takes less than 15 minutes. This guide explains the complete edge architecture, zero-port-forwarding security model, gateway configuration steps, and tag mapping process.

Edge Gateway Architecture: How the Bridge Works

The standard Modbus protocol operates on a local client/server request-response paradigm. Because Modbus lacks built-in authentication and encryption, opening port 502 to the public internet is a critical security vulnerability.

The edge gateway architecture solves this by acting as an intelligent on-premise protocol converter:

1. Local Polling: The edge gateway connects physically to the RS-485 2-wire serial bus or local Ethernet switch, polling Modbus registers at user-defined intervals (e.g., every 1000ms).
2. Data Normalization: Raw 16-bit integer holding registers and bitwise coils are converted into structured JSON payloads with engineering timestamps and unit IDs.
3. Outbound TLS Push: The gateway establishes an outbound encrypted TLS socket to SCADA Cloud (MQTT over port 8883 or HTTPS REST over port 443).
4. Live Dashboard Render: SCADA Cloud ingests the telemetry, evaluates alarm rules, logs time-series data to the historian, and broadcasts real-time updates to connected browser clients via WebSockets.

Step 1 — Create Your SCADA Cloud Account

Step 2 — Connect Field Devices to Edge Gateway

Step 3 — Configure Edge Gateway Modbus Polling

Inside your gateway's management interface (or Node-RED flow), define the polling parameters for your connected slaves:

• Unit ID / Slave Address: The Modbus address assigned to the physical device (e.g. Unit 1 for Inverter, Unit 2 for Power Meter).
• Function Code: Use FC03 (Read Holding Registers) or FC04 (Read Input Registers).
• Start Register & Count: Address 40001 (offset 0), count 10.
• Polling Rate: 1 second to 5 seconds depending on telemetry requirements.

Step 4 — Format and Transmit Telemetry Payloads

The gateway formats polled register values into lightweight JSON strings before publishing to your designated SCADA Cloud device topic. Below is an example payload for a 3-phase power meter:

{
  "device_id": "gateway-plant-01",
  "slave_id": 1,
  "timestamp": 1790623800,
  "telemetry": {
    "voltage_l1_v": 230.4,
    "current_l1_a": 15.8,
    "active_power_kw": 3.64,
    "frequency_hz": 50.02,
    "power_factor": 0.98,
    "total_energy_kwh": 142850.5
  },
  "status": "NORMAL"
}

Step 5 — Map Registers to Dashboard Tags

Step 6 — Design Your Web SCADA Dashboard

Using the intuitive drag-and-drop web builder, assemble your plant monitoring interface:

• Radial Gauges & Level Bars: Visualize real-time motor RPM, tank liquid levels, and pressure transducers.
• Interactive Trend Charts: Overlay power consumption curves against production volume over 24-hour, 7-day, or 30-day spans.
• Alarm Annunciator Banners: Highlight tripped VFDs or low pressure thresholds with automatic SMS alerts to maintenance engineers.

Testing Edge Gateways Without Real Hardware

Before installing physical equipment on-site, test your entire architecture using Modbus Slave Simulator or Modbus TCP Simulator running on your development laptop. The simulator generates realistic register values (voltage fluctuations, ramp frequencies, alarm codes) that your gateway polls and transmits to SCADA Cloud, confirming that all widgets and alarm triggers function perfectly.