RFXTrx433 & WGR800 - Bad sensor data, "chill x10"
Posted: Thu Jan 10, 2013 10:43 am
I've been running meteohub (4.9q) with my RFXTrx433 for a couple of months now and I have an intermittent re-occuring problem that occurs sometimes when data logging is restarted (or when I reboot meteohub).
The problem is that meteohub starts to error on the data it's receiving from my WGR800, shortly after the logger process has started. The log messages look like this:
I'm not sure if this problem is connected in any way with the problem I previously reported about the battery low warning, which is still ongoing.
Any thoughts most appreciated!!
Cheers
The problem is that meteohub starts to error on the data it's receiving from my WGR800, shortly after the logger process has started. The log messages look like this:
I know it's not a problem with the WGR800, as the console continues to receive data without issue, and also if i restart logging again, it often corrects the problem (or sometimes it fixes itself after a few hours).logger (09.01.2013 22:59:11): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 22:59:25): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 22:59:39): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 22:59:53): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 23:00:07): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 23:00:21): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 23:00:35): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 23:00:49): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
logger (09.01.2013 23:01:03): Bad wind5636639(56021f) sensor data, "chill x10" (758145640) out of range [-700:1500]
I'm not sure if this problem is connected in any way with the problem I previously reported about the battery low warning, which is still ongoing.
Any thoughts most appreciated!!
Cheers