Author Topic: VPLive v. 1.1.6 released  (Read 3395 times)

0 Members and 1 Guest are viewing this topic.

Offline tinplate

  • Moderator
  • Forecaster
  • *****
  • Posts: 368
    • http://www.softwx.com/products.html
VPLive v. 1.1.6 released
« on: January 07, 2007, 01:44:31 AM »
VPLive v. 1.1.6 is now available. http://www.softwx.com/weather/vplive.html

This update addresses the recent changes in the servers used to upload CWOP data.
changes:
Improved error detection on APRS/CWOP sends.
Changed the default servers and ports.

Steve

Offline tinplate

  • Moderator
  • Forecaster
  • *****
  • Posts: 368
    • http://www.softwx.com/products.html
Re: VPLive v. 1.1.6 released
« Reply #1 on: January 07, 2007, 02:15:38 AM »
Darn!!
If you are one of the two people that have already downloaded the new version, please download again. I transposed a digit in the new port. The version on the website now has this fixed.

Steve

Offline Mark / Ohio

  • Live from Mars!
  • Forecaster
  • *****
  • Posts: 2511
    • Fairfield County Weather
Re: VPLive v. 1.1.6 released
« Reply #2 on: January 07, 2007, 02:23:02 AM »
Thanks Steve.   8)

I have it running with "Automatic Server Selection" checked again now like I originally used before today's server owner brewhah.   :roll:

http://www.findu.com/cgi-bin/wxpage.cgi?call=CW3403

The charts look a little funny at the moment anyway.  I'm finally on DSL and switched from a 1 hour to a 5 minute update late Thursday night.
Mark 
2002 Davis VP I Wireless, WeatherLink (Serial), GRLevel3, VirtualVP, StartWatch, Weather Display, Windows 10


Offline W3DRM

  • Forecaster
  • *****
  • Posts: 3360
    • Emmett Weather
Re: VPLive v. 1.1.6 released
« Reply #3 on: January 07, 2007, 02:30:50 AM »
Hmmm, I did download and install it as soon as I saw your post and it seemed to work okay. I saw the data loading (white light lit) and then the green light indicating the upload was successful. Have done another download and install as you suggested. The installation went smoothly and I have another green APRS light so I'm assuming all is well. I may have d/l'd after you made the correction though.

Anyway, thanks again for the quick response and update to a really gREAT software package. My problems with VP2 Barometer readings have been non existant since installing VPLive. At 4801' altitude that was really killing me with VWS and the VWaprs routine.
Don - W3DRM - Emmett, Idaho --- Blitzortung ID: 808 --- FlightRadar24 ID: F-KBOI7
Davis Wireless VP2, WD 10.37s150,
StartWatch, VirtualVP, VPLive, Win10 Pro
--- Logitech HD Pro C920 webcam (off-line)
--- RIPE Atlas Probe - 32849

Offline tinplate

  • Moderator
  • Forecaster
  • *****
  • Posts: 368
    • http://www.softwx.com/products.html
Re: VPLive v. 1.1.6 released
« Reply #4 on: January 07, 2007, 09:14:57 AM »
Yes, the first version I put up would still work even though it had the wrong port. The reason is that now the VPLive error detection for bad connections works. First VPLive tries to send to rotate.aprs.net:14580, then if that fails it tries rotate.aprs.net:23 (this covers the case where some people's firewall blocks high numbered ports), and if that fails, it tries several of the tier 2 servers on port 14580.

So, even though I had the wrong port set (I put in 14850 instead of 14580), the program would use port 23 after the failure of port 14850.

14580 is the preferred port now for send only. Port 23 still works, but the core servers send back a bunch of data in response (which is unneeded and ignored by weather programs sending CWOP data), so it wastes some bandwidth.

I may change the order of servers VPLive tries in the future after this core server/tier 2 server debate gets resolved. But for now, the way I have it set up should be fairly reliable since it will fallback to tier 2 servers if the core servers get swamped and begin refusing some connections. The tier 2 servers are, for the time being back accepting weather data, but they've switched from using port 23 to using port 14580. They also may drop supporting the rotate.aprs2.net address, which is why I try specific individual servers in the tier 2 fallback code.

Steve

 

anything