Upload an HMI panel project to your PC

Upload reads from the panel, download writes to it

Upload and download name opposite directions, and mixing them up is how running panels get erased. Upload moves the project file from the HMI panel to the PC. Download sends a project from the PC into the panel and replaces the configuration it runs. For recovery you want upload.

The two commands sit close together in the vendor software, in many packages as a pair of toolbar icons and in others under the Project menu. Confirm the direction from the label or tooltip before you select anything. If a download dialog appears during a recovery job, cancel it, recheck the icon and start again.

The panel is the right source because the machine runs whatever is inside it. A file on a shared drive may be older, belong to a different panel or carry changes nobody documented. The upload returns the configuration the panel is actually running, which makes it the reference copy for that machine.

What you need

• A PC with the vendor's project software installed, at a version that supports your panel family. The panel manual or the vendor's support pages list that pairing.
• A connection that reaches the panel: Ethernet if the panel has a port, otherwise the serial link with the cable and communication settings from the panel's documentation.
• An empty folder on the PC for the retrieved file, so the transfer cannot overwrite an existing copy.
• The panel's identity: line, machine and panel position. It goes into the filename.
• A window agreed with operations if the software has to take the panel out of run mode for the transfer. The same coordination that keeps PLC schedules running when an HMI panel is offline applies here.

Run the upload

1. Write down the panel identity and today's date. Both go into the filename in step 5.
2. Open the project software and locate the upload and download commands. Read the labels and confirm the direction. Keep the download command out of play for this job.
3. Connect the PC to the panel and let the software establish communication. Serial settings such as port, baud rate and station number come from the panel's documentation.
4. Start the upload and let it run. Do not interrupt the transfer, unplug the cable or close the software partway through.
5. Save the retrieved project in the empty folder under a new name that carries the machine, the panel number and the date, for example pressline1-panel2-2026-03-18. Write the date as year, month, day so the backups sort in order. Never save over the last known PC copy.
6. Set the saved file read-only so the master cannot be edited by accident, and make any future edits on a copy. If a read-only flag ever blocks a backup from opening, clearing the read-only flag on a project backup walks through that.

Example: timing a 2 MB upload over a 9600 baud serial link

The inputs: the panel has no Ethernet port, so the transfer runs over serial at 9600 baud with 8 data bits, no parity and 1 stop bit, the classic default for HMI serial links; the panel's documentation gives the real setting. The project is 2 MB, a typical size for a mid-size machine project and an illustrative figure here; your software reports the true size after retrieval. The conversion constants are fixed: a byte takes 10 bits on a serial line (1 start bit, 8 data bits, 1 stop bit) and 1 MB is 1,048,576 bytes.

The rule in words: transfer time in seconds equals project size in bytes divided by payload bytes per second. The payload in bytes per second is the baud rate divided by the bits each byte needs.

The arithmetic:

• 2 MB = 2 × 1,048,576 = 2,097,152 bytes
• 9600 baud ÷ 10 bits per byte = 960 bytes per second
• 2,097,152 bytes ÷ 960 bytes per second ≈ 2185 seconds
• 2185 seconds ÷ 60 ≈ 36.4, so the raw transfer needs about 36 minutes

Result: about 36 minutes as a floor, because per-block handshakes between the software and the panel add time on top.

Decision: let a serial upload run for 40 minutes before you treat it as hung; at the 10 minute mark a 2 MB transfer is only about a quarter done (600 seconds × 960 bytes per second = 576,000 bytes, roughly 27% of the file). When the panel also has an Ethernet port, use it: at 100 Mbit/s with half the line realistically free, 2,097,152 bytes ÷ 6,250,000 bytes per second ≈ 0.34 seconds, so the same project arrives in seconds even with handshakes. Ethernet whenever the panel offers it; serial otherwise, started early and left alone.

Check the copy before you call it a master

• Close the software and reopen the saved file from disk. It must load with no errors.
• Open the screen list and then open each screen that matters on that machine, the ones operators touch every shift, and confirm the objects and tag addresses came across.
• Record the upload in the machine's maintenance note: filename, date and the panel it came from.
• A completed transfer alone is not a checked backup. The reopening and the screen inspection turn the retrieved file into a master.

This master is also what lets you rebuild quickly if a panel loses its project after a power cycle; that failure has its own checklist, and a good master file is the part you control in advance.

Before anything goes back to a panel

Restore is a separate job from recovery, and it runs in the download direction. Compare the candidate project against the master first, confirm the machine is ready for the change, and check the panel's software revision before the transfer, the way checking the HMI firmware revision before a project transfer lays out. The read-only master stays untouched no matter what the restore does.

Recommendation: Pull an upload master from every HMI panel on the line while its project still runs, before the next project change rather than after a failure. Name the file with the machine, the panel number and the year-month-day date, set it read-only, reopen it once, and record it. Use the Ethernet port when the panel has one; budget the full serial time when it does not.

Questions