IMDTouchKnowledge BaseShop main store

Troubleshooting

Keeping PanelView Plus User Passwords After an MER Download

HMI and touchscreens Published 6 min read

Short answer

There is no download option that leaves terminal users intact: a .mer replaces the runtime's users and passwords with the project's accounts. The working path is to upload the running runtime, restore it in FactoryTalk View Studio ME 8.00 or higher, which returns the terminal's current users to the project, then edit, rebuild and download, qualified once per terminal family. If downloads must never touch accounts, manage them with FactoryTalk Administration Console instead.

On this page
  1. Why the download resets the passwords
  2. Fixes that address the wrong layer
  3. The workflow that carries terminal users through
  4. Qualify once per terminal family, then commit
  5. Moving the accounts out of the .mer entirely
  6. Why PLC-stored passwords fail the requirement
  7. The decision, case by case
  8. Questions asked

No download option preserves them. When a .mer reaches a PanelView Plus, the terminal's users and passwords become the ones packaged inside that file — that is how runtime security works on every firmware from 5.0 through 9.0. The fix is not on the password screen; it is in what you build the replacement from. Upload the running runtime off the terminal, restore it to a project in FactoryTalk View Studio ME 8.00 or higher — the documented minimum that also returns the runtime security users — make your edits there, and download the rebuilt file. Qualify that round trip once per terminal family before trusting it fleet-wide, or move the accounts out of the runtime entirely.

Why the download resets the passwords #

Two account states coexist: the account list inside your engineering project, and the runtime security users on the terminal — the live list the panel authenticates against. An operator's password change edits the terminal's list, never your project. A .mer built from the project carries the project's list, and the download installs it as the terminal's list. The password function worked; the replacement discarded its result. On the Siemens MP277 sharing this plant, a project download leaves current passwords alone — that is the operational model you want, and runtime security on PanelView Plus does not work that way.

Use the timing of the failure to pick the next check:

  • The changed password works until the next .mer download: the replacement carried an older account list. Fix what you build the replacement from.
  • The password change fails with no download involved: diagnose the account, its permissions, and the password-change configuration.
  • Login succeeds but a protected action stays unavailable: authorization, not authentication. Check the account's group and the security setting on the object.

On the account-structure side — groups, security codes, and recovering accounts on the RSView Studio lineage of this software — the practice is laid out in user account password security design and recovery procedures.

Fixes that address the wrong layer #

Each of these feels productive, and none changes which account list ships in the next .mer:

  • Rebuilding the password-change screen. If a user can change a password and log in with it before any download, the screen already does its job.
  • Downloading the same project again. That repeats the replacement with the same account state; a clean transfer proves nothing about persistence.
  • Moving the passwords into PLC tags. Anyone with controller access can read them, which is exactly the disclosure your plant refuses.
  • Encoding them anyway. An offset on character codes, or a transform inside a know-how protected block or AOI, is reversible encoding whose source someone must hold. You moved the gate; you did not remove it.
  • Replacing the terminals. That is a migration project, not a diagnostic step, and it carries the same unanswered question with it.

Spend no commissioning hours on the login display until the round trip below has carried one account change end to end.

The workflow that carries terminal users through #

The sequence is upload, restore, edit, rebuild, download — with the terminal, not an old archive, as the source of the latest account state. None of it requires the terminal's Windows desktop.

  1. Record what runs: catalog number, firmware revision, application name, and the runtime file the terminal actually loads.
  2. Archive the current engineering project and the last built .mer, separately, before touching either.
  3. Create a test account with limited permissions, and never run this experiment with the only usable administrator account. If a lockout happens anyway, the recovery path is redownloading the HMI project after a user lockout.
  4. Change the test account's password at the panel, log out, and confirm the new password works and the old one is rejected.
  5. Upload the running runtime from the terminal. Name the file with the terminal's identity and the date, and treat it as security-sensitive material.
  6. Restore it into a separate project in FactoryTalk View Studio ME. Restoring the runtime security users is documented for version 8.00 and higher, and the 8.20 seat clears that minimum. A restore can still come back without its users, so read why a restored MER loses its runtime users before trusting one. Where no source project exists at all, this upload-and-restore is also how to recover the HMI program when the source file is lost.
  7. Rebuild at the same runtime version the terminal runs today; anything else is the separate failure mode covered in fixing an HMI MER runtime version mismatch.
  8. Download to that one terminal and repeat the checks from step 4. When the changed password survives, fold the real edits into the restored project.

Qualify once per terminal family, then commit #

This fleet names four families — original PanelView Plus, PanelView Plus 6 Standard, PanelView Plus 6 Compact, PanelView Plus 7 Standard — across firmware 5.0 to 9.0. That is a 4.0 major-version span (9.0 − 5.0 = 4.0), so one good result on one terminal proves nothing about the rest.

