Okay, VWS/WD gurus, what could be causing this to happen? It used to work just fine before I installed Weather Display in preparation for switching from VWS to WD. Now, every night - without fail - VWS simply stops inputting data but it still continues to run all of the other routines and updating webfiles and my webcam which uses Image Salsa.
I don't like having to get up at midnight every night just to restart VWS and need to figure this out soon. I am now using WD for all of my CWOP/APRS & WU uploads.
I suspect I have something interacting between VWS and WD and possibly WeatherLink that is causing it to stop but so far, I haven't found it.
My setup is as follows:
- HP Laptop running Win7 Ultimate - lots of memory and multi-core i7 CPU.
- Software:
- StartWatch
- VVP
- VPLive
- VWS
- WeatherLink
- ImageSalsa
- WD
- VVP handles
- VPLive, VWS, WL & WD via TCP/IP connections
A few seconds after midnight, I see the VVP Activity line for VWS change to "Sent response to Wake Up Console" but, it never changes after that. The only way to get it running again is to shut-down StartWatch and then restart it once all of the processes have stopped. Restarting VWS by itself does not work either. One more thing - WD and the other programs just keep running nicely and don't seem to be impacted by this behavior of VWS except that those relying on VWS data updates show stale data elements.