Troubleshooting
PanelView Plus logic module shows question marks on live values
Short answer
Question marks on live values while graphics keep working mean the terminal cannot reach the controller, not that the .MER is corrupt. The same runtime running on another logic module proves the application is serviceable. Compare the two modules with the same cable, switch port and runtime, then fix the original's IP settings or its FactoryTalk Linx controller path; replace the module only when its network interface will not link.
On this page
Question marks on live values while buttons, screen changes and labels keep working mean one thing on a PanelView Plus: the runtime cannot reach the controller. The application is not corrupt — you proved that the moment the same .MER ran on another logic module and the values came back. The fault is in the original terminal's configuration or in its network interface. Work it in this order: reproduce the fault with the working module under identical conditions, read the original module's IP settings, verify the runtime's controller shortcut, and only then test the module's Ethernet interface.
What the question marks tell you #
A data object draws question marks when the runtime cannot obtain the value behind it. Buttons, navigation and static text come from the runtime file on the terminal, so they keep working while the runtime executes normally. Live values are the only objects that depend on the controller connection, which is why a screen can look healthy and still be dead on data.
Before changing anything, record:
- Which objects fail — every controller-backed value on every screen, or one group.
- That navigation, buttons and static text still work, which proves the runtime is executing.
- The terminal's diagnostic messages for the failing connection, with the exact text.
- That this is a live-value failure and not static text; text that turns into question marks after a project conversion is a different fault, such as text lost as question marks when an RSView ME .mer project is converted.
| Observed symptom | Most likely cause | Next check |
|---|---|---|
| Graphics work, all live values show question marks | Terminal cannot reach the controller | IP settings, then the runtime controller path |
| Only one group of values fails | One shortcut or one tag group | That shortcut's path in the runtime communication setup |
| Same .MER works on the other module | Terminal-side configuration or interface | Controlled comparison, below |
| No link on the original module with a proven cable | Network interface fault | Interface test before replacement |
Reproduce the fault with the working module #
The second module is your reference standard, but only if the comparison is controlled; swapping module, cable and switch port together hides the cause. Put the machine in a safe state before you open the terminal, because the operator loses both view and control while the logic module is out.
- Identify the exact .MER the working module runs — filename and revision.
- Load that same file on the original 2711P-RP8D.
- Test both modules with the same cable, the same switch port and the controller in the same state.
- Record from each terminal's own configuration screens: IP address, subnet mask, default gateway, firmware version and runtime version.
A matching runtime file does not make the two terminals identical. The communication configuration stored on the terminal can still differ, and downloading a runtime does not always overwrite it — read how a PanelView keeps its old FactoryTalk Linx configuration after a download before assuming the transfer carried the settings across.
Decision here: if both modules now fail, move upstream to the cable, switch port, controller or project path. If only the original fails, continue with its settings.
Read the original terminal's IP settings #
Read the settings from the terminal itself; a project file is a record of intent, not a measurement of the active interface.
- IP address: correct for this network, and not claimed by another device.
- Subnet mask: matching the controller's network plan.
- Default gateway: only needed when the controller sits on another subnet.
- Link LEDs at the terminal and the switch; reseat the connector and retest on the proven cable and port.
Illustrative worked example. The working module reports IP 192.168.1.15, mask 255.255.255.0, and the controller answers at 192.168.1.10. IPv4 subnetting per RFC 950 delivers locally only when the destination AND the mask equals the sender's own network:
- Working module: 192.168.1.15 AND 255.255.255.0 = 192.168.1.0
- Controller: 192.168.1.10 AND 255.255.255.0 = 192.168.1.0
Same network, so the terminal resolves the controller locally and the tags read. The original module instead reports 192.168.10.15: 192.168.10.15 AND 255.255.255.0 = 192.168.10.0, which is not 192.168.1.0. The terminal now treats the controller as remote and hands the traffic to the default gateway; with the gateway unset at 0.0.0.0, the route goes nowhere and every controller-backed object shows question marks while the graphics keep working. One digit in the third octet is the entire fault: put the terminal back on 192.168.1.0/24 and the values return.
Decision here: link up and addressing wrong — fix it and retest. Link missing on the original module only — go to the interface test. Link up, addressing correct and values still dead — the runtime path is next.
Verify the runtime's controller path #
The runtime resolves a controller shortcut to a device through the terminal's FactoryTalk Linx configuration (RSLinx Enterprise on older firmware). Graphics load from the local file, so a wrong destination still shows a working screen with dead values — the layout proves nothing about the path.
- Open the editable project in FactoryTalk View Studio when you have it, and inspect the runtime target of the communication setup, not the design-time browse tree.
- Trace the shortcut used by the failing objects to its controller and path.
- Compare that destination with the configuration that works on the replacement module.
- Confirm whether the loaded application carries its own communication configuration or inherits the terminal's.
- Correct the destination, reload, run and read the diagnostics again.
One documented edge case: a PanelView Plus 7 Standard shown with a yellow question mark in the RSLinx Enterprise browse tree is a browse-display issue fixed by applying the manufacturer's patch roll-up of Jan-2015 or later — a different fault from question marks on live values. For a shortcut that resolves but points at a controller that is not answering, the sequence in why a PanelView Plus shortcut fails to reach an offline PLC applies.
Decision here: values return after the path change — configuration was the cause, closed. Only some objects stay dead — their shortcut or tag references, not the network.
Test the original module's interface #
- Connect the original module on the cable and switch port proven with the working module; inspect the connector for damage and read the link LEDs at both ends.
- Move the working module onto that same connection without changing anything else, and note whether link follows the module.
- If both link, compare reachability and terminal diagnostics, and look for a duplicate address before calling it hardware.
The decision, case by case #
- Wrong address or mask on the original module: correct it, verify the values, keep the module.
- Shortcut or path wrong in the runtime configuration: fix the communication setup, reload, keep the module.
- Both modules fail on the same connection: the fault is upstream — cable, switch port, controller or the project's path — and a replacement module would show the same question marks.
- Original module only, no link on a proven connection after verified settings and path: the module's network interface is the fault; replace the logic module.
When the module is dead and the repair stops being worth it, industrial panel PCs running the same FactoryTalk View ME runtime can take over the operator station.
Questions asked
Why do buttons and screen changes still work when the values show question marks?
Navigation, buttons and static text are drawn from the runtime file stored on the terminal, so they keep working while the runtime executes normally. Only data objects need the controller connection, so they are the only objects that fail when that path is lost. That split also clears the display and touch hardware of suspicion: the fault is in data access, not in the panel itself.
Could the .MER file be corrupt anyway?
Not as a whole. If the identical file restores live values on another logic module over the same cable, its displays and tag references resolve correctly, which rules out general file corruption. What the test does not rule out is the communication configuration the terminal uses at runtime, because a runtime can carry its own path or inherit the one stored on the terminal depending on how it was loaded. Check that configuration on the failing terminal before touching the file.
What if only some tags show question marks?
A limited group of failing objects points to one shortcut or one controller, not the terminal's whole network setup. Open the runtime communication setup and check the path behind that shortcut against the configuration that works on the replacement module. If the path is right, check the tags the failing objects reference: the fault then sits in that object group rather than in the network.
When should I actually replace the logic module?
Replace it only after the original fails to establish a link on the cable and switch port that work with the other module, and after its IP settings and controller shortcut are verified. That combination is an interface fault in the module. If both modules link and the settings match, the fault is elsewhere and a new module will show the same question marks. Match the replacement module to the terminal series as the manufacturer's installation instructions specify.