[weewx-user] Re: weewx-sdr driver modified for rtl-sdr plus extra ttyACM1 input; getting gaps

[William Garber]

here is another version that blocks less.   
On Sunday, April 30, 2023 at 11:05:37 PM UTC-7 William Garber wrote:

> Until now the Atlas emitted NEW_LOOP_PACKET events about every 7 seconds, 
> so I had my indoor weather data arduino (wpa) set to emit at the same 
> interval.  I just sped that up to every 3 seconds (just the wpa emitter).  
> You can "$ cat /dev/ttyACMwa" which prints the serial data output over usb 
> from the arduino (wpa) directly to the linux console.  That shows (the  new 
> interval) is 3 seconds.  I will run it over a long time to see if there are 
> any long intervals.  But what I suspect is happening is ... I have three 
> weather stations.  I built two with Adafruit parts plus the indoors part of 
> this one (wpa/Atlas).  The "merged" reports are run as a fourth instance of 
> weewx which is not the server, just "wee_reports_merge" which is just 
> "wee_report" with the configuration file for the merged report.  The worst 
> thing is that this was being run every 90 seconds (DUH).  I slowed it down 
> to every 10 minutes.  The archive interval for Atlas/wpa is 5 minutes.  
>
> The hard part was reading the serial port to get the inside data (one line 
> of json data).
> (1) flush input buffer
> (2) read discard first line in case it is partial
> (3) read next line or timeout
> the readline() commands are blocking with timeout.  Not sure how to do non 
> blocking but see this discussion:
>
> https://stackoverflow.com/questions/1093598/pyserial-how-to-read-the-last-line-sent-from-a-serial-device
> they all seem to think that at least part of the procedure is blocking 
> (not all !)
>
> it works so far.  will leave it to run overnightservice 
> attached. service processes  inside data in NEW_LOOP_PACKET as you 
> described.  weewx uses service plus original unmodified weewx-sdr.py driver 
> for outside data.
>
> On Sunday, April 30, 2023 at 4:47:56 PM UTC-7 gjr80 wrote:
>
>> On Sunday, 30 April 2023 at 13:42:56 UTC+10 william...@att.net wrote:
>>
>> Just one question please :-).  Suppose the read of the arduino could 
>> possibly take a relatively long time, and you want to have a timeout after 
>> which it gives up and saves None/NULL for the indoor data.  
>>
>> What is the max timeout that would be reasonable relative to the archive 
>> interval ?
>>
>>  
>> I would be more concerned about the loop packet interval than the archive 
>> interval. Your initial post indicated the Atlas emits packets every 7 
>> seconds so the SDR driver will be emitting loop packets every 7 odd 
>> seconds. If you have a plain vanilla WeeWX install WeeWX will not be doing 
>> much else during the loop packet interval other than calculating derived 
>> obs so dwelling for up to, say, a second should have no significant effect. 
>>
>> What happens if the delay goes past the end of the main archive interval 
>> the event you are handling was in?
>>
>>  
>> Delaying past the end of the archive interval will not have a significant 
>> impact (within reason). Say your service delays 20 seconds past the end of 
>> the archive period, when the driver gets it's turn again it will emit 
>> another loop packet which will cause an archive record to be generated by 
>> WeeWX and ultimately the report cycle is run maybe 20+ seconds later than 
>> usual (note the exact behaviour of the driver is very much driver 
>> dependent; some drivers may skip loop packets, others may emit a loop 
>> packet immediately and yet others may delay emitting a loop packets - the 
>> SDR driver is threaded and I believe it is the former). So really you will 
>> probably only noticed delayed report output.
>>
>> Where you will probably get more problems from delaying the WeeWX main 
>> loop is in the generation/processing of loop packets. As mentioned above 
>> driver behaviour varies from driver to driver. For example, the vantage 
>> driver obtains loop packets every 2 odd seconds; if a loop packet is missed 
>> it is gone forever. Other drivers poll the hardware much less frequently, 
>> say every 50 odd seconds, in that case there could be an entire minute 
>> might go by with no data. The consequences of a missed loop packet depends 
>> on the system config. A vantage station with a five minute archive interval 
>> would see around 120 loop packets per archive period, so the loss of one 
>> loop packet will have no real impact. Consider the second system with loop 
>> packets arriving every, say, 50 seconds; if it had an archive interval of 
>> one minute, you could conceivably see no loop packets in an archive 
>> interval and hence no archive record is generated and no report cycle 
>> occurs.
>>  
>> Remember loop packet data is accumulated by WeeWX and many obs in the 
>> resulting archive record are simply the average value of the obs from all 
>> loop packets seen during the archive interval. So for slow changing obs, 
>> such as air temperature/atmospheric pressure, losing the odd loop packet 
>> during an 

