That means "wind" data packets are being reported, but it does not tell you 
the contents.
For that, enable "debug_packet=1"
and run for a short time while you know it is windy. A few minutes will be 
enough then disable debug-packet again.

A separate test is stop weewx for maybe 20 to 30 minutes and restart - see 
if the wmr300 reports sensible wind results in the history.

Cameron.

On Saturday, 6 October 2018 19:20:27 UTC+10, Juan Antonio Mosquera wrote:
>
> It's weird, it seems that wind data does read no?
>
>
> Oct 06 11:17:13 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 
> 135; TH_0: 11; TH_1: 16; TH_2: 10; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; 
> TH_7: 10; TH_8: 10; barom: 10; forecast: 12; rain: 12; wind: 16; x57: 1
> Oct 06 11:17:13 meteomontaos weewx[10621]: wmr300x: write counts; xa6: 1
> Oct 06 11:17:33 meteomontaos weewx[10621]: wmr300x: read counts; Loop: 
> 135; TH_0: 10; TH_1: 16; TH_2: 11; TH_3: 10; TH_4: 10; TH_5: 10; TH_6: 10; 
> TH_7: 10; TH_8: 10; barom: 10; forecast: 10; rain: 12; wind: 16; x57: 1
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to