One HMI reads two PLCs by holding one connection to each controller. For display-only readings that is the whole architecture. Add a controller-to-controller exchange only when one bank's logic consumes the other bank's values, or consolidate the analog inputs into one controller when the banks sit close.
Yes, one touch panel can read two PLCs. For eight analog transmitters that only feed a screen, the panel holds one connection to each controller, binds every tag to the connection it reads, and the controllers never talk to each other. A controller-to-controller link enters the design only when logic in one bank consumes a value measured in the other, and only when a free port exists at both ends. Check the simplest option first: if the two banks sit close together and one controller takes all eight analog inputs, one controller and one connection replace two of everything. The sections below give the decision rule, the port arithmetic, and the checks to finish before any cable is terminated.
Does any value cross the bank boundary
This one question picks the architecture. Take the eight transmitter values one at a time and write down two things for each: which screen object shows it, and which rung of controller logic consumes it. When every value is consumed only by the bank that measured it, the two controllers are independent, and the panel is the only device that needs to see both. When one or more values feed logic in the other bank, each of those values needs a documented path from its source controller to the consuming controller.
A panel that reads both controllers shows values from both; it does not move data from one controller's memory into the other's. The screen displays a number, it does not feed the second controller's logic. Plan each crossing value as a controller-to-controller exchange: controllers that share a network protocol such as EtherNet/IP can exchange tag values directly, configured in the two controller projects, with no panel involved. A copy scheduled by the panel can serve as a convenience transfer where the controllers cannot exchange data themselves, but the copy stops when the panel is powered down, so keep trips and interlocks off that path.
How one panel holds two connections
Current panel software handles multi-controller projects as a connection list. You add one connection entry per PLC, each with its own driver and path, then bind every tag and screen object to the connection it belongs to. Two controllers can use identical register addresses without colliding, because each tag names its connection as well as its address. The pattern is documented across panel families; the wording differs, the structure does not.
The limits live in both manuals. The panel manual states how many device connections one project supports: at least one current family documents 16 simultaneous device drivers in a single project, others allow fewer, and some panels allow a single connection only. The controller manual states how many clients may connect at once, and that cap can bind first. Check both numbers before promising two controllers on one panel.
Wiring follows the protocol. Over Ethernet, both connections ride the plant switch and each controller needs one free Ethernet port. Over serial, one shared multidrop bus can carry the panel's connection to several controllers; the wire-level rules live in wiring one HMI panel to three PLCs on an RS-422 multidrop. RS-422, the TIA/EIA-422 electrical standard, is rated to about 1,200 m of cable at 100 kbit/s at its long-reach end, so the short hop between two nearby banks sits far inside the limit.
The arrangements that work
Four arrangements cover the job; three are structurally sound, and the fourth carries one condition.
| Arrangement | Choose it when | What to watch |
|---|---|---|
| One controller with eight analog input channels | Both banks sit within wiring reach of one cabinet, and the controller has the slots and channels | Analog channel count and card slots; one program to maintain instead of two |
| Two controllers, panel polls each | The readings are display-only, the banks are far apart, or the machines already exist | The panel's connection limit and each controller's client cap; bind every tag to its connection |
| Two controllers plus a controller-to-controller exchange | Logic in one bank consumes the other bank's values | A free port at both ends, or a shared Ethernet network; a defined response in the receiving logic for a lost link |
| Two controllers plus a panel-scheduled tag copy | A convenience transfer is needed and the panel project supports scheduled events | The copy runs only while the panel is powered and its project runs; keep trips and interlocks off this path |
Count the ports before you commit
Draw the ledger before you buy or terminate anything. List every communication link in the design, and for each one write the port it uses at each end. Then compare, controller by controller, the ports the ledger needs against the ports the hardware has.
Serial ports earn the closest look. Plan one relationship per serial port unless both manuals document sharing it, because the classic failure here is a single serial port that the panel already holds while the controller-to-controller link is told to use the same connector. Over Ethernet the ledger is short: one free Ethernet port per device carries the panel connection and the tag exchange together, since a switch lets many sessions share one physical port.
Where a crossing value drives an output, write the communications-loss response into the receiving controller's logic: a defined state on timeout, so a broken link cannot leave a frozen last value holding a pump or a contactor. The same ledger arithmetic returns later when someone wants a second screen or a data collector; adding another operator interface when the PLC ports are full works that case step by step.
Example: two banks of four transmitters, 10 ft apart
Scenario: eight analog transmitters, four in bank A and four in bank B, mounted 10 ft apart, feeding a 6-inch touch panel. No output in either bank depends on the other bank's inputs; every value feeds a screen object.
Count the crossing values: walk the eight transmitters, and each lands on the list with a single consumer, its own bank's display. Crossing values: 0.
Size the links: two panel connections, one per controller, and 0 controller-to-controller links. Total: 2 links.
Run the ledger. On serial, the panel's multidrop bus reaches both controllers, one relationship per port, so the panel connection takes each controller's serial port. Ports needed per controller: 1. Ports available: 1. Margin: 0, which holds as long as the design adds no further link. Bus length lands in the tens of feet, far inside the RS-422 rating of about 1,200 m at 100 kbit/s. Decision: the panel polls both controllers and the design is finished, with no exchange hardware and no shared memory to configure.
Flip one condition. Bank A's transfer pump must trip when bank B's level transmitter passes a high limit. Crossing values: 1, consumed by a rung in bank A. Links: 2 panel connections plus 1 controller-to-controller exchange, 3 total. Serial ledger: 2 ports needed per controller against 1 available, a shortfall of 1, so serial fails. Ethernet ledger: 1 free Ethernet port needed per device, and each controller has 1 spare, so it passes. Decision: move both links onto Ethernet, configure the tag exchange in the two controller projects, and write the trip response for a lost exchange into bank A's logic so the pump lands in a defined state instead of holding its last command.
When to pick something else
- The panel manual allows one device connection only. Two PLCs then need a different panel or a single controller. Do not chain the second controller through the first controller's registers unless the controller manual documents that transfer.
- Several screens or a plant-wide collector want the same values. Give the polling job to one master controller and let the screens read it; two HMI panels polling many PLCs: use a master PLC lays out that arrangement.
- A duplicate of the eight numbers belongs on a board in the office. That is a one-way signage display fed by prepared content, not a second panel connection; specify a read-only process display for a plant lists what to send with that quote.
What to ask for
Bring four lists to the bench and the architecture decides itself:
- From the panel manual: the driver list with the protocol each driver speaks, the number of simultaneous device connections one project supports, and the rule for binding a tag to a connection.
- From each controller manual: the physical ports, the protocol available on each, and any cap on simultaneous clients.
- From the process: the crossing-value list, the consumer rung for each, and the required response when an exchange is lost.
- From the drawings: the bank separation distance for the serial run, and the free ports per controller.
Recommendation: When the eight readings feed screen objects only, let the panel hold one connection per controller and build no controller-to-controller link at all. The moment a rung in one bank consumes a value from the other, add a documented tag exchange on a second port or on Ethernet, and put the loss-of-communications response in the receiving controller's logic. When both banks sit within one cabinet's wiring reach, consolidate the analog inputs into a single controller with eight channels and run one program.
Questions
Can one HMI also write values to both PLCs?
Yes, over the same two connections. Give every writable value one owner: the panel writes it to the controller whose logic uses it, and the other controller receives a copy through the controller-to-controller exchange if it needs one. Two writers to one register, the panel and the controller logic both setting the same value, produce values that jump between two numbers. Document the owner of each writable tag in the I/O list before you build the screens.
How do I keep identical register addresses in the two PLCs straight on screen?
Bind every tag to its connection, and name that connection in the tag or screen object so bank A's address 0 and bank B's address 0 stay separate values. Duplicate addresses across two controllers are legal on a connection list; the collision happens only when a tag omits its connection. A quick commissioning check: force a value in bank A and watch the identical address in bank B stay unchanged on the screen.
What if the two PLCs use different protocols?
The panel needs a supported driver for each controller, and panel families publish a driver list per protocol. If no driver exists for one of the two, the panel cannot read that controller directly. The practical fixes are a protocol converter on that link, a controller-to-controller exchange that hands the needed values to the controller the panel can read, or moving the odd controller's analog inputs onto the controller the panel supports.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.