Re: [weewx-user] Belchertown graphs stopped working

[pannetron]

I also downloaded local copies and made the changes to the Belchertown 
code.  Hopefully the Highcharts license agreements permit downloading the 
code.

On Wednesday, April 26, 2023 at 11:26:42 AM UTC-6 vince wrote:

> Thanks for the heads-up here.  I'd have never found it in the belchertown 
> issues.
>
> I tested both workarounds.  Switching to newer highcharts works yet does 
> have the font change issues.  I went with @roe-dl's original workaround in 
> the github issue to grab a local copy of the required pieces of highcharts 
> rather than relying on downloading it every time and hoping that upstream 
> doesn't break anything.
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/eaa41288-e3fb-411a-9771-7f222be20670n%40googlegroups.com.

Re: [weewx-user] Belchertown graphs stopped working

[František Slimařík]

If my company would be dying, I would charge also basic Highchart product 
and search who is using it :)

Dne sobota 29. dubna 2023 v 12:21:57 UTC+2 uživatel Karen K napsal:

> Consider what happens if that company Highcharts suddenly dies. And 
> companies can die.
>
> František Slimařík schrieb am Mittwoch, 26. April 2023 um 20:24:49 UTC+2:
>
>> I believe the best solution is the one already implemented on Belchertown 
>> web pages (use specific version of Highcharts in your code like  "
>> https://code.highcharts.com/10/highcharts.js; to pick latest version of 
>> 10 or  "https://code.highcharts.com/10.3.3/highcharts.js 
>> "
>> for specific one). Code is stored on cloud so should be available all the 
>> time. You can even go back to version 1 released in 2014 so I wouldn´t be 
>> afraid you will loose access soon :)
>>
>> Dne středa 26. dubna 2023 v 19:26:42 UTC+2 uživatel vince napsal:
>>
>>> Thanks for the heads-up here.  I'd have never found it in the 
>>> belchertown issues.
>>>
>>> I tested both workarounds.  Switching to newer highcharts works yet does 
>>> have the font change issues.  I went with @roe-dl's original workaround in 
>>> the github issue to grab a local copy of the required pieces of highcharts 
>>> rather than relying on downloading it every time and hoping that upstream 
>>> doesn't break anything.
>>>
>>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b5370a70-58ab-42ba-886b-a789d68efc93n%40googlegroups.com.

Re: [weewx-user] VantageVue rain collector delay

[Graham Eddy]

is the funnel empty when reading slowly?
⊣GE⊢

> On 1 May 2023, at 9:56 pm, Steve C  wrote:
> 
> The wx station is mounted on a steel pole in an open space in my backyard and 
> is very easy to access. As I mentioned, I disassembled it as recently as 
> yesterday. No birds, no spiders, no nuts, no trees. It is almost like a 
> clock. I am (as of this writing) still collecting .01" every 10 minutes or 6 
> times an hour. 
> 
> On Monday, May 1, 2023 at 7:47:17 AM UTC-4 bgra...@umw.edu  
> wrote:
>> I think Graham has the answer. About twice a year, squirrels crack nuts into 
>> my rain gauge funnel and I get the slow drip.
>> It must be a very uncomfortable task with all the bird spikes around the 
>> outside…
>> Cheers,
>> Bob
>> grattans.org/wx 
>> 
>> On Monday, May 1, 2023 at 7:28:56 AM UTC-4 Paul R Anderson wrote:
>>> Very strange blocked rain funnel would be the number one suspect. Only 
>>> other thing that comes to mind is residual 'rain' falling from a tree 
>>> canopy, or any other object that could hold rain droplets, and release them 
>>> long after the rain shower has ended. Wondering if any trees have started 
>>> to encroach on the area above your rain gauge?
>>> 
>>> Paul
>>> 
>>> On Mon, May 1, 2023 at 7:03 AM Steve C > wrote:
 I removed it again yesterday and checked the tip bucket and entrance and 
 exit paths for blockages but found none. The rain ended several hours ago, 
 but my Vue is still counting .01" every few minutes this morning.
 
 http://livefreeorpi.com  
 
 On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
