Hi Gary,
After a fresh install of OS and WeeWX, the problem persists. I took your
advice and inserted the logging line into fileparse. I am seeing windGust
data in the incoming data stream, I see it in the LOOP packets and I see it
in the output of the logging command. What I see in the REC is "None" for
windGust. How is it possible that with a new database and a new input file
it is interpreting None for a 0.0 value? I have even changed around the
order of the input stream to see if that would affect anything. Nothing
changed. If the issue is my input data stream, why would it be
consistently THIS observation and not affect any other? Previous issues
with the data file showed fileparse errors and inconsistent values, etc. I
can send in the logging file, but it quite large. I will up load it if you
need to see it. Is there anywhere else I can look?
Ron
On Wednesday, July 3, 2019 at 8:47:17 AM UTC-4, Ron Walker wrote:
>
> Hi Gary,
>
> Two things! First, you were quite right about the amount of logging that
> would result! Is it possible to upload a file of greater that 15 mb here?
> 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!
>
> Ron
>
>
>
> On Tuesday, July 2, 2019 at 9:37:40 PM UTC-4, gjr80 wrote:
>>
>> Can’t comment on the error when stopping WeeWX, I guess it’s possible
>> something was messed up that prevented the ‘stop’ script running
>> successfully. I’d give it the benefit of the doubt for now.
>>
>> I note from your previous thread I mentioned there was no need for a
>> label map (field map) as your label names were the same as WeeWX field
>> names. This is not the case, radiation being a case in hand. That being
>> said fileparse expects a label map to be under a [label_map] stanza but you
>> have a [Label_Map] stanza. Case matters here so you might want to change
>> that. This won’t fix your windGust problem though.
>>
>> Other than the label map case issue the startup log seems to indicate no
>> config issues.
>>
>> The malformed field name could be a sign you still have some issues with
>> your data.csv. Appreciate the data going into data.csv may be correct but
>> the fileparse driver uses what is actually in the file; the two could be
>> different. You might want to try some additional logging in the fileparse
>> driver. Adding a loginf line like the following in genLoopPackets() will
>> log each line read from data.csv:
>>
>> with open(self.path) as f:
>> for line in f:
>> loginf(“line=%s” % line)
>> eq_index = line.find('=')
>> name = line[:eq_index].strip()
>> value = line[eq_index + 1:].strip()
>>
>> It’s going to log a lot but at least we can see the raw data WeeWX is
>> reading from data.csv.
>>
>> It’s also interesting that windGust is coming through loop packets as 0.0
>> but is accumulated in an archive record as None; I would have expected it
>> to come through as 0.0.
>>
>> Gary
>
>
--
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/b0dd2468-53aa-4dd1-9cdd-1d19f1ecf5fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
