Don't just back up the graphics layout. Configure your MCGS project to automatically export daily or weekly CSV logs of alarms and recipes to a networked FTP server.

| Pitfall | How to Avoid It | |---|---| | | Use FAT32 format, capacity ≤16 GB, and place the tpcbackup folder in the root directory. | | “No original project in the target device” error | When downloading, always select “支持工程上传”. If you inherit a system without this, request the source files from the original programmer. | | Backup file cannot be opened after copying to a PC | Make sure you are using the same version of MCGS group‑editing software that created the project (or a compatible version). Check the .bak and .old methods described in Section 3. | | Restored HMI does not communicate with PLC | Verify that IP addresses, node names, and serial port settings were backed up and correctly restored. These details are often stored outside the project file, in separate configuration files. | | Backup overwritten by a newer (wrong) version | Implement strict version control. Never save a new backup over the old file without keeping a dated copy. | | USB drive carries malware into the OT network | Use dedicated USB drives for control system work only. Always scan the drive on an approved workstation before inserting it into any OT device. |

Human-Machine Interfaces (HMIs) are critical components in modern industrial control systems. MCGS (Monitor and Control Generated System) is a widely used configuration software for HMIs in China and global markets. One of the most overlooked yet vital maintenance tasks is proper backup of MCGS HMI projects. This paper examines the architecture of MCGS HMI systems, the risks associated with inadequate backup, step-by-step backup and restoration methods (including USB, Ethernet, and cloud-based approaches), version management strategies, and disaster recovery planning. Empirical comparisons of different backup media are provided, along with a case study from a water treatment facility. The paper concludes with a checklist for engineers to ensure zero data loss during HMI replacement or failure events.

Another common situation: you open a project created with an older version of MCGS software, and the software automatically converts the project to a newer format. The original older‑version project is saved as an .old file.

An MCGS HMI typically houses the compiled runtime project (often saved with the file extension .MCE ), historical alarm logs, production recipes, and runtime user accounts. Relying solely on the original project file stored on a single engineering PC leaves your operations vulnerable. Executing a proper backup allows you to:

This is where becomes not just a best practice, but an operational necessity. This article will walk you through everything you need to know about creating, storing, and restoring backups for your MCGS HMI panels.

Which of the MCGS software are you currently running?

Most MCGS panels (TPC series, cMT series) support runtime backup via USB. This is the fastest way to clone an HMI for replacement.

: Ensure the .mcp or compiled files are visible on the drive. 💻 Method 2: MCGS Software Backup (Via PC)

This is the ultimate guide to MCGS HMI backup, designed to provide a systematic and standardized operational process for industrial automation engineers.

Use an older, smaller USB drive (16GB or smaller) and double-check that it is formatted strictly to FAT32 . Best Practices for Industrial Data Redundancy