Luc and Rich

Had been doing the testing on a laptop which didn't have Weewx installed 
on. Today I installed everything on my PI3 development machine. I can't 
seem to get humidity to report correctly.This message shows in weex log:

Mar 28 19:49:54 pi3-dev weewx[1837]: engine: 2019-03-28 19:49:54 EDT 
(1553816994) LOOP value 'outHumidity' 216.9 outside limits (0.0, 100.0)

If I change line 1182 of  rtldavis.py  from: humidity = humidity_raw / 
10.0    to humidity = humidity_raw / 10.0 no errors but wrong humidity 
value. Current real humidity here is 50% to 60%
Where to start? :)

Thanks,
Paul

On Thursday, March 28, 2019 at 7:40:22 AM UTC-4, rich T wrote:
>
> Luc
>
> Thanks...I figured it was a configuration error on my part. Later this 
> evening will give it a try.
>
> Thanks
> Rich
>
> On Thursday, March 28, 2019 at 7:30:52 AM UTC-4, [email protected] wrote:
>
>> On Wednesday, 27 March 2019 18:27:40 UTC-3, rich T wrote:
>>>
>>> Looks like I'm only decoding a couple of the data fields, in which could 
>>> be configuration error on my part.  The driver did crash due to a "none 
>>> type" error, again the cause could be configuration error on my part.
>>>
>>
>> Rich,
>>
>> Your command line contained the phrase "[options]". This is not 
>> recognized by the go-parser and all entries which come after are neglected. 
>> Therefore no messages were received because you've got the default 
>> EU-frequencies.
>> The init value of pct_good was none, I better change it to 0.0 to avoid 
>> the type error. This error only happens when no single message is received 
>> during 5 minutes.
>>
>> I will change the programs main.go and weewx-rtldavis as follows:
>> - The -tf and -tr option are required (program weewx-rtldavis will add 
>> them automatically)
>> - When -tf and/or -tr is missing, main.go report: EXIT PROGRAM with a 
>> description.
>> - weewx-rtldavis will end itself (and rtldavis.go) when it sees this 
>> message. (when rtldavis should stop itself, it won't help because 
>> weewx-rtldavis will restart the program again after 60 seconds).
>>
>> Luc
>>
>

Reply via email to