Applicable Systems
GP4000 Series
Symptoms
The HMI runtime application has crashed. The screen shows a white screen or error message with a stack trace reference number.
Possible Causes
- Scripting error in a custom script causing a runtime exception
- Memory leak in the HMI runtime depleting available RAM over days of operation
- Corrupted project file after an interrupted download
- Incompatible third-party ActiveX or widget installed on the screen
Troubleshooting Steps
- Step 1: Record the error message and stack trace reference for manufacturer support
Include the HMI model, firmware version, and project version in the report - Step 2: Reboot the HMI by cycling power to clear the runtime state
If the crash recurs, investigate the project file and scripts - Step 3: Re-download the project from a known-good backup
Use the last verified project file to eliminate corruption as a cause - Step 4: Disable any custom scripts or third-party widgets and test for stability
Re-enable one at a time to identify the problematic element
How to Reset
Reset: The HMI restarts after a power cycle. Clear the crash report from the diagnostic menu.
Common Replacement Parts
- USB backup drive: 8GB, FAT32 (Store the last known-good project file)
- Memory module: 512MB-2GB DDR3 SODIMM (Match to HMI model specification)
Frequently Asked Questions
- Q: How do I prevent HMI crashes?
Keep firmware updated, use error handling in scripts, avoid excessive screen complexity, and reboot the HMI monthly as preventive maintenance.
- Q: What is a stack trace?
A report showing the sequence of function calls that led to the crash. It helps developers identify the exact location of the error in the code.
- Q: Can a virus infect the HMI?
Rare on embedded HMIs, but possible on Windows-based panels. Use OEM antivirus tools and avoid untrusted USB drives.
Source: OEM Technical Manual
Category: HMI