IMDTouchKnowledge BaseShop main store

Troubleshooting

HMI Screen Goes Blank for Seconds Then Recovers

HMI and touchscreens Published 7 min read

Short answer

A blank of a few seconds that recovers on its own, and survives a project reload, points first at a PLC-controlled backlight, screen-saver or visibility tag being overwritten at runtime. Separate backlight loss from a panel restart by checking the rear status LEDs and tracing the tags the Reset action writes before swapping hardware.

On this page
  1. Tell a backlight blank from a panel restart
  2. Why the backup project reproduced the blank
  3. Trace the Reset action and its tags
  4. The disappearing pushbutton is the same fault class
  5. Worked example: matching the blank to a timer
  6. When the panel itself is at fault
  7. Fix the tag ownership and verify
  8. Decision by case
  9. Questions asked

No — a blank of two or three seconds that returns on its own, and reproduces after you reload the backup project, is almost never a panel about to die. A backlight that is failing goes dark and stays dark; it does not run a two-second errand and come back clean. The reproduction after the reload is the clue: it says the blank lives in the project configuration or in tag behavior, not in the glass. Work the Reset button's action and the tags that touch the backlight, the screen saver and object visibility before you order hardware.

Tell a backlight blank from a panel restart #

Three conditions produce "the screen went blank," and each has a different fix. During the next controlled occurrence, watch four things:

  • The rear status LEDs, with the panel documentation open beside you: read what the backlight-fault indication actually is, and do not decode colors from memory.
  • Runtime survival: after the blank, does the panel come back on the same screen with live values, or does it play a boot logo and land on the startup screen?
  • Depth of the blank: fully black means the backlight is off; a dimmed but readable image is a saver.
  • Touch during the blank: a beep or click on press says the runtime is alive behind dark glass.
What you see What it is Where to work next
Black screen, same page and values return, LEDs normal Backlight commanded off by a tag or an object action Trace the backlight and screen-saver tags and the button action
Boot logo, then the startup screen Panel restart Check the button action for a reset function; meter the 24 V supply during the press
Dimmed but readable, first touch restores it Screen saver on its inactivity timer Adjust the saver settings — but a blank that starts at a press cannot be this

The last row is a hard exclusion. The screen saver dims the display after a set period with no touch activity, and a press is touch activity: a blank that begins the moment a button goes down is commanded, not timed. If the screen instead stays dark after a restart and never recovers, you are on a different fault — the power and display chain behind a panel PC HMI that stays dark after a reboot.

Why the backup project reproduced the blank #

On C-more panels, the screen saver and backlight saver are project-level settings: every download writes them to the panel again. Reloading the backup reinstalled the same display-control configuration, so that test could never clear the blank — it could only confirm it. Read the result the right way round: reproduction after a reload moves the panel down the suspect list and moves the project and its tags up. The meaningful download is the one after you correct the button action or remove the savers.

Trace the Reset action and its tags #

  1. Open the running project and the backup side by side. The backup is a comparison copy; do not assume it differs from what is in the panel.
  2. Open the Reset pushbutton's press event and read what it actually does: write a tag, change screens, call a system function, or restart the panel. The word "Reset" on the key is caption text and tells you nothing about the action.
  3. Check the display-related system functions your platform provides. C-more ships an "Activate Screen Saver" object that starts the screen saver when its button is pressed, and dimming the backlight is what the saver does. If the Reset button's action was pointed at that class of function, every press blanks the panel.
  4. Open the screen saver and backlight saver setup and record the mode: inactivity timer, tag control, or both.
  5. Cross-reference every address involved — the button's write tag, the backlight or saver control tag, and each disappearing object's visibility tag — and list every writer of each in the PLC program.
  6. Go online and watch those tags through one controlled press: values before, during and after the blank.

If that Reset button clears machine state, make this single press with the machine in a safe condition under your site's procedure — do not keep pressing it to make the blank happen.

One tag with two writers is the commonest root cause: the button writes the display tag, the PLC reset sequence writes it again a moment later, and the display follows whichever value lands last. It is the same failure class as a PID process variable being overwritten by a second writer — last write wins, and the symptom shows up exactly where the losing value is displayed. The overwrite can also run the other way: HMI-to-PLC writes land at connection startup.

The disappearing pushbutton is the same fault class #

An object whose visibility is driven by its own press state is hidden for exactly as long as the press bit is set. A stuck bit keeps the object off the screen until something rewrites it, which is why holding the button for a few seconds brought it back. That missing button and the blanking display share one root: display-state tags with the wrong or competing writers. One distinction before you move on: if an object is visible on screen but its presses do nothing, that is a touch fault rather than a visibility fault, and it is worked as a screen where only one icon responds to press.

Worked example: matching the blank to a timer #

Take the symptom as reported: a press, about 2 seconds of black, full recovery, same screen. The documented pattern for tag-driven backlight control is the pseudo screen saver built on PanelView Plus: a backlight intensity tag where 100 is full brightness and 0 (or a low value) is dark.

