It’s been working no problem since last June. Now, when WD comes up, it doesn’t connect the first time. I have to unload and reload, sometimes twice to get it to connect. Once it connects, it’s good.
Running version: v10.37Q-(b41)
System OS: XP SP3
Dell Computer
VVP version: 1.2.1.1
This actually started happening with build 38.
Steve,
Similar issues here and looks like we have very similar configurations. I upgraded from 10.37Pb15 last month and nothing but issues. Brain has looked into and resolved most. The others I figured out myself, or thought both forums.
I noticed over the weekend a FLAT LINE (no data change) that started on the 16th. It looks like VirturalVP was sending o.k. and three weather programs (WeatherLink, VWS & VPLive) were receiving except for WD. This issue caused my CWOP stats to go south and even WUnder took me off-line due to bad data. I had another issue on the 15th where 10.37Q41 just stopped updating all together; however VirturalVP shows no issues with WD. I tried changing WD from Serial-USB to IP; however after an hour or so a few times it stopped getting updates from VirturalVP so I went back to old config. I’m now using VWS to update WUnder and I’m thinking of changing CWOP to one of the other programs also. I spent a ton of time deleting all the bad data on WUnder (which there was a bulk delete) and re-sent all data for the 17th (still working on the 15th).
10.37Qb41 looks like it was re-compiled on 4/14 based on date/timestamp so I re-installed it Sunday. I also updated VirturalVP to 1.2.5, even though the only issue was with WD. I’ve been baby sitting my dedicated weather computer for 3 days now and all is still good; however I’m VERY frustrated in upgrading from a very stable (other than some memory leaks) version of WD (10.27Pb15) and I’m really thinking of going back to it. I can’t remember why I upgraded in the first place as I’m not a believer of keep fixing things (new versions) until it BREAKS!!!
I’ve had this configuration since Jan '10, so I know it’s not VirturalVP or anything else except WD
WDisplay has been up for 6 1/2 days without any “Flat Lines” or loss of communication from VirtualVP. XP PC has been up for 7 days without a reboot. StartWatch only shows one kill/restart of VWS during the week (typical).
Maybe this new configuration with re-complied 10.37Qb41 and VirturalVP to 1.2.5 might be the ticket.
Keeping my fingers and toes crossed.
Using weatherlinkIP
I have to reboot to connect Only when I update WD to latest version. Otherwise I have WD start 1 minute after VVP, always connects for me.
Startwatch starts VVP 1min after it loads, then 1 min later WD starts, then 5 min later WxSim, etc
WinXP on dedicated netbook.
WDisplay has now been up for a month (WOW) without any “Flat Lines” or loss of communication from VirtualVP. My dedicated Weather Station PC running Windows XP SP3 hasn’t needed a restart for 47 days (Double WOW!!!). StartWatch only shows kill/restart(s) of VWS (typical) which I’m thinking of removing it completely; however I use VWS to send data to WUnder due to an issue I was having with a previous build of WD 10.37Q.
From my system status page:
This new configuration with a re-complied version of WD 10.37Qb41 and VirturalVP upgrade to v1.2.5 rocks solid!!!
:greenjumpers:
Brian (Windy), I hope your monitoring this tread 
Brian (Windy), I hope your monitoring this treadwhy do you think I would not be? strange
however I use VWS to send data to WUnder due to an issue I was having with a previous build of WD 10.37Q.not enough information provided to be able to offer any help there
you should find that build 46 or later of WD works even better overall (with the new buffered ini file)
Because a lot of us that have Davis units use WD use Virtual VP
When the PC finally needs a re-boot I’ll try the latest build out.
however I use VWS to send data to WUnder due to an issue I was having with a previous build of WD 10.37Q.and that issue is?
Windy,
As stated in my 1st reply this tread (summarized as):
Upgrade from WD v10.37Pb15 to V10.37Qb?? caused FLAT LINE (no data change). VirturalVP was sending o.k. and three weather programs (WeatherLink, VWS & VPLive) were receiving o.k. except for WD. This issue caused my CWOP stats to go south, and WUnder took me off-line due to bad data (FLAT LINE, no data change).
This is the reason I starting using VWS to update WUnder. I spent a ton of time deleting all the bad data on WUnder and re-senting data for the that period of time caused by the FLAT LINE.
Since I installed your re-compiled v10.37Qb41 (4/14/11 based on date/timestamp), and updated VirturalVP to 1.2.5 I haven’t seen any FLAT LINE issues.
Now that I’ve seen such a good WD uptime, with no issues it’s time for me to think once again about using WD for WUnder data sending and possibly retiring VWS once and for all.