Helps a lot – thanks! I’m still trying to “sort out’ the eventual configuration – there are some reasons that I might want some of the readings in a “flat file” which would cut down on my network traffic; and I also have a pressure temp sensor that I might be able to set up.
I’ll post whatever I wind up doing. Thanks! Clay From: [email protected] [mailto:[email protected]] On Behalf Of mwall Sent: Sunday, February 12, 2017 11:21 AM To: weewx-development <[email protected]> Subject: [weewx-development] Re: Loop vs Archive On Thursday, February 9, 2017 at 1:00:08 AM UTC-5, Clay Jackson wrote: I've got an Acurite 5n1 that I'm reading using the SDR radio driver. Since that doesn't provide a barometer, I'm reading an APRS formatted stream from another station I have, and grabbing the barometer from there (will be using a Pi sensor as soon as it arrives). I'm a bit confused about loop vs archive. The barometer readings show up ABOUT every 10 minutes, but can be a bit shorter or a bit longer. So, based on the docs, it seems like I should be using LOOP and the "packet" structure; but, the examples I've seen, and the code I have working right now uses the ARCHIVE and record structure. Can anyone give me some additional insight here? does this bit from the customizing guide help: http://weewx.com/docs/customizing.htm#Data_architecture the sdr driver will spit out data more frequently than every 10 minutes, but you're getting pressure changes only every 10 minutes or so. no problem. assuming that you have a service to read the pressure from an APRS file, simply bind that service to NEW_LOOP_PACKET and add the pressure reading to each loop. or bind it to NEW_ARCHIVE_RECORD and add the pressure reading to each archive record. since pressure is slow-moving, either approach will work. if you did the direct connect approach with a separate thread (as discussed in the weewx-sdr issues), please consider posting your implementation so that others can learn from it. m
