Nothing has changed. The VP2 only provides wind data in whole mph. Any averaging can generate decimal points, that’s just math. WD’s added complication is that it converts the mph from the Davis, to knots. Then it converts knots back to mph or whatever other units the users are using for display. The knots to mph conversion factor is 1.1507784538296349319971367215462 so the result of the conversion will frequently have decimals, but those are get rounded off generating minor errors when converting from smaller values of mph → knots → mph.
There really should be a lot of threads about this.
Thanks Niko, that explains it, was just wondering why the main dial was rounded when everything else is to tenths in WD, i did find one or 2 threads when i searched but they were very old, hence this new one as something “may have” changed with Davis since 2005
Maybe lost in the server crash. I know I did a table one time showing the possible conversion error for multiple wind values, but I don’t see that now I do recall that Brian added a decimal point to some knot values to minimize errors.
Understandable re data loss, it’s not an issue, more of a query, the decimal is neither here nor there, just takes a bit of getting used to Thanks again for you input as usual
I ain’t got a clue as to what’s happened or what I have done but I have just looked at WD and it’s now showing to the tenth, perhaps it’s cause rather speed has increased some?