WD wind gusts are low compared to WeatherLink

the davis weatherlink IP data logger is not designed to have 2 connections like that
WD is likely missing out on data

Okay, thanks. I shutdown weatherlink this morning and tomorrow is supposed to be a relatively windy day (gusts to 30-35 mph). I’ll see how my wind gusts compare to the two other weather stations in my neighborhood.

you can see the daily max on the console easy enough

The console max gust for today was 24 and WD was 20. Is that just an artifact of the way the console receives the data versus how often WD grabs it?

I don’t know how WD works (but I’ll proffer a view anyway! :lol:), but WD will not see every ‘live’ update as it cannot receive loop packets continuously, it has to do other stuff stuff as well which requires different queries. Also I’m not convinced the loop packets come in fast enough to send every 2.5 second windspeed reading?

The way Cumulus handles this is to read the highest gust for today from the console every minute, and use that if is higher than the highest value obtained from the “live” data. It does mean that some lower speed gusts may still be missed, but ensures that the console and your recorded data agree about the value and time (approx) of the days highest gust figure.

Maybe something that Brian could add to WD? - Assuming it doesn’t already do something similar.

WD has a similar gust comparison:

Just checked and WD’s max windspeed (gust) for the day matches the console.

Maybe I have an option set incorrectly in WD?

Maybe it’s an issue with the data logger - it’s new as of January 2018 but my console is the original I purchased new in 2005. I still have my old serial-to-USB data logger, which I could try.

Actually, it’s probably not the new data logger since weatherlink, when I had it running up until yesterday, did record the maximum gust of 35 mph that matched the console.

Any suggestions for what I might look for in WD?

It would be interesting to hear the experience of other WLIP users.

I discuss a similar issue under bug reports (I don’t use the IP logger, though). Max gust value on the console and WD match if you check them the same day. It happens that the max gust of a particular day in the history is not in the WD’s records (even though it was correctly displayed on the day it happened).
The loop-readout works in WD (10min period) but the issue is this value doesn’t make it into log/data files, plots and historical records. I don’t blame but just tell my view.

that is not the same issue
(and I do not have that issue myself)

it might be that the query of the console every 10 minutes is not working correctly with the IP data logger
I will do some checking/testing today

OK, its not working correctly, with an IP data logger, getting the console max gust
working on fixing that

ok, use a new .zip update,build 68, to fix this for IP data logger :wink:
you can see debug info about it under view, debug info, if you tick to log the raw data , under setup, advanced/misc

Thanks Brian. I downloaded and installed the new .zip, build 68. Under advanced/misc I ticked “Log raw data for testing (as rawultimeterdata.txt)”. Here’s what I copied from view, program debug info and does it make sense based on your changes? Tomorrow’s forecast calls for wind gusts to around 29 mph - another good day to test.

11:37:55
today sunrise time 03/08/2018 06:30:48
today sunset time 03/08/2018 18:11:15
11:40:27
diff in time 00:02:32
yest sunrise time 03/08/2018 06:32:19
yest sunset time 03/08/2018 18:10:14
11:37:55
today sunrise time 03/08/2018 06:30:48
today sunset time 03/08/2018 18:11:15
11:40:27
diff in time 00:02:32
doweatherbug
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting to get vp hi/low 20:40
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
Forecast icon from station number 0
yest sunrise time 03/08/2018 06:32:19
yest sunset time 03/08/2018 18:10:14
11:37:55
today sunrise time 03/08/2018 06:30:48
today sunset time 03/08/2018 18:11:15
11:40:27
diff in time 00:02:32
yest sunrise time 03/08/2018 06:32:19
yest sunset time 03/08/2018 18:10:14
11:37:55
today sunrise time 03/08/2018 06:30:48
today sunset time 03/08/2018 18:11:15
11:40:27
diff in time 00:02:32
yest sunrise time 03/08/2018 06:32:19
yest sunset time 03/08/2018 18:10:14
11:37:55
today sunrise time 03/08/2018 06:30:48
today sunset time 03/08/2018 18:11:15
11:40:27
diff in time 00:02:32
doweatherbug
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero
setting WU gust to zero

you should see
setting to get vp hi/low 2:30:31 PM
Console daily maximum gust 0mph 2:30:33 PM

every 10 minutes or so

Looks like it didn’t work. The console is reporting a maximum gust for today (as of about 7:00 AM local time) of 17 mph at 00:09 and WD is showing a maximum gust of 11.5 mph at 00:34. See attached images of the console and WD screen capture. The file rawultimeterdata.txt is empty. I copied all of the text from the Debug Info window into a text file but the file is too large to upload.

From that text file, it looks like the “setting to get vp hi/low” was updating every 5 minutes through 23:55 but the next time I can find this character string is at 02:05, which might explain why the 17 mph gust at 00:09 was not recorded by WD? I can split up the text file and upload it in several posts or maybe I can email it to you if you’d like to look at it.


I’d just point out that WD has gust of 11.5 when the console only reports in integer values, maybe a clue?

The regular wind in the Davis data feed to the PC is whole mph*, but the ten minute wind gust in the data is:

10-Min Wind Gust 22 2 It is a two-byte unsigned value in 0.1mph resolution.

  • WD’s conversion to and from knots can result in decimals.

that is not the data that WD is requesting
its requesting the daily hi/low
and the value returned for that is whole mph

it looks like for the IP version, it does not always sync very well, getting that daily hi/lo data back
I will have to see if I can get that working more reliably

the problem is the ip data logger is not as good as the usb data logger at handling lots of commands, etc