Hi, It all comes down to how your second source service (I'll refer to it from now on as the service) is providing data. Your VP2 will be providing loop data every 2 odd seconds, if your service adds its data to the loop packet then you should have a similar time resolution for data from your service as for your VP2 data. This is what Andrew meant by binding your service to loop. Your service may be augmenting loop packets but only doing it every so often, say every 60 seconds, in this case the best time resolution you will see for data from your service is 60 seconds. The other way your service may be working is to bind to the archive record, in this case your service is adding data to the archive record and then, depending on your service, it is quite likely that the time resolution for data from your service will be your archive period (lets say 5 minutes). As long as (1) your service is bound to loop (2) you have loop_hilo = True set in weewx.conf and (3) your service is included in the service list at the bottom of weewx.conf before StdArchive then loop data from your service will be used to come up with highs and lows. The thing to note though is that the best time resolution you can get for data from your service is the shortest period between it providing data to WeeWX.
Its a complex arrangement with many variables, the best way for us to let you know exactly what you should expect would be to know what station you are using (provided - VP2), some info on how it is configured (provided - loop_hilo = True) and how is your service coded (not yet provided). If you are prepared to show us the code your are using for your service we can then give you some definitive advice. Gary On Thursday, 6 September 2018 14:22:24 UTC+10, Thomas Carlin wrote: > > Thank you for your replies. > > > A couple points of clarification: The main datasource for my station is a > Vantage Pro2, and it is using weewx as designed, LOOP packets, etc. I have > added a second data source as described here > http://www.weewx.com/docs/customizing.htm#Adding_2nd_source, which > specifically discusses adding data to the record dictionary. > > Weewx is currently configured to get the hilo data from the loop packets as > described, and this is working for the Pro2. My question is specifically > about the additional custom service that has been added to the data_services > section as described in the doc linked above. > > > Does that clarify anything? > > > Based on the comments it sounds like there is no way to add the hilo data > manually as part of the additional service, correct? > > Is there a way to have my custom service run as part of a loop, rather than > the record without reinventing the wheel, or disrupting the Pro2 and its data? > > > Thomas > > -- 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.
