Since WeeWX v2.4, LOOP packets have included windGust and windGustDir. They are set by the driver to the max values seen since the last archive record.
If you set loop_hilo to False, then they will not be used to calculate max and min values. What gets recorded in the database depends on what kind of record generation you are using. If record_generation=hardware (the default), then what gets recorded will be whatever your Vantage supplies from the archive records in the logger. If record_generation=software, then no value of windGust will be recorded. From your symptoms, I suspect you are using software record generation. If there is nothing in the database, then WeeWX does a "catch up," which always uses the archive records from the logger. So, the behavior you are getting is consistent with loop_hilo=False and record_generation=software. If I'm wrong in my analysis and you're using hardware generation, let me know. Which begs the question: why not stick with the defaults? These two options are for hardware that are not as capable as the Vantage. Leave them at the defaults, and I'm betting your problems will go away. -tk -tk On Sun, Dec 31, 2017 at 9:27 AM, stefano siega <[email protected]> wrote: > > I think I have found a problem concerning wind gusts. > I have a Davis Vantage Pro2 and Weewx 3.7.1. > I select loop_hilo=False and the windgust are not recorder in database! > But, if I restart WEEWX with a new database, the old entries that are > added to the database, contain the correct wingust data. > I think weewx ignores the wingust data read from the station at each > archive interval. > If weewx reads old data from the station's memory, then these contain the > correct windgust data. > > Il giorno lunedì 6 ottobre 2014 16:35:46 UTC+2, Tom Keffer ha scritto: >> >> If you have loop_hilo=False, then LOOP records are not used to record the >> wind high and low. This means that on weather stations that do not emit >> windGust in their archive records (nearly every station except Vantage), >> there will be no windGust field. >> >> We could change this behavior so that the windGust is set to the average >> wind speed (that is, set it to windSpeed), but I'm reluctant to do this. >> That's not really what windGust is intended to capture. It would solve your >> display problems, but introduce semantic problems. >> >> Changing the archive interval will not make any difference in all of this. >> >> Fundamentally, you need to figure out why the rain rate is incorrect. I >> know you have a separate thread going on that., >> >> -tk >> >> On Sat, Oct 4, 2014 at 8:02 AM, Steve2Q <[email protected]> wrote: >> >>> Is it possible that too short of an archive interval could cause >>> incorrect wind data? >>> >>> I presently have loop_hilo = False in order to keep the rain rate >>> correct. >>> >>> This setting keeps the High Wind table value and Wind Speed graph to be >>> incorrect (too low and wrong date/time) >>> >>> My archive interval is presently 120. Would it make a difference to set >>> it back to the default of 300? >>> >>> Thanks, Steve >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Weewx user's group" 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. >>> >> >> -- > 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. > -- 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.
