Yes on both counts. Every panel shows the same toggle state when the toggle's write address and the displayed state both point at one shared PLC bit, and a ladder rung that unlatches that bit shows on every panel within one update period. The checks that make it true: the same address on every panel, a write-once toggle, and a live test with the PLC online.
Yes on both counts. Every panel on the network shows the same toggle state when the toggle's write address and the displayed state both point at one bit in the PLC, and ladder logic that unlatches that bit shows on every panel at its next read. The panel that pressed the button owns nothing; the PLC bit is the state. What you verify is the bit and the two addresses bound to it on each panel, plus one behavior of the button object: whether it writes once per press or rewrites its commanded state every cycle. This page walks the data path, the timing, and the test order that proves it on the floor.
Why every panel follows the bit
A toggle object in HMI software does one job: each press inverts the value at its configured address and writes the result to the PLC. The graphic then shows whatever value the panel reads back. Agreement between panels needs no extra wiring, because no panel keeps the state; PLC memory does. Press the enable button on panel one and panel two shows it pressed too, for the plain reason that both screens draw the same variable in the PLC.
That agreement has one limit worth naming: each panel refreshes on its own update cycle, so a panel can show an old value until its next read. The state is shared; the instant of display is per panel. Networking many remote panels to one PLC is the plumbing; the shared bit is the discipline on top of it.
One bit for the write and for the display
Two addresses decide whether the panels agree. The first is the toggle's write address. The second is the source of the displayed state: the button's own state indication, or the indicator object next to it. Bind both to the same PLC bit in every project on the network.
The common mismatch is a button that writes the PLC bit while its indication reads a panel-local tag or a neighboring address. The panels then disagree for good, and pressing harder fixes nothing. Read both addresses out of each project and compare them; that is a five-minute check per panel that settles most out-of-sync toggle calls.
Keep one bit for the whole network. Giving each panel its own bit creates separate states, and nothing in the PLC copies one to the other unless you write that rung yourself. The single-panel version of the wiring, linking an F key to toggle a memory bit, shows the same two-address rule on one screen.
What the PLC may do to the bit
Ladder executes against the same memory the panels read, so a rung that unlatches the bit wins whenever it scans, and every panel shows the result at its next read. Plan for two PLC-side behaviors.
A startup clear. A retained bit can come back on with the machine after a power cycle, so clear shared command bits on the PLC's first scan. Panels simply read the cleared value.
A fight with the button. Toggle objects differ in one way that matters here: some write the new state once per press, and some keep writing the last commanded state on every update cycle. With the rewriting kind, an unlatch holds only until the panel's next write, and then the bit comes back. When the PLC must override the operator, that difference decides whether the override sticks; the symptoms of the PLC overriding an HMI toggle start here. If the ladder owns the bit, use an ON/OFF pair of buttons that set and reset once each, or let the panels write a command bit and display a state bit the ladder computes. Shared writes have one more failure mode: when a PLC output turns on too early, the first suspect is a second rung writing the same bit.
Example: two panels, one shared bit, a 1 s update
The case: two panels, A and B, writing and showing one PLC bit, with a door interlock in ladder that unlatches it.
Inputs:
- One discrete bit in PLC memory; call it
RUN_CMD, the same address in both panel projects. The two panels and the unlatch come from the job itself. - The bit's update period on both panels: 1 s. That is the assumed setting for a status tag when you have not set one.
- The operator presses the toggle on panel A at t = 0 s.
- The door opens at t = 5 s and its rung unlatches
RUN_CMD.
The rule in words: a panel displays the bit no later than one update period after the PLC last changed it, and two panels can disagree with each other for at most one period, because each reads on its own clock.
The walk:
- t = 0 s: the press on panel A writes
RUN_CMD= 1. Panel A shows 1. - Worst case for panel B: its read of
RUN_CMDfinished just before the write, so it shows 1 at its next read, at t = 1 s. The two screens disagree for at most 1 s. - t = 5 s: the door rung unlatches
RUN_CMDto 0. The PLC changes its own memory the moment the rung executes; every delay after that is panel read time. - Both panels show 0 by t = 6 s, which is 5 s + 1 s.
- Run the same six seconds with a rewriting toggle: at t = 6 s panel A's next write restores
RUN_CMD= 1, and the door interlock never sticks.
The result: at a 1 s update period, no operator sees a state older than 1 s, the two screens disagree for at most 1 s, and a rewriting toggle defeats the interlock inside one period.
The decision: keep the shared bit's update period at 1 s or faster for state you merely read, and at 250 ms or faster when an operator must act on the change; a 2 s period already means up to 2 s of stale display. Keep the toggle write-once, at any period, wherever ladder can clear the bit.
Reading the state from the floor
Operator screens sit at arm's length. A shared state on a floor board is read from across the aisle, so size the words by distance: plan 30 ft of viewing distance per inch of letter height (FHWA), and 20 ft per inch when the reader is walking. A board read from 30 ft wants 1 in capitals, 1.5 in for walking readers, with lines spaced 1.7 x the capital height. Show the states as words, RUN and STOPPED, driven by the same bit; two text states from one PLC bit is the wiring for that.
If the job is a board that only shows status, put a signage screen on that wall and keep the writes on the HMI. Our shop-floor signage displays cover exactly that wall; they are signage, not operator interfaces, so the control stays where it is.
What you can check without the PLC
The address review is an offline job. Open each project and read out three things: the toggle's write address, the source feeding the displayed state, and the bit's update period. Every panel should name the same address, and the period should match the decision from the example. Layout, colors and wording can all be finished with the PLC absent.
What waits for the live system is behavior: the write landing, the propagation to the other panels, the unlatch from ladder. An offline test cannot confirm any of those, so book the commissioning window for the four steps below. A panel programmed without its PLC is a drafted screen, and the network holds up only in the live test.
The live test, in order
- Bring the PLC online and open the shared bit in the programming software's data monitor.
- Press the toggle on panel A. Confirm
RUN_CMDchanges in the monitor and both panels show the new state within one update period. - Trigger the real unlatch condition, the door switch itself and not a forced rung input if the interlock guards anything. Confirm the bit clears and both panels follow it to 0. If the bit returns with nobody at a panel, the toggle rewrites; change the button or move to the command-bit pattern.
- Repeat from panel B, then press both toggles inside the same second. The last write to reach the PLC is the value that stands, and both panels settle on it; two HMIs writing to one PLC covers the ordering.
Recommendation: Bind the toggle write and the state indication to one shared PLC bit on every panel, keep that bit's update period at 1 s or faster for status and 250 ms when an operator acts on it, and confirm the toggle writes once per press. Where ladder logic must command the state, let the panels write a command bit and display a state bit the ladder computes, and clear both on the PLC's first scan. Run the four steps above before you call the panel network done.
Questions
Will the panel that made the press show the new state before the others?
It shows its own press immediately, and the others follow within one update period each. No panel owns the state. If one panel lags by more than one update period, suspect its communication link and check the panel's status before touching any button address.
Why does the shared bit come back on after the ladder unlatches it?
Some toggle objects write the new state once per press; others rewrite the last commanded state on every update cycle, and that kind re-raises the bit within one period of the unlatch. To tell them apart, watch the bit in the PLC's data monitor with nobody at the panels: a value that flips back on a steady rhythm is being rewritten. Fix it with a write-once toggle, an ON/OFF button pair, or a command bit plus a ladder-owned state bit.
What happens when two operators press toggles at nearly the same moment?
Both writes reach the PLC, and the last one to arrive is the value that stands; both panels then read that same value and settle together. The losing press leaves no trace unless you log it. If two stations can command one machine, give each a command bit so the ladder can see who asked.
How many panels can share one toggle bit?
The bit itself has no panel-count limit; the limits are the PLC driver's connection count and the polling load. Each panel adds one read of the same address per update period, so a dozen panels at 1 s is light traffic. The number to check is the connection limit your PLC documentation states.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.