OK, understand. Ideally you want all of the processing of a loop packet (ie
all of the services that do something with or to the loop packet, eg
StdCalibrate, StdQC, StdArchive, your service etc - all those with a
binding to NEW_LOOP_PACKET) to execute within a loop period. The loop
period vari
I am augmenting the VP2 data, and looking for an idea what the maximum time
my code could run to without interrupting or missing data from my VP2.
Right now, on my 'production' system I expect additional code to run about
3/4 second, with most of it spent connecting to MQTT, but I know that I c
Um, ah yes. Will mention that one to Tom.
Gary
On Friday, 5 October 2018 12:05:05 UTC+10, Thomas Carlin wrote:
>
> Re: the new_archive_packet() recommendation, I didn't think about it, but
> I agree. It is posted written in the "second data source" documentation
> with the function new_archive
On Friday, 5 October 2018 11:58:44 UTC+10, Thomas Carlin wrote:
>
> Perfect! thank you Gary! I knew it had to be something simple like
> that. Everything is up and running now, and I'll just need to catch the
> necessary exceptions, and optimize the collection as much as possible. Is
> there
Re: the new_archive_packet() recommendation, I didn't think about it, but I
agree. It is posted written in the "second data source" documentation with
the function new_archive_packet().
On Thursday, October 4, 2018 at 7:52:37 PM UTC-6, gjr80 wrote:
>
> Hi Thomas,
>
> It sounds like you should b
Perfect! thank you Gary! I knew it had to be something simple like that.
Everything is up and running now, and I'll just need to catch the necessary
exceptions, and optimize the collection as much as possible. Is there a
target time I should shoot for, or just try to make it as fast as possi
Hi Thomas,
It sounds like you should be using event.packet rather than event.record.
Archive records are found in event.record, loop packets are found in
event.packet. It's a subtle but important distinction. You have probably
moved on from the code you posted above, and I probably should have
Hi Gary,
I've started working on this service, and I have run into an issue.
A quick refresher so you don't have to read through the whole thread: I am
writing an MQTT service to add data to the loop packets. You pointed me in
the right direction with the NEW_LOOP_PACKET, and I'm 99% of th
On Wednesday, 12 September 2018 13:36:00 UTC+10, Thomas Carlin wrote:
>
> Perfect Thank you Gary! That gets me what I need. Now I just need to
> reprogram all my sensors and my driver, or create another service to
> collect and queue data. I'm leaning towards MQTT, for its simplicity,
> speed
Perfect Thank you Gary! That gets me what I need. Now I just need to
reprogram all my sensors and my driver, or create another service to
collect and queue data. I'm leaning towards MQTT, for its simplicity,
speed, and scalability. This sounds more like a winter project to me!
A couple quic
Hi Thomas,
If it is any consolation I am not a programmer either, I get by Googling,
trying things out, seeing how existing things work etc and am always
learning new and better ways to code.
Your service is bound to the NEW_ARCHIVE_RECORD event so each time a new
archive record appears your s
Hi Gary,
All that makes sense, thank you. My service is coded directly from the
documentation linked above, with the addition of a function to "somehow
downloads the data", and I have included it below. One thing to note, I am
not a programmer, I dabble as a hobby, so if there is something don
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 s
BTW, I missed Thomas Carlin's last reply before posting. My apologies for
getting his thread a little sidetracked.
--
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
Hi Thomas,
I use it mainly for the NOAA Climatological monthly and yearly summaries,
and also compile yearly and all time highs and lows from the database, and
appreciate having the database available for any other kind of record
manipulation or graphing. As i mentioned, I don't keep a full ti
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 s
Thanks for your comments, Jeff, but you've got me curious. If you don't use
WeeWX for its ability to accumulate LOOP packets and make records out of
them, and you don't publish to the web, what do you use it for? Internal
LAN publishing? Something else?
-tk
On Wed, Sep 5, 2018 at 9:08 AM Jeff A.
If I may chime in on the subject, but there are various reasons I don't
have a full time connection to my wx station (Davis VP), and therefore rely
on the archive records to download from the data logger periodically. Even
using a fairly long archive interval of 30 minutes, the archive records
Andrew pretty much has the right idea.
The whole value of weewx is in its archiving abilities. If your driver(s)
don't emit LOOP packets, then your missing out on half the reason to use
the program!
-tk
On Tue, Sep 4, 2018 at 9:46 PM Andrew Milner
wrote:
> If you bind your service to loop rath
If you bind your service to loop rather than record then
weewx will build an archive record at the archive interval, with the value
being the average value for the period
if you specify use loop for hilo in weewx.conf then weewx will populate the
max and min from the loop data and the archive re
20 matches
Mail list logo