Now the illustrative logic. Suppose the reset sequence works like this: the press writes the intensity tag to 0, and a reset-done timer with a 2.0 second preset fires and writes 100 back. The blank duration is the gap between the two writes:

2.0 s preset → blank = 2.0 s, against roughly 2 s observed — a match inside the ±0.5 s a hand stopwatch resolves.

Prove it: change the preset from 2.0 s to 5.0 s and press once. If the blank grows to about 5 s, the tag drives the display and the fix is in the logic, not the panel. If it stays near 2 s, that timer is not your writer and you move to the restart branch.

The inactivity saver is excluded by arithmetic. With a 5 minute setting — 300 s of no activity — the saver cannot fire 2 s after a press, because the press restarts the inactivity clock; 2 s is one 150th of the window. Whatever your setting is, a blank that begins at the press is commanded, never timed.

When the panel itself is at fault #

Two findings move the blame to hardware. First, the rear LEDs showing the documented backlight-fault indication: a failing backlight does not recover in two seconds, it goes and stays gone. Second, a boot logo where the blank was: that is a restart. If the button's action contains no reset function, meter the 24 V rail at the panel terminals during the press — a reset sequence switching its loads can sag the supply below the panel's rated minimum input and drop the display until the rail recovers.

A spare panel settles the ambiguous case. Load the identical project, keep the conditions the same, make the one press: if the blank follows the original panel, work its backlight and power; if it stays with the project, return to tag ownership. If you maintain several machines, one spare HMI panel covering several machines is the comparison unit you already own.

Fix the tag ownership and verify #

  • Give each display-state tag one writer. If the reset sequence must dim the display, the same sequence restores the intensity to 100 when it finishes; the HMI button and the PLC rung do not both own one tag.
  • Point the Reset button's action at the single write it was meant to perform, and strip any screen-saver or reset function out of it.
  • If you do not want the saver at all, disable it in the project before the next download — a setting that rides with the project never ages out of the panel on its own.
  • Replace visibility driven by the object's own press state with a dedicated tag the PLC controls.
  • Verify at runtime, not at download: one controlled press with the tags online, then exercise the inactivity window and the visibility transitions that previously hid the object. A clean download proves nothing about runtime behavior.

Decision by case #

  • Blank starts at the press, runtime survives, LEDs normal: display-control tag or button action. Fix the ownership; the panel stays in service.
  • Blank with a boot logo: restart. Remove the reset function from the action, or fix the supply dip; the panel stays in service.
  • Backlight-fault indication on the LEDs, or the blank follows the panel when a spare runs the same project: backlight or panel hardware. Repair or replace it and keep the corrected project.

Questions asked

Is a blank that recovers after a few seconds the start of backlight failure?

Usually not. A failing backlight announces itself over weeks — a dim display, and on CCFL-lit panels a pink or red cast — and when it dies it stays dark. A clean two-second blank with normal status LEDs and an intact runtime is a commanded display state, so the fix sits in the project, not the glass.

Why would a button set to visible-when-not-pressed disappear?

An object like that is hidden for exactly as long as its press bit is set. If the bit sticks — a held touch contact or a latched PLC rung — the object stays off the screen until something rewrites the bit, which is why holding the button for a few seconds brought it back. Check who writes that bit before blaming the touch surface.

How do I turn the screen saver or backlight saver off in the project?

In EasyBuilder Pro, deselect the "Back light saver" and "Screen saver" options in the project settings, then download. On C-more panels the two are project-level settings written to the panel at every download, so removing them from the project is the only way the panel stops receiving them.

Can the HMI overwrite a PLC tag on its own?

Yes. An HMI tag that carries an initial value writes that value to the PLC the moment the connection establishes, so a zero initial value can wipe a retained PLC value at every HMI start. Remove the initial value from the tag or set the tag so the HMI only reads it.

Keep reading

  • Troubleshooting

    Fixing an HMI Project That Fails After a Git Clone

    The clone is broken because a referenced bitmap .PLK was never committed, not because of an ignore rule. Read the HMI Output tab for the exact filename, prove the file is untracked with git check-ignore followed by git ls-files, then restore and commit it and re-test from a clean clone. Track the .tgt and .def files for the HMI BIOS version as well.

    HMI and touchscreens

  • Troubleshooting

    Fixing TwinCAT HMI publish failures after a NuGet update

    The publish task fails with every symbol unresolved because TF2000, TE2000 and the HMI NuGet packages are at mixed versions after a partial TcPkg upgrade. Update all three groups together on the engineering PC and the IPC, redeploy an empty project to prove the path, then republish: the failure sits in the environment, not the project.

    HMI and touchscreens

  • How-to

    How to Upload an HMI Program Without the Right Cable Pinout

    Upload an HG3F with the documented programming cable HG9Z-XCM1A, which runs from a 9-pin RS-232 port on the PC to Serial Interface 2 on the panel. Do not fabricate a pinout, and confirm the installed WindOI-NV2 version permits upload before you connect.

    HMI and touchscreens