Worked example, illustrative counts for that fleet: run the unchanged round trip on one terminal per family, so 4 families × 1 terminal = 4 tests. Each test carries three checks — old password rejected, new password accepted, administrator account untouched — giving 4 × 3 = 12 checks before any production edit is trusted. All 12 pass: adopt the workflow fleet-wide and make upload-before-build the rule for every future download. Any family fails: that family stays on re-issued passwords or moves to console-managed accounts, and the record of files, versions, firmware and result goes to the vendor's support channel before anyone improvises. Record the runtime version you built for each family so the next rebuild matches.

Moving the accounts out of the .mer entirely #

If downloads must never touch users, stop storing them in the runtime: point the application's security at accounts managed with FactoryTalk Administration Console instead of the runtime's own list. Users and groups then live in the security database that console manages, a .mer download replaces displays and logic but never accounts, and account changes need no download at all. This is the only configuration on this platform where the MP277 behavior — downloads leave passwords alone — holds by construction.

The costs are a host for that security database, reachability from every terminal at login time, and password administration moving from the panel to the console. Accept those and this is the long-term answer. Refuse them and the round trip is the only runtime-security path left.

Why PLC-stored passwords fail the requirement #

Machines that keep the password in the controller put authentication data where maintenance reads it: a tag is data, and whoever holds program access sees it. A daily rule-based password still lands in a tag. Wrapping the compare inside a know-how protected routine hides the method, not the trust — someone must hold the source, and only the reader of credentials has changed. The IEC 62443 series expects human users to be uniquely identified, their accounts centrally managed, and their credentials protected from disclosure; nothing of that survives a plaintext or reversibly encoded tag. Migrate authentication off controller data — no encoding trick makes tag-stored credentials meet a no-disclosure requirement.

The decision, case by case #

  • Console-managed accounts refused, brief downtime acceptable: the upload-restore round trip, qualified per family with all 12 checks passing.
  • Central, auditable account management wanted: Administration Console accounts, with the database host and its reachability treated as machine-uptime items.
  • Passwords in PLC tags today: schedule their removal; they fail the disclosure requirement however they are encoded.
  • A family that fails the round trip: keep re-issuing passwords on that family and take the test record to support rather than improvising.

Questions asked

If we upgrade every terminal to one firmware version, does the password problem go away?

No. A .mer download replaces runtime users on every PanelView Plus firmware from 5.0 through 9.0, so consolidation does not change the behavior. What it changes is qualification effort: one family means one round-trip test instead of four, and one runtime version to build against. Consolidate for maintenance reasons if you want, but still run the unchanged round trip once before trusting it.

Our Studio version is older than 8.00. Can we still restore the runtime users?

No. Restoring the runtime security users from a .mer is documented for FactoryTalk View Studio version 8.00 and higher; older releases restore the application without returning the account list. Upgrade Studio rather than rebuilding users by hand, then repeat the round-trip test, because the version jump is exactly the kind of change that deserves one controlled verification before production edits.

What happens to logins if the central security database is unreachable?

Authentication against a remote security database needs that database reachable, so an unreachable host blocks logins exactly when you need them. Treat the host, its backups and its recovery path as machine-uptime items before pointing production terminals at it. If that dependency is unacceptable, stay with runtime security and the upload-restore workflow.

Can operators still change their own passwords under console-managed accounts?

Not at the panel. Console-managed accounts are administered centrally, so resets become an administrator task with whatever approval flow you attach, which is the model that gets controls engineering out of the password business. Self-service password change at the terminal belongs to runtime security, where the round trip applies. Choose the model by deciding who should own resets.

We lost the original project. Is the round trip still possible?

Yes, and it is the same first move: upload the running runtime from the terminal and restore it to a project, which on Studio ME 8.00 or higher also returns the terminal's current users. Keep that restored project as the new engineering baseline under source control, because from then on it, not the terminal, is the record of the application.

Keep reading

  • How-to

    How to find the runtime file an HMI terminal actually loads

    The startup configuration, not the file list, selects the loaded .MER. Cycle power and press the white box in the lower-left corner (touch, firmware 5.0 or later) or hold F1 on a directly connected USB keyboard to reach the configuration screen and read the loaded runtime name. Copy every stored runtime off before deleting anything in File Management.

    HMI and touchscreens

  • Troubleshooting

    Why a restored MER loses your PanelView Plus runtime users

    Restoring an MER gives you back the screens but not the users: a runtime restore cannot carry the FactoryTalk Directory contents, so every stored login stops working while the panel keeps running. Recreate the missing users and groups in the restored project's runtime security, build a new MER, download it, and store the project as an APA or APB archive from then on.

    HMI and touchscreens

  • Troubleshooting

    Reaching HMI Config Mode With No Startup Square

    Test the documented USB keyboard path once - Ctrl+Shift+Alt+Windows held for a few seconds - because on terminals that never show the startup square it is the supported route in. A password-protected GO TO CONFIG button is application access control: get the credentials or the project from the owner, never a reset file. If you only need the IP address, discover it on an isolated link and skip configuration mode entirely.

    HMI and touchscreens