10 Min Peak Gust

[Mapantz]

It's currently 10:44pm

Max gust was 43mph at 10:41pm.

10 Min Peak Gust says 42mph.

[Mapantz]

Just happened again. A 43mph gust, 10 min peak only went to 42mph.

[mcrossley]

I don't suppose you have a MXdiags with logging enabled?

Where are you seeing the 43 mph? And where is MX getting its data from?

With the WLL, MX reads each 2.5 second update and will use the latest gust value, and also once a minute cross checks the current MX 10-minute peak gust from those real-time data packets with the stations own peak gust which it also updates once a minute. If the stations 2 (or 10) minute peak gust is greater (implying a 2.5 second update was missed), then it uses that instead.

[Mapantz]

It's an issue with the WLL.

I was watching the app for quite a long time. The higher gusts were occurring every time a shower rattled through. The 10 min peak gust was considerably lower when the higher gusts happened. It was showing 21mph, then a gust of 43mph came in and it changed to 42mph. I saw that twice.

[mcrossley]

So in the app you saw a latest live reading of 43, but the 10 minute gust reading only went up to 42?

Hmm, so which is correct! It would appear that it is also sending the 42 value out in the 2.5 second network broadcasts as well. Otherwise I would expect MX to pick up the 43.

But the app also just picks up the 2.5 second broadcasts for the live data, so how is that different from MX. Very puzzling, especially as this is all in the WLL native units, so no conversions/rounding errors coming into play.

One to report to Davis I think.

[Mapantz]

Back to this again

Screenshot 2024-01-02 131849.png

I took this snapshot at 13:16, but the 10 minute high gust doesn't show it as 52mph. 52mph wasn't logged in my graphs because of that either.

[mcrossley]

I'm going to need a log file with debug and data logging enabled to look into this.

[Mapantz]

That's the trouble, you don't know when it's going to happen, unfortunately.

It's the WLL that has the problem. I sent an email to Davis with my station ID, explaining it.

I've turned on debug & data logging, just in case it happens when I don't see it.

[Mapantz]

I left it running for a bit while I went out. I don't know if anything happened in that time?! It's one of those things that is hard to catch unless you leave the logging permanently on.

20231218-224451.zip

[The PIT]

Your 52mph gust is in your table data so it has been logged unless you inputted it manually that is.

I wonder if Davis are using the asos method to calculate the 10 minute gust value.

[Mapantz]

Your 52mph gust is in your table data so it has been logged unless you inputted it manually that is.

I didn't say it didn't..

I said that when it occurred, the 10 minute peak gust value didn't change to 52mph, it stayed at 46mph

[mcrossley]

OK, so I can see why this is happening (partially).

MX relies on the 2.5 second broadcasts for most of its data, those broadcasts do not contain a peak gust value, only the latest value. So periodically MX fetches the "current" data (which is actually the last data sent to wl.com, not current!), which does have a peak gust value. It uses that to determine if a peak gust has been missed from the broadcast data (lost packet, network issue etc). If it has it checks if it has exceeded any of the records (today, month, year, all-time, monthly) and if it has logs the new record.

What it should also do is stuff that peak gust value into the cached wind data that is used by MX to calculate the latest peak 10-minute gust. It sounds like that step is not working for some reason,

[mcrossley]

Ah, I recall it doesn't do it routinely, because of the staleness of the "current" data - it could extend the 10 minute period beyond 10 minutes. But what I can do is make it do it if it exceeds todays max so far.

[Mapantz]

The problem occurs in the WeatherLink app, so it's definitely an issue on Davis' end.

I should get a reply from them within the next two months.

[The PIT]

You said quite clearly the 52mph wasn't logged

"I took this snapshot at 13:16, but the 10 minute high gust doesn't show it as 52mph. 52mph wasn't logged in my graphs because of that either."

The gust won't show instantly only when the app decides to update and only then if your wifi is connected. Any drop outs on that will balls it up as well.

The weatherlink app is buggy when it updates it switches back to the old value then back to the new.

I wonder if it's also messing up the rounding which may explain 43 back to 42.