Troubleshooting
Why HMI Variable Values Reset After a Project Transfer
Short answer
HMI values reset after a transfer because the transfer's Initialize settings requested it, the variables were never marked retentive, or the editor's newer version forced a firmware update that initializes all variable memory. Clear [Variable Value] and [Backup Memory] under Initialize, mark operator values retentive, and retrieve the program plus current values with Shift + X before you transfer. Only the firmware-update path wipes retentive values; capture them first, because no setting protects them through it.
On this page
- The three things that initialize your values
- Clear the Initialize check boxes on every transfer
- Mark the values that must survive as retentive
- Retrieve the program and the current values first
- When the editor is newer, the update wipes everything
- Worked example: five values through a same-version edit
- Verify the panel before you hand it back
- Questions asked
Values come back as zeros after a download because the transfer itself asked for initialization: the [Variable Value] check box under [Initialize], a variable nobody marked retentive, or a firmware update the editor forced on the panel. On a Pro-face panel edited in GP-Pro EX, the fix is three moves made before you write anything: clear [Variable Value] and [Backup Memory] in the transfer settings, mark the operator values [Retentive] in the symbol variable list, and retrieve the program plus current values from the panel as a recovery copy. One case defeats all three: when your editor version is newer than the panel's runtime, the required firmware update initializes every variable, retentive marks included, so capture the values first and plan to restore them.
The three things that initialize your values #
GP-Pro EX gives you three independent paths to the same symptom, and each has its own setting. Trace which one fired before you change anything:
- Transfer initialization. In the [Transfer Settings] dialog box, on the [Transfer Settings] tab, the [Initialize] group controls what a download wipes. With [Variable Value] selected, the transfer initializes variable values. This is the most common cause after a routine screen edit.
- A variable never marked retentive. Each variable carries its own [Retentive] setting in the symbol variable list. A variable without the mark has not been designated to hold its value, and the Initialize check boxes do not protect it on your behalf: the two settings do different jobs.
- A forced firmware update. When the editor version is newer than the runtime on the panel, the transfer requires a firmware update, and that update initializes the entire variable memory.
The first two you control with settings. The third you control with timing, because no setting protects values through an update.
Clear the Initialize check boxes on every transfer #
Open Project > Transfer Project > Transfer Settings. Under [Initialize], clear [Variable Value] and [Backup Memory]. With [Variable Value] selected, every download re-initializes the panel's variable values, and the retentive mark does not hold against this option; with both boxes cleared, a same-version transfer leaves the stored values in place.
Open that dialog on the machine doing the transfer, every time, rather than trusting the last state of the check boxes. The worked example below shows what one selected box costs.
Mark the values that must survive as retentive #
Open the symbol variable list, double-click the variable whose value operators depend on, and select [Retentive]. The setting is per variable; it does not spread to the rest of the list on its own, so go through every preset, batch target and alarm delay that must hold.
The mark lets a variable keep its stored value through a normal same-version transfer. It does not override the [Initialize] group or a firmware update. Treat it as the third leg of the set: Initialize boxes cleared for the transfer, retentive marks on the variables, retrieval copy for the values you cannot afford to re-key.
Retrieve the program and the current values first #
Before any transfer to a panel whose values matter, pull a copy off it. In the transfer window, press Shift + X: two extra buttons appear, and one of them retrieves the program and the current variable values from the panel. Save what it brings back as the recovery copy, then edit a separate working copy so the recovery file stays untouched.
If the project came off the panel, keep the file name it was last transferred under and overwrite the backup-folder copy under that same name. Re-transferring under a different name has been reported to wipe the panel's stored values, so treat the transferred name as part of the project. The retrieval route is the same one described in how to upload a program from an old touchscreen HMI; it reads the project and the values straight off the panel, no matter who transferred last.
When the editor is newer, the update wipes everything #
A GP-Pro EX version newer than the panel's runtime forces a firmware update as part of the transfer, and the update initializes all variables; the retentive marks do not help for that transfer. So the protection is entirely in what you do before it: make the Shift + X retrieval copy, write the current presets down or photograph the screens, transfer, then restore and check each value against your record.
The update also needs the correct firmware file for that panel, and the groundwork is the same as in getting the right firmware file for a legacy HMI panel.
Run the update while the machine cannot act on zeroed setpoints, and re-check alarm delays, speed limits and batch targets against your record before the line runs again.
Worked example: five values through a same-version edit #
A packaging line panel carries five operator values in internal variables, all marked [Retentive]: line speed 320 cartons/h, batch target 1250 cartons, and alarm delays of 5 s, 10 s and 30 s, so 1 + 1 + 3 = 5 stored values. The project was edited in GP-Pro EX 4.09 and the panel runs a 4.09 runtime, so no firmware step is involved.
Transfer with [Variable Value] and [Backup Memory] cleared: 5 values kept, 0 reset. After the download the screens still read 320, 1250, 5, 10 and 30. The same transfer with [Variable Value] selected: 0 kept, 5 reset, and all five fields read 0 despite the five retentive marks. Had the project come from a newer editor instead, the forced update initializes 5 of 5 regardless, and the retrieval copy made the week before is the only thing that puts the numbers back.
Verify the panel before you hand it back #
Run this before calling the transfer done:
- Compare every recorded value on screen with your pre-transfer record, not just the fields you edited.
- Confirm no firmware update ran mid-transfer; if one did, treat every internal variable as initialized and restore from your record.
- If one value reads 0, check that variable's [Retentive] mark, then the [Initialize] group, then whether an update ran, in that order, because each explains a different case.
- Save the working project over the backup-folder copy under the transferred name.
- If values are gone and no record was kept, re-enter them from the PLC registers the screens mirrored; controller-held data survives a panel wipe, internal variables do not.
The decisions, then: editor version matching the panel runtime — clear the two Initialize boxes, mark the presets retentive, transfer, and the values hold. Editor newer than the panel — nothing protects the values through the update, so retrieve and record first, transfer, restore, and verify every value before release.
Questions asked
Which variables survive a transfer without any settings at all?
Variables mapped to PLC addresses. The controller holds those values, so after any download the panel simply re-reads them from the register. The [Retentive] mark and the Initialize check boxes exist for internal variables, which live only in panel memory, and that is why operator presets stored internally are the ones that vanish. After a retrieved edit, still confirm the address mapping: a changed address reads the wrong register, which looks like a reset value but is not.
Does the retentive mark carry values across a power cycle too?
Yes, that is its main job. A variable without the mark starts from its initial value after a power loss; a marked variable keeps the last value written to it across power cycles and, with the Initialize check boxes cleared, across transfers. A forced firmware update overrides both, because the update initializes the whole variable memory including retentive marks.
The values are already wiped — what is the fastest recovery?
Re-enter them from your recorded setpoints, or read them back from the PLC registers the screens mirrored, since initialization is not reversible by transferring again. Once the values are back, close the path that wiped them: clear [Variable Value] and [Backup Memory] under Initialize, mark the presets retentive, and press Shift + X in the transfer window for a recovery copy before every future transfer.
Why did the panel initialize values on my transfer but not my colleague's?
The Initialize selection is stored with the project file, not with the panel. A project edited on another machine can arrive with [Variable Value] already selected, so the same panel and the same runtime wipe on one transfer and hold on the next. Open Project > Transfer Project > Transfer Settings on the machine doing the transfer and check the [Initialize] group rather than assuming yesterday's state still holds.
How do I find the project name currently loaded on the panel?
You cannot read the last transferred file name back out of the unit. Work from the newest file in your backup folder, and make it a rule that every transfer overwrites that backup under the same name. Renaming between retrieve and re-transfer has been reported to wipe the panel's stored values, so record the transferred name at every handover and treat a rename as a decision, not a tidy-up.