IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing a PanelView Plus selector that does not respond

HMI and touchscreens Published 6 min read

Short answer

When the PLC sees the selector signal but the PanelView Plus screen does nothing, compare the communication shortcut's PLC address with the controller's real IP first. In the case behind this article, repointing the shortcut from 192.168.1.150 to 192.168.1.105 was the entire fix. Only if other tags still update should you open the object and compare its Value and Indicator connections.

On this page
  1. Whole screen or one object: pick the fault first
  2. Check the shortcut address before the application
  3. Worked example: one transposed octet
  4. If other tags update: the Value and Indicator split
  5. Confirm the selector end to end
  6. The version 5.10 .MER file
  7. Questions asked

When the PLC sees the selector signal but the PanelView Plus screen does nothing, the fix is usually one address: the communication shortcut's PLC address, checked against the controller's real IP. In the case behind this article the shortcut said 192.168.1.150 while the controller was 192.168.1.105; repointing it and restarting the runtime fixed the screen with no application edit. That is where you start. Open the object's connections only when other tags on the screen still update — then the path is healthy and the fault is local, most often Value and Indicator connections pointed at different tags.

Whole screen or one object: pick the fault first #

A selector on a PanelView Plus screen is typically a Maintained Pushbutton or a Multi-State Indicator, and the object is only as alive as the terminal's link to the controller. Decide first whether the whole screen is stale or one object is dead; the two faults get different fixes.

What you see Likely cause First check
Nothing on any screen updates; values stale or in error Shortcut points at the wrong controller address, or the path is down Shortcut address against the controller's real IP, then ping
Other tags update; only the selector is dead Value and Indicator connections on different tags Object properties, connections
Object changes on press, then snaps back PLC logic overwrites the written tag, or the indicator tag is driven separately The tag the object writes against the tag it displays
First press works, the next sends the wrong state Multi-State next-press source set to the internal value instead of the indicated value General tab of the Multi-State object

Unreadable tags have a look of their own: on a terminal with the control module in the back, they come up as the pattern explained in PanelView Plus logic module shows question marks on live values, not as frozen numbers. Stale everywhere means path; stale in one place means object.

Check the shortcut address before the application #

The terminal holds no selector state of its own. It reads and writes controller tags through a communication shortcut, so one wrong address makes every tag on every screen unreadable and every press fail together — which is exactly what a dead selector looks like from the operator's side.

Work in this order:

  1. Read the PLC's IP from the controller itself — its project or status screen — not from a drawing or memory.
  2. Ping that address from a laptop on the same subnet and note whether it answers.
  3. On the terminal, open Terminal Settings > Networks and Communications and record the terminal's own IP address, subnet mask, and gateway.
  4. Open the communication setup where the application's device shortcuts are defined — FactoryTalk Linx on current versions — and read the address in the shortcut that targets the controller.
  5. Correct the address, save, and restart the runtime application so it reloads the path.

One documented trap: if the PLC's IP address has been changed, the terminal loses communication because the shortcut still carries the old address. The fix is the shortcut, not the objects. When the controller is powered but still unreachable, the failure modes in why a PanelView Plus shortcut fails to reach an offline PLC are the next thing to work through.

Worked example: one transposed octet #

Representative numbers, the same arithmetic you run on site.

  • Terminal address: 192.168.1.24, subnet mask 255.255.255.0
  • Controller address, read from the controller: 192.168.1.105
  • Address in the shortcut: 192.168.1.150

Subnet check first. 192.168.1.24 AND 255.255.255.0 = 192.168.1.0, and 192.168.1.105 AND 255.255.255.0 = 192.168.1.0. Terminal and controller share the 192.168.1.0/24 subnet, so the mask and gateway are not the fault.

Ping test next. 192.168.1.150 times out — nothing owns that address. 192.168.1.105 answers in 1 ms.

Decision: repoint the shortcut from 192.168.1.150 to 192.168.1.105 and restart the runtime application. Live values return, and the selector follows the physical switch through every position. That correction is what resolved the reported case, with no object edits.

If other tags update: the Value and Indicator split #

When the rest of the screen is alive and only the selector misbehaves, open the object and read its connections. A Maintained Pushbutton has two: the Value connection is what the HMI writes to the controller, and the Indicator connection is what the object displays.

