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.
Gary On Wednesday, 13 January 2021 at 07:49:05 UTC+10 galfert wrote: > Well then this seems to be a big limitation for any Davis station that is > not using a WLL! Seems like the WLL is a better solution than other > loggers and then ending up with a mess of combined calculated and received > values for barometric pressure. Unless it is possible to set things so that > Altimeter is only calculated during LOOP2 reads, and to only accept sea > level during LOOP1. I'm not sure if that makes sense or if it is even > possible, nor what ramifications messing with all this entails nor what the > other undesired results may be. > > Bottom line....seems like WLL is a better way to get complete live data > from the station. > > On Tuesday, January 12, 2021 at 4:36:03 PM UTC-5 gjr80 wrote: > >> I have no WLL experience so short answer is I don’t know. >> >> But the loop_request setting is a vantage driver setting, as far as I >> know you need to use a different driver for WLL. Also, there are a number >> of WLL drivers; looking at one just now I see it appears to emit pressure >> and altimeter, though as I said I don’t know enough about WLL to draw any >> conclusions. >> >> Gary >> On Wednesday, 13 January 2021 at 07:22:28 UTC+10 galfert wrote: >> >>> Gary, >>> That is very interesting and possibly important information. Is what you >>> mention dependent on the type of logger used? Meaning is the data switching >>> (LOOP1 / LOOP2) still an issue with the WLL? >>> >>> >>> On Tuesday, January 12, 2021 at 4:14:00 PM UTC-5 gjr80 wrote: >>> >>>> Assuming can be a dangerous business! If you have not specified >>>> anything for loop_request then you will be using LOOP1 only (the default), >>>> whether that is the ‘best available format’ depends on your circumstances >>>> I >>>> guess. Should you happen to specify loop_request = 3 in order to get the >>>> best of both worlds (by alternating between LOOP1 and LOOP2 packets) be >>>> aware that this can cause WeeWX loop packets to alternate between hardware >>>> provided and software calculated values for station pressure and altimeter >>>> (and archive records will then have a blend of both). If you do use >>>> loop_request I suggest you carefully read the loop_request stanza >>>> <http://weewx.com/docs/usersguide.htm#%5BVantage%5D> in the User’s >>>> Guide. >>>> >>>> Gary >>>> >>>> >>>> On Wednesday, 13 January 2021 at 06:12:20 UTC+10 n0...@n0nb.us wrote: >>>> >>>>> >>>>> > If you don't have the latest firmware then you may not have Loop2 >>>>> data. Not >>>>> > having Loop2 data will inhibit greater Altimeter calculation by >>>>> WeeWX >>>>> > because station pressure will be missing and it will have to work >>>>> backwards >>>>> > and that is less accurate. Better to send the software station >>>>> pressure >>>>> > which is done by having Loop2 data. >>>>> >>>>> According to the Davis site the latest firmward for the Vantage Pro2 >>>>> is >>>>> 3.15 and wee_device reports my console is at 3.15. I have not >>>>> specified >>>>> which LOOP data WeeWX is to use as I assume it is coded to use the >>>>> best >>>>> available format. >>>>> >>>> -- 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/68e3919b-3c79-47a3-9af6-d2f3bc5df04an%40googlegroups.com.
