MB PRO: Conversion wind and to high values **mostly solved**

[tofe]

Hello
I have noticed two things at wind data.

1. Wind values are not converted correctly in km/h.
2. Wind data is captured too high.

Join at 3 Davis VP 2 consoles and 2 Envoy:
19:22: 27.3 km/h (7.6 m/s)

MB PRO:
19:22: 8.1 m/s (29.2 km/h)

logfile:
19:24 (!): 23.8 km/h (6.6 m/s)

Variable used for log file: [wind0wind-max = kmh.1: x]

When the wind data would be too deep, could be assumed that data has been lost. But here they are too high. In the logfile, other wind data and at a different time than in the History. For current information, I may be a time difference of max. a minute to understand. In statistics, the time should be no different. How this comes about?

high_wind_2016-04-24_mb_pro.png (93.86 KiB) Viewed 2883 times

high_wind_2016-04-24_logfile.png (9.05 KiB) Viewed 2883 times

high_wind_2016-04-24_envoy.png (8.92 KiB) Viewed 2883 times

[admin]

Thanks for sharing your data. Regarding your findings:

1) I can't see which conversion between m/s and km/h should be wrong. Can you please explain a bit more where exactly conversion is wrong.

2) Davis captures wind data inside their console in mph without any decimals. RF data from wind sensor does not come through in that way, but is a funny number that needs a polynom to approximate and Davis does not share their polynom with me. Therefore, I use a pretty good approximation but a difference of one mph can happen. To be honest, hard to say which of the values is right as these wind sensors do all have a very limited resolution

Time of gust max also looks fine to me. It is at 19:22, 8.1 m/s (29.2 km/h) in all the data you attached except for the last table.
Unfortunately, you did not share the code that builds up the table at the end and when the generation of this table was triggered.
Does it still show 19:22 as maximum, when you generate the table now? Did you inspect the database with tool on "History" tab?
It allows you to select wind0wind and to see the min/max of different time resolution levels.

[tofe]

Hello

Thanks for the detailed answer!

1) I ignored data (two lines above is the correct data), please forgive me. The conversion factor is absolutely correct, sorry!

2) Ooohhh, thanks for the insight into the DAVIS VP radio protocol! I have again found differences between consoles, Envoy ond MB PRO in the gusts of wind from 30.04.2016. Now I know, thanks to your explanations why are and also have doubts about which data is correct.

Too bad that the DAVIS polynomial used does not advertise. I hear myself something to and sign up if I found something. Hopes I'm not, but if you do not try ...

In this sense, thanks for your statement and for your use.