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 Chandrasekaran wrote:
>>
>> 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 weewx uploads all these? 
>>
>> https://github.com/weewx/weewx/blob/master/bin/weewx/restx.py  
>>
>> winddir - [0-360 instantaneous wind direction]
>> windspeedmph - [mph instantaneous wind speed]
>> windgustmph - [mph current wind gust, using software specific time period]
>> windgustdir - [0-360 using software specific time period]
>> windspdmph_avg2m  - [mph 2 minute average wind speed mph]
>> winddir_avg2m - [0-360 2 minute average wind direction]
>> windgustmph_10m - [mph past 10 minutes wind gust mph ]
>> windgustdir_10m - [0-360 past 10 minutes wind gust direction]
>>
>>
>> On Mon, 29 Jul 2019 at 15:10, Praveen Chandrasekaran <prave...@gmail.com> 
>> wrote:
>>
>>> 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. But then how does the table have different values. U never know with 
>>> WU! :)  
>>>
>>> As you mentioned will set debug=1 and observe sometime.  
>>>
>>> On Mon, 29 Jul 2019 at 12:29, Andrew Milner <andrew....@gmail.com> 
>>> wrote:
>>>
>>>> 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 sent to WU
>>>>
>>>>
>>>>
>>>> On Monday, 29 July 2019 09:24:19 UTC+3, Praveen Chandrasekaran wrote:
>>>>>
>>>>> 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 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 from loop records wind speeds received.  If your 
>>>>>> station provides partial packets as LOOP data you could always try and 
>>>>>> set 
>>>>>> the wu flag that set specifies windGust must be present before rf is 
>>>>>> uploaded
>>>>>>
>>>>>> 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 Jul 2019 at 11:57, Andrew Milner <andrew....@gmail.com> 
>>>>>>> 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 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 graphs!!
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Friday, 26 July 2019 09:01:30 UTC+3, Praveen Chandrasekaran 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> The table somehow has it right. The graph alone is wrong.
>>>>>>>>>
>>>>>>>>> On Fri, 26 Jul 2019 at 11:29, Andrew Milner <andrew....@gmail.com> 
>>>>>>>>> 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 interval is probably too 
>>>>>>>>>> short - so 
>>>>>>>>>> gust will always equal speed in rf situations.  
>>>>>>>>>>
>>>>>>>>>> On Friday, 26 July 2019 08:26:49 UTC+3, Praveen Chandrasekaran 
>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> 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. 
>>>>>>>>>>>> However in 
>>>>>>>>>>>> stations without rapidfire it is fine.
>>>>>>>>>>>>
>>>>>>>>>>>> Example my station with rapidfire:
>>>>>>>>>>>>
>>>>>>>>>>>> https://www.wunderground.com/dashboard/pws/IBANGALO9
>>>>>>>>>>>>
>>>>>>>>>>>> Another station without rapidfire:
>>>>>>>>>>>>
>>>>>>>>>>>> https://www.wunderground.com/dashboard/pws/IMUMBAI16
>>>>>>>>>>>>
>>>>>>>>>>>> Is this issue arising from weewx by any chance?
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Praveen
>>>>>>>>>>>>
>>>>>>>>>>> -- 
>>>>>>>>>> You received this message because you are subscribed to a topic 
>>>>>>>>>> in the Google Groups "weewx-user" group.
>>>>>>>>>> To unsubscribe from this topic, visit 
>>>>>>>>>> https://groups.google.com/d/topic/weewx-user/E5uzJiv_ThY/unsubscribe
>>>>>>>>>> .
>>>>>>>>>> To unsubscribe from this group and all its topics, send an email 
>>>>>>>>>> to weewx...@googlegroups.com.
>>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>>> https://groups.google.com/d/msgid/weewx-user/51caf745-7385-40f9-ad35-81cfed29553e%40googlegroups.com
>>>>>>>>>>  
>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/51caf745-7385-40f9-ad35-81cfed29553e%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>> -- 
>>>>>>>> You received this message because you are subscribed to a topic in 
>>>>>>>> the Google Groups "weewx-user" group.
>>>>>>>> To unsubscribe from this topic, visit 
>>>>>>>> https://groups.google.com/d/topic/weewx-user/E5uzJiv_ThY/unsubscribe
>>>>>>>> .
>>>>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>>>>> weewx...@googlegroups.com.
>>>>>>>> To view this discussion on the web visit 
>>>>>>>> https://groups.google.com/d/msgid/weewx-user/e1c86274-2f2a-4005-a3e3-8ac0d9028b66%40googlegroups.com
>>>>>>>>  
>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/e1c86274-2f2a-4005-a3e3-8ac0d9028b66%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>> .
>>>>>>>>
>>>>>>> -- 
>>>> You received this message because you are subscribed to a topic in the 
>>>> Google Groups "weewx-user" group.
>>>> To unsubscribe from this topic, visit 
>>>> https://groups.google.com/d/topic/weewx-user/E5uzJiv_ThY/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to 
>>>> weewx...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/7d2e07d8-d98a-41b3-a3b4-0c9cdcea6f25%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/7d2e07d8-d98a-41b3-a3b4-0c9cdcea6f25%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>

-- 
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/38ff484c-9cde-46b0-90f0-d41857ccb061%40googlegroups.com.

Reply via email to