Connecting Devices to SCADA and Multiple HMI Displays – Protocols, Wiring, Diagnostics

Connecting machines, inverters, PLCs and operator panels to a SCADA system is now standard in factories and increasingly on farms, in forklift fleets and on solar plants. A well-executed integration gives real-time machine status, alarm and trend archives and remote diagnostics. A poor one means communication drops, frozen screens and hours spent hunting for a fault that turns out to be a single RS-485 connector. This guide collects hard data: protocols, link parameters, wiring rules, multi-display configurations and the most common faults we see in our workshop.

SCADA versus an HMI panel

SCADA (Supervisory Control And Data Acquisition) is a supervisory system that collects data from many controllers, archives it, visualises it and lets operators issue commands. An HMI panel is a local screen at the machine – it shows status and allows operation, but usually sees only one controller or line. In practice they work together: the HMI serves the machine on site, while SCADA collects data from many machines into one central view.

Architecture: how data flows from machine to screen

A typical system has four layers: field devices (sensors, drives, energy meters, engine controllers), PLCs or protocol gateways that normalise the data, the network (RS-485, CAN, Ethernet), and the supervisory layer (SCADA server, HMI panels, possibly the cloud). The joints between layers – gateways, converters and serial-to-Ethernet transitions – are where most problems occur.

Communication protocols used with SCADA

RS-485 (Modbus RTU): the parameters people forget

Most serial communication problems come from installation, not software. RS-485 is a twisted pair (A/B or D+/D−) plus reference ground and shield. It must be wired as a line, not a star, and needs terminating resistors at both ends.

The most used Modbus functions are 03 (read holding registers), 04 (read input registers), 06 (write single register) and 16 (write multiple registers). Watch the address numbering: some vendors count from 1, others from 0, causing the classic off-by-one error.

Sample inverter register map

Every manufacturer has its own map, but the data scope is similar. Always verify actual addresses in the device manual.

Heavy and mobile machinery: CAN, J1939 and gateways to SCADA

Tractors, forklifts, lifts and trucks communicate internally over CAN. They are not connected directly to SCADA – a CAN → Modbus TCP / OPC UA / MQTT gateway reads the frames (engine speed, coolant temperature, oil pressure, active DM1 fault codes) and exposes them in a format the supervisory system understands. For electric forklifts, drive controller data (current, temperature, faults, battery voltage) enables condition-based rather than calendar-based servicing.

Multiple displays: connecting several HMI panels and SCADA screens

Three rules matter. First, a single source of truth: tags should come from one controller or server. Second, separated permissions: shop-floor operators can control, office views read only. Third, load control: every panel polling the same inverter over RS-485 reduces line throughput, so let one unit collect data and the others read from it.

Ethernet in the cabinet: addressing, segmentation, security

Use a separate subnet for automation devices, static IP addresses with a documented table and industrial-grade switches. Services such as Modbus TCP (502) or S7 (102) must never be exposed directly to the internet – use a VPN or a secure authenticated gateway. Prefer OPC UA with encryption over open Modbus TCP wherever possible.

• Segmentation – separate automation from office networks (VLAN or separate switches with a firewall).
• IP documentation – one table with device, address, mask, gateway and protocol.
• Monitoring – SNMP or simple pings alerting on device loss.
• Backups – keep copies of PLC, HMI and gateway projects off the machine.

Commissioning checklist

1. Gather documentation – register maps, tag lists, wiring diagrams and serial settings.
2. Plan addressing – slave addresses, IP addresses, CAN bitrates, node IDs.
3. Verify wiring – continuity, A/B polarity, termination, shield grounding, separation from power cables.
4. Test each device on its own with a Modbus master tool or CAN sniffer.
5. Add devices to the network one at a time and note when communication destabilises.
6. Define tags in SCADA / HMI – names, types, scaling, units, alarm limits.
7. Configure alarms and trends – priorities, acknowledgement, archiving, notifications.
8. Run a load test with the full tag count and all stations for several hours, watching CRC errors and timeouts.
9. Save backups – project, device configuration, address table, operator manual.

Common communication faults and how to diagnose them

In our workshop we also see hardware failures: damaged RS-485 transceivers, burnt Ethernet ports in HMI panels and controllers, dead 24 V supplies and communication modules after surges. These can usually be diagnosed and repaired at component level instead of replacing the entire controller or panel.

Design best practices

• Use consistent tag naming (e.g. LINE1_DRIVE2_CURRENT) and keep a central tag register.
• Separate operator, service and management views.
• Design clear alarms with priorities and short descriptions – avoid alarm floods.
• Size the 24 V supply with margin and surge protection; many "strange" communication faults start at the power supply.
• Do not run communication cables alongside power and inverter motor cables; cross them at right angles if necessary.
• Plan spare tags and ports – installations almost always grow after the first year.

When to call a service workshop

If communication is unstable, SCADA loses data, an HMI cannot see the controller after a replacement or a machine lost connectivity after a surge, bring in a workshop that understands both electronics and protocols. We help with communication diagnostics, repair of damaged ports and communication modules, gateway commissioning and cleaning up the variable map of inverters, PLCs, HMI panels and mobile machine controllers. We work on weekdays, Monday to Friday, 8:00–16:00, around Knurów, Gliwice and the Silesia region.

See also: inverter repair after a surge and forklift controller repair. Have a device that will not talk to SCADA? Contact us – quotes are individual, after diagnostics.