You do not have to choose between your HMI panels and modern SCADA. Here are the three topologies plants actually use — parallel polling, panel-as-device, and panels as browser displays — with setup steps and the pitfalls for each.
A vendor HMI panel is excellent at one job: local control of the machine it is bolted to. Where panels struggle is everything beyond that machine — plant-wide overviews, long-term trends, alarm history, remote access, and screens that update without a USB-stick download. That is SCADA's job. The good news: the two combine cleanly, because almost every panel and PLC on the market speaks Modbus.
One hard truth up front: you cannot install third-party SCADA screens natively onto a vendor panel's runtime — every vendor locks its panels to its own design software. Every practical integration therefore uses one of the three patterns below.
The panel keeps doing exactly what it does today. The SCADA connects to the same PLC as a second Modbus TCP client and polls the same (or additional) registers for supervision: trends, alarms, dashboards, remote view. Modbus TCP PLCs routinely accept several client connections, so the two never conflict.
1) In the SCADA's Device Manager, add the PLC: Modbus TCP, the PLC's IP, port 502, correct unit ID. 2) Click Test Connection. 3) Define tags for the registers you care about. 4) Build screens and alarms. Total time for a first working dashboard: under an hour.
Serial (RTU) PLCs: one master per RS-485 line — if the panel is the serial master, the SCADA cannot join the same wire. Use the PLC's Ethernet port if it has one, or add a Modbus RTU-to-TCP gateway. Connection limits: some small PLCs cap simultaneous TCP clients at 2–4; check before adding many pollers. Write ownership: decide which system writes which registers, and keep it one-directional per register to avoid tug-of-war.
Many panels (Weintek, Delta, Kinco and others) can expose their internal memory as a Modbus TCP server. If the panel already aggregates data from several drives or controllers, the SCADA can read the panel directly — one connection instead of five.
1) In the panel's design software, enable the "Modbus server" / "Modbus slave" feature and map internal registers to Modbus addresses. 2) In the SCADA, add the panel's IP as a Modbus TCP device. 3) Create tags against the mapped addresses. Validate the map against a Modbus TCP simulator first if you want to rehearse without touching production.
Address mapping is the whole game here — panel documentation for Modbus server address offsets is notoriously confusing (0-based vs 1-based, 4x prefixes). Our register map guide covers the traps.
Current-generation panels with an HTML5 browser or web-client mode — and every Android-based industrial panel — can display web SCADA screens directly. The panel becomes a display; screens, alarms and history live on the SCADA server. Update a screen once and every panel shows it immediately.
1) Host your SCADA where the panel can reach it (plant server or cloud). 2) Build the HMI screens in the drag-and-drop designer. 3) On the panel, open the browser/web-client, enter the SCADA URL, log in with a view-or-operate role, and enable kiosk/full-screen mode with auto-start. 4) Prefer wired Ethernet for fixed panels.
Older panels with no browser cannot do this — they stay on Setup 1 or 2. Check the browser generation on mid-2010s panels; anything HTML5-capable from roughly 2018 onward is generally fine. For dedicated displays, cheap Android panels or tablets are often better value than upgrading a panel just for its browser — see our web-based HMI guide.
| Your situation | Best setup | Why |
|---|---|---|
| Panels doing local control, want plant-wide visibility | 1 — parallel polling | Zero changes to what works; SCADA adds supervision on top |
| Panel already aggregates several machines | 2 — panel as device | One connection reads everything the panel knows |
| New stations / replacing aging panels | 3 — browser kiosk | Cheapest hardware, centrally managed screens |
| Serial-only legacy line | 1 via RTU-TCP gateway | Keeps the single-master rule intact |
| Greenfield with no panels yet | 3 (+ PLC direct) | Skip vendor panel lock-in entirely |
Most plants end up mixing all three — and that is fine. The SCADA does not care whether a value came from a PLC, a panel's Modbus server, or a gateway; a tag is a tag.
Not meaningfully at sane poll rates. A supervisory poll every 1–5 seconds adds trivial load next to a panel polling at 100–500 ms. If the PLC is connection-limited, lengthen the SCADA poll interval.
Technically yes; operationally, give each register one writing owner. A common split: the panel owns machine-local commands, the SCADA owns supervisory setpoints — enforced by role permissions and the tag list you configure.
Stand up a Modbus slave simulator with the PLC's register map, point the SCADA at it, and rehearse tags, screens and alarms. Swap the IP when you go live.
Yes — the SCADA also speaks OPC UA and MQTT, so mixed fleets (Modbus panels + OPC UA PLCs + MQTT sensors) land on the same screens.
Modbus TCP/RTU, OPC UA and MQTT device support, drag-and-drop HMI screens, alarms, trends and browser access — alongside the panels you already own. SCADA Cloud is free for 30 days; SCADA Desktop is $199 perpetual.