I am finding that despite the archive interval within Weather Link 5.9.2 being set to 10 minutes, it is only uploading the 10 minute intervals after one hour instead of every 10 minutes. It is also not logging data for the first 20 minutes of an hour. It's first entry is always 20 minutes past the hour and then 30,40,50 and 1 hour. The data for thes periods only appear after 60 minutes. The program, usb device including drivers have been uninstalled and reinstalled without any problems. The console has been restarted and archive data deleted. However the problem persists. How can I solve this problem?

Attached is a copy of some recent Weather Link records. note the missing 10 minutes past the hour entries.

That filename and file format doesn't look quite like a standard WL
file - have you just renamed it or are you deriving it from one of the
standard files, in which case the problem may well be your derivation
process. Is some other CPU-hogging process running at around 10 mins
past the hour? Can you try a different offset time for this process?

But first place to check would be to see if the main WL archive files
are being correctly saved or not. What do you see if you Browse the
main WL database - are the HH:10 records there or not?

But there also looks (as far as one can judge from such a small data
sample) as if there's something odd about the station configuration.
Packet reception is 100% on the hour, but only around 40% at HH:20.
Maybe it dropped to zero at HH:10? If that's a consistent pattern then
it may be that you have some cycling interference issue or maybe the
console is being asked to do too many other things in the HH:00 to HH:
20 timeframe.

John Dann
www.weatherstations.co.uk

My Davis AWS has twice had the same problem that you mention and the only
way I could cure the issue was to take the backup battery out of the unit
and turn off the power supply, leave it for a minute then turn the power
back on.

Of course you then have to set it all up again but it did fix the problem.
______________________
Nick
Otter Valley, Devon
83 m amsl
http:\\www.ottervalley.co.uk

On Dec 28, 9:18*am, "Nick Gardner"
wrote:
My Davis AWS has twice had the same problem that you mention and the only
way I could cure the issue was to take the backup battery out of the unit
and turn off the power supply, leave it for a minute then turn the power
back on.

You need to do this whenever you want to 'reboot' a Davis Vantage
console - you need to remove _all_ power and leave for at least a
minute or two before repowering. This procedure is always worth trying
to you encounter any operating glitches - it only takes a couple of
minutes and so you'll lose just a negligible amount of data. Rebooting
the console will not clear the logger - all the logged data should
still be there, although nonetheless it's considered good practice to
download the logger if you can (ie if the problem isn't a stuck
download) before performing the reboot.


Of course you then have to set it all up again but it did fix the problem..

You should not need to re-enter any information - all the set-up data
is stored in EEPROM ('permanent') memory. All that should be necessary
on a non-Envoy console when rebooting is to remember to exit Set-up
mode. (The Envoy does this automatically.)

John Dann
www.weatherstations.co.uk