> I remember such behavior when a spider let the remains of her meals drop 
> into the rain bucket.
> 
> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>> is the outlet from rain bucket partially blocked?
>> ⊣GE⊢
>> 
>> 
>>> On 29 Apr 2023, at 11:48 pm, Steve C > wrote:
>>> 
>> 
>>> Important distinction! I meant to mention that. Yes, the software seems 
>>> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs 
>>> it accordingly. Being a hardware issue I can move this to a Davis forum 
>>> if it is inappropriate here. 
>>> 
>>> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
  What does the console show?
 
 On Sat, Apr 29, 2023 at 6:27 AM Steve C > wrote:
> Sorry for the long post, but the details might matter. We had a 
> significant rain event last weekend and my rain gauge responded in a 
> very weird way (which it has done before). It was raining when I got 
> up in the AM, 1/2 inch collected already. After about 3/4in, it 
> POURED and the rain rate slowed to something like .07in/hour. I 
> replaced the rain gauge (with the Davis rehab kit) last fall and went 
> out in the downpour to check the bucket/collector. No blockages, not 
> full of water...
> 
> My next door neighbor's device report 2.19" of rain when it ended 
> that day. Mine reported 1.90", however it continued to report .01 or 
> .02 clicks at a time until it finally stopped at .42" the next day 
> (although we had no rainfall) for a storm total of 2.32", not 
> terribly far off from my neighbor's 2.19".  I have attached the chart 
> that illustrates the slow collection- as if the collection was full 
> of water that slowly leaked out (can't be the case). 
> 
> The very next day we had a brief, heavy thunderstorm. Both my 
> neighbor and I reported the same .30" for the event.
> 
> Weewx  4.9.1
> Vantage Vue with an IPconnect.  
> 
> We're looking at another 1-3" of rain this weekend, and I'd love to 
> hear any suggestions!
> 
> Thanks,
> Steve
> 
 
> -- 
> 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 weewx-user+...@googlegroups.com <>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
>  
> .
>>> 
>>> 
>>> -- 
>>> 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 weewx-user+...@googlegroups.com <>.
>> 
>>> To view this discussion on the web visit 
>>> 

Re: [weewx-user] VantageVue rain collector delay

[Steve C]

The wx station is mounted on a steel pole in an open space in my backyard 
and is very easy to access. As I mentioned, I disassembled it as recently 
as yesterday. No birds, no spiders, no nuts, no trees. It is almost like a 
clock. I am (as of this writing) still collecting .01" every 10 minutes or 
6 times an hour. 

On Monday, May 1, 2023 at 7:47:17 AM UTC-4 bgra...@umw.edu wrote:

> I think Graham has the answer. About twice a year, squirrels crack nuts 
> into my rain gauge funnel and I get the slow drip.
> It must be a very uncomfortable task with all the bird spikes around the 
> outside…
> Cheers,
> Bob
> grattans.org/wx
>
> On Monday, May 1, 2023 at 7:28:56 AM UTC-4 Paul R Anderson wrote:
>
>> Very strange blocked rain funnel would be the number one suspect. Only 
>> other thing that comes to mind is residual 'rain' falling from a tree 
>> canopy, or any other object that could hold rain droplets, and release them 
>> long after the rain shower has ended. Wondering if any trees have started 
>> to encroach on the area above your rain gauge?
>>
>> Paul
>>
>> On Mon, May 1, 2023 at 7:03 AM Steve C  wrote:
>>
>>> I removed it again yesterday and checked the tip bucket and entrance and 
>>> exit paths for blockages but found none. The rain ended several hours ago, 
>>> but my Vue is still counting .01" every few minutes this morning.
>>>
>>> http://livefreeorpi.com 
>>>
>>> On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
>>>
 I remember such behavior when a spider let the remains of her meals 
 drop into the rain bucket.

 Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:

> is the outlet from rain bucket partially blocked?
> *⊣GE⊢*
>
> On 29 Apr 2023, at 11:48 pm, Steve C  wrote:
>
> Important distinction! I meant to mention that. Yes, the software 
> seems perfectly fine. The console is reporting the 'slow drip' and WeeWX 
> logs it accordingly. Being a hardware issue I can move this to a Davis 
> forum if it is inappropriate here. 
>
> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>
>>  What does the console show?
>>
>> On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:
>>
>>> Sorry for the long post, but the details might matter. We had a 
>>> significant rain event last weekend and my rain gauge responded in a 
>>> very 
>>> weird way (which it has done before). It was raining when I got up in 
>>> the 
>>> AM, 1/2 inch collected already. After about 3/4in, it POURED and the 
>>> rain 
>>> rate slowed to something like .07in/hour. I replaced the rain gauge 
>>> (with 
>>> the Davis rehab kit) last fall and went out in the downpour to check 
>>> the 
>>> bucket/collector. No blockages, not full of water...
>>>
>>> My next door neighbor's device report 2.19" of rain when it ended 
>>> that day. Mine reported 1.90", however it continued to report .01 or 
>>> .02 
>>> clicks at a time until it finally stopped at .42" the next day 
>>> (although we 
>>> had no rainfall) for a storm total of 2.32", not terribly far off from 
>>> my 
>>> neighbor's 2.19".  I have attached the chart that illustrates the slow 
>>> collection- as if the collection was full of water that slowly leaked 
>>> out 
>>> (can't be the case). 
>>>
>>> The very next day we had a brief, heavy thunderstorm. Both my 
>>> neighbor and I reported the same .30" for the even[image: 
>>> Screenshot2023-04-24.png]t.
>>>
>>> Weewx  4.9.1
>>> Vantage Vue with an IPconnect.  
>>>
>>> We're looking at another 1-3" of rain this weekend, and I'd love to 
>>> hear any suggestions!
>>>
>>> Thanks,
>>> Steve
>>>
>>> -- 
>>> 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 weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
> -- 
> 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 weewx-user+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%40googlegroups.com
>  
> 
> .
>
>
> 

Re: [weewx-user] VantageVue rain collector delay

[bgra...@umw.edu]

I think Graham has the answer. About twice a year, squirrels crack nuts 
into my rain gauge funnel and I get the slow drip.
It must be a very uncomfortable task with all the bird spikes around the 
outside…
Cheers,
Bob
grattans.org/wx

On Monday, May 1, 2023 at 7:28:56 AM UTC-4 Paul R Anderson wrote:

> Very strange blocked rain funnel would be the number one suspect. Only 
> other thing that comes to mind is residual 'rain' falling from a tree 
> canopy, or any other object that could hold rain droplets, and release them 
> long after the rain shower has ended. Wondering if any trees have started 
> to encroach on the area above your rain gauge?
>
> Paul
>
> On Mon, May 1, 2023 at 7:03 AM Steve C  wrote:
>
>> I removed it again yesterday and checked the tip bucket and entrance and 
>> exit paths for blockages but found none. The rain ended several hours ago, 
>> but my Vue is still counting .01" every few minutes this morning.
>>
>> http://livefreeorpi.com 
>>
>> On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
>>
>>> I remember such behavior when a spider let the remains of her meals drop 
>>> into the rain bucket.
>>>
>>> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>>>
 is the outlet from rain bucket partially blocked?
 *⊣GE⊢*

 On 29 Apr 2023, at 11:48 pm, Steve C  wrote:

 Important distinction! I meant to mention that. Yes, the software seems 
 perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it 
 accordingly. Being a hardware issue I can move this to a Davis forum if it 
 is inappropriate here. 

 On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:

>  What does the console show?
>
> On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:
>
>> Sorry for the long post, but the details might matter. We had a 
>> significant rain event last weekend and my rain gauge responded in a 
>> very 
>> weird way (which it has done before). It was raining when I got up in 
>> the 
>> AM, 1/2 inch collected already. After about 3/4in, it POURED and the 
>> rain 
>> rate slowed to something like .07in/hour. I replaced the rain gauge 
>> (with 
>> the Davis rehab kit) last fall and went out in the downpour to check the 
>> bucket/collector. No blockages, not full of water...
>>
>> My next door neighbor's device report 2.19" of rain when it ended 
>> that day. Mine reported 1.90", however it continued to report .01 or .02 
>> clicks at a time until it finally stopped at .42" the next day (although 
>> we 
>> had no rainfall) for a storm total of 2.32", not terribly far off from 
>> my 
>> neighbor's 2.19".  I have attached the chart that illustrates the slow 
>> collection- as if the collection was full of water that slowly leaked 
>> out 
>> (can't be the case). 
>>
>> The very next day we had a brief, heavy thunderstorm. Both my 
>> neighbor and I reported the same .30" for the even[image: 
>> Screenshot2023-04-24.png]t.
>>
>> Weewx  4.9.1
>> Vantage Vue with an IPconnect.  
>>
>> We're looking at another 1-3" of rain this weekend, and I'd love to 
>> hear any suggestions!
>>
>> Thanks,
>> Steve
>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
>>  
>> 
>> .
>>
>
 -- 
 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 weewx-user+...@googlegroups.com.

 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%40googlegroups.com
  
 
 .


 -- 
