This week I am trialling running WeatherLink 5.7.1 plus WD 10.37f using Virtual VP hooked to a Weather Envoy / Logger (original VP system). VVP ver 1.1.4.22 and N8VBvCOM. Silicone Labs driver CP210x ver 4.40.1.0. Win XP Pro SP 2.
At two apparently random times (5 AM Tuesday, then Midday Thursday) WeatherLink has stopped reading data from the Envoy/Logger. WD is completely unaffected.
The WeatherLink log shows no errors, just that logger downloads and website uploads have stopped.
WeatherLink is still running, but constantly using 47% CPU (about 10% max is normal during uploads, 0% at idle). I’ve had WL running as a service (under FireDaemon), so it was impossible to tell if it was ‘not responding’ or exactly what it was trying to do. Restarting WeatherLink resolved the issue for a time.
Virtual VP still showed a green light for WeatherLink, but ‘last heard’ and ‘last sent’ as 5 hours ago (or whatever time). The log for V VP only shows entries like:
31/08/2007 06:06:06:846 PreCondition - TVirtualVp.ReceiveLoop: PreCondition 1 failed
Which seems to coincide with WD synchronising the clocks each morning; and:
31/08/2007 09:00:33:846 Warning - VpConsole: Far too long since last loop = 8.422, last command= Get Live Sensor Data
Which happen from time to time, but don’t ever coincide with WeatherLink “hanging”.
Without V VP, WeatherLink has worked flawlessly for a couple of years (apart from occasionally not recognising the USB logger after a reboot).
I have had V VP set to “Restart Davis USB Data Logger” all along (so including when these “hangs” occurred).
I have since set WeatherLink to ‘interact with desktop’ (still as a service) so I can hopefully see more of what what might be going on if it happens again.
Any other suggestions as to where to look or what might be happening?
Thanks for your help.