Two HMI panels cannot share one PLC serial port, because a master/slave serial port serves one master at a time. Give each local panel its own serial port and reach the office panel through an Ethernet option module in each PLC. RS-232 stays inside about 50 ft at 9600 bps; Ethernet carries each supervisory connection 100 m per segment.
Several HMI panels and one office panel can share a building full of PLCs without fighting over a port. Each panel just needs its own physical path. The rule is short: a PLC serial port set up for a master/slave protocol serves one master. The local panel in each zone owns that port, and the office panel reaches every PLC through an Ethernet option module instead. This article gives the parts list per zone cabinet, the device entries the office panel needs, the cable length each medium tolerates, a three-zone example with the arithmetic shown, and the checks that prove each zone before setpoint writes go live. One figure decides most projects. If a screen and its PLC sit more than about 50 ft apart at 9600 bps, RS-232 is the wrong medium and the network is the right one.
Can several HMI panels share one PLC serial port?
A PLC serial port configured for a master/slave protocol serves one master at a time. Two panels polling the same RS-232 port collide on the wire, and the fix is a separate physical path for each panel. RS-232 is a point-to-point interface: two transmitters driving one receive line corrupt each other's traffic. The symptoms are timeouts, partial screens and garbled values. That failure has a predictable shape; the article on why two HMI panels fail on one PLC serial port walks it symptom by symptom.
RS-485 wiring is multi-drop, which gives one port many slaves. Under these protocols it still serves one master; multi-drop is not a licence for two panels. Hardware sharing exists for special cases, such as a power-switching arrangement that connects multiple RS-232 devices to one serial port. Treat that class of solution as the exception. The default design gives every panel its own port or its own network path.
What do you need for a multi-panel setup?
Each zone needs one PLC with a free serial port for its local panel and an option slot for an Ethernet communications module. The office panel needs project software that holds one device entry per zone PLC. Everything else is ordinary wiring:
- Per zone: the PLC, a local HMI panel sized for the cabinet and its task, the panel's serial cable, and the Ethernet option module seated in the PLC's option slot.
- At the office: a supervisory HMI panel whose project supports multiple devices, one entry per zone.
- Between them: an Ethernet switch with one port per PLC module plus one for the office panel, and patch cables cut to the route.
The module is the whole trick. Once each PLC has a serial client, the local panel, and an Ethernet interface for the office, the two paths never meet. No port carries two masters.
How long can each cable run be?
Plan RS-232 panel cables at about 50 ft or less at 9600 bps. Plan RS-485 multi-drop runs to about 4000 ft with termination resistors fitted. Plan Ethernet at 100 m per 100BASE-TX segment. The RS-232 figure is the common planning point for that signaling at that rate. The signals are referenced to ground and carry little noise immunity, so a run draped past drives or welders fails before the distance does. RS-485 signals are differential, which is what lets a multi-drop segment stretch to about 4000 ft, and termination resistors at both ends of the segment are part of that figure. Ethernet's 100 m limit is between one switch port and one device. 100 m converts to 328 ft, so a run longer than that needs a switch or a different medium partway.
| Medium | Planning limit | What the limit assumes |
|---|---|---|
| RS-232, point-to-point | about 50 ft at 9600 bps | one master, one slave, ground-referenced signal |
| RS-485, multi-drop | about 4000 ft | termination resistors at both segment ends |
| Ethernet, 100BASE-TX | 100 m (328 ft) per segment | one switch port to one device |
How do you wire each zone so the panels stay separate?
Wire the local panel to the zone PLC's serial port. Seat the Ethernet option module in the PLC's option slot. Run one patch cable from that module to the building switch. Each panel then owns a different physical interface. The serial cable's wiring, straight or null modem, comes from the PLC manual; a swapped transmit and receive pair shows as total silence, not as bad data.
- At each cabinet, record the zone name, the PLC, the serial port the local panel's cable lands on, and the Ethernet module installed. Do this before editing anything.
- Confirm the local panel is on a serial port and the module is seated in its option slot.
- Set the same protocol, baud rate and station address on both ends of the serial link, reading the values from each manual; a mismatch reads as no response.
- Patch every Ethernet module to the switch and label both cable ends with the zone name.
With that done, each cabinet contains two independent connections: a short serial link that only its own panel uses, and a network drop that the office side uses.
How do you configure the office panel for every zone?
Create one device entry per zone PLC over Ethernet. Then point every screen tag at the entry for its own zone, so a setpoint typed for zone 2 can only ever reach the zone 2 controller.
- In the office panel's project, create a device entry for each zone PLC and name it after the zone.
- Point each entry at that zone's module network address, read from the installed project record; do not copy one entry to the next and adjust on trust.
- Build each zone's screens using only that zone's device entry.
- Keep exactly one entry per PLC. A controller added twice produces confusing symptoms, such as a screen showing valid-looking data from the wrong zone.
- Leave central setpoint writes disabled until the checks in the last section pass.
Each extra zone costs one serial link, one Ethernet module and one switch port. Nothing else in the arrangement changes.
What does a three-zone example look like?
In a three-zone building the office panel reaches every PLC over Ethernet. Two of the three cable routes exceed the 50 ft RS-232 planning limit while every run stays inside Ethernet's 328 ft. Each cabinet holds one PLC and one local panel; the local panel sits on its PLC's serial port through a 6 ft cable inside the cabinet. Cable-route distances from the office switch measure 40 ft to zone 1, 130 ft to zone 2 and 210 ft to zone 3.
Run the numbers both ways:
- Direct RS-232 from the office to each PLC, planning limit 50 ft at 9600 bps: zone 1 at 40 ft fits with 10 ft to spare. Zone 2 is 130 ft − 50 ft = 80 ft over the limit. Zone 3 is 210 ft − 50 ft = 160 ft over. A serial office panel could serve zone 1 and nothing else.
- Ethernet, 100 m per 100BASE-TX segment: 100 m × 3.28 ft/m = 328 ft. The longest run is 210 ft, leaving 328 ft − 210 ft = 118 ft of margin, so all three zones reach the same switch.
- Device entries: three, one per zone PLC. Local serial links: three, each 6 ft, every one inside the 50 ft figure.
| Path | Zone 1 | Zone 2 | Zone 3 |
|---|---|---|---|
| Office to PLC over RS-232 (50 ft limit at 9600 bps) | 40 ft, fits | 130 ft, 80 ft over | 210 ft, 160 ft over |
| Office switch to Ethernet module (328 ft limit) | 40 ft | 130 ft | 210 ft |
| Local panel to its own PLC (50 ft limit) | 6 ft | 6 ft | 6 ft |
The result: each PLC's serial port serves exactly one master, its own local panel. The office panel works as an Ethernet client with three device entries. No port carries two masters, and every physical limit has margin.
Can more than one master use the Ethernet path?
Over Ethernet, several Modbus TCP masters can share one PLC port because each master holds its own connection. A PC node and the office panel both belong on the network while the serial port keeps its single panel. That asymmetry is the design rule to remember: serial serves one master, Ethernet serves several. The connection behavior behind it, including what each master keeps distinct, is set out in a page on multiple Modbus TCP masters sharing one Ethernet port. A PC that joins as a third reader goes in on the same switch; connecting a PC HMI to a PLC over a serial protocol or Ethernet covers the protocol pick.
Every extra master adds polling traffic, and panels that multiply slow every screen. The countermeasures live in connecting many operator panels to one PLC without slow updates. When two supervisory panels must poll many PLCs and the PLCs cannot keep up, put a master PLC in the middle; that arrangement is two HMI panels polling many PLCs: use a master PLC.
How do you prove each zone before setpoints go live?
Test one zone at a time. Read the zone value on the local panel, read the same value on the office panel, then send one small setpoint change from the office and confirm it arrives at the intended PLC. Work down the checks in this order:
- Local read and adjust first. If the local panel reads and adjusts its zone, its serial link works for those operations; leave it alone while you debug the office side.
- One dead zone, rest healthy: compare the failing zone's patch cable, module power and link lights, device entry and screen references against a working zone. The fault is per-zone until two zones fail the same way.
- Then the write test. Change one controlled, authorized value from the office, confirm the intended PLC reflects it on the local panel, and confirm the local panel still controls its zone afterward.
- A correct office display is not proof that a write reached the right PLC; the write test is that proof.
- Record the final device-to-zone mapping and hand it to maintenance with the panel project.
Recommendation: give every local panel its own PLC serial port, reach the office panel through an Ethernet option module in each PLC, and keep central setpoint writes off until every zone passes the read-and-write test. Run direct RS-232 from the office only where a single run stays inside 50 ft at 9600 bps, and put everything farther on the network.
This setup is machine wiring, and it stays that way. If a zone also needs a standalone notice board, one that plays its own images and video files from memory card or USB with no subscription, that is a different screen doing a different job. Our panel-mount Android displays are built for it, and they take no part in the PLC link described here.
Questions
Does a network switch failure take down the local panels too?
No. Each local panel talks to its own PLC over the serial port, which never passes through the switch. A switch failure or a broken patch cable stops office monitoring and central setpoint adjustment, and every zone keeps running under its local panel. When the switch comes back, the office panel reconnects to each Ethernet module. That split is the reason the two paths are kept physically separate: the wiring that can fail at building scale is never the wiring a zone depends on for control.
How many zones can one office panel watch?
As many device entries as its project software supports, and the panel's specification is the only source for that number; no universal figure exists. The wiring does not set the limit: each extra zone adds one serial link, one Ethernet module and one switch port, and each extra master adds polling traffic. If you approach the panel's device limit or updates slow down, split the building between two office panels or put a master PLC in the middle before the project grows again.
Can the local panel and the office panel use the same protocol?
Usually yes, and it does not matter, because they never share a wire. The local panel runs the protocol its PLC serial port speaks, and the office panel runs whatever Ethernet protocol the module and the project support, often the same protocol family over a different transport. Set each link from its own manual: baud rate and station address on the serial side, network address on the Ethernet side. A mismatch on either link shows up as no response from that one device only.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.