IMDTouchKnowledge BaseShop main store

How-to

Connecting One HMI Panel to Two PLCs Over Serial

HMI and touchscreens Published 6 min read

Short answer

Yes. A two-port panel — one RS-232-only port, one selectable RS-232/RS-485 port — runs two PLCs: one point-to-point link per port, or both PLCs as separately addressed slaves on the single RS-485 bus. Give each link its own cable, driver and matching serial settings, and prove one link before configuring the next.

On this page
  1. Pick the arrangement before the cable
  2. Wire each link for its electrical standard
  3. Configure and prove one link at a time
  4. Worked example: the wire-time floor on the shared bus
  5. When one link talks and the other stays silent
  6. Questions asked

Yes — a two-port HMI panel runs two PLCs over serial, with no gateway in between. On the common two-port layout, one port is RS-232 only and the second is set in software to RS-232 or RS-485, which gives three workable arrangements: one PLC on each port over RS-232, RS-232 on the first port with RS-485 on the second, or both PLCs as separately addressed slaves on the single RS-485 bus. One rule picks between them: a serial port runs one protocol. PLCs speaking different protocols take the two physical ports; PLCs speaking the same addressable protocol such as Modbus RTU can share the RS-485 port. Configure and prove one link at a time, and the second link is a repeat instead of a rework.

Pick the arrangement before the cable #

Match each PLC's serial interface and protocol first; the cable follows that decision, not the other way around.

Arrangement Ports used Choose it when What must be right
One PLC per RS-232 port Both ports as RS-232 (selectable port set to RS-232) Both PLCs have RS-232 ports and sit close to the panel A cable with the correct pinout for each PLC, one point-to-point link each
RS-232 plus RS-485 The RS-232-only port, plus the selectable port set to RS-485 One PLC is RS-232 only, the other has RS-485 The selectable port's interface mode set before wiring; pair polarity observed
Both PLCs on one RS-485 bus The selectable port only, set to RS-485 Both PLCs speak the same addressable protocol such as Modbus RTU Distinct station addresses, daisy-chained trunk, termination at both trunk ends

One rule decides the third row: an HMI serial port executes a single driver. A port polling Modbus RTU cannot simultaneously serve a different PLC protocol, so two different protocols mean one port each. On the shared bus, both PLCs answer to the one protocol the port runs, each at its own station address. If the job also needs the controllers handled as separate operating modes rather than simply as two links, connecting one HMI to two PLCs with independent modes covers that half of the design.

RS-232, in TIA-232 terms, is single-ended: each signal is one conductor referenced to ground, one driver and one receiver, with the standard's classic reach of about 15 m at 19200 baud. Where the panel manufacturer specifies a cable for a given PLC, use it — pinouts differ between PLCs, and a connector's shape says nothing about the wiring behind it. The method in building the RS-232 Modbus cable between an HMI and a controller transfers directly to any point-to-point PLC link.

RS-485 (TIA-485) is differential: the signal is the voltage difference between the two conductors of a pair, which is why it tolerates the noise and the distance — up to 1200 m at reduced data rates — that a single-ended link cannot. Polarity is the wiring trap, because A/B markings are not standardized across vendors: follow both devices' manuals and keep the same polarity at every node. Daisy-chain the trunk with short drops, terminate the two physical ends with 120 Ω, and set any bias resistors the manuals call for. The protocol half of that bus is worked through in choosing the RS-485 protocol for one HMI and multiple PLCs.

  1. Record the panel model and both PLC models from their labels, then each device's serial interface, protocol and connector from the manuals.
  2. Set the selectable port's interface mode — RS-232 or RS-485 — to match its PLC before wiring it.
  3. Create each PLC as its own device connection in the HMI project, on its own port, with its driver selected.
  4. Make baud rate, data bits, parity and stop bits identical at both ends of that link; the two links do not have to match each other.
  5. On the shared RS-485 bus only, set the two PLCs to distinct station addresses — 1 and 2 — and point the HMI connection at those addresses.
  6. Download the project with only the first PLC wired, and confirm a known register reads with the expected value.
  7. Wire the second PLC and confirm its known register through its own connection, then check every screen for values coming from the intended PLC.

Worked example: the wire-time floor on the shared bus #

