IMDTouchKnowledge BaseShop main store

Troubleshooting

Why a PanelView 5310 reverts to the old project after reboot

HMI and touchscreens Published 6 min read

Short answer

Nothing usually reverts. A completed View Designer download replaces the application a PanelView 5310 runs, and the download dialog has no startup-project selector. In the reported case the terminal is almost certainly running the new build while a copied screen still displays the old Revision A text label: prove source, destination, and download completion, then verify one marker across a single controlled restart.

On this page
  1. The label reverted, not the application
  2. Fixes that do not exist in View Designer
  3. Match the symptom to the cause
  4. Prove the source and the destination
  5. The Logix project path is a design-time address
  6. Verify persistence with one controlled restart
  7. If the marker really disappears after a verified download
  8. The decision, case by case
  9. Questions asked

Most of the time nothing reverted. A View Designer download that completes replaces the application the PanelView 5310 runs, and the documented download path contains no startup-project selector — there is no checkbox you forgot to set. What usually survives a revision change is a text object on the screen that still reads Revision A, because the project was copied, edited, and saved as Revision B without anyone touching the displayed name. The terminal then runs the new build under the old label, and one reboot makes it look like a rollback. Prove the source, the destination, and the completion of the download, then verify one marker across a single controlled restart.

The label reverted, not the application #

The workflow that produces this symptom is common: open Revision A, make a small change, use Save As to create Revision B, download, reboot. Static text is part of the application, so the copied project carries the old revision string onto the terminal. The name an operator reads on the screen is not the identity of the running application; it is whatever the last editor typed into that text object.

Before concluding anything about persistence, add a deployment marker to Revision B: a unique string such as a date and revision on a screen operators can reach, plus one small unmistakable visual change. Save that exact project. From then on, trust the marker and the terminal's own report of what it runs, never the filename on the engineering computer. The discipline behind how to verify the HMI project version running on a panel applies here unchanged.

Fixes that do not exist in View Designer #

Three habits imported from the FactoryTalk View Studio workflow for FactoryTalk View ME runtimes waste time here:

  • The "run on startup" checkbox belongs to the FactoryTalk View Studio workflow. The View Designer download has no equivalent, because there is nothing to select: the completed download is the deployment.
  • The "Replace Communications" radio button belongs to the MER transfer in FactoryTalk View Studio. The Download Runtime Application dialog in View Designer contains three pages and no such option, so it cannot be the missing step. A related trap on the Studio side is a PanelView keeping an old FactoryTalk Linx configuration after a download; both symptoms tempt the same wrong fix, reaching for a communications option to solve an application-identity problem.
  • Saving the project as Revision B deploys nothing. Saving and downloading are separate acts; see why an HMI edit needs a new runtime download for where the change actually has to travel.

Two more time-wasters: restarting the panel again and again before anyone confirmed the download result, and changing controller settings just because the Controller Reference page appears during download. That page appearing is normal, and a working reference is not the cause of a revision symptom.

Match the symptom to the cause #

What you observe Most likely cause First check
"Revision A" text shows immediately after a reported-successful download New build running with the old label, or the wrong source file was open Marker present in the open project
Revision B runs, then disappears when power is removed Transfer never finished, or the terminal failed to retain it The explicit success message in View Designer
One panel updated, an identical panel still shows Revision A The download targeted a different terminal Network identity on the destination page
New screens visible, controller values blank Application deployed; controller reference or communication path wrong Live tag values, not the label
Dialog closes but no visible change on the panel The edit was not in the downloaded project, or there was no marker to see Unique marker

Prove the source and the destination #

  1. Open the Revision B file directly. A recent-projects list is how near-identical revisions get swapped.
  2. Confirm the marker exists in the open project. If it does not, the edit was never saved into this file.
  3. Save, and clear anything View Designer reports as an error before downloading.
  4. Click Communications > Download. The Download Runtime Application dialog opens.
  5. On Specify Destination and Language, match the configured network identity to the physical panel in front of you. Position in the device list proves nothing.
  6. On Controller Reference, confirm each project reference maps to the intended controller connection. Do not change a working mapping to treat a revision symptom.
  7. On Download, check the source and destination shown, start the transfer, and wait for the explicit success message. The dialog closing is not success; the reported message is.

If the transfer cannot be tied to the physical panel you are standing at, stop. A successful download to a different terminal cannot correct the one in front of you.

The Logix project path is a design-time address #

The Controller Reference page shows where the Logix project file lived on the machine builder's computer when the reference was configured. That path supports design-time work such as tag browsing and project association on the engineering side. The terminal does not open that Windows path at startup; runtime traffic uses the configured controller connection. A missing local copy of the file blocks future editing and tag synchronization on your computer, and nothing else. Keep a current local copy for maintenance, and stop treating that path as the cause of the rollback.

Verify persistence with one controlled restart #

One safety note first: restarting the operator interface briefly removes operator control of the machine, so do it when the process and the crew can accept the interruption.

