A failing HMI PC running Automa Super-Flash and communicating with an Allen-Bradley SLC 5/03 requires more than a disk copy. Select the recovery method from the installed Super-Flash version, operating-system compatibility, communication interface, and runtime-license hardware. Record these dependencies before changing the working PC.
Identify the Existing HMI Dependencies
Confirm whether “Automa SCADA” means Super-Flash and record its installed version. Also identify the operating system, the folder containing the application, the communication path to the SLC 5/03, and whether the runtime license uses a hardware key. The evidence does not identify the current operating system, Super-Flash version, communication interface, or required credentials, so none should be assumed.
Distinguish a hardware runtime key from software credentials. If a hardware key is present, the replacement PC requires both the key and its compatible driver. Confirm driver and licensing requirements through official Automa support before relying on a copied application.
Compare the Replacement Strategies
| Strategy | Supported use | Primary constraint |
|---|---|---|
| Full disk image | Recovery to genuinely compatible hardware | PC hardware changes quickly, so an image is not assured to start or retain device compatibility on a different platform. |
| Copy the application folder | Moving the Super-Flash application to another PC | The same operating system offers the most direct compatibility path; operation on a newer operating system is not guaranteed. |
| Virtual machine image | Preserving the existing software environment on newer host hardware | This is most practical when SLC communication uses LAN. Serial communication and USB-to-RS232 conversion introduce additional interface and driver dependencies. |
| Upgrade the project | Installing on a current PC and operating system | Project conversion and runtime compatibility must be confirmed for the installed and target Super-Flash versions. |
Prepare the Replacement Without Disturbing Production
- Record the Super-Flash version, operating system, application-folder location, and SLC 5/03 communication method.
- Check for a runtime hardware key and preserve its driver installer and licensing information.
- Classify the spare PC as either equivalent to the existing platform or a newer platform requiring compatibility validation.
- Create the selected backup artifact: a full image for compatible recovery hardware, an application-folder copy for software migration, or a virtual-machine image when the communication architecture supports it.
- Keep the operating source PC unchanged until the replacement has passed an offline startup and communication test.
Verify Before Accepting the Backup
Start the copied or virtualized environment on the target PC and confirm that Super-Flash opens the intended application, recognizes any runtime hardware key, and establishes the configured connection to the SLC 5/03. A successful image creation or folder copy alone does not prove recoverability.
If the target uses a newer operating system or a USB-to-RS232 converter, treat successful operation as an item to test rather than an assumed capability. If compatibility fails, evaluate upgrading the project to a Super-Flash version supported by the target PC.
FAQ
Can I restore a Super-Flash HMI disk image to another PC?
Only after confirming hardware and driver compatibility. A full image is not guaranteed to start correctly on a different PC because storage, chipset, display, licensing, and communication interfaces may differ.
Can I move a Super-Flash project by copying its folder?
In principle, copy the folder containing the application and install the required Super-Flash runtime environment. Using the same operating system reduces compatibility risk; a newer operating system requires validation.
What must I check before replacing an SLC 5/03 HMI PC?
Record the Super-Flash version, operating system, application folder, PLC communication interface, and runtime hardware-key requirements. Then test application startup, license recognition, and SLC 5/03 communication on the replacement.