When objects you place in the HMI editor draw only after a screen switch and stop responding seconds later, while the same file edits normally on a desktop, the fault is in the laptop's graphics and software environment. Hold the project constant, compare the two computers, then fix the driver, the display utilities and the scaling on the laptop.
Objects that will not draw, move or respond until you switch to another screen and back are a redraw fault in the programming computer, not damage in the project file. The evidence is a clean split: an 11 MB, 50-screen project edited normally on a desktop and stalled on the laptop. Importing it into a new project file changed nothing. A second laptop showed the identical failure on a 2.8 MB project. Hold the project constant, test it on both computers, then fix the laptop's graphics environment. This page gives the checks in order, the numbers for each, and the acceptance test that tells you the editor is genuinely repaired.
Why do objects stop drawing on the screen I am editing?
The editor's redraw is failing on that one computer. You place an object, it draws only after you switch to another screen and back, and it stops responding within seconds. That is a display fault in the laptop, not damage in the project file. That is the reported case in full: a plant running four shop-floor screens at 15, 12, 8 and 6 inches, all cut from one growing project, and the stalls appearing only while editing the 15 inch version on one laptop. The panels themselves kept running. The editor on the programming computer is the broken piece, so that is where the testing goes. If an operator later reports a fault at a panel, treat it as its own problem with its own test.
Is an 11 MB, 50-screen project too big to edit?
No: file size is cleared as the cause. A second laptop running 64-bit Windows 7 with 8 GB of RAM and a solid-state drive showed the identical redraw failure on a 2.8 MB project, a quarter of the file size. On the original laptop the smaller variants edited fine, which is why size looked guilty at first. The second machine settles it: fast processor, plenty of memory, fast drive, and a small file stalling exactly the same way. Size loads the editor; the repaint fault follows the machine. If you want small files for testing, the variants cut for the 12, 8 and 6 inch panels are ready-made, and rebuilding a project for a smaller panel is covered separately.
Which symptoms point to the laptop and not the project?
Four behaviors together identify a workstation fault. The failure follows one computer, survives a project import, appears on a machine with strong hardware, and clears for a few seconds whenever a screen change forces a full repaint.
| What you see | What it tells you | What to do next |
|---|---|---|
| A new object is invisible and will not move until you switch to another screen and back, then freezes again within seconds | The screen change makes the editor repaint everything, so the machine's normal drawing path is the broken part | Go to the graphics driver and display utilities on that laptop |
| The same saved file edits normally on the desktop | The file and its data are sound; the fault travels with the computer | Hold the file constant and compare the two machines |
| Importing the project into a brand-new project file changes nothing | You rebuilt the container and kept the fault, so the container was never the problem | Stop repeating the import and move to the environment tests |
| The identical failure on a second laptop with 8 GB of RAM and a solid-state drive | Speed and memory are not the gate; a 2.8 MB file stalls the wrong machine just the same | Spend the hours on the software environment, not on upgrades |
What should you check before changing anything on the laptop?
Run the two-computer comparison first. It takes about 40 minutes and tells you which side of the desk the fault lives on: open the same saved file on both machines and place, drag and select one test object on three screens. Work through these checks before you uninstall or update anything:
- Copy the project to a dated backup on each machine and close the production copy. Every test below runs on the copy.
- Confirm both computers run the same release of the HMI programming software. A version difference produces editor faults of its own, and running two HMI software versions side by side on one machine is the documented way to hold two releases.
- Write down the graphics driver version and date on each machine. The laptop driver is the item under test.
- Write down the Windows display scaling on the laptop. Editor display faults from scaling are real, and Windows DPI and missing editor text is the documented example of one.
- Run the comparison in the example below before you change a single setting.
What does an example isolation test look like with numbers?
Example: an 11 MB, 50-screen project and one small variant, each opened on the affected laptop and on the desktop, four working sessions of about 10 minutes each, so the whole comparison fits in 40 minutes plus file-copy time. Two files times two computers is four tests, and four tests at 10 minutes each is 40 minutes of editing.
On each machine, open the file, place one new object, drag it, select it, then switch to another screen and back once. There are three ways it can land:
| Result | Decision |
|---|---|
| Stalls on the laptop, edits on the desktop | Laptop environment. This is where the reported case landed; go to the fix section. |
| Edits on both machines | Intermittent. Update the laptop driver, then rerun all four tests before touching the project. |
| Stalls on both machines | The file or the software release is the suspect; compare releases first. |
Follow the laptop leg with the second-drive install and the same 11 MB file. A clean pass there closes the case: the file is sound and the laptop's normal setup carries the fault.
How do you run the clean-environment test on a second drive?
Put a second drive in the laptop, install your licensed Windows on it, add only the HMI programming software, and open the copied project. If objects draw and stay responsive there, the fault sits in the original installation, and your main drive stays untouched. Steps:
- Back up the project and confirm the desktop copy opens.
- Fit a second drive in the laptop, solid-state if the bay takes one.
- Install Windows from your licensed media and skip the laptop maker's utility suite.
- Install the HMI programming software only, the same release as the desktop.
- Update the graphics driver to the release the GPU maker currently publishes.
- Copy the project file over, open it, and run the redraw test in the last section. Swap back to the original drive when you are done; nothing on it changed.
What is the actual fix for the laptop?
Update the laptop's graphics driver to the release the GPU maker currently publishes. Leave the laptop maker's display utility suite off the machine. Set Windows display scaling to 100 percent for editing. Those are the three differences the clean-drive test isolates. Apply the same three to the main drive: the current driver in place of whatever the machine shipped with, the utility suite uninstalled, scaling at 100 percent while editing. Then retest with the acceptance test below before production work goes back to the laptop.
If the clean install still stalls with a current driver, the editor installation is the next suspect: repair or reinstall the HMI programming software on the laptop, with the same discipline as diagnosing an editor fault before repairing software. And if the laptop is due for replacement anyway, buy against the spec in what a controls laptop needs, with current graphics driver support on the list.
Recommendation: Keep production edits on the desktop while you repair the laptop. Update the laptop's graphics driver, take the maker's display utilities off, set scaling to 100 percent, and pass the second-drive test before real work returns to the laptop. Rebuild the 50-screen project only if it still stalls on the clean install with a current driver; at that point, and only then, the file is the suspect.
How do you confirm the editor redraw is stable again?
Pass a fixed acceptance test on the machine before you trust it: place 10 new objects, drag each one, switch to another screen and back 5 times, save, close and reopen the file twice, and repeat the whole round after 30 minutes of editing. Pass means every object stays visible and responsive through the whole sequence with no screen-switch trick. Fail once and the laptop goes back to the bench while the desktop keeps the production work. Rerun the same acceptance test after each change you make, one change at a time, so a pass tells you which change carried the fix.
Questions
Will more RAM or a solid-state drive stop the stalls?
No. The same redraw failure was reported on a laptop running 64-bit Windows 7 with 8 GB of RAM, a solid-state drive and a fast processor. Upgrading speed and memory leaves the drawing path alone, so spend the hours on the graphics driver and utilities instead of the hardware.
Is it safe to keep forcing redraws by switching screens while I finish an edit?
As a stopgap only, and on a copy. A screen switch buys a few seconds of responsiveness, and an edit approved through a half-drawn screen can save something you never actually saw. Finish production edits on the desktop, where the file already draws correctly.
Did my running panels get corrupted too?
No. The fault sits in the programming computer's editor. The panels kept running while the editor misbehaved, and a panel gets its own investigation only if operators report a symptom at the machine. Editor redraw trouble and panel faults are separate problems with separate tests.
How long should the whole diagnosis take?
About half a day. The two-computer comparison is 40 minutes, the second-drive Windows installation with the HMI software is 2 to 3 hours, and the acceptance test adds 30 to 40 minutes. Keep editing on the desktop throughout so production work never waits on the diagnosis.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.