High gust display

[HansR]

I ran my station with Ecowitt GW1000 HTTP protocol. During Eunice there were peak high gusts which caused me to look into the wind more specific.
I doubted some things I saw and changed my GW1100 to the GW1000 protocol to get the higher sample frequency. But then apparently the Recent High Gust in the monthly log (which is apparently displayed) remains at the same value and so does the chart. So I think something is wrong here. Why do I have 4 values of High Gust the same and the last value of 95 is also reproduced the next time? I change back to the HTTP protocol.

Schermafbeelding 2022-02-18 201659.jpg

Schermafbeelding 2022-02-18 201617.jpg

Schermafbeelding 2022-02-18 201743.jpg

[mcrossley]

I think the question is why are you not getting the same values using the Ecowitt protocol!

Unless you have changed it the gust value should be a 10 minute high. So a peak value should "hold" until it is exceeded or 10 minutes passes.

The Ecowitt station should be doing the same, I'll have to check why it isn't as I'm pretty sure it did when I last tested it....

[HansR]

I did only change the protocol.
Could you be specific on which setting you mean?
Could you also say where I can set the 2 second or instantaneous High Gust? And what the difference should be?

I assume the current gust is instantaneous and the Recent High Gust is then a ten minute value? But that ten minute then must be a running average shifting every minute? Obviously I am missing a point here. Sorry.

[EDIT] And I did look back and can confirm that the Ecowitt HTTP protocol also gives same values on the five minute steps.

[HansR]

I think it must be my error than while changing the protocol and the fact that the gust remained the same four registrations of 5 minutes in a row. It must have been the reboot / restart which has caused that.

So than the only question remains the 2 second of the instantaneous value. Where can that be setup?

[HansR]

OK, I was misguided by the four successive Recent High Gust figures which should not occur but must have been caused by the change of device.
Forget it, my bad.