PLC/HMI Backups: Prove Editability Separately from Download Recovery
A maintenance folder called “PLC backup” is not proof that the next technician can recover or modify a machine. A transferable runtime file and an editable engineering project answer different questions. Verify both, and record exactly which PLC logic, HMI screens, settings and supporting files the package covers.
The practical answer is to give each backup two acceptance results: recovery evidence and editability evidence. A successful upload alone earns neither a complete recovery claim nor a promise that source information is present. Use the following checks when accepting an OEM handover or reviewing an existing maintenance archive.
Start with the exact device and two separate scopes
For a combined controller such as the ProSight 5 Inch HMI PLC All-in-One Controller, record the complete model and treat the PLC application and HMI project as separate items in the backup inventory. Sharing an enclosure does not establish that one exported file contains everything needed for both.

Make an inventory before attempting transfers: device identity, installed firmware or operating-system version where available, PLC engineering software, HMI engineering software, project revision and the authorised project owner. Confirm the software against the exact series documentation. A family name or familiar programming cable is insufficient evidence of compatibility.
Why upload can stop short of editable source
Coolmay’s MX3G PLC/HMI programming manual provides a concrete example in section 4.3.1. It describes an HMI upload saved as a .tpo object file. Editing the uploaded program requires decompiled information to have been included before the original download. Without that information, the uploaded program can be downloaded but cannot be edited.
That is an MX3G-specific condition, not a universal Coolmay or ProSight procedure. Do not apply its file format, software menus or programming-software assumptions to another series. If source information is absent, request the authorised original project from its owner; a later upload does not demonstrate that it has been recovered.
A different manufacturer illustrates another dependency: Schneider Electric’s EcoStruxure Machine Expert V2.0 source-archive documentation describes storing a project archive in the controller and selecting additional files such as referenced devices, libraries and profiles. Its Source Upload workflow retrieves archived sources. This is specific to that environment, but it explains why a backup review must consider the engineering environment as well as the main file.
A practical acceptance checklist
Label what each file actually is. Distinguish an original editable project, a device upload, a compiled transfer package and exported settings. Record how and when each was obtained, and keep the untouched original alongside any working copy.
Open authorised project copies offline in the documented software version. Verify that the expected logic, HMI pages, device definitions and comments are available. Record missing libraries, conversion prompts and password restrictions. Do not overwrite the archive with a converted project.
Check settings coverage separately. Identify recipes, retained values, communication configuration and other application data that the manufacturer says require separate handling. List excluded items explicitly rather than assuming a program backup includes them.
Define recovery evidence. An offline project opening successfully proves something about editability; it does not prove replacement hardware will run the application. Have competent personnel plan an approved test on suitable spare equipment or a controlled test arrangement, with the required model, versions and functional checks documented.
Control revisions and access. Keep a dated manifest, protected copies and an accessible recovery procedure. Store credentials in the organisation’s approved credential system, not in the article, an unsecured project folder or a public maintenance note.
Worked example: one folder, three different results
Consider a hypothetical machine handover containing an HMI upload, an editable PLC project and a spreadsheet of setpoints. The HMI upload transfers successfully during an approved bench test, but its engineering software cannot expose editable screens. The PLC project opens offline, yet a required library is missing. The setpoint spreadsheet has no revision or capture date.
Record the HMI as having demonstrated transfer recovery under the tested conditions, with editable source unavailable. Record the PLC package as incomplete pending its library, and the setpoint list as unverified. Ask the OEM for the missing source and dependencies, then repeat the affected checks. Calling the whole folder “verified backup” would hide three materially different maintenance risks.
Common mistakes and the next maintenance action
Avoid treating file size, a recent timestamp or the presence of a download button as acceptance evidence. A compile without errors also does not establish correct I/O mapping, machine behaviour or current process settings. Keep a clear distinction between checks performed, results observed and checks still outstanding.
Do not test recovery by downloading to a production controller during normal operation. Machine-specific isolation, change control, installation and functional validation belong with competent people using the current manufacturer instructions. An ordinary PLC/HMI backup is not evidence that any safety function has been validated.
For the next archive review, choose one machine and produce a one-page manifest with two explicit outcomes for each application: “Can we restore it?” and “Can we edit it?” Attach the supporting evidence and name the unresolved dependencies. This makes a maintenance enquiry actionable before a failed controller turns a missing source project into an urgent stoppage.
Need help with your application?
ProSense Instruments - discuss controller selection and model-specific documentation: sales@prosenseinstruments.com.au or 1800 560 854.
ProSense Solutions - discuss complete monitoring and automation requirements: sales@prosense.com.au. ProSight Software - discuss software requirements: info@prosightsoftware.com. Device integration must be confirmed for your application.




Comments