Hi Andrew, Thanks for your reply. The undervoltage reports resulted from me using a Pi UpTime UPS as power backup. I have removed it from the equation and the undervoltage reports have ceased.
The reason for the multiple wind observation in the input file was two-fold. First, the averages are of more use to us in our application because we don't have real-time information available. If we just used windGust, we might miss gusts between loop intervals. The second was as a test of using observations that were not in the database on the web page. I have tested with those included and removed. It made absolutely no difference. On the subject of the input data, I will do the logging as you suggest and post the results. One thing that bothers the snot out of me is the consistency of this. No matter what changes are made, new database, new input file, changes to the order of the observations in the input file, the result is consistently the same. I find that very strange. To get around this in the short term, I've added two observations in the input file. 'mywindGust' is mapped in the input file to my 'windGust' variable and 'mywindGustDir' is mapped to 'windGustDir'. Doing this, I am able to display the actual values for 'windGust' and 'windGustDir' on the web page. As an aside, these values display with many decimal places. Is there a way to change that so that they display the windGust would? On Thursday, July 4, 2019 at 10:57:11 AM UTC-4, Andrew Milner wrote: > > Looking at a log file you have posted earlier I see loads of undervoltage > reports from your kernel. You should not be getting these at all. > Combining that with what I assume to be bad data transfers from the arduino > over possibly usb (ustWindDir10avg for example instead of what I think > should have been GustWindDir10avg) and other similar instances. > > I think you need to go step by step, getting full logs and debug info > along the way (regardless of the file sizes). Your input data appears to > have loads of different wind speeds and gust speeds available - do you need > all these?? > > > > On Thursday, 4 July 2019 17:18:26 UTC+3, Ron Walker wrote: >> >> Hi, >> >> I definitely did not have an interval of 10 seconds set anywhere. This >> was just another of the weird issues that suddenly appeared after the unit >> had been working well over the last couple of weeks. I did a clean install >> of the OS and WeeWX and that problem is no longer an issue. >> >> The lack of windGust data being displayed, unfortunately, has not. >> >> On Thursday, July 4, 2019 at 12:23:04 AM UTC-4, mwall wrote: >>> >>> On Wednesday, July 3, 2019 at 8:47:17 AM UTC-4, Ron Walker wrote: >>>> >>>> The second thing is a new issue that started occurring as I was try to >>>> gather data. I started seeing the following in the syslog: >>>> >>>> xisting report thread still running >>>> Jul 3 08:44:55 WeatherPi weewx[627]: engine: Launch of report thread >>>> aborted: existing report thread still running >>>> Jul 3 08:45:05 WeatherPi weewx[627]: manager: Added record 2019-07-03 >>>> 08:45:00 EDT (1562157900) to database 'weewx.sdb' >>>> Jul 3 08:45:05 WeatherPi weewx[627]: manager: Added record 2019-07-03 >>>> 08:45:00 EDT (1562157900) to daily summary in 'weewx.sdb' >>>> Jul 3 08:45:05 WeatherPi weewx[627]: engine: Launch of report thread >>>> aborted: existing report thread still running >>>> Jul 3 08:45:15 WeatherPi weewx[627]: engine: Launch of report thread >>>> aborted: existing report thread still running >>>> Jul 3 08:45:25 WeatherPi weewx[627]: engine: Launch of report thread >>>> aborted: existing report thread still running >>>> Jul 3 08:45:29 WeatherPi weewx[627]: cheetahgenerator: Generated 8 >>>> files for report SeasonsReport in 51.84 seconds >>>> Jul 3 08:45:30 WeatherPi weewx[627]: manager: Daily summary version is >>>> 2.0 >>>> Jul 3 08:45:35 WeatherPi weewx[627]: engine: Launch of report thread >>>> aborted: existing report thread still running >>>> Jul 3 08:45:45 WeatherPi weewx[627]: engine: Launch of report thread >>>> aborted: existing report thread still running >>>> >>>> Is there a way to stop this 'existing thread'? I've tried stopping and >>>> restarting and rebooting the PI. Nothing seems to stop it! >>>> >>> >>> it looks like you are trying to generate a report every 10 seconds, and >>> the hardware on which you are running weewx is unable to complete all of >>> the reports that you have requested in that time. >>> >>> change your archive interval to something more reasonable such as 5 >>> minutes (300 seconds) >>> >>> if you need real-time display, consider uploading to influxdb or an MQTT >>> broker, with something like grafana attached for the display. >>> >>> m >>> >> -- 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/0d00ea15-e9d2-422c-9bbd-a835743839d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
