Hi Gary, Not sure but you've been probably away when I posted my delayed response. Is there anything you could extract from the losgs and reports I attached to my previous message?
Best regards Benrhard Am Dienstag, 31. Juli 2018 16:40:11 UTC+2 schrieb [email protected]: > > Hi Gary, > > Sorry for the delayed response. Here is the requested data. I'm curious > about what you will extract from that data... > > Best regards > > Bernhard > > > > Am Montag, 30. Juli 2018 02:02:50 UTC+2 schrieb gjr80: >> >> Bernhard, >> >> On Monday, 30 July 2018 02:40:46 UTC+10, [email protected] wrote: >>> >>> Hi Gary, >>> >>> Many thanks for the details. I just experienced what you described when >>> I added the follwoing lines to my weewx.conf in the [StdWXCalculate] >>> [[Calculations]] section: >>> >>> [StdWXCalculate] >>> [[Calculations]] >>> ... >>> WindGust = software >>> WindGustDir = software >>> >>> It didn't change anything. >>> >> >> Correct, StdWXCalculate has no concept of windGust and windGustDir so >> those settings will do nothing, they are just ignored. >> >> >>> No I have already in my weewx.conf already the setting: >>> >>> [StdArchive] >>> ... >>> record_generation = software >>> >>> And as I'm using a Fine Offset WH1080 with the fosub driver weewx >>> reports on my website for WindGust "n/a". >>> >>> What exactlx would I need to change to get a direction reported for >>> WindGust although my station doesn't report it. >>> >> >> Provided your station is emitting windSpeed and windDir you should be >> seeing windGust and windGustDir in your archive records (and >> consequently on your web pages). Here are a few things to do to help >> diagnose the problem: >> >> 1. Post a the output from a wee_debug >> <http://weewx.com/docs/utilities.htm#wee_debug_utility> run. Before you >> post the output just check to ensure that any sensitive info like >> passwords, keys, user names etc have been obfuscated; wee_debug does a >> good job at this but it is not perfect. >> 2. Set WeeWX to run in debug mode so we get more info in the log: >> >> - edit weewx.conf >> - set debug = 1 >> - save weewx.conf. >> >> 3. Run WeeWX directly so we can see the loop packet and archive record >> data: >> >> - stop WeeWX if it is running >> - run WeeWX directly and let it run for at least 2 archive periods, >> you should see a number of entries on the screen starting with LOOP: and >> REC:; these are the loop packets and archive records respectively >> - stop WeeWX >> - capture the terminal output from when WeeWX was run directly and >> post it here >> >> 4. Post a log extract covering the period over which WeeWX was run >> directly. We need to see the entire startup sequence. >> >> When posting screen output or log extracts don't edit/change them, post >> them as is. >> >> 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]. For more options, visit https://groups.google.com/d/optout.
