IMDTouchKnowledge BaseShop main store

Troubleshooting

Why an HMI Loses Its Program After Every Power Cycle

HMI and touchscreens Published 7 min read

Short answer

A flash-based panel keeps its project through power-off without a battery, so loss on every cycle means a supply dip below the panel's documented limit, a transfer that never completed, or failing storage. Classify what the screen shows at restart, capture the supply voltage at the terminals through a switch-off and on, then do one clean transfer and prove it survives a controlled power cycle.

On this page
  1. Classify the post-restart state first
  2. What actually keeps the project through power-off
  3. Measure the supply through the switching event
  4. One clean transfer, then a retention test
  5. Screens survive but setpoints reset
  6. When the storage itself is failing
  7. Decisions by case
  8. Questions asked

A panel that comes up empty every time the machine is switched off is not losing its project at random. On a current flash-based panel the transferred project sits in nonvolatile storage that needs neither supply power nor a battery, so when it disappears on every power cycle, one of three things is true: the supply dips below the panel's documented input range during switch-on, the last transfer never completed cleanly, or the storage itself is failing. Downloading the same project a third time will not separate those causes. Classify what the screen shows after a restart, capture the supply voltage at the panel's own terminals through a switch-off and switch-on, then make one clean transfer and prove it survives a controlled cycle.

Classify the post-restart state first #

Restart the panel and record exactly what appears, including the full text of any error message, photographed before you touch recovery. Each state points to a different fault:

  • Dark screen, no backlight, no logo. The panel is not being supplied. Measure at the panel's terminals, not at the cabinet bus; fuse, breaker, conductor and terminal torque are the suspects, and the project is untouched.
  • Boot loop — logo, dark, logo again. The panel starts, its inrush adds to the cabinet's, and the supply collapses. A reset timed to power-up is a supply fault, and the project is usually intact.
  • Startup or transfer screen instead of runtime. If a project is listed but does not launch, the start mode is wrong — configuration, not loss. If the list is empty, the last transfer never completed or the storage did not hold the write.
  • Normal screens, dead values. Runtime and project are fine; the PLC connection is the fault. Treat it as comms, not retention.
  • Normal screens, defaulted setpoints. The project is present and value retention is missing — a different mechanism with its own fix below.

What actually keeps the project through power-off #

Transfer writes the project into the panel's nonvolatile storage, where it holds unpowered for the life of the device. Nothing on that path depends on the backup battery: where the panel carries one, its documented job is the real-time clock or retained settings, so a battery that measures good proves nothing about project retention, and replacing it will not stop this fault.

Two real failure modes remain. Storage that is failing can drop a write that the engineering software reported as complete, and an interruption during a transfer or an operating-system update leaves storage half-written, which presents as a missing project at the next start. For the feed itself, size the 24 V circuit from the panel's documented power consumption — the manual's power-loss figure corresponds to that consumption value — and count the panel's share of inrush when checking the budget.

Measure the supply through the switching event #

This is live electrical work at the panel terminals: use a meter rated for the category and voltage, and de-energize before touching any wiring.

  1. Read the permitted input range from the rating plate or data sheet; a 24 V DC panel carries a stated lower limit, and that number is the pass/fail line.
  2. Measure at the panel's own terminals with the machine running, and confirm the steady reading is inside the range.
  3. Put a storage oscilloscope or power-quality logger on the terminals. A multimeter's min/max holds a sag lasting seconds but misses a dip of tens of milliseconds — long enough to reset a panel.
  4. Switch the machine off, wait at least 30 s so any ride-through buffering is fully discharged, switch it back on, and capture the whole event.
  5. Read out the minimum voltage and how long it spent below the documented lower limit.

DC-input equipment is immunity-tested for voltage dips and short interruptions to IEC 61000-4-29. In plain words, that standard defines how dips and brief interruptions on a DC input are applied and graded, which is where the dip depth and duration figures in a panel's data sheet come from — so compare your captured event against the panel's declared ride-through, not against the nominal 24 V.

Worked example with illustrative numbers; substitute your own label values and capture. Rating plate: 24 V DC, permitted range 20.4–28.8 V. Steady reading with the machine running: 24.1 V. The capture during switch-on shows a minimum of 17.4 V held for 40 ms while the cabinet inrush peaks, then recovery to 24.0 V. Arithmetic: 20.4 V − 17.4 V = 2.8 V below the documented lower limit, and 17.4 V ÷ 24.1 V = 0.72, a dip to 72% of nominal. Decision: every start drives the panel 2.8 V under its documented limit and resets it mid-start. Fix the supply path — 24 V capacity, contactor bounce, shared inrush, conductor size, terminal torque — or give the panel a dedicated feed or a small 24 V UPS once the event is measured, and repeat the capture until the minimum lands inside the range.

