CMX and <#wdirdata>

[steve]

That's because your direction was already (intermittently) giving 7FFF but your wind speed was zero, so the set of wind data didn't get ignored as it did subsequently.

Dealing with that set of data (valid wind speeds but invalid wind direction) sensibly is quite tricky. What I can do is check for the 7FFF value separately and use zero instead. The only issue with that is that any offset would still get applied. Doing anything about that is very messy because the offset is applied in the common code.

[mcrossley]

Does that apply to the insert at the end of file though? The wind speeds are being reported as...

2017-01-22 19:22:00.327 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.

just before the insert, and for every data packet received above that after I changed station.

Anyway, I have fixed my relay code so this shouldn't happen any more (intermittent 'not connected' messages), but I'm not sure I fully understand what MX is doing.

[steve]

Once the speeds went out of range, it started ignoring all of the wind data, so the values in MX stayed at what they were previously.