>> 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 weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/8bed9005-ec36-4258-8acd-0d392c00d0a1n%40googlegroups.com
>>  
>> 
>> 

Re: [weewx-user] VantageVue rain collector delay

[Paul R Anderson]

Very strange blocked rain funnel would be the number one suspect. Only
other thing that comes to mind is residual 'rain' falling from a tree
canopy, or any other object that could hold rain droplets, and release them
long after the rain shower has ended. Wondering if any trees have started
to encroach on the area above your rain gauge?

Paul

On Mon, May 1, 2023 at 7:03 AM Steve C  wrote:

> I removed it again yesterday and checked the tip bucket and entrance and
> exit paths for blockages but found none. The rain ended several hours ago,
> but my Vue is still counting .01" every few minutes this morning.
>
> http://livefreeorpi.com
>
> On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:
>
>> I remember such behavior when a spider let the remains of her meals drop
>> into the rain bucket.
>>
>> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>>
>>> is the outlet from rain bucket partially blocked?
>>> *⊣GE⊢*
>>>
>>> On 29 Apr 2023, at 11:48 pm, Steve C  wrote:
>>>
>>> Important distinction! I meant to mention that. Yes, the software seems
>>> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it
>>> accordingly. Being a hardware issue I can move this to a Davis forum if it
>>> is inappropriate here.
>>>
>>> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>>>
  What does the console show?

 On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:

> Sorry for the long post, but the details might matter. We had a
> significant rain event last weekend and my rain gauge responded in a very
> weird way (which it has done before). It was raining when I got up in the
> AM, 1/2 inch collected already. After about 3/4in, it POURED and the rain
> rate slowed to something like .07in/hour. I replaced the rain gauge (with
> the Davis rehab kit) last fall and went out in the downpour to check the
> bucket/collector. No blockages, not full of water...
>
> My next door neighbor's device report 2.19" of rain when it ended that
> day. Mine reported 1.90", however it continued to report .01 or .02 clicks
> at a time until it finally stopped at .42" the next day (although we had 
> no
> rainfall) for a storm total of 2.32", not terribly far off from my
> neighbor's 2.19".  I have attached the chart that illustrates the slow
> collection- as if the collection was full of water that slowly leaked out
> (can't be the case).
>
> The very next day we had a brief, heavy thunderstorm. Both my neighbor
> and I reported the same .30" for the even[image:
> Screenshot2023-04-24.png]t.
>
> Weewx  4.9.1
> Vantage Vue with an IPconnect.
>
> We're looking at another 1-3" of rain this weekend, and I'd love to
> hear any suggestions!
>
> Thanks,
> Steve
>
> --
> 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 weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
> 
> .
>

>>> --
>>> 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 weewx-user+...@googlegroups.com.
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%40googlegroups.com
>>> 
>>> .
>>>
>>>
>>> --
> 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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/8bed9005-ec36-4258-8acd-0d392c00d0a1n%40googlegroups.com
> 
> .
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAOAVAefq4iT8ij-Xy0%3D%3D9zcCs_U_HUe16OLq8wtcz4E2MFqM-g%40mail.gmail.com.

