Description from a user:
The PV750 they have locked up from time to time, with or without connecting to CANbus. We don’t know whether it is a hardware related issue or a software one. They couldn’t switch screen and the data on the screen is not updating when the lock up occurred. They felt that it would lock up when it stays on one screen for a while, say, 5 minutes.
My config causes the unit to lock up
- jpurdum
- Enovation Controls Development
- Posts: 153
- Joined: Mon Jun 21, 2010 11:19 am
- jpurdum
- Enovation Controls Development
- Posts: 153
- Joined: Mon Jun 21, 2010 11:19 am
Re: My config causes the unit to lock up
ANSWER
Issue:
Configuration Tool: 2.0.20115
PV750 App: 2.0.7
The issue in this case was caused by a bug in the 2.0 release where the configuration tool allows the user to enter the rate at which a user defined variable is saved to non-volatile memory in seconds (as intended), but the PV750 reads that same value as milliseconds. This causes the PV750 to become overloaded if the number is too small. In this particular case, it was set to one, which was causing it to try and save to it's flash filesystem every 1 ms. See the attached graphic
Workaround in current release:
If you need to save a variable periodically, enter the number as milliseconds. So, if you need to save once per second (more often than once per second is not currently recommended), enter 1000 for this value.
Info on release with fix:
This issue is resolved in the 2.0 Update 1 release (Configuration Tool 2.0.xxxxx, App 2.0.10) released in July, 2010.
Issue:
Configuration Tool: 2.0.20115
PV750 App: 2.0.7
The issue in this case was caused by a bug in the 2.0 release where the configuration tool allows the user to enter the rate at which a user defined variable is saved to non-volatile memory in seconds (as intended), but the PV750 reads that same value as milliseconds. This causes the PV750 to become overloaded if the number is too small. In this particular case, it was set to one, which was causing it to try and save to it's flash filesystem every 1 ms. See the attached graphic
- VariableSavePeriod.JPG (53.33 KiB) Viewed 146 times
If you need to save a variable periodically, enter the number as milliseconds. So, if you need to save once per second (more often than once per second is not currently recommended), enter 1000 for this value.
Info on release with fix:
This issue is resolved in the 2.0 Update 1 release (Configuration Tool 2.0.xxxxx, App 2.0.10) released in July, 2010.