IMDTouchKnowledge BaseShop main store

Troubleshooting

When HMI user management works in simulation but not on the panel

HMI and touchscreens Published 8 min read

Short answer

The simulator reads user management from the project; the panel keeps its own local user data store that keep-current-values downloads never refresh. Download to the panel once with Reset to start values for runtime values, confirm the role's runtime rights for that HMI, then test one login and one permitted function.

On this page
  1. Why does HMI user management work in the simulator but fail on the panel?
  2. Which project and user data are actually running on the panel?
  3. Should the download reset user data or keep current values?
  4. Why can a user log in but still have no administrator rights?
  5. How do you test one change at a time on the panel?
  6. When is a factory reset the right recovery step?
  7. Which fault does each outcome point to?
  8. Questions asked

Your WinCC Unified users work in the TIA Portal simulator and fail on the panel because the simulator and the panel are different runtime targets: simulation runs the users stored in the project, while the panel keeps its own local user data store, and a download that keeps current values never replaces it. The fix is a sequence, not a single switch: confirm the panel runs the project you edited, download once with Reset to start values selected for the runtime values that carry user data, check that each role holds runtime rights for that HMI device, then test one login plus one function the role should allow. Treat a factory reset as the last step only. The sections below follow that order so each download changes exactly one thing.

Why does HMI user management work in the simulator but fail on the panel? #

The simulator and the panel are separate runtime targets: simulation runs the users stored in your project, while the panel keeps its own local user data store, and a download that keeps the current values leaves that store untouched, so old or empty users survive every transfer.

Simulation rebuilds its environment from the project on every start, so a user configured with one role logs in simulation exactly as configured. The panel differs in two ways. Its user data is runtime data: accounts and passwords physically stored on the device, including changes made at the panel. And that store survives transfers by default, because the documented download procedure groups user data with tag values and active alarms as runtime values that the keep choice preserves. Whether the transfer carries configuration settings or not does not matter here; the runtime-values choice decides what the store holds.

Read the simulator result as evidence about the project only. It proves the user exists and the role is assigned; it cannot prove what the panel store holds. The checks below test the panel itself, ordered so the fault is found with the fewest downloads.

Which project and user data are actually running on the panel? #

Verify the target before touching settings: confirm the panel is running the project you edited and that its active user management matches the project configuration, because the runtime reports a mismatch when the local user management differs from what the project defines.

Compare the project loaded on the panel against your engineering project first — the procedure in verify the HMI project version running on a panel takes a minute and rules out testing a revision that predates your new users. Where the target is a PC running RT Unified, the runtime manager activates user management and reports when the active user management does not match the project's configuration, with a documented warning that data loss can occur while resolving the mismatch. On a panel, the same disagreement shows up as login behavior that does not follow the project.

If the active project predates your user changes, or a mismatch is reported, fix the transfer before anything else — the download in the next section is that fix.

Should the download reset user data or keep current values? #

Choose Reset to start values for the runtime values when you load user data to a panel after changing users: the documented download procedure says exactly that for the first transfer, and keep-the-current-values leaves the panel's old user store in place, which is the failure behind this symptom.

The WinCC Unified engineering documentation is explicit for the first download of user data to a runtime device: select Reset to start values for Runtime values. The download dialog offers two behaviors for that runtime-values group, keep the current values or reset to start values, and only the reset writes your project's users, groups and roles into the panel's store.

Worked example: revision 1 of the project defined two users, Admin and Service1, and the panel store still holds exactly those two. Revision 2 defines three users, Admin, Operator1 and Viewer1. A keep-values download leaves the store untouched: of the 3 users revision 2 defines, 3 - 3 = 0 are present, while 2 - 0 = 2 stale accounts remain. A Reset to start values download rebuilds the store: 3 - 0 = 3 of the current users are present and 2 - 2 = 0 stale accounts remain. Login as Operator1 then behaves exactly as configured.

Download choice for runtime values Store after the transfer Current project's users available Stale accounts left
Keep the current values Unchanged, revision 1 state 0 of 3 2 of 2
Reset to start values Rebuilt from revision 2 3 of 3 0 of 2

A reset also discards user changes made at the panel itself, and the engineering documentation warns that data loss can occur around user-management changes. If the reset leaves the panel locked against your own account, the recovery path is redownloading an HMI project after a user lockout.

Why can a user log in but still have no administrator rights? #

A successful login proves only that the credentials match a configured user; what that user may do comes from the role, and each role must carry runtime rights assigned for that specific HMI device, so check the role's rights whenever login works but protected functions stay locked.

Authentication and authorization are separate decisions. The login dialog authenticates the user name and password against the store. Every protected screen object then authorizes against the rights of the user's role. A user with an administration role is still refused everywhere if that role's runtime rights were never assigned for this panel.

The documented assignment lives in the project's user management: open Roles, select the role, open its runtime rights, select the HMI device, and tick the rights that role must have on that device. Then confirm the object you are testing requires one of those rights — a function no role grants stays locked for everyone, which is a project gap rather than a transfer problem.

Decision: after the reset download, log in with the single-role test user and operate exactly one function the role permits. Login passing while the function refuses means the role's runtime rights for this device are the remaining fault, corrected in the project and transferred again.

How do you test one change at a time on the panel? #

Change one variable per download and record five fields before you start: target device, test user name, expected role, user-data choice, and observed result, because an uncontrolled run of downloads can make a working configuration look broken.

Record these before the first transfer:

  • Target device: the panel you download to, never the simulator instance
  • Active project and its revision
  • Test user name, spelled exactly as entered at the login screen
  • User-data choice for the download: keep the current values or Reset to start values
  • Observed result: login outcome plus one function operated or refused

Then run the sequence once:

  1. Confirm the active project on the panel.
  2. Download once with Reset to start values for the runtime values.
  3. Log in with the single-role test user.
  4. Operate exactly one function the role permits.
  5. Write down the result before changing any other setting.

A passing simulation belongs in the record as evidence about the project only — what an HMI simulation proves against a live PLC is its own exercise, covered in testing HMI simulation against a live PLC. Keep service packs and engineering updates out of this sequence; they are routine maintenance, not a fix for retained runtime data, and they deserve their own controlled test afterwards.

When is a factory reset the right recovery step? #

Treat a factory reset as the last step, after a confirmed project download with reset user data and a rights check still fails, and make a project backup first because the reset clears runtime data that no download choice can bring back.

A reset is justified when the store is demonstrably beyond the project: security settings were deleted during earlier testing, the store holds users no project revision explains, or the verified reset download still leaves logins that match no configured account. Back up the project, record what the reset will clear, run it, restore the project, and repeat the two-step test: one login, one permitted function. While user management is not working, the panel's access restrictions are open to anyone at the screen, so keep the machine out of production or under direct supervision until a login refuses a function it should refuse.

Which fault does each outcome point to? #

Three outcomes decide it: credentials refused means the store lacks the project users, so rerun the reset download; login accepted but functions refused means missing role runtime rights; both failing after a verified download and rights check means factory reset, then restore.

Observed result at the panel Fault Action
Correct credentials refused The store never received the project users Download again with Reset to start values for runtime values
Login accepted, permitted function refused The role lacks runtime rights for this HMI Assign the rights under the role's runtime rights for this device, then transfer again
Both fail after a verified download and rights check Device state beyond the project Back up, factory reset, restore the project, retest

Work the table left to right after every download: the observed result names the fault, and the action column is the next download's only change.

Questions asked

Do I have to reset user data on every download after the first?

No. Reset to start values is for the first load after user changes or when the store is suspect. Once login and rights verify on the panel, return the runtime-values choice to keep the current values, so routine transfers preserve changes made at the device, tag values and the active alarm list.

What is lost on the panel when runtime values are reset?

The reset rebuilds the user store from the project, so accounts or password changes made directly at the panel disappear, and the documented runtime-values group also covers tag values and active alarms. Record panel-side passwords and export anything you need from the device before the download that resets.

Why does the runtime report that active user management does not match the project?

That message means the device's local user management and the project's configured user management differ, typically after security settings were deleted or an older store survived a keep-values download. The engineering documentation warns data loss can occur while resolving it, so back up, then reload with reset to start values and retest.

Should each test user hold only one role while you diagnose access?

Yes. A single role per test user ties every observed refusal to one rights list, so a failed authorization points at that role's runtime rights for the device instead of the combined result of several roles. Add the remaining roles only after the single-role account passes both the login and the function test.

Keep reading

  • Troubleshooting

    Why an HMI Writes Integers but Not B3 Bits Over DF1

    When an HMI writes T4, C5 and N7 data but B3 bits never change over DF1, the serial link is proven and the failure sits in the HMI software's binary-file translation. Check the engineering software version before baud, cable or PLC settings: a documented case was fixed by upgrading EBplus from 2.10 to 5.07.

    HMI and touchscreens

  • How-to

    Testing HMI Simulation Against a Live PLC

    A standalone HMI simulator proves screens and navigation, not communications. Test against a live controller only through a documented online-simulation mode or a physical panel, and verify every read at two data states and every write at the controller before release.

    HMI and touchscreens

  • Troubleshooting

    Why an HMI Transfer Fails in Initial Start Mode Despite Ping

    Ping success proves only that the panel's IP stack answers. On a new Magelis XBTG in Initial Start Mode, run three checks in order: build in the engineering version that still supports the target (Vijeo Designer 6.2 for XBTG), clear the license so the download command activates, then load runtime and application over one transport at a time.

    HMI and touchscreens