Re: [weewx-user] VantageVue rain collector delay

[Steve C]

I removed it again yesterday and checked the tip bucket and entrance and 
exit paths for blockages but found none. The rain ended several hours ago, 
but my Vue is still counting .01" every few minutes this morning.

http://livefreeorpi.com 

On Sunday, April 30, 2023 at 1:27:57 PM UTC-4 Karen K wrote:

> I remember such behavior when a spider let the remains of her meals drop 
> into the rain bucket.
>
> Graham Eddy schrieb am Sonntag, 30. April 2023 um 02:46:00 UTC+2:
>
>> is the outlet from rain bucket partially blocked?
>> *⊣GE⊢*
>>
>> On 29 Apr 2023, at 11:48 pm, Steve C  wrote:
>>
>> Important distinction! I meant to mention that. Yes, the software seems 
>> perfectly fine. The console is reporting the 'slow drip' and WeeWX logs it 
>> accordingly. Being a hardware issue I can move this to a Davis forum if it 
>> is inappropriate here. 
>>
>> On Saturday, April 29, 2023 at 9:42:42 AM UTC-4 Tom Keffer wrote:
>>
>>>  What does the console show?
>>>
>>> On Sat, Apr 29, 2023 at 6:27 AM Steve C  wrote:
>>>
 Sorry for the long post, but the details might matter. We had a 
 significant rain event last weekend and my rain gauge responded in a very 
 weird way (which it has done before). It was raining when I got up in the 
 AM, 1/2 inch collected already. After about 3/4in, it POURED and the rain 
 rate slowed to something like .07in/hour. I replaced the rain gauge (with 
 the Davis rehab kit) last fall and went out in the downpour to check the 
 bucket/collector. No blockages, not full of water...

 My next door neighbor's device report 2.19" of rain when it ended that 
 day. Mine reported 1.90", however it continued to report .01 or .02 clicks 
 at a time until it finally stopped at .42" the next day (although we had 
 no 
 rainfall) for a storm total of 2.32", not terribly far off from my 
 neighbor's 2.19".  I have attached the chart that illustrates the slow 
 collection- as if the collection was full of water that slowly leaked out 
 (can't be the case). 

 The very next day we had a brief, heavy thunderstorm. Both my neighbor 
 and I reported the same .30" for the even[image: 
 Screenshot2023-04-24.png]t.

 Weewx  4.9.1
 Vantage Vue with an IPconnect.  

 We're looking at another 1-3" of rain this weekend, and I'd love to 
 hear any suggestions!

 Thanks,
 Steve

 -- 
 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 weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/f4c19b77-1dd3-4573-9bec-ac5098a68158n%40googlegroups.com
  
 
 .

>>>
>> -- 
>> 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 weewx-user+...@googlegroups.com.
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/47944903-4d2a-4ca7-94d9-a3e0add0fd86n%40googlegroups.com
>>  
>> 
>> .
>>
>>
>>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8bed9005-ec36-4258-8acd-0d392c00d0a1n%40googlegroups.com.

[weewx-user] Re: weewx-sdr driver modified for rtl-sdr plus extra ttyACM1 input; getting gaps

[William Garber]

