Thanks. Posted in weewx-development group also.
On Mon, 29 Jul 2019 at 16:11, Andrew Milner
wrote:
> I suspect there is some history involved. As far as I can make out, if
> LOOP2 data were to be read then the packets are alternated with LOOP -
> which would result in LOOP packets being receive
I suspect there is some history involved. As far as I can make out, if
LOOP2 data were to be read then the packets are alternated with LOOP -
which would result in LOOP packets being received every 5 seconds instead
of every 2.5 seconds - perhaps that is why they are not being read!!! As
to w
Understand that weewx does not read LOOP2 packets. Did not get the part
about " LOOP2 data is more than likely software generated by weewx"
The LOOP2 packet format is specified in Davis protocol and it seems to be
containing some data that WU is expecting. Shouldnt weewx be reading it
then? Not su
slight correction - the LOOP2 data is more than likely software generated
by weewx
On Monday, 29 July 2019 13:18:22 UTC+3, Andrew Milner wrote:
>
> I do not think weewx reads LOOP2 packets - so none of the LOOP2 data is
> available.
>
>
>
> On Monday, 29 July 2019 12:54:52 UTC+3, Praveen Chandra
I do not think weewx reads LOOP2 packets - so none of the LOOP2 data is
available.
On Monday, 29 July 2019 12:54:52 UTC+3, Praveen Chandrasekaran wrote:
>
> Looking at below:
>
>
> https://feedback.weather.com/customer/en/portal/articles/2924682-pws-upload-protocol?b_id=17298
>
>
> WU expects
Looking at below:
https://feedback.weather.com/customer/en/portal/articles/2924682-pws-upload-protocol?b_id=17298
WU expects wind speed average over 2 min average and 10 min gusts and
instantaneous speed. Did something change in this recently? Looking at
weewx code from restx.py I am not sure if
Hmm. Will try. Before the WU overhaul it was showing them separately on the
graph though. The gust value from LOOP2 seems to be 10 min wind gust while
the wind speed sent out is the instantaneous wind speed from LOOP packet I
believe? This may explain why wind speed and wind gust are same in graph.
I really do not see how you can have a meaningful gust value from readings
submitted every few seconds!! I see from the Davis comms protocol the gust
values are in LOOP2 packets and the smallest appears to be a 2 minute gust
value.
Setting debug=1 may shed more light on what is actually being
My weather station is Davis Vantage Vue. I believe it never emits partial
packets.
On Friday, 26 July 2019 15:02:51 UTC+5:30, Andrew Milner wrote:
>
> i doubt it very much. what weather station do you have?
> changing the rf frequency changes the upload to wu interval but the
> station will sti
i doubt it very much. what weather station do you have?
changing the rf frequency changes the upload to wu interval but the station
will still be being polled as before. Does the station provide the gust
value in the LOOP data? If not then the gust value is an artificial one
created by weewx
i would doubt it very much but you could try. it certainly would not help
it if wu just ignores gust from rf feeds anyway.
On Friday, 26 July 2019 10:42:14 UTC+3, Praveen Chandrasekaran wrote:
>
> If I set rtfreq to a higher value like 5 seconds, should that resolve the
> issue?
>
> On Fri, 26
If I set rtfreq to a higher value like 5 seconds, should that resolve the
issue?
On Fri, 26 Jul 2019 at 11:57, Andrew Milner
wrote:
> if from rf it has no gusts it cannot graph them. non rf sites will
> provide a gust value per archive interval. who knows what wu do when they
> receive both rf
if from rf it has no gusts it cannot graph them. non rf sites will provide
a gust value per archive interval. who knows what wu do when they receive
both rf and archive record data!! The tables may well create an artificial
gust value from rf speeds, but again who knows what wu use to create
The table somehow has it right. The graph alone is wrong.
On Fri, 26 Jul 2019 at 11:29, Andrew Milner
wrote:
> I would suspect WU ignore windgust on rapidfire because you need a
> sustained period of I think 3 seconds for the gust to count as a gust in
> metereological definitions - and the rf i
I would suspect WU ignore windgust on rapidfire because you need a
sustained period of I think 3 seconds for the gust to count as a gust in
metereological definitions - and the rf interval is probably too short - so
gust will always equal speed in rf situations.
On Friday, 26 July 2019 08:26:
Related wxforum post:
https://www.wxforum.net/index.php?topic=36611.msg386071#msg386071
On Friday, 26 July 2019 10:45:52 UTC+5:30, Praveen Chandrasekaran wrote:
>
> Hi,
>
> I am seeing that on stations with rapdifire, WU is not differentiating
> wind speed and wind gust in graph correctly. Howe
16 matches
Mail list logo
