If I understand weewx correctly then a) Stations provide LOOP records which are station dependant and range from frequent partial packets for stations such as Accurate, full packets every 2 seconds for say Davis, and full packets every 48 seconds for say FineOffset. b) These LOOP records can be aggregated into ARCHIVE records at an interval set by archive interval by weewx, or can be generated in the station and transmitted as ARCHIVE packets to weewx. c) The ARCHIVE records (station generated or weewx generated) are stored in the weewx database d) When an ARCHIVE record is stored / available then reports and restful services (which are bound to the archive record event) will be triggered. e) The WU rapidfire restful service is (I think) bound to the Loop packet event and not the archive event.
The ftp is I think just another report – so would require the use of the report interval setting in weewx reports as detailed in the user guide for report frequency. Sent from Mail for Windows 10 From: John Jensen Sent: 03 July 2017 15:14 To: [email protected] Subject: Re: [weewx-user] Archive question I would have to probably also use the post interval code in my ftp settings for my website also so it does not post every 1 minute to my website to correct. So if I understand you correctly the archive setting of 300 is for how fast it takes the readings into the database only. On Jul 3, 2017 07:06, "Andrew Milner" <[email protected]> wrote: As you are trying to post to WU and WB at 60 second intervals I think you will find that you will need your archive interval to be set to 60 seconds, and then use the post_interval settings to delay the postings to other sites such as CWOP - rather than trying to output on LOOP records (which as far as I am aware is only implemented for WU rapidfire, and which you have already said won't woprk for Accurite stations anyway since they output partial packets. On 3 July 2017 at 14:57, John Jensen <[email protected]> wrote: I am trying to achieve 1) posting to a services default and 2) get weather underground and weatherbug to as close to real time as possible. I do know the rapid fire does not work with Acurite stations. It gives a -- in the barometer and a nAn in the temp. So I was thinking by using the code Tom posted earlier that it would tell that service to post at that set interval. So I had set WU and WB to 60 second post to try and achieve as close to real time and then set PWS to 300 seconds and WeatherCloud and CWOP to 600 seconds. Tom had said it was untested so I tried it. On Jul 3, 2017 06:38, "Andrew Milner" <[email protected]> wrote: I think there may be a terminological issue here. What exactly are you trying to achieve? Weewx will create archive records in the weewx database according to the archive interval specified - I your case every 300 seconds Reports are run every archive interval, but specific reports may be delayed using the cron-like facility. Except for WU rapidfire (which is bound to LOOP records) the restful services are run every archive record. I THINK that the post_interval is similar in that the restx services are attempted to be run once per archive interval, but may be deferred until at least post_interval has passed for specific services. ie the post_interval may defer a restx update until post_interval or the next running, but cannot be used to increase the frequency to less than archive interval. I may be talking total gibberish though!! On Monday, 3 July 2017 13:48:24 UTC+3, JJ Drones1 wrote: Well it has been running over night and will run like this till I get home from work. But it only updates at archive rate default of 300 seconds and does do the posting intervals. So I am unable to do real time 60 second updates on weather underground or rapid fire, with rapid fire set to true acrite stations get nA or -- in the updates. I set rapid fire before I put the code of the post interval in to test it again. Then returned it to false then inserted the post interval code to test. Oh well guess I have to live with the 5min 300sec archival update. -- 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 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 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 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.
