Hmi Backup Hot! — Mcgs

Performing a regular MCGS HMI backup is a critical maintenance task to protect industrial automation projects from data loss due to hardware failure or accidental deletion. Whether you are working with the TPC series or other embedded models, there are two primary methods for backing up your system: using a PC with configuration software or using a USB flash drive directly at the panel. Method 1: Backup via PC and MCGS Software

The most comprehensive way to back up and manage project files is through the official MCGS Embedded Configuration Software. This method allows you to upload the project from the HMI to your computer for editing or archiving.

Establish a Connection: Connect your PC to the HMI using a USB communication cable or an Ethernet (LAN) cable.

Open the Software: Launch the MCGS configuration tool on your computer.

Navigate to Upload: Go to the File menu and select Upload Project. Configure Settings: Set the save path and provide a file name for your backup. Select the communication method (e.g., USB or Ethernet).

If using Ethernet, scan for the device or enter its specific IP address. mcgs hmi backup

Start Backup: Click Start Upload. If the project is not password-protected or restricted, the software will transfer the project files, including variables and graphics, to your PC. Method 2: Backup to a USB Flash Drive

If you do not have a PC on-site, you can use the built-in file management tools on the HMI to create a backup on a FAT32-formatted USB drive.

Enter the System Menu: Access the panel's internal settings. On many MCGS models, this involves a specific touch sequence or finding the "Service and Commissioning" or "File Operations" menu.

Select Backup Tool: Look for the file operation icons. For example, in some TPC series menus, a disk icon with a green arrow typically represents the Backup (archive) function.

Choose Storage: Select the USB drive as the target storage location. Performing a regular MCGS HMI backup is a

Execute: Confirm the backup process. The HMI may restart to begin creating a full image of the flash memory, including the operating system and applications. Step of MCGS screen upload program-ZhongpingTech

5. The Scripted Backup Routine (McgsPro Advanced)

Stop doing manual USB backups. Use the built-in !FileCopy() and !Rename() functions inside a cyclic strategy (run every 24h at 3 AM).

Sample Logic:

IF Time = "03:00:00" THEN
    !FileCopy("\MCGS\Program\Project.mcg", "\HardDisk\Backup\Project_%Date%.mcg")
    !FileCopy("\MCGS\Program\Config.ini", "\HardDisk\Backup\Config_%Date%.ini")
    !FileDelete("\HardDisk\Backup\*.bak", 30) //Keep 30 days
ENDIF

Note: This requires an external USB drive or network folder mapped as \HardDisk\.

11. Conclusion

MCGS HMI backup is not a one-time event but a recurring engineering discipline. This paper has demonstrated that while USB backup is straightforward for single units, large installations demand automated Ethernet-based strategies and version control. The presented case study confirms that proper backup reduces recovery time from days to minutes. Future work should explore incremental backup algorithms for MCGS’s proprietary database format and integration with industrial SIEM systems. Note: This requires an external USB drive or

All plants using MCGS should adopt a formal backup policy based on the checklist in Section 10. Doing so ensures operational continuity and compliance.

4.3 Cloud Backup (Optional via Gateway)

• Using an industrial gateway (e.g., MCGS TPC with 4G) to upload compressed projects to AWS S3 or local NAS.
• Pros: Geographically redundant.
• Cons: Cost, latency, and data egress fees.

Review: MCGS HMI Backup – Reliable but Requires Care

Overall Rating: ⭐⭐⭐⭐ (4/5)

Limitations to Know

• Upload requires project password – By default, MCGS disables upload from HMI unless the developer enabled "Upload" permission and set a password. Many first-time users lose source code this way – always enable upload in your project settings before deployment.
• No incremental backup – It’s full-project only. For frequent changes, you’ll manually manage versions.
• Firmware mismatch risk – Restoring a project from a newer firmware version to an older HMI may fail. Always match firmware or use "Export as Package" with compatibility mode.
• USB format fussiness – Some older MCGS units only accept FAT32, not exFAT or NTFS.

1. The “Three-Layer” Deception

An MCGS runtime is not a monolithic file. It is an ecosystem. To truly recover, you need three distinct layers:

• Layer A (Development): The .mcgs or .mce project source. This is the blueprint.
• Layer B (Runtime Configuration): The Config.ini, UserDB.mdb, and alarm/recipe .dat files on the HMI’s flash disk.
• Layer C (Kernel & Drivers): The specific MCGS runtime version (e.g., v1.6 vs v3.3) and Windows CE/Embedded drivers. A 2024 runtime will not open a 2016 kernel backup.

The Deep Truth: Backing up only Layer A means you lose historical trends, user management permissions, and recipe values.