Topic: New beta Version: 14.00p100

[mmorris]

   1.  Date: Updated September 9, 2009
   2. Version: 14.00p100
   3. Download Location: http://site.ambientweatherstore.com/vws/beta/vws_install.exe


P100. Supports the new Vantage Vue by Davis Instruments.

[TorH]

You get the p100 as the latest realese on ambient's site, i upgraded from there two days ago 

[gsownsby]

VWS V14 p100 w LaCrosse 2310 TWC

Based on a lot of hair-pulling and lots of phone discussions with Ed at AmbientWeather, there appears to be a bug in the Total Rain/Year Rain calculations and the Rainfall Panel.  Ed has identified the problem and says it will be corrected in the next update.

The problem popped up after my LaCrosse unit lost power and the batteries became exhausted.  Data gathering stopped and I was attempting to adjust VWS to display the correct month-to-date readings for rainfall.  Data that was manually entered into the VWS Rainfall Panel wouldn't take or took but after changes were made, data displayed on the Rainfall Panel reverted to previous values.

Since some rainfall data is directly gathered/measured but other data is based on calculations, rainfall can be a testy adjustment to make.  I'm looking forward to Ed's update.

[gsownsby]

VWS V14 p100 - LaCrosse 2310 TWC

After upgrading to this beta version, VWS will no longer start automatically at Windows Vista startup (PC reboot).

The AmbientWeather Wiki info on this topic doesn't match what I see in my PC as far as startup location.  I located the Vista startup folder location, placed a VWS shortcut there but that doesn't work.

I also unchecked "run as administrator" on VWS but no joy there either.

Generally, I think it is Windows Vista User Account Control that is blocking startup.  Turning UAC off isn't recommended by Microsoft and I have many other programs that auto-start without problems with UAC turned on.  What is it with VWS??

Any ideas as to how to get VWS to auto-start when my PC boots up?

Thank you.

[Anthony]

If it was auto starting before. It should be auto starting now. Are you sure you installed the upgrade into the same folder that vws is currently installed in. In my case it is C:\vws. By default vws installs in the rood directory & not in the program file directory like mose other programs.

[Weather Display]

try putting a short cut to it in the windows start up folder
but if UAC needs you to confirm to run the program, then that is a problem (happens when a program does not have a certificate from Microsoft (alot of niche programs wont due to cost limitations)
I think

[gsownsby]

Anthony,

That's what I thought too but it doesn't.  I did find a solution though.  See http://www.wxforum.net/index.php?topic=5618

Thanks for your reply.

[DaculaWeather]

Been running p100 for a couple of weeks now, it seems very stable. It's been up today for about 18 hours and using 83Mb so far. It started at 35mb.

[DaculaWeather]

I'm impressed with this version, good job!

Up almost 30 hours now:

Page file usage has been between 81-89 MB
Code and data in memory has been between 17-36 MB and is currently 17 MB

But the memory leak, at least in my case, doesn't seem to be there.

[Mark / Ohio]

I went for p100 and received p101 which is not posted yet.  Ed's slowly sneaking another update out.   

[stevebrtx]

On the 19th brought a new OS200 online, on that day I recorded a 687mph gust, being a new piece of hardware I didn't think much about it. On the 20th again a high spike. I was/am also getting multiple days in the daysum.txt. On the 23rd I upgraded to 101p and again yesterday I got the 687mph spike, each time about 10am and nothing is happening at that time of day. Also getting random bin files in Summary like 2026.bin and 2026_00_35.bin.

Because 2 of the mph spikes hit before the VWS upgrade they're apparently hardware related, but the multiple daysum entries look more like VWS, any suggestions?

Thanks

[Weather Display]

maybe you could test if other software for the wmr200 also gets the supposedly hardware caused windspikes and in correct date data?
e.g try running the software that comes with the station as well (should be able to run it at the same time)

[stevebrtx]

I hope I found a solution in the VWS "manual" sec 6.6 on Ranges. I had left it at 0-999 mph default as the old OS100 never had a problem, but it says "some stations may give spurious readings" and to eliminate that problem set the range to a realistic value and VWS will ignore anything outside that range, so it's now set at 0-50mph, we'll see if that eliminates the problem. I've also set a graph on the VWS console to show wind speed and autorange so it's easy to glance and see if the range has changed.

I'll watch the daysum.txt file next to see if the changes also result in only a single reading per day. So far today there is no reading for the 27th. The problem with daysum is that it doesn't have a time stamp as it is normally generated once at end of day so I can't tell when the spurious daysums were generated.

[DaculaWeather]

It's been almost 5 days now, that's the longest I've ever had VWS running until this version.

[gman19]

I am running Ver. 14.00 p103.
I cannot get it to interface with my HeavyWeather Pro Ver. 1.0 which is working
in conjunction with a new LaCrosse 2810 station.  It appears that it cannot find
the currdat.lst file because the HWPro software does not generate it.

Is there a fix for this?

Thanks!
Gman19

[stevebrtx]

The daysum.txt and daily files continue to be corrupted at totally random times on p101 so I replaced the batteries in the console, did a total reset and then installed p103, we'll see if that changes anything.

Well, a day later, no joy, last night at 9:20pm the files were corrupted again and 2 lines were entered into the daysum.txt file, the following files were created in Summary: 2013.bin, 2013_21.bin, 2013_21_20.bin. So far today it's running perfect.