We are using CR1000 to measure the number of tips from a tipping bucket rain gauge. We have two systems; one of them is working appropriately. However, in the other system, scan is missed usually everyday at 8pm for a certain time (usually 20 mins-1 hour). The counters of tips in the program are cleared at the time and it will restart later. We are using the pulse counter and control port as the channel for switch closure.
The program is very simple:
Scan (TB_scanRate,mSec,1,0)
'Rain Gauge
PulseCount (Rain,1,1,2,0,1.0,0) 'P1 = Rain Gauge
Rain_total=Rain_total+Rain
If Rain>0 then
CallTable tblRain
Endif
NextScan
Here is part of the output of the table, at 8:10pm, the program stopped scanning for about 30 minutes and it restarted at 8:37pm.
Time total tips Accumulated counter time between last scan
04:42.4 72551 540
06:02.6 72552 541 01:20.2
2009-4-8 20:08 72553 542 02:32.4
09:04.4 72554 543 00:29.4
2009-4-8 20:10 72555 544 01:39.6
37:21.6 72556 1 26:37.6
39:04.6 72557 2 01:43.0
40:25.2 72558 3 01:20.6
Any ideas about this problem? Thanks
If the variable rain is being set to zero without human intervention when you see this problem it seems likely the logger is being reset entirely and the program recompiling, rather than it skipping scans (although it would be good to know the scan rate).
This could happen due to a bad battery or connection to it, some external transient (lightning), an operating system crash or a hardware fault.
Can you please check the status table of the datalogger, to see if it reports and Watchdog errors, low battery events, skipped scans or any similar errors. Also please report the logger operating system version.