Frank, Experience has shown that some stations do not play well when using RF. Such stations are usually what we call partial packet stations (ie the loop packets they emit do not always include all observations). As a result caching of loop packet data is applied when operating in RF mode and this allows partial packet stations to play much better with RF (though I still have my suspicions that RF, caching and partial packet stations cause the occasional problem) . You might like to try and find some Davis RF stations to see if they populate wind gust on WU, Davis stations play pretty well with WU and in RF and they do not emit windGust in loop packets.
By your question re increasing the WU report interval I assume you mean 'reporting more often' rather than actually increasing the report interval (which would report less often). The answer is 'it depends' A little background. WeeWX can report to WU on receipt on an archive record (non-RF mode) or on receipt of a loop packet (RF mode). How often a station reports depends on what mode it is operating in and its archive interval or the period between loop packets. For example, a station with a one minute archive interval with loop packets every 2.5 seconds operating in non-RF mode would see WU update every one minute (in this case the interval between loop packets is irrelevant); a station with a five minute archive interval with 60 seconds between loop packets and operating in RF mode would also update WU every one minute (in this case the archive interval is irrelevant). There is one constraint though; the WeeWX archive interval needs to be a multiple of one minute, so you cannot do non-RF updates every 30 seconds, one minute is as low as you can go with non-RF. So provided you observe this constraint you can post more often by operating in non-RF mode and reducing your archive interval. To go under one minute you need to operate in RF mode and have loop packets arrive in sub-one minute intervals. Further complicating the matter (or rather giving the user more control over RESTful uploads) is the post_interval <http://weewx.com/docs/usersguide.htm#Wunderground> config option. post_interval specifies the minimum period in seconds between posts (the documentation implies that post_interval affects archive record based posting (ie non-RF mode) but I believe it is actually used in RF mode as well (why you would use it for RF posts I don't know)). If you specify post_interval = 900 then posts will only be made if a least 900 seconds have elapsed since the last post. post_interval is intended for use with services that only want to hear from your station every (say) 15 minutes but you are running your station with a five minute archive interval (which would normally result in posts every five minutes). post_interval defaults to 0 which means every archive record/loop packet results in a post being made. Gary On Sunday, 6 December 2020 at 14:19:53 UTC+10 [email protected] wrote: > > Thanks Gary for your analysis, it make sense, I will have to dig a little > bit more in other stations since I think I have seeing other (not WF) > sending rapidfire with windgust at the same time. Not sure where / how they > calculate it. > > In the same line of thought is there a way to increase the WeeWx WU report > interval? Right now it report every 5 minutes and I have seeing stations > reporting every 1 minute so it seems to be supported by WU. > > Thanks, > > Frank. > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f7cb0f94-0d23-4525-ac48-6185c1a6fcfbn%40googlegroups.com.
