IMDTouchKnowledge BaseShop main store

Troubleshooting

PanelView Keeps Old FactoryTalk Linx Config After Download

HMI and touchscreens Published 8 min read

Short answer

The terminal keeps its resident FactoryTalk Linx configuration because the download changed graphics only. The .mer carries a comms configuration only when you build it by hand on the Runtime (Target) tab, and the terminal takes it only when the transfer utility is set to replace communications and the terminal reboots afterward.

On this page
  1. Why does the PanelView keep the old FactoryTalk Linx configuration after a download?
  2. Where does the communication configuration actually live?
  3. Why did the fix work once and then stop working?
  4. How do I build a runtime that carries the new communication configuration?
  5. How do I transfer the .mer so the terminal replaces communications?
  6. How do I verify the new configuration on the terminal itself?
  7. What does the RSLinxNG fatal error on the panel mean?
  8. When is firmware the fix, and which runtime versions does it accept?
  9. When is the terminal not worth fixing?
  10. Questions asked

The download finishes, the screens change, and every tag still follows the old FactoryTalk Linx shortcut. A PanelView Plus takes a new communication configuration only when the .mer carries it and the transfer is told to replace communications; anything less rewrites the graphics over the resident configuration. This article shows where the configuration lives, how to build a runtime tree by hand, how to force the replace at download, and how to verify the result on the terminal itself.

Why does the PanelView keep the old FactoryTalk Linx configuration after a download? #

Because the download changed graphics only: the terminal overwrites its resident FactoryTalk Linx configuration just when the transfer is told to replace communications, and it then writes whatever tree the .mer actually carries — which, if the file predates your edit, is the old one.

A resident FactoryTalk Linx configuration is device-level state on the terminal, not application state: it survives deleting the application and it survives a plain download. The replacement tree loads when the runtime restarts after the transfer, so a download that ends without that restart leaves new graphics running on the old path. Every failure you can meet here falls into one of four patterns:

  • The change appeared once, then every later download reverted: the .mer was not rebuilt after the communication edit, so each transfer faithfully carries the stale tree.
  • A clean-looking download leaves the retired device path active: the transfer was not set to replace communications, so the terminal kept its resident configuration.
  • Studio browses fine but the panel shows dead tags: the shortcut resolves on the design tree only, and the runtime tree holds devices no shortcut references.
  • The terminal rebooted and still runs the old path: the replace happened and wrote the old tree again, which convicts the file, not the panel.

Where does the communication configuration actually live? #

The configuration lives in two trees that never track each other: the Design Local tab serves FactoryTalk View Studio on your laptop, while the Runtime (Target) tab is what the project serializes into the .mer and what the terminal loads.

Serialization happens when you build the runtime application, not when you transfer it. Edit the communication setup, skip that rebuild, and the transfer utility pushes the old configuration for the tenth time — the most common reason a change lands once and never again.

Rockwell's FactoryTalk Linx documentation treats the runtime target as its own configuration and walks through carrying the design-side setup into the Runtime (Target) tab as a deliberate, separate step, precisely because the two sides do not synchronize by themselves.

Why did the fix work once and then stop working? #

Because the first success transferred a .mer that still carried your new tree, and the later transfers pushed a file that no longer does — nothing on the terminal broke between the two attempts, and clearing the resident configuration changes nothing either.

Restoring the FactoryTalk Linx configuration on the terminal to nothing removes the old path but installs nothing, so the panel sits without communications until a proper replace-transfer lands. The next transfer then reinstates whatever tree the file carries, and when that file was built before the edit, the old configuration goes straight back. The terminal is obedient; the input is stale.

Resident settings surviving reboots and downloads are normal PanelView Plus behavior, the same class of fault as why a PanelView Plus IP address reverts after a reboot.

How do I build a runtime that carries the new communication configuration? #

Open the project's communication setup, select the Runtime (Target) tab, and build the tree by hand — driver, path, controller, then every shortcut bound to its controller — deleting each device no shortcut uses before you create the runtime application.

Rockwell's documented route is copying the design configuration into the runtime tab; with a cluttered design tree, that copy is the problem. Illustrative example: three engineers' laptops have left the design tree holding 7 devices — 3 drivers and 4 browsed controllers — while the application uses 1 driver, 1 controller and 2 shortcuts. Built by hand, the runtime tab ends at 3 devices and you delete 7 − 3 = 4. Copied, it lands with all 7, including two devices that resolve to the same controller, which is the exact contradiction that drops RSLinxNG on the terminal.

The sequence that works:

  1. Add the one driver and the controller path the terminal actually uses on the Runtime (Target) tab.
  2. Delete every device no shortcut references; a shortcut with no device under it looks identical in the list and resolves to nothing.
  3. Bind each shortcut to its controller and apply: shortcut names are the binding key between graphics and communications, so a rename on one side only leaves dead tags with no error dialog.
  4. Build the runtime application under a new name with a revision suffix, for example Line1_RevC.mer, so the loaded file is identifiable at the terminal.
  5. Run the .mer on the laptop the way the terminal will: load the runtime file and let it start. Pressing play in the editor runs the design tree and will pass while the runtime tree is broken.

How do I transfer the .mer so the terminal replaces communications? #

Select the replace-communications option in the transfer utility, let the download finish, and make sure the terminal restarts the runtime, because the new FactoryTalk Linx configuration takes effect on that restart and a download that ends without a reboot leaves new screens on old communications.

Stop the running application before the transfer; files in use do not get replaced cleanly and produce half-updated panels. Deleting the old application first gives a clean slate, but deletion alone changes no communications. If the utility offers to run the application after download, accept it, and if the terminal does not restart on its own, cycle power before you judge the result.

One safety note: taking the operator terminal out of runtime or cycling power removes the operators' view of the machine, so do the transfer in planned downtime with someone at the process able to see the states the screen normally shows.

How do I verify the new configuration on the terminal itself? #

Verify on the terminal, not in Studio: with the runtime stopped, open the terminal's own FactoryTalk Linx configuration display and browse the tree, and the driver, path and shortcut assignments there must match the Runtime (Target) tab you built.

Studio tells you what you configured; the terminal tells you what it has. Confirm the loaded application name carries the revision suffix you assigned — a panel starting a differently named .mer is a common false trail, and verifying the HMI project version running on a panel covers that check step by step.

Then open the terminal's diagnostics and read the shortcut resolution failures, which name the shortcut that did not bind. Prove the path with a throwaway application: one numeric display, one shortcut, one PLC value that changes. If the throwaway reads live and the real application does not, the fault is in the shortcut mapping; blank tags with no error banner are the pattern behind why an MER download shows no live data on the HMI.

What does the RSLinxNG fatal error on the panel mean? #

The RSLinxNG fatal error means the terminal's runtime communication service crashed, and on a panel that points at the runtime device tree rather than the network: duplicate devices, two devices resolving to one controller, or a device aimed at an address that is not on the plant network.

The pop-up reading RSLinxNG has encountered a fatal error normally appears while you edit the Linx setup on the terminal, and it convicts the tree, not the network. The hand-built single-device tree of the previous sections removes the duplicates that trigger the crash. If RSLinxNG keeps faulting after a verified replace-transfer of that clean tree, the terminal's own installation is the suspect and firmware moves from last resort to next step.

When is firmware the fix, and which runtime versions does it accept? #

Firmware is the last step, taken only after a clean single-device runtime tree and a verified replace-communications transfer still fail, and before you flash you must confirm which runtime versions the target firmware accepts, because a panel moved to v14 does not automatically load every older .mer on the bench.

Field experience moving FW 10 panels to v14 puts the accepted runtime floor at v11 runtimes; treat that as a practitioner report to verify, not a published specification, and check the release notes for the exact firmware before the terminal is on the bench stripped. Rockwell's application and firmware compatibility FAQ states which application versions each firmware accepts, so look up your target before you rebuild.

Order matters: flashing before the runtime tab is clean inherits the same bad device tree the moment you push the same .mer. Rebuild, prove the result with a replace-transfer, then upgrade — and if the panel rejects the rebuilt file after the flash, fixing an HMI MER runtime version mismatch is its own troubleshooting path.

When is the terminal not worth fixing? #

Stop iterating when a verified replace-communications transfer of a proven-good .mer still leaves the resident configuration in place and RSLinxNG keeps faulting on a clean single-device tree; capture the firmware revision, the runtime version, the runtime tree and the diagnostics list for a support case, or replace the unit.

When repair is not worth the cycle time, the fallback is moving the operator interface off the proprietary terminal: running the HMI runtime on a touchscreen computer at the machine puts the communications under the PC's control instead of the terminal's resident configuration, which is what industrial panel PCs are for. If the source project is lost, read the program off the failing panel first so the rebuild starts from fact rather than memory, following how to upload a program from an old touchscreen HMI.

Questions asked

How do I back up the application before I start deleting and flashing?

Copy the current .MER file off the terminal before you delete applications or flash firmware, so the working project can be reloaded if the new transfer misbehaves. Rockwell's PanelView Plus Terminals user manual builds its upgrade flow on exactly that order: back up the .MER files first, do the work, then reload the file and run the project.

Is editing the Linx configuration directly on the terminal a valid shortcut?

Treat terminal-side edits as temporary. Local changes made in the terminal's configuration screens persist and become the configuration the next download has to overcome, which is how panels end up running a path no project file describes. Set the path once from the project's runtime tab and leave the terminal's Linx editor alone.

Which application versions run on a PanelView Plus 7 Standard?

Rockwell's application and firmware compatibility FAQ states that Compact applications built in versions 5.10, 6.00, 6.10 and 7.0 run on the PanelView Plus 7 Standard. For other PanelView Plus terminals and firmware levels, look up that exact firmware's entry before rebuilding, because the accepted .mer versions move with the firmware release.

Keep reading

  • How-to

    Replacing a Fleet of PanelView 550 Terminals on DH-485

    There is no direct swap: the PanelView 550 is Silver Series, so each terminal is a migration. The PanelView Plus 6 600 keeps the 550 cutout but needs a third-party DH-485 adapter; a Plus 6 700 takes the 2711P-RN6 but modifies the cutout. Audit all 25 catalog numbers, convert one application in FactoryTalk View Studio ME, pilot one machine, then buy the fleet.

    HMI and touchscreens

  • 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

  • Troubleshooting

    EcoStruxure Operator Terminal Expert download fails to HMI

    A failed Operator Terminal Expert download has three separate causes: Windows firewall blocking the transfer executable, fixable with inbound and outbound allow rules scoped to EcoStruxure Operator Terminal Expert.exe; a VMware virtual USB controller that needs its compatibility set to USB 1.1; or a terminal still running Vijeo Designer firmware, which no Operator Terminal Expert project can load until a manufacturer recovery converts it. Match the fix to the runtime you read on the terminal.

    HMI and touchscreens

PanelView Plus 600 With No Config Button and Full Flash