If they are two different tags, the object writes one and shows the other. The display moves only when PLC logic copies the written value into the indicated tag — the vendor's own guidance describes this split as the way to see that the write reached the controller. If that copy logic does not exist, the button looks dead while the controller value is actually changing.

The split is sometimes deliberate. A Manual/Auto selector that must drop to Manual on a fault or an emergency stop needs the PLC to change the indication without the HMI, so logic other than the operator's press controls what is displayed. That logic must echo the commanded state back to the indicated tag. Test any fault- or emergency-stop-forced position with the machine in a safe state before it returns to production.

On a Multi-State Indicator, the General tab decides what the next press sends: the internal value last written to the controller, or the value arriving on the indicator connection. The wrong source makes the selector skip states or send stale ones. A list that lags one press behind is a different behavior, covered under why PanelView Plus piloted list selectors do not update.

None of this is visible in the screen graphic. Read the actual connections before changing anything.

Confirm the selector end to end #

  • Watch a fast-moving tag, such as a counter, and confirm it updates on screen.
  • Turn the physical selector and watch the controller tag change in the programming software.
  • Press the object from the HMI and confirm the controller tag takes the commanded value.
  • Cycle through every position, including any fault- or emergency-stop override, and confirm the display matches the controller state in each.
  • Cycle terminal power and confirm the application starts with a healthy connection and the selector still tracks.

The version 5.10 .MER file #

The runtime .MER in this case was created in version 5.10 and would not convert into an editable project in the newer software. That blocks editing, not diagnosis: the address and shortcut checks above need no project at all.

To inspect object connections, copy the .MER from the terminal to USB and open it in the software version that created it. For vendor support, go through the manufacturer's official channels with the terminal catalog number, firmware revision, and software version, and get the owner's permission before sharing a project file.

Questions asked

Does a wrong PLC IP stop HMI writes as well as reads?

Yes. The shortcut path carries every tag in both directions, so one wrong address makes the whole screen go stale and every press fail together. That pattern, nothing updating anywhere, is your clue that the fault is the path, not the selector object. Reads and writes recover together once the shortcut points at the real controller address.

The PLC IP address was changed and now the HMI does not respond. Same fault?

Yes. The documented behavior is that the terminal loses communication because the shortcut still carries the old address. Update the shortcut to the new address and restart the runtime application; no object edits are needed.

Where on the terminal do I check its own network settings?

Open Terminal Settings > Networks and Communications. Record the terminal's IP address, subnet mask, and gateway, and check that the terminal and controller share a subnet. If they do not, fix that before touching the shortcut.

Why would anyone point Value and Indicator at different tags?

When something other than the HMI must change the indication, such as a Manual/Auto selector that drops to Manual on a fault or emergency stop. The PLC then controls what the operator sees, and its logic must echo the commanded state back to the indicated tag or the button appears dead.

Can I fix the project if the .MER will not convert?

Only in the version that created it, 5.10 here — but never edit the only copy on the terminal. Copy the .MER to USB first, work on that copy, and test the edited application before replacing the runtime on the terminal, so a bad edit cannot take the operator station down with no rollback.

Keep reading

  • Troubleshooting

    Why a PanelView Plus Shortcut Fails to Reach an Offline PLC

    The shortcut that runs is the one on the Runtime (Target) tab, and it must end at the ControlLogix CPU, not at the 1756-EN2T. Map the route through the EN2T to the CPU slot, copy it to the runtime schema, and download with "replace communications" checked. The EN2T revision is not this fault.

    HMI and touchscreens

  • How-to

    How to Disable a Remote HMI Display Through PLC Control

    Put the interlock in the PLC, not the panel. Read each panel's current screen through Remote Display Number, force display 21 through Replace Display Number while the disable bit is latched, and on release write the stored number back, hold one second, then write 0 so the panel never reports it is being controlled remotely.

    HMI and touchscreens

  • Troubleshooting

    Fixing invalid PLC type in Vijeo Designer 6.2 SP12

    When Vijeo Designer 6.2 SP12 leaves %M and %MW exchanging but kills %I and %Q with Invalid PLC Family/Model/Type (ModbusEquipment01), the fault is the software build, not the addressing. Request the SP12 hotfix from Schneider Electric technical support — HF5, build 6.2.12.2056, or the earlier HF3, build 6.2.12.2052 — then rebuild, download, and verify each address class separately.

    HMI and touchscreens