If you look in the documentation, you'll see that it suggests using hardware settings for pressure, altimeter, and barometer. That way, there will not be a problem of alternating between hardware and software computed values.
On Wed, Jan 13, 2021 at 6:35 AM Greg Troxel <g...@lexort.com> wrote: > > gjr80 <gjroder...@gmail.com> writes: > > > Not at all. If you blindly set loop_request = 3 then yes your archive > > record pressure values (as well as some other obs) may end up being a > > combined hardware/software value. If you read the loop_request stanza it > > warns you of this and points out the solution. > > It strikes me as at least suboptimal that an alternating stream of > LOOP1/LOOP2 packets leads to calculating values from LOOP1 when those > values are present in LOOP2. Stepping back, I would view LOOP1/LOOP2 as > a data transport protocol and view the most recent report of a value > received as valid for some short interval, perhaps 5 nominal LOOP times. > Basically, if something is in LOOP2 and that is received as often or > almost as often as it should be, don't try to use a computation from > LOOP1. > > Note that this comment is from looking from away, disregarding how the > software works now. And I realize ENOPATCH :-) > > -- > 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 weewx-user+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/rmiczy8oqet.fsf%40s1.lexort.com > . > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEA2isys%2BKPHXWaahvw0qQ%3DYogQGb4Bg4wsFRWZU-KTLpA%40mail.gmail.com.