Calculated example, not a measurement. Both PLCs are Modbus RTU slaves at addresses 1 and 2 on the selectable port set to RS-485, at 19200 baud with 8 data bits, even parity and 1 stop bit — 11 bits per character.

  • Character time: 11 bits ÷ 19200 bit/s = 0.573 ms.
  • Request reading two holding registers: 8 bytes × 0.573 ms = 4.58 ms.
  • Reply carrying those two registers: 9 bytes × 0.573 ms = 5.16 ms.
  • Frame gap of 3.5 character times after the request and again after the reply: 2 × 3.5 × 0.573 ms = 4.01 ms.
  • One slave per cycle: 4.58 + 5.16 + 4.01 = 13.75 ms.
  • Both slaves polled in turn: 2 × 13.75 ms = 27.5 ms per round, so each PLC refreshes about 36 times per second on the wire.

That 27.5 ms is the serial floor, not the delivered rate: the PLC's response time, the driver's poll scheduling and the screen refresh add on top, so measure once both links run. The floor scales predictably — 38400 baud halves it — and splitting the two PLCs onto the two ports polls them in parallel, giving each its own 13.75 ms cycle, about 73 refreshes per second.

Decision by case: both PLCs on Modbus RTU within one cable run, and roughly 36 updates per second is enough — share the RS-485 port with addresses 1 and 2 and keep the RS-232-only port free. Two different PLC protocols — two ports, one link each, polled in parallel. Faster updates than the shared bus delivers — two ports, or a faster baud rate both devices support.

  • The selectable port still set for the other electrical standard: an RS-232-wired PLC on a port driven as RS-485 stays silent, and so does the reverse.
  • A cable built for a different PLC or port: fit the specified cable for that exact PLC-and-port pair before touching software.
  • Settings on the dead link only: the working link proves its own port, cable and parameters, nothing about the second port. Compare baud, data bits, parity, stop bits and station address end to end.
  • A duplicated station address on the shared bus: two slaves answering one address corrupt both replies.
  • The connection assigned to the wrong port or the wrong driver in the project: check the connection's port assignment, not just its address.

To make a fault follow the hardware, change one element at a time — cable first, then port — with the machine in a safe state. A controller that loses and regains its HMI link mid-cycle can react when the link returns, so know what the PLC is configured to do on communications loss before pulling a connector.

Questions asked

Can both PLCs share one port if they speak different protocols?

No. A serial port executes one driver at a time, so two different PLC protocols need the two physical ports. Both PLCs can share the RS-485 port only when they speak the same addressable protocol, each answering to its own station address — that is what lets one bus carry two controllers.

Does the selectable port detect RS-232 or RS-485 automatically?

No. Nothing in TIA-232 or TIA-485 negotiates the electrical interface, and the panel does not guess. Set the selectable port's interface mode before wiring, because a mismatch leaves the link silent instead of producing an error that names the cause.

How fast do screens update with both PLCs on the RS-485 port?

At 19200 baud with 11-bit characters, one request-and-reply cycle reading two registers takes 13.75 ms of wire time, so both PLCs polled in turn refresh about every 27.5 ms — roughly 36 updates per second each before PLC response time and driver scheduling add delay. Doubling the baud roughly halves those figures; putting the PLCs on separate ports roughly doubles the per-PLC rate.

Can I add a third PLC later?

On the RS-485 bus, yes: give the third PLC its own station address and tap it onto the trunk, keeping termination at the two physical ends. Each added slave consumes its own slice of the same poll cycle, so the refresh rate divides across however many slaves the bus carries. The RS-232 port cannot take a second device; it is strictly one port, one PLC.

Keep reading

  • How-to

    Connecting Multiple HMIs to One PLC Over 200 ft Serial

    RS-232 on good cable can reach 200 ft at 9600 baud, but RS-232 connects exactly two devices, so three HMIs cannot share one PLC port. Put an RS-232-to-RS-485 adapter at the PLC and at each panel, daisy-chain one twisted pair, and terminate only the two ends. Confirm the PLC port's protocol accepts more than one master before ordering adapters.

    Industrial networks

  • How-to

    How to Share One RS-485 PLC Port Between Multiple HMIs

    Yes: several HMIs can share one RS-485 PLC port when the protocol coordinates who transmits — DH-485 token passing is the classic case — and every node holds a unique address. RS-485 itself only sets the electrical layer: 32 unit loads per segment, up to 1,200 m (4,000 ft) at low speed. Prove one panel, then add the rest one at a time and retest together.

    Industrial networks

  • Troubleshooting

    Why One PLC to Two HMIs Fails Over RS-422 Multilink

    A 1:1 serial test proves one cable and one framing set; it cannot prove a shared n:1 multilink. Fix two HMIs on one RS-422 trunk by running the multilink driver entry on both panels, giving each a unique link identity, matching every serial parameter, and terminating only the trunk ends. The documented limit is 16 displays, so two panels are a configuration problem, never a capacity one.

    Industrial networks