For more info on loop2 the davis portal document <https://www.davisinstruments.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf> is the definitive word on the fields and their definition. Forgot that I have a little test file that shows what you get from Loop2:
ALL LOOP2 DATA trendIcon -20.000000 barometer 29.913 inHg inTemp 73.8F inHumidity 63% outTemp 65.1F windSpeed 1 mph windDir 338 windSpeed10 2 mph windSpeed2 2.000000 windGust10 0.900000 windGustDir10 67.000000 dewpoint 62.0F outHumidity 89% heatindex 66.0F windchill 65.0F THSW 64.0F rainRate 0.00 in/h UV 0.0 radiation 0 W/m stormRain 0.00 in stormStart ?'stormStart'? dayRain 0.00 in rain15 0.000000 hourRain 0.00 in dayET 0.038000 rain24 0.00 in bar_reduction 0.002000 bar_offset 0.028000 bar_calibration 17.606000 pressure_raw 29.716000 pressure 29.744 inHg altimeter 29.918 inHg Paul On Sun, Aug 16, 2020 at 8:06 PM Paul R Anderson <[email protected]> wrote: > Alternative method would be to set Vantage driver loop_request to 3 so > that you would get loop1 and loop2 data. Vantage loop2 provides dewpoint to > 1 decimal point . Please review User Guide > <http://www.weewx.com/docs/usersguide.htm#[Vantage]> and be sure you > understand how to set it up , further changes are required. > > On a system here that is set up to alternate loop1 and loop2 here is a > database query for dewpoint: > > sqlite> select datetime(dateTime,'unixepoch','localtime'),dewpoint from > archive ORDER BY datetime desc limit 10; > 2020-08-16 20:00:00|62.0 > 2020-08-16 19:55:00|62.0 > 2020-08-16 19:50:00|62.0 > 2020-08-16 19:45:00|62.0 > 2020-08-16 19:40:00|62.0 > 2020-08-16 19:35:00|62.0 > 2020-08-16 19:30:00|62.0 > 2020-08-16 19:25:00|62.0 > 2020-08-16 19:20:00|62.0 > 2020-08-16 19:15:00|62.0 > > Paul > > On Sun, Aug 16, 2020 at 7:24 PM Tom Keffer <[email protected]> wrote: > >> Archive records are what are stored in the database. A Vantage station >> produces its own archive record (unless record_generation is set to >> 'software'). However, for whatever reason, Vantage stations do not include >> dewpoint in the hardware generated record, so WeeWX must calculate it. By >> default, WeeWX calculates the average dewpoint seen over the archive >> interval. If dewpoint changes over the interval, the average is not >> necessarily an even number. >> >> One way around this is to have WeeWX calculate the last value seen, >> instead of the average. Add this to the end of your weewx.conf file: >> >> [Accumulator] >> [[dewpoint]] >> extractor = last >> >> Alternatively, what sort of external programs are you writing? Does the >> language you are using provide a way to format decimal output? >> >> -tk >> >> >> On Sun, Aug 16, 2020 at 3:16 PM [email protected] <[email protected]> >> wrote: >> >>> Hi, >>> >>> I searched the group for this subject and couldn't find anything so I am >>> posting. >>> >>> I have the Vantage Pro 2, serial interface to Weewx 3.9.2 run on an >>> Ubuntu server. >>> >>> Below is a sample line from the archive database (broke into individual >>> lines due to width) using the command: >>> sqlite3 -header -csv /var/lib/weewx/weewx.sdb "select * from archive;" >>> >>> One line from the output: >>> 1597612740,1,1,29.617,28.0238601652778,29.7814033867068,83.7,*115.4*, >>> 38.0,18.0,0.0,,1.0,225.0,0.0,0.0,*61.1737982063856*,115.4, >>> 115.4,0.0,,,,,,,,,,,,,,,,,,,,93.9583333333333,0.0,5.31,,,,,,,,,, >>> >>> Note the temperature is reported as 115.4 degs (ugh...this is Arizona). >>> The dewpoint is reported as 61.1737982063856. All dewpoint values in the >>> database have a decimal precision of 13 places, clearly outside the sensor >>> quality range. The sensor documentation indicates that it provides Relative >>> Humidity values so apparently the console software derives the dewpoint >>> value as it can be displayed on the console. I write a lot of external >>> programs and have to repeatedly reduce the precision for this variable. >>> >>> Is there an easy way to modify my Weewx to store only 1 decimal place >>> for dewpoint or other variables? I did check /etc/weewx/weewx.conf and >>> could not find any obvious setting for this. >>> >>> Thanks for any assistance, >>> >>> Ken >>> >>> -- >>> 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/20d1b87c-afd9-4f1c-b00c-88f9011057d8n%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-user/20d1b87c-afd9-4f1c-b00c-88f9011057d8n%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/CAPq0zEBuz-FwYAt2z6YT4mZ39WipiBhLny4zwnbd3FZYkRci1Q%40mail.gmail.com >> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBuz-FwYAt2z6YT4mZ39WipiBhLny4zwnbd3FZYkRci1Q%40mail.gmail.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/CAOAVAedm96Wsefa2t_zmd-te2VnuLDtrOTcO7tQpocrDJRarrw%40mail.gmail.com.
