My apologies. I probably could have phrased that better. You are correct 
that VP2s can generate windchill via hardware; however, an older unit like 
mine with older firmware doesn't send the windchill value in the LOOP 
packets.  

On Tuesday, January 3, 2023 at 9:39:03 AM UTC-5 [email protected] wrote:

> > Tom and Gary confirmed that the VP2 hardware generated values for 
> windchill are only available in the LOOP2 packets.
>
> I’m not sure why you think that is relevant.  The question is, whether 
> software or hardware generated, do the loop packets have windchill.  I 
> confirmed they do contain windchill (for my VP2) before my initial reply.
>
> On Jan 3, 2023, at 6:06 AM, Steve Schindler <[email protected]> wrote:
>
> 
>
> Thanks for the suggestion but I don't think that's the issue with my 
> setup.  In a previous discussion (
> https://groups.google.com/g/weewx-user/c/roOG0u8YPX4/m/Tc4vWnznAgAJ), Tom 
> and Gary confirmed that the VP2 hardware generated values for windchill are 
> only available in the LOOP2 packets.
>
> -------
> [email protected]
> Jul 24, 2020, 8:21:48 PM
>
> to weewx-user
> Geez, Gary, you're right! So, you would also have to specify LOOP2 
> packets. See the section [Vantage] 
> <http://www.weewx.com/docs/usersguide.htm#[Vantage]> in the User's Guide.
>
> [Vantage]
>   loop_request = 2
>
>
> -tk
>
> On Fri, Jul 24, 2020 at 5:13 PM gjr80 <[email protected] 
> <https://groups.google.com/>> wrote:
> Windchill is only in included in the Davis LOOP2 packet, it’s not in the 
> LOOP packet or archive record (the defaults) from the console. So unless 
> you have set WeeWX to use the LOOP2 packet WeeWX will never see windchill 
> from the console, irrespective of StdWXCalculate settings.
>
> Gary
> -------
>
> And the User's Guide states "Not all stations support LOOP2 data. You need 
> firmware version 1.90 or later."
>
> So I don't think the loop_hilo parameter will affect the windchill value 
> with my setup.
>
>
> On Saturday, December 31, 2022 at 1:07:01 PM UTC-5 [email protected] 
> wrote:
>
>> Tom and friends will know for sure, but I believe the low you are seeing 
>> (at 07:31) is from the archive_day_windchill table.
>>
>> You likely have the following in your weewx.conf
>>     # Whether to include LOOP data in hi/low statistics
>>     loop_hilo = True
>>
>> This tells weewx (well, it tells it to do exactly what the comment says). 
>>  Note: vantage loop packets do indeed include windchill.
>>
>> The archive table (produced from vantage archive records) does not 
>> include this low and the graphs are produced from archive records.
>>
>> I don’t think you are seeing anything *wrong*.
>>
>> Note: these highs and lows in the daily stats get wiped out if you run 
>> wee_database —rebuild-daily (which is unfortunate).
>>
>> On Dec 31, 2022, at 9:21 AM, Steve Schindler <[email protected]> wrote:
>>
>> During the recent cold weather, I noticed a discrepancy between the 
>> windchill minimum value in the table and the value/time shown on the graph. 
>> For 12-24-22, the Low Wind Chill in the Since Midnight table is 23.6F at 
>> 07:31, but the graph doesn't reflect that value. It shows a low of about 
>> 27F at about 8:00. For 12-25-22, the temperature discrepancy is about the 
>> same but time difference is greater. See the screenshots below. All other 
>> values (temp, humidity, wind) agree between the table and the graphs.
>>
>>
>>
>> I'm using a Davis VP2 with firmware version 1.82 so WeeWX is calculating 
>> the windchill value. 
>>
>> Any thoughts on what's happening and how it can be corrected?
>>
>> I'm in Florida so my troubleshooting/testing opportunities are limited to 
>> when a cold front passes through. However, I suspect that heat index has 
>> the same problem and, if so, I'll have plenty of time to work on that that 
>> this summer. :-)
>>
>> 12-24
>>
>> <wx 2022-12-24 20:42:02.png>
>>
>>
>> 12-25
>>
>> <wx 2022-12-25 20:56:20.png>
>>
>> -- 
>> 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].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/183e065c-2fc6-4b2b-aaff-99ec35fa8ca1n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>> <wx 2022-12-25 20:56:20.png>
>>
>> <wx 2022-12-24 20:42:02.png>
>>
>> -- 
> 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].
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/70448a2d-6bfb-4e85-9e56-97f489dbf515n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/70448a2d-6bfb-4e85-9e56-97f489dbf515n%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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/906d57be-209b-429c-b235-4f52e55e8c62n%40googlegroups.com.

Reply via email to