Troubleshooting
Fixing Goto Display Buttons Locked by HMI Global Connections
Short answer
While the Global Connections remote display number is active — its DINT tag still holding 21 — FactoryTalk View ME disables every other form of navigation, so Goto Display buttons stay dead whether or not the popup is visible. Write 21 with a one-shot on bit A and let a startup macro on display 21 reset the tag to 0; the popup stays up and the buttons respond.
On this page
- Why do Goto Display buttons stop working after a popup opens?
- Where is the remote display number configured?
- How do you release the display call without losing the popup?
- What does the timer workaround do differently?
- When is a remote display call the wrong tool?
- Which fix fits which requirement?
- How do you confirm the lockout is gone?
- Questions asked
Fix it with two writes: a one-shot move of 21 into {[Local]PopupControl} on bit A's rising edge, and a startup macro named resetremotedisplay on display 21 that writes 0 back to that same DINT. Your Goto Display buttons are dead because the Global Connections remote display number is still in control: once {[Local]PopupControl} holds 21, FactoryTalk View ME disables every other form of screen navigation, and it stays disabled until that tag reads 0 again. The buttons themselves are fine — the active remote display request is what blocks them, whether the popup is visible or hidden. This fix keeps the automatic call and releases control the moment it is served, so the popup stays up and the buttons respond. The sections below cover the diagnosis, the macro fix, the timer variant, the cases where a display call is the wrong tool, and the checks that prove the lockout is gone.
Why do Goto Display buttons stop working after a popup opens? #
Because the Global Connections remote display number is still active: while {[Local]PopupControl} holds 21, FactoryTalk View ME disables every other form of screen navigation, including Goto Display buttons that have nothing else assigned to them.
The lockout follows the tag value, not the popup. The two buttons ignore touches with the popup shown and with it hidden, because hiding the display changes nothing in the request tag — it still reads 21. Everything else on the control screen keeps working because those objects are not navigation; the Goto Display buttons are.
Do not reconfigure the buttons. Their destinations are correct, and no amount of reassignment restores them while the remote display request owns navigation. And do not treat this popup as a visibility-only object: a remote display call takes over navigation control, while showing and hiding an object on the current display never touches navigation at all.
Match what you see against the three cases before changing anything:
- Both Goto Display buttons dead after display 21 is called, rest of the screen working — the remote display number is still active. Monitor the tag and confirm it still holds 21.
- Popup opens on bit A, but no Goto Display action can take over afterward — the active call keeps directing the HMI, because the request tag has not returned to 0.
- Popup never opens at all — this is not the lockout. Trace bit A, the move of 21, and the tag assignment in the Global Connections field.
Where is the remote display number configured? #
In FactoryTalk View Studio, double-click Global Connections in the project tree, open the Display tab, and read the Remote Display Number field — in this application it holds {[Local]PopupControl}, the DINT that bit A loads with 21.
That field is the whole mechanism. When the runtime reads the value the tag carries, it calls the display whose number matches, so 21 opens display 21 on top of the control screen. The same Display tab can also write the number of the current display back to a PLC tag; that field only reports which display is up. The navigation lockout comes from the Remote Display Number field alone.
The intended cycle in this application: bit A turns on and the PLC moves 21 into the tag, and the popup is called; bit B turns on and the PLC moves 0, and the request is released. Monitor the tag while the symptom is present — a value stuck at 21 is the lockout; a value that never leaves 0 means the call path, not navigation, is your problem.
How do you release the display call without losing the popup? #
Make the PLC write 21 once, then let the called display clear the request itself: a one-shot move of 21 on bit A's rising edge, plus a startup macro on display 21 that writes 0 to PopupControl.
- Leave the Global Connections field pointing at the DINT it already uses, and confirm the field text is exactly the tag your PLC logic writes.
- In the PLC, condition the move of 21 with a one-shot on bit A's rising edge. A plain move rewrites 21 every scan while bit A stays high, which re-locks navigation right after every reset.
- In the HMI, create a macro named
resetremotedisplaywhose single action writes 0 to PopupControl. The macro must write to the exact tag named in the Remote Display Number field — a name or scope mismatch is the same family of fault as why an HMI macro PLC tag is missing from the PLC program. - Open display 21, right-click the display background, choose Display Settings, open the Behavior tab, and under Macros set
resetremotedisplayas the Startup macro. - Download the application and run the sequence. Rehearse it first the way testing an HMI simulation against a live PLC describes, rather than discovering the behavior on the running machine.
The order is what makes it work: the call requests display 21 first, and the macro clears the request only after that display has started. The popup stays on top and the two Goto Display buttons respond again. The original bit B logic remains the close path in concept, but once the macro has already returned the tag to 0, a further write of 0 changes nothing — plan the close as an operator control on the popup or as part of the sequence-complete logic, and test it.
One caution before you download: if this popup exists to keep the operator out while a sequence moves the machine, releasing navigation control changes what they can touch during that sequence — confirm that is intended.
What does the timer workaround do differently? #
It clears the request on elapsed time instead of display start: one-shot 21 at bit A, a timer that runs while bit A stays high, then a one-shot 0 when the timer finishes — 3 seconds in the implementation it came from.
This variant touches only the PLC, which is its point: use it when the HMI application cannot be modified. Bit A rises, a one-shot moves 21 into the tag, a timer runs for as long as bit A stays high, and the timer's done bit drives a second one-shot that moves 0.
Run the numbers on the example's values. Timer preset: 3000 ms, which is 3.0 s. Bit A stays high for 12 s during the sequence. The call lands at t = 0 s; the accumulator reaches 3000 ms at t = 3.0 s; the done-bit one-shot writes 0. The request is active for 3.0 s of the 12 s high time — 3 ÷ 12 = 0.25, so the buttons are dead for 25% of the sequence and alive for the remaining 9.0 s. The macro fix instead clears the request at display start, so its dead window is a single display load.
The 3 s is that implementation's choice, not a requirement. Set the preset above the display's load time with margin, and know the failure mode: if bit A drops before the accumulator reaches the preset, the timer resets, the done bit never fires, and the tag stays at 21 until bit B writes 0 — the exact lockout you were removing.
When is a remote display call the wrong tool? #
When the goal is an indication rather than a navigation takeover: show the content on the existing display with a visibility animation, or make the popup operator-initiated, and no remote display request ever exists to lock the buttons.
- Indication only — put the popup content on the base display as objects with a visibility animation driven by an expression on bit A. Nothing navigates, so nothing can lock. The tradeoff is screen clutter, which is exactly why a separate display was wanted on a busy screen; weigh the two against each other.
- Operator decides — the pattern used as a stopgap in this application: a button visible only while bit A is active, wired as a normal Goto Display to the popup. Navigation stays ordinary; the interaction becomes operator-initiated instead of automatic.
- Notify without leaving the screen — a Local Message fits a condition the operator must see but not act on.
- Block the operator deliberately — then the lockout is the feature. Keep the request active for the whole sequence and write 0 only at sequence end, accepting that the two Goto Display buttons are dead until then. If operators must keep using the control screen during the sequence, do not design the call as a blocking interaction.
Which fix fits which requirement? #
Pick by what the operator must do during the sequence: forced popup with working navigation takes the macro reset, an unmodified HMI application takes the timer, and anything short of a forced call takes visibility or a button.
| Requirement | Approach | Navigation locked for |
|---|---|---|
| Forced popup at sequence start, buttons must keep working | One-shot 21 on bit A plus resetremotedisplay as display 21's Startup macro |
One display load |
| HMI application cannot be modified | One-shot 21, timer while bit A is high, one-shot 0 on the done bit | The timer preset — 3.0 s in the example |
| Indication only, no separate display needed | Visibility animation on the base display, expression on bit A | Not at all |
| Operator chooses when to open the popup | Button visible while bit A is active, normal Goto Display | Not at all |
| Operator must be blocked during the sequence | Keep the request active, write 0 at sequence end | The whole sequence, intentionally |
How do you confirm the lockout is gone? #
Watch two values and two presses: bit A and {[Local]PopupControl} through one full trigger, then each Goto Display button after the popup opens — the tag must read 0 while the popup is up, and both buttons must navigate.
- Trigger the sequence and watch the tag: the one-shot writes 21 and display 21 opens on top.
- Confirm the tag returns to 0 while the popup is still displayed — that is the macro doing its job.
- Press both Goto Display buttons; each must reach its alarm or indicator display and return.
- Repeat the full sequence. One good cycle does not prove the reset fires on every trigger.
- Close the popup through its own close path and confirm the next trigger still works.
If the tag sits at 0 and the buttons are still dead, the remote display request is no longer the suspect: confirm the macro is assigned to display 21 itself under Display Settings, Behavior, Startup, confirm the macro writes the exact tag in the Global Connections field, then troubleshoot the buttons' own configuration.
Questions asked
Does the popup close when the startup macro resets the tag to 0?
No. The reset only hands navigation control back; the called display stays on top. That means the original close path — bit B moving 0 — has nothing left to change once the tag already reads 0, so plan a separate close: an operator close control on the popup, or a close action in the sequence-complete logic, and test it.
Is the remote display number the same as the display number the HMI writes back?
No. The Display tab of Global Connections does two separate jobs. The write-back reports the number of the display currently on screen to a tag, which is useful for logging and PLC-side logic. The remote display number works the other direction: the tag value drives which display the runtime calls. Only the second one locks navigation.
Why does bit A need a one-shot instead of a plain move?
A plain move rewrites 21 on every PLC scan while bit A stays high. The startup macro's 0 then survives only until the next scan, the tag settles back at 21, and the buttons lock again. The one-shot issues the request exactly once per trigger, so the macro's reset is the last write and navigation stays free.
The tag already reads 0 but the buttons are still dead. What now?
Confirm the macro is assigned to display 21 itself under Display Settings, Behavior, Startup — a macro attached to a different display never runs. Then confirm the macro writes to the exact tag named in the Remote Display Number field, including its scope. If both check out, the remote display request is not your problem; the fault is in the buttons' own configuration.