Tom Mine seems to be correct:
*+ Options* <http://rpi3/phpmyadmin/import.php#displayoptions> Partial texts Full texts Relational key Relational display column Show binary contents Show BLOB contents Show binary contents as HEX Hide browser transformation Geometry Well Known Text Well Known Binary *dt [image: Descending] [image: Ascending] **1* <http://rpi3/phpmyadmin/sql.php?db=archive&table=archive_day_windSpeed&sql_query=SELECT+archive_day_windSpeed.dateTime+as+dt%2C+date%28archive_day_windSpeed.dateTime%29%2C+archive_day_windSpeed.max%2C+archive_day_windGust.max%0AFROM+archive_day_windSpeed%0AINNER+JOIN+archive_day_windGust%0AON+archive_day_windSpeed.dateTime%3Darchive_day_windGust.dateTime%0AORDER+BY+%60archive_day_windSpeed%60.%60dt%60++ASC+limit+20&session_max_rows=25&token=2e8c6022d2ac257794ad912c5f716495> *date(archive_day_windSpeed.dateTime)* <http://rpi3/phpmyadmin/sql.php?db=archive&table=archive_day_windSpeed&sql_query=SELECT+archive_day_windSpeed.dateTime+as+dt%2C+date%28archive_day_windSpeed.dateTime%29%2C+archive_day_windSpeed.max%2C+archive_day_windGust.max%0AFROM+archive_day_windSpeed%0AINNER+JOIN+archive_day_windGust%0AON+archive_day_windSpeed.dateTime%3Darchive_day_windGust.dateTime+limit+20&session_max_rows=25&token=2e8c6022d2ac257794ad912c5f716495> *max* <http://rpi3/phpmyadmin/sql.php?db=archive&table=archive_day_windSpeed&sql_query=SELECT+archive_day_windSpeed.dateTime+as+dt%2C+date%28archive_day_windSpeed.dateTime%29%2C+archive_day_windSpeed.max%2C+archive_day_windGust.max%0AFROM+archive_day_windSpeed%0AINNER+JOIN+archive_day_windGust%0AON+archive_day_windSpeed.dateTime%3Darchive_day_windGust.dateTime%0AORDER+BY+%60archive_day_windSpeed%60.%60max%60+ASC+limit+20&session_max_rows=25&token=2e8c6022d2ac257794ad912c5f716495> *max* <http://rpi3/phpmyadmin/sql.php?db=archive&table=archive_day_windSpeed&sql_query=SELECT+archive_day_windSpeed.dateTime+as+dt%2C+date%28archive_day_windSpeed.dateTime%29%2C+archive_day_windSpeed.max%2C+archive_day_windGust.max%0AFROM+archive_day_windSpeed%0AINNER+JOIN+archive_day_windGust%0AON+archive_day_windSpeed.dateTime%3Darchive_day_windGust.dateTime%0AORDER+BY+%60archive_day_windGust%60.%60max%60+ASC+limit+20&session_max_rows=25&token=2e8c6022d2ac257794ad912c5f716495> 1484258400 *NULL* 23.4000581604882 27.0001342166779 1484172000 *NULL* 29.5200733716927 33.1201646391249 1484085600 *NULL* 19.440048317944 24.480121689788 1483999200 *NULL* 58.6801458486088 68.4003400155841 1483912800 *NULL* 34.2000850037904 42.840212957129 1483826400 *NULL* 34.2000850037904 41.7602075884619 1483740000 *NULL* 41.7601037941019 51.4802559064659 1483653600 *NULL* 21.9600545813812 25.5601270584551 1483567200 *NULL* 31.6800787403532 37.8001879033491 1483480800 *NULL* 17.2800429492836 20.8801037942309 1483394400 *NULL* 27.0000671082556 33.1201646391249 1483308000 *NULL* 36.7200912672276 47.8802380109088 1483221600 *NULL* 17.2800429492836 20.8801037942309 1483135200 *NULL* 37.8000939515578 46.440230852686 1483048800 *NULL* 35.6400885828973 43.9202183257961 1482962400 *NULL* 51.4801279530739 70.920352542474 1482876000 *NULL* 36.7200912672276 42.840212957129 1482789600 *NULL* 41.7601037941019 60.1202988558028 1482703200 *NULL* 36.7200912672276 45.3602254840189 1482616800 *NULL* 18.3600456336138 20.8801037942309 hard to see the columns, but they are different. I have a fineoffset, using fousb - but weewx seems to have handled things correctly. I messed up getting the date correct in MySQL though from your sql statement!!! On Friday, 13 January 2017 16:53:55 UTC+2, Tom Keffer wrote: > Marked as issue #195 <https://github.com/weewx/weewx/issues/195>. > > -tk > > On Fri, Jan 13, 2017 at 6:49 AM, Thomas Keffer <[email protected] > <javascript:>> wrote: > >> "dwhile" I have been able to replicate the problem where >> archive_day_windSpeed.max is always equal to archive_day_windGust.max. Let >> me dig into it deeper. >> >> -tk >> >> On Fri, Jan 13, 2017 at 6:48 AM, dwhile839 via weewx-user < >> [email protected] <javascript:>> wrote: >> >>> Ok Added that code and turned debug on. Will monitor to see if it occurs. >>> >>> Interestingly the following appears: >>> >>> Jan 13 14:46:50 weather weewx[8513]: wmr100: Bad USB report received. >>> Jan 13 14:46:50 weather weewx[8513]: ***** could not detach kernel >>> driver from interface 0: No data available >>> Jan 13 14:46:55 weather weewx[8513]: wmr100: Bad USB report received. >>> Jan 13 14:46:55 weather weewx[8513]: ***** tuple index out of range >>> Jan 13 14:47:00 weather weewx[8513]: wmr100: Bad USB report received. >>> Jan 13 14:47:00 weather weewx[8513]: ***** tuple index out of range >>> Jan 13 14:47:05 weather weewx[8513]: wmr100: Bad checksum on buffer of >>> length 26 >>> Jan 13 14:47:05 weather weewx[8513]: wmr100: Bad checksum on buffer of >>> length 7 >>> >>> Although everything seems to work OK. Note that the hardware is actually >>> a WMR180 not a 100. >>> >>> -- >>> 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] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
