We have about 100 units running in the field by differente customres with the same type of code template. The code has been stable for abiut 3 years now. Today a customer called me stating his program was stopping do to low battery voltage condition, this started happening a couple of weeks ago but he was able to start the program and it would run for a while. The last few days it would not start at all. Today he swapped a battery out eventhough the original was 13 plus volts and got same results with new battery. We are recording the event to an array which indicates low battery.
The numeric screen label sometimes indicates negative voltage, INF or some volatge below 11 volts . I then had the customer open the case and measure several points on the panel and they all indicated the same as read on the battery posts, slightly over 13 volts.
I then had him add int_temp to the numeric screen and it reported +4C, it should have been around 25 or so !
When he open the case the humidity indicator was all blue, so there was no moisture involved to cause the bad readings, I'm certain of that.
Cr10x has the latest OS, the program was reloaded twice just in case, all other functions in manual mode work. Any ideas ?
Thank you in advance.
fred
Did you check the internal battery? We had to change a lot of ours out recently with our old CR10x's.
You need to do a "*B" on the keypad, then "A" to advance to I believe the seventh or eight reading for the internal battery voltage. It should be around 3.2v for a newer battery.
I believe errors will happen if this voltage is under 2.8v (again can't remember the exact voltage).
It is a button type battery internal to the unit.
HTH
To close this one off, it turnned out to be losse hardware! After removing the protective cr10x canister we found the cr10x panel latch wrattling around inside and the cr10x module barely connected to its panel. I guess the thumb screw came lose! Inserted it back in and tightened the latch,it worked first time.