Until now the Atlas emitted NEW_LOOP_PACKET events about every 7 seconds, 
so I had my indoor weather data arduino (wpa) set to emit at the same 
interval.  I just sped that up to every 3 seconds (just the wpa emitter).  
You can "$ cat /dev/ttyACMwa" which prints the serial data output over usb 
from the arduino (wpa) directly to the linux console.  That shows (the  new 
interval) is 3 seconds.  I will run it over a long time to see if there are 
any long intervals.  But what I suspect is happening is ... I have three 
weather stations.  I built two with Adafruit parts plus the indoors part of 
this one (wpa/Atlas).  The "merged" reports are run as a fourth instance of 
weewx which is not the server, just "wee_reports_merge" which is just 
"wee_report" with the configuration file for the merged report.  The worst 
thing is that this was being run every 90 seconds (DUH).  I slowed it down 
to every 10 minutes.  The archive interval for Atlas/wpa is 5 minutes.  

The hard part was reading the serial port to get the inside data (one line 
of json data).
(1) flush input buffer
(2) read discard first line in case it is partial
(3) read next line or timeout
the readline() commands are blocking with timeout.  Not sure how to do non 
blocking but see this discussion:
https://stackoverflow.com/questions/1093598/pyserial-how-to-read-the-last-line-sent-from-a-serial-device
they all seem to think that at least part of the procedure is blocking (not 
all !)

it works so far.  will leave it to run overnightservice 
attached. service processes  inside data in NEW_LOOP_PACKET as you 
described.  weewx uses service plus original unmodified weewx-sdr.py driver 
for outside data.

On Sunday, April 30, 2023 at 4:47:56 PM UTC-7 gjr80 wrote:

> On Sunday, 30 April 2023 at 13:42:56 UTC+10 william...@att.net wrote:
>
> Just one question please :-).  Suppose the read of the arduino could 
> possibly take a relatively long time, and you want to have a timeout after 
> which it gives up and saves None/NULL for the indoor data.  
>
> What is the max timeout that would be reasonable relative to the archive 
> interval ?
>
>  
> I would be more concerned about the loop packet interval than the archive 
> interval. Your initial post indicated the Atlas emits packets every 7 
> seconds so the SDR driver will be emitting loop packets every 7 odd 
> seconds. If you have a plain vanilla WeeWX install WeeWX will not be doing 
> much else during the loop packet interval other than calculating derived 
> obs so dwelling for up to, say, a second should have no significant effect. 
>
> What happens if the delay goes past the end of the main archive interval 
> the event you are handling was in?
>
>  
> Delaying past the end of the archive interval will not have a significant 
> impact (within reason). Say your service delays 20 seconds past the end of 
> the archive period, when the driver gets it's turn again it will emit 
> another loop packet which will cause an archive record to be generated by 
> WeeWX and ultimately the report cycle is run maybe 20+ seconds later than 
> usual (note the exact behaviour of the driver is very much driver 
> dependent; some drivers may skip loop packets, others may emit a loop 
> packet immediately and yet others may delay emitting a loop packets - the 
> SDR driver is threaded and I believe it is the former). So really you will 
> probably only noticed delayed report output.
>
> Where you will probably get more problems from delaying the WeeWX main 
> loop is in the generation/processing of loop packets. As mentioned above 
> driver behaviour varies from driver to driver. For example, the vantage 
> driver obtains loop packets every 2 odd seconds; if a loop packet is missed 
> it is gone forever. Other drivers poll the hardware much less frequently, 
> say every 50 odd seconds, in that case there could be an entire minute 
> might go by with no data. The consequences of a missed loop packet depends 
> on the system config. A vantage station with a five minute archive interval 
> would see around 120 loop packets per archive period, so the loss of one 
> loop packet will have no real impact. Consider the second system with loop 
> packets arriving every, say, 50 seconds; if it had an archive interval of 
> one minute, you could conceivably see no loop packets in an archive 
> interval and hence no archive record is generated and no report cycle 
> occurs.
>  
> Remember loop packet data is accumulated by WeeWX and many obs in the 
> resulting archive record are simply the average value of the obs from all 
> loop packets seen during the archive interval. So for slow changing obs, 
> such as air temperature/atmospheric pressure, losing the odd loop packet 
> during an archive interval will have no real impact on the archive record 
> data provided there are numerous other loop packets received in the archive 
> interval. This may not be the case for rapidly changing obs such as wind 
> speed and