One restart, two checkpoints:

  1. After the explicit success message, navigate to the marker and record it; a photograph is enough.
  2. Confirm the changed function behaves as intended.
  3. Restart the terminal the way the installation normally does, and do not start another download while it comes up.
  4. After startup, return to the same screen and confirm the identical marker and function.
  5. Check live controller data as a separate question. Correct screens with dead values are a communication fault, not a rollback.

Worked example with illustrative times: the transfer reports success at 14:32 and you confirm the marker at 14:35, so 14:35 − 14:32 = 3 min from success to the first checkpoint. You restart at 14:41 and re-confirm the marker at 14:46, so 14:46 − 14:41 = 5 min for the restart and 14:46 − 14:32 = 14 min end to end. Both checkpoints pass inside 14 min, persistence is proven, and the "Revision A" on the screen was a label all along. The decision: edit the label, keep the marker in your template, download once more.

If the marker really disappears after a verified download #

If the marker was present after the success message and provably absent after one normal restart, with no second download in between, you have a terminal retention fault, not a missed setting. Stop re-downloading: every attempt overwrites the one clean failure sequence you need to report. Confirm the terminal's firmware is current before going further, because the PanelView 5310 manual's update procedure starts at terminal firmware before any application download, then take the failure to the supplier with the evidence intact.

The decision, case by case #

  • Old label on the new build, which is the reported case: edit the revision text, keep the marker, download once, verify across one restart. Nothing else was wrong.
  • Wrong terminal received the download: re-download to the verified destination; the untouched panel still needs its own download.
  • No explicit success message was ever seen: the download did not complete; repeat it and watch it finish, and never remove power during transfer or activation.
  • Marker verified, then gone after restart: retention fault; stop, check firmware, escalate with the evidence.
  • Screens correct, values blank: controller reference or communication path; fix the connection and leave the application alone.

Questions asked

Does the PanelView 5310 store older projects and pick one at startup?

The download path gives you nothing to pick. Communications > Download opens the Download Runtime Application dialog with Specify Destination and Language, Controller Reference, and Download, and no page in it selects between stored builds, so a completed download is the deployment. Whether the terminal can hold other files is a storage question you never need to answer to fix this symptom.

Why does Controller Reference point at a Logix project on the machine builder's hard drive?

That path was recorded when the reference was first configured and serves design-time work such as tag browsing and project association. The terminal never opens that Windows path at startup; runtime traffic goes through the configured controller connection. A missing local copy hurts only your future editing and tag synchronization. The next time the project is open, point the reference at your own current copy of the Logix project.

What evidence should I collect before reporting a true rollback?

Record the exact success message View Designer reported, the timestamps of the download and the restart, the terminal's diagnostics, the firmware version, both project files, and the restart method used. The PanelView 5310 manual's update procedure begins at terminal firmware, so that version belongs in the report. Do not run another download first, because each attempt overwrites the failure sequence you are trying to describe.

The new screens are running but every value is blank. Did the old project come back?

No. New screens with blank or stale values mean the application deployed and the controller reference or runtime communication path is wrong or offline. The revision label tells you which build is running; live data tells you whether the reference works. Treat it as a communications fault on the same terminal and leave the application alone.

Is one controlled restart enough to call the deployment persistent?

Yes. Two checkpoints, the marker present right after the success message and present again after one normal restart, separate an unfinished download from a retention fault. If both pass, the deployment is persistent and any remaining Revision A text is a label to edit. If the second checkpoint fails, you have a terminal fault, and more random power cycles only destroy the evidence.

Keep reading

  • Explainer

    Start a published WebIQ HMI project without Runtime Manager

    No current WebIQ version starts a project automatically after publishing: start and stop live in Runtime Manager, and Designer only shows the running state. During development, point panel devices at the Designer preview server on port 10124 instead; publish and start only for tests that need the ctrlX reverse proxy.

    HMI and touchscreens

  • Troubleshooting

    Fix WebIQ Designer Stuck Loading an HMI Project ZIP

    WebIQ Designer sticks on the Loading HMI project screen because the ZIP was packed by hand: it carries an extra HMI wrapper directory and file entries stored with method 0 instead of deflate method 8. The runtime tolerates the archive; the Designer import does not. Unpack it into the projects directory without the wrapper folder, then export the HMI from Designer or Runtime Manager.

    HMI and touchscreens

  • Troubleshooting

    Why HMI Variable Values Reset After a Project Transfer

    HMI values reset after a transfer because the transfer's Initialize settings requested it, the variables were never marked retentive, or the editor's newer version forced a firmware update that initializes all variable memory. Clear [Variable Value] and [Backup Memory] under Initialize, mark operator values retentive, and retrieve the program plus current values with Shift + X before you transfer. Only the firmware-update path wipes retentive values; capture them first, because no setting protects them through it.

    HMI and touchscreens