IMDTouchKnowledge BaseShop main store

How-to

Redownloading an HMI Project After a User Lockout

HMI and touchscreens Published 7 min read

Short answer

Yes — WinCC flexible 2008 SP3 opens and converts an SP2 project, and the converted project downloads to the panel. The lockout itself only clears if you remove the failed-login limit in the project and transfer with the option that replaces user administration on the panel; a plain application download leaves the locked account in place.

On this page
  1. Can I download an SP2 project with WinCC flexible 2008 SP3?
  2. What are the steps to redownload the project and clear the lockout?
  3. What happens to my original project when SP3 converts it?
  4. What if the project was originally a ProTool project?
  5. Why does the account stay locked after restarting the HMI?
  6. Does a plain application download replace the panel's users?
  7. Why force a full compilation before the transfer?
  8. How long will the panel be out of service during the download?
  9. Questions asked

Yes, WinCC flexible 2008 SP3 can redownload the project. Opening an SP2 project in SP3 converts it, and the converted project transfers to the panel — a service pack is an update to the engineering software on your PC, not a change to the panel's firmware family. The redownload only fixes the locked operator account if you also remove the failed-login limit inside the project and transfer with the option that replaces user administration on the panel. The steps below cover the conversion, the lockout policy, the full compilation, and the transfer choices, in the order you meet them.

Can I download an SP2 project with WinCC flexible 2008 SP3? #

Yes. Opening an SP2 project in WinCC flexible 2008 SP3 converts it to that service pack's format, and the converted project then transfers to the configured panel with no separate firmware step.

A service pack updates the engineering tool on your PC; it does not reflash the panel. The panel changes only through an explicit image update, and installing SP3 is not a reason to run one. The device configured in the project decides which runtime the editor generates, so before you open transfer settings, confirm that device matches the panel on the machine and that the configured PLC connection matches the real network.

If a transfer message reports an image incompatibility, stop and identify the panel and its installed image, then follow the device documentation for the supported update path and its backup requirements. On older panels, device identity is the same first check described in planning an HMI terminal replacement from an older operator panel.

What are the steps to redownload the project and clear the lockout? #

Eight steps, in order: archive the original, convert a copy in SP3, verify the device and connection, fix the failed-login policy, compile completely, transfer with user-administration replacement, restart, and test the operator login on the panel.

  1. Archive the SP2 project and make a separate working copy. Never open the original in SP3.
  2. Open the working copy in WinCC flexible 2008 SP3 and accept the conversion prompts. Read every message the conversion produces.
  3. Confirm the configured HMI device matches the physical panel and the PLC connection settings match the installation.
  4. In the project's user administration, open the affected operator account, check its group and authorization assignments, and locate the setting that limits failed login attempts.
  5. Set that limit to unlimited, or remove it, and confirm an administrator account you can still reach remains in the project.
  6. Save, then run a full compilation of the complete project. Resolve every error and read the warnings.
  7. Open the transfer settings, select the interface the panel supports, and enable the option that transfers users and replaces user administration on the panel.
  8. Coordinate the machine stop, run the transfer, let the panel restart, and log in with the operator account to confirm the fix.

For the physical link on legacy panels, the transfer cable is its own problem: uploading an HMI program without the right cable pinout covers the mapping you need before step 7.

What happens to my original project when SP3 converts it? #

The conversion moves the working file to SP3 format when you save, so the SP2 version exists only in your archived copy — keep it, because the older service pack cannot reopen what SP3 has saved.

Do the archive step before anything else: copy the project folder, store the original where nobody opens it, and work only on the copy. Conversion messages that appear while the project opens deserve a full read — an unresolved conversion error blocks generation later, and you want to know that before the machine is stopped. If you still support other machines on SP2, keep an SP2 installation alive on a separate PC or virtual machine, because that installation plus your archived original is the only way back.

What if the project was originally a ProTool project? #

ProTool projects migrate only up to WinCC flexible 2008 SP2 — SP3 cannot perform that migration, so a ProTool-era project needs an SP2 installation first, and the migrated result then opens in SP3.

Check the project's origin before you schedule the outage. A project that was migrated from ProTool years ago and edited since is already a WinCC flexible project and converts in SP3 normally; a raw ProTool database does not. The path for the raw database is two steps: migrate it in an SP2-or-earlier installation, then open and convert the result in SP3.

Why does the account stay locked after restarting the HMI? #

Because the failed-attempt state lives in the panel's stored user administration, not in the running screens, a restart reloads the same locked account — persistence across power cycles is the mechanism working as designed.

User administration on the panel is stored data, separate from the screens the runtime draws, and it survives restarts the same way recipes do. Authentication checks credentials; authorization decides what an authenticated user may operate. The lockout acts on the authentication side, and its purpose is to slow repeated password guessing by disabling the account after a configured number of invalid attempts. One caution belongs here: setting that number to unlimited removes the guessing protection, so make the change as a deliberate access-control decision with whoever owns machine access, and keep a known administrator account for the next recovery.

Does a plain application download replace the panel's users? #

Not reliably — a transfer that sends only screens and logic can leave the panel's existing user records, including the locked account, untouched, so select the transfer option that replaces user administration with the project's user data.

Two consequences follow. Replacing user administration also discards changes made at the panel, such as a password changed at runtime or an account created on the panel, so re-apply the intentional ones from your own record afterward. And back up recipes and logged data before the session, because depending on the device, a transfer or an image action can affect different stored data sets. The decision is still replacement: the locked account state is exactly what you are there to remove.

Why force a full compilation before the transfer? #

Because a full compile processes screens, connections, and user management together and catches what conversion and editing broke, while transferring only changed objects can leave missing or stale elements on the panel.

Practitioners report that in TIA Portal from version 15 on, buttons and other screen elements sometimes go missing from a downloaded panel unless a full compilation runs first; that failure is not documented for WinCC flexible 2008. It does not change the practice: after a service-pack conversion you want one complete generation anyway, because it is the checkpoint that catches broken references, lost connections, and user-management errors in a single pass. Resolve every error, read the warnings, and accept only the ones you understand.

How long will the panel be out of service during the download? #

Plan a 15-minute outage for a mid-size project over serial, or a few minutes over Ethernet — an 8 MB project at 115.2 kbit/s needs about 9.3 minutes of pure transfer time before overhead.

Worked example, with illustrative inputs — read your own project's size in the editor and redo the arithmetic with it:

  • Project size: 8 MB = 8,000,000 bytes × 8 bits/byte = 64,000,000 bits
  • Serial link at 115,200 bit/s: 64,000,000 bits ÷ 115,200 bit/s = 555.6 s ≈ 9.3 min
  • Ethernet at 10 Mbit/s: 64,000,000 bits ÷ 10,000,000 bit/s = 6.4 s of line time

Line time is not elapsed time: protocol overhead and the panel's flash write speed dominate, so even the Ethernet case takes minutes, not seconds. Add the restart and the login test on top. Use Ethernet where the panel has the port; if the panel is serial only, stop the machine in a controlled state and schedule the full 15-minute window with production.

Keep reading

Questions asked

How do I keep an SP2 installation available after moving to SP3?

Keep it on a separate engineering PC or a virtual machine. A project saved by SP3 does not reopen as an SP2 project, so the archived original plus an SP2 installation is your way back, and practitioners routinely run several WinCC flexible versions in separate VMs for exactly that reason.

How many failed login attempts should I allow before lockout?

Set a finite limit of 3 attempts only when an administrator account is reachable on every shift that runs the machine; that limit slows password guessing and gives you a recovery path. If no administrator is available on nights or weekends, set unlimited attempts and control access with the panel's physical enclosure instead — a permanently locked-out operator is the worse failure.

Will replacing user administration delete recipes and logged data on the panel?

Not by itself. The transfer options treat the application, user administration, and other stored data as separate sets on devices that store them separately, so replacing users leaves recipes in place. An operating-system image update is the action with wider reach. Back up recipes, logs, and user data before any transfer session on a panel you have not tested, not only before an image update.

Is migrating to TIA Portal an alternative fix for this lockout?

Not for the lockout — clear it in WinCC flexible today. The move to TIA Portal is a separate project: a migration tool prepares the WinCC flexible project, and on a 32-bit installation the tool first converts the .hmi project file into an AM13 migration file that TIA Portal imports. Do that migration on its own schedule, with its own tests.

What should I test after the redownload finishes?

Log in with the operator account, then enter one wrong password and log in correctly to prove the account still works after a failed attempt. Then confirm screen navigation, verify live values against the PLC, and check that an administrator login still works before you hand the machine back to production.

Keep reading

  • Troubleshooting

    HMI Text Runs Off the Screen After Downloading the Project

    The panel and the project are both fine: the engineering PC's Windows display scaling is above 100%, so the downloaded layout lands past the panel edge even though the editor and offline simulation look correct. Set the scale to 100%, restart the PC, then redownload.

    HMI and touchscreens

  • Selection guide

    Planning an HMI Terminal Replacement From an Older Operator Panel

    Decide an operator-terminal replacement on installed cost — the terminal, cutout adaptation, application software, engineering, commissioning, downtime and a spare — never on terminal price alone. Measure the opening against the replacement's documented cutout range and count displays before ordering: a slightly smaller terminal needs a bezel adapter, and a large converted application can force the higher-performance model. Convert in the same brand when the source project opens cleanly; rebuild cross-brand when you accept the extra engineering hours for source control.

    HMI and touchscreens

  • Explainer

    HMI OPC UA Server vs Client: Which Direction Works

    OPC UA support on an HMI spec sheet almost always means the panel runs a server that serves its tags to external clients. Reading PLC symbols by name needs an OPC UA client driver, a separate capability you verify in the driver list for your exact software release, target and license.

    HMI and touchscreens

Keeping PanelView Plus User Passwords After an MER Download