One clean transfer, then a retention test #

  1. Open the project in the engineering tool, confirm the target device matches the panel's exact hardware, and compile until it is error-free.
  2. Keep an editable source copy of the project; a device backup is not the same thing, and project recovery and backup practice decides what you can still restore after a failed transfer.
  3. Put the panel in its transfer state, download, and hold supply and connection steady until the software reports completion.
  4. Start runtime, then verify the HMI project version actually running on the panel — an older project surviving on the device is a classic false retention result.
  5. Run the retention test with the capture still connected: switch off and on exactly as in the measurement above, and confirm the application starts unaided with the supply minimum in range. Two consecutive passes prove retention; one pass proves nothing.

Screens survive but setpoints reset #

If the application returns intact and only operator-entered values default, the project is fine and the values were never stored anywhere retentive. Values held in HMI memory reset with the runtime; the fix is to move them into the controller — keeping HMI-entered timer presets in PLC memory with those addresses marked retentive — so a power cycle restores them from the PLC side.

When the storage itself is failing #

If the supply is proven inside its documented range through a full switch cycle, and a completed, verified transfer still vanishes at the next start, the storage subsystem is the prime suspect. Run the manufacturer's operating-system recovery or reset for the exact panel, exactly as documented, and establish what it erases before you begin; then transfer once more and repeat the retention test.

If it fails again with supply and transfer both clean, this is a repair-or-replace decision. The file that makes it one support round instead of three: order number from the rating plate, operating-system and firmware versions, the transfer log, the supply capture, and photographs of the failed start. When the terminal is old enough that recovery and repair stop being worth it, industrial panel PCs are the replacement path for a machine-side operator station. Proving a PC-based HMI before you replace the terminal keeps that migration cheap to reverse.

Decisions by case #

  • Dark after restart: no supply at the panel terminals — fix the fuse, breaker or wiring; the project is intact.
  • Boot loop at power-up: the supply dips below the documented lower limit during inrush — fix the supply path or add a dedicated feed; the project is intact.
  • Startup screen with a listed project that does not launch: wrong start mode — correct the configuration and restart.
  • Startup screen with an empty project list: incomplete transfer or a dropped write — one clean transfer with the supply verified first.
  • Supply in range, clean completed transfer, project still vanishes: failing storage — manufacturer recovery, then repair or replace the terminal.
  • Screens fine, values dead: a PLC comms fault, not a retention fault.
  • Screens fine, setpoints defaulted: value retention — move the values into retentive PLC memory.

Questions asked

Does a dead backup battery delete the HMI project?

Not on a flash-based panel. The transferred project sits in nonvolatile storage that needs no power and no battery to keep it; where the panel carries a battery, the manual assigns it to the real-time clock or retained settings. A battery that measures good proves nothing about flash memory, so replacing it will not stop this fault. Only panels from the era of battery-backed memory cards lose a project when their battery dies.

Can a power cut during the download itself cause this?

Yes. Interrupting a transfer or an operating-system update can leave the panel's storage half-written, and the panel then behaves as if the project is missing. Repeat the transfer once with the supply verified stable, keep power on until the engineering software reports completion, and only then run the controlled power-cycle test. If the panel reports a load or operating-system error instead of completing, use the manufacturer's recovery procedure for that exact model.

Is a multimeter enough to catch the supply dip?

A multimeter on min/max will hold a sag that lasts seconds, but it can miss a dip of a few tens of milliseconds, which is long enough to reset a panel. Use a storage oscilloscope or a power-quality logger on the panel terminals for the switch-on event. Record the minimum voltage, how long it stayed below the panel's documented lower limit, and exactly when it happened relative to the machine starting.

Does the project have to be reloaded after an operating-system recovery?

Yes, plan for it. A manufacturer's operating-system recovery or reset puts the panel back to its delivered state, which normally means storage is emptied and the project, plus any panel-side settings, must be downloaded again afterwards. Run the recovery with the supply measured and stable, transfer once, then pass the two-cycle retention test before you call the panel fixed.

Keep reading

  • How-to

    How to verify the HMI project version running on a panel

    A panel does not expose a build signature you can read back, so make the project carry its own: a release label on a maintenance screen, an approved archive, and a deployment-record entry per panel. Read the label on every panel and compare it with the record; a checksum of runtime files is a different check over different bytes, and neither value substitutes for a safety signature.

    HMI and touchscreens

  • Troubleshooting

    Troubleshooting an HMI Panel Stuck on the Autotest Boot Screen

    A panel that hangs on the autotest or splash screen is failing before the application loads, and the touchscreen is almost never the cause. Record the stop point, measure input voltage during a failed start, reseat the display-to-logic-module connection de-energized, then test a known runtime before touching firmware. The check order below splits supply, connector, application and firmware causes and ends with the decision for each outcome.

    HMI and touchscreens

  • Troubleshooting

    OP15 project recovery: ComText, ProTool or ProSave

    Recovering a project from a Siemens OP15 starts with the panel's generation, not software preference. First-generation OP5 and OP15 hardware belongs to ComText, second-generation hardware belongs to ProTool, and firmware version 2.2 draws the line. ProSave is not in the decision: it writes a backup image, not an editable project, and the OP15 is not on its supported-device list.

    HMI and touchscreens