I will do the set raw on Thursday evening. I have the model 1036RX
On Jul 5, 2017 8:17 AM, "gjr80" <[email protected]> wrote: > Thanks John, > > I know little of the AcuRite stations but your log extract indicates a > few things: > > 1. outTemp is frequently None in the raw packets being seen by the WU > uploader. outTemp appears with a numeric value in the raw packets at > 15:06:17, 15:06:53 and 15:07:29 (the end of the log extract). Reading the > comments up front of the AcuRite driver this appears to be correct > operation; outTemp should be included in a loop packet every 36 seconds. > The WU uploader subsequently uploads the numeric outTemp and all is good. > The second extract you provide, which is actually from before the weeWX > stop/start at 15:06:13, includes outTemp in numerous raw packets but in > every case it is None. The cache appears to do it job and it provides a > cached outTemp up until 14:53:56 after which the last cached outTemp > value is too old and outTemp is dropped from the cache. The WU uploader > now omits outTemp (tempf). > > 2. The AcuRite stations provide what is called station pressure or gauge > pressure which is stored in the weeWX pressure field. WeeWX calculates > barometer from this pressure and outTemp (it also uses station altitude). > If outTemp is None then barometer is not calculated and is None. There WU > uploader ignores None values and therefore does not upload barometer. > > 3. The AcuRite does not provide dewpoint so again weeWX calculates it. To > calculate dewpoint you need outTemp and outHumidity, if either is missing > dewpoint is None. So again the missing outTemp means dewpoint is None and > the WU uploader does not upload dewpoint. > > So it seems that the barometer, dewpoint and outTemp problems are all > becuase outTemp is frequently being set to None in the loop packets. > > I think it is worthwhile seeing what the driver is doing (the previous log > extract showed us what the WU uploader was doing). If you are up for > another log extract, in weewx.conf you could set debug = 0 again (if you > have not already done so) and under [AcuRite] add a line debug_raw = 1 > like so: > > [AcuRite] > debug_raw = 1 > .... > > Stop and start weeWX again. Let weeWX run for 15 minutes or so and then > take a log extract from when you just started weeWX through until the 15 or > so minutes is up. Post the entire log extract. This will give us a picture > of the raw data straight off the station. Once you have the log extract you > can remove debug_raw = 1 or set it to 0 then stop/start weeWX to cut down > on the driver logging. > > Oh, and just by the by, what model AcuRite do you have? > > Gary > > -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/weewx-user/qhdN8xgyPxE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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.
