If it wasn't for that one port allowing me to connect to the station, I wouldn't have even been able to retrieve the past several weeks' worth of data from the datalogger. Two laptops, five USB ports, and only one was able to connect to my station! ALL of the USB ports on both laptops work perfectly I tested the two USB flash drives I had with me on all of the ports, and both drives worked on all of the ports. I tried plugging the USB logger into the first port - and WeatherLink could NOT find the station! I then tried the second port, and WeatherLink finally found the station. Luckily, I had my main laptop with me today (which I also installed WeatherLink on back in September, just in case the laptop at the remote site were to crap out), which has two USB ports. I tried restarting the computer a couple times and did the above process again - no dice. I tried both of the other two USB ports on the laptop, and, again - neither VirtualVP nor WeatherLink could find the station, despite the fact that the USB logger was securely plugged in on both ends, and despite the fact that the exact setup I was using had worked flawlessly for an entire month! I decided to open WeatherLink and used its AutoDetect feature to find the virtual COM port in case the computer had changed it for some reason, but WeatherLink also could not find it. Yet when I hit "connect," VirtualVP could not find the station on the specified virtual COM port. The USB logger was still plugged into the same port it always had been, and I had changed absolutely nothing since I was last at the house on 10/30 (when everything was working fine, and had been for an entire month). So today, back on-site, I put the house power back on, turned on the laptop, and opened VirtualVP. So when I got back on-site today, I noticed the power was off and the laptop battery, of course, had long since died - this all happened on 10/30, coinciding with my records cutting off that day.
This year, we left a note on the circuit board specifically telling the plumber to keep the power on (for the 24/7 dedicated laptop), but it seems that he ignored the note. I found out today that the power was shut off in the house later in the day on 10/30 (after I left) by the plumber, who blows out the pipes each year when the house is closed for the winter and is usually supposed to turn the power to the house off as well. All ran perfectly, 24/7 every day, right through the last time I visited the site in October (10/30) - but once I got back on-site for the first time again today, I noticed that the laptop was off I turned it back on to find that records cut off on 10/30. I set it up with VirtualVP and kept Cumulus, WxSolution, and WeatherLink running with it.
#Vantage vue usb logger software#
Eventually, despite the fact that I changed nothing, both pieces of software did find the station, and were able to connect to it. When I first set up the software, I had trouble getting it (WeatherLink first, then VirtualVP) to recognize the station (plugged in via the USB logger) - both programs couldn't even find the station at first. I installed the Vue on 9/16 and the on-site laptop with all of the software on 9/30.
#Vantage vue usb logger archive#
I also use WeatherLink with a 30-minute archive interval to access up to 53 days of backup data in the logger in case anything goes wrong with the laptop. I set up a laptop at the site in order to run VirtualVP, Cumulus, and WxSolution 24/7 in real time. I have a Vantage Vue installed at a remote location (see this thread for details: ) that I'll only be accessing about once per month from November through March, and more frequently from April through October.
I noticed there's a thread similar to this currently active in the forum, though my issue appears to be for totally different reasons than the other person's Vue/USB logger communications problem - so I'm starting this thread instead.
0 kommentar(er)
