Hello,

1.) Configuration Studio 2.7.10319
2.) Display - PV350/PV380

Recently I had loaded a previously created configuration into a PV350 that contained many non-volatile variables. I noticed that variable values were not being saved across power cycles. The functionality in this particular configuration had worked fine the last time it was loaded. All variables of interest are set to "SurvivesPowerCycle" and I perform Database Save upon variable change and a Database Restore at Power on. I suspected that the configuration conversion to the latest version of Configuration Studio was the culprit. So I created a new simple Configuration that increments a variable every second, Database Saved every 5 seconds, and Database Restored at Power on. The variable was not either saved and/or restored properly because it was reset to the default value at Power on. I loaded the same configuration into a PV380 and the variable save/restore functioned correctly. I then loaded my original configuration into a PV380 and all variable values were stored and retrieved correctly.

We currently use the non-volatile function extensively with our customer implementations. So until this issue is resolved, we are unable to update any PV350s in the field.

I have attached my simple configuration for reference.

Dan Sellers

Hi Dan,

Have you left something out of your sample configuration? As far as I can tell, your configuration does save the variable to persist through a power cycle. The issue I see is that the display gauge is set to a maximum value of 100, so that no matter what the value is, if it is greater than 100, 100 is what will be displayed. When I change the maximum to a greater value, it still works. What have I missed?

I could not open this configuration with the 2.7.10319 as you have indicated. It appears to have been built with the 2.7.10439 and that is what I am testing with. If you were importing from a 2.6 version in to the 2.7.10319, I think there was an issue with persistant variables. This issue should have been fixed in 2.7.10419 and may be why it works properly in 2.7.10439.

Please let me know if I have missed something in trying to recreate the problem. It sounds like something that needs immediate attention to make PowerVision a reliable tool.

Sara,

I am running version 2.7.10439. Copy/paste error.

For the sake of this test, the value maxing out at 100 doesn't really matter. If I load the configuration into a PV350, the counter will always start counting from 0 (default value) at power on regardless of the value at the previous power down. If I load the same configuration into a PV380, the counter variable will power up with the last value saved before the previous power down. I've confirmed this behavior with multiple configurations. It seems to be a 350 vs. 380 issue.

Thanks,
Dan

So, I've got your configuration on a PV350. I've power cycled several times. I haven't had it go back to 0.

I'm trying to come up with factors that might cause the problem so that we can get to the root cause of your problem. I will need more information. I apologize for asking basic questions, but I need to eliminate some of the simple things.

Have you verified that the converted configuration still has the variables selected to persist through a power cycle?

What was the PowerVision Configuration Studio version of the old version? You are importing it to the 2.7.10439?

What is the bootloader version on the PV350s?

When you updated the PV350, did you do a full install or just a configuration update?

Thank you for your patience and your help to solve this problem. I'm sorry for the inconvenience.

Sara,

Your inability to reproduce the problem led me to try another PV350 I have in the office. The variable persistence across power cycles functions as expected. My initial PV350 must have suffered a hardware failure somewhere in the EEPROM circuitry.

Thanks for your help,
Dan

You might want to check the bootloader on the PV350 that had the problem. There was a problem with a previous version of the bootloaders.

Glad to help.

Unfortunately both displays have boot 2.7.10112.

Dan