Well you did not actually post for two archive intervals. Weewx usually reads vantage loop data every few seconds and rec data according to the archive interval specified in the console. this can be adjusted using wee_device. the start up sequence usually gives the archive interval which weewx will use (ie the console or as specified in weewx.conf) - but your log file does not start from the beginning of the start up sequence. Data is usually output once every archive interval to reports and/or WU, CWOP etc. The fact that your CWOP is at 30 minute intervals makes me think that the console is probably set taking records at 30 minute intervals. If you want 5 minute intervals then you will need to idealy set console = weewx.conf = 5 minute (300 seconds) interval.
On Sunday, 25 August 2019 20:22:21 UTC+3, Roy Lamberton wrote: > > The CWOP and PWS updated at 1200, 1230, & 1300, regardless of the time of > the setting under CWOP in the .conf file. > > I'm not sure where you tell the system to generate the transmissions, but > that is happening every 30 minutes at the top and bottom of the hour. > > Here is the log: > roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: manager: Daily summary version > is 2.0 > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: message repeated 2 times: [ > manager: Daily summary version is 2.0] > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Clock error is -1.20 > seconds (positive is fast) > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Getting archive > packets since 2019-08-25 13:00:00 EDT (1566752400) > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of > console successful > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Retrieving 0 page(s); > starting index= 0 > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: engine: Starting main packet > loop. > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of > console successful > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP > packets. > Aug 25 13:06:21 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of > console successful > Aug 25 13:07:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: > CTRL-EVENT-SCAN-STARTED > Aug 25 13:11:30 roy-STCK1A8LFC wpa_supplicant[1179]: message repeated 2 > times: [ wlan1: CTRL-EVENT-SCAN-STARTED ] > Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Requesting 200 LOOP > packets. > Aug 25 13:12:57 roy-STCK1A8LFC weewx[8075]: vantage: Gentle wake up of > console successful > Aug 25 13:13:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: > CTRL-EVENT-SCAN-STARTED > Aug 25 13:15:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: > CTRL-EVENT-SCAN-STARTED > Aug 25 13:17:01 roy-STCK1A8LFC CRON[8141]: (root) CMD ( cd / && > run-parts --report /etc/cron.hourly) > Aug 25 13:17:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: > CTRL-EVENT-SCAN-STARTED > > It appears that WeeWx is asking the console for an update every 5 minutes, > but then sits on the data until the top and bottom of the hour. Because of > my location, CWOP always wanted a 5 minute reporting interval. So did > Wunderground. > > I can't find anything that changes the time between reports that I haven't > changed. > > > On Sunday, August 25, 2019 at 1:05:35 PM UTC-4, Andrew Milner wrote: >> >> Posting the log from startup until two archive intervals have passed >> would help analysing your problem. >> >> >> >> On Sunday, 25 August 2019 19:49:48 UTC+3, Roy Lamberton wrote: >>> >>> Update - it is posting the latest information every time I restart >>> WeeWx, but then it asks for the LOOP Packets every 5 minutes, but doesn't >>> process them. >>> >>> It almost seems like the software is getting the data but doesn't know >>> what to do with it. >>> >>> I can't find anything in the Doc about the conf file that talks about >>> timing of upload, except the Wunderground flash, which I turned off >>> temporarily. >>> >>> But I need to talk with someone fast, or I'm going badcfk to my old >>> Cumulus setup and putting WeeWx on hold. >>> >>> >>> rsl >>> On Sunday, August 25, 2019 at 12:19:43 PM UTC-4, Roy Lamberton wrote: >>>> >>>> OK, I have WeeWx running on an Ubuntu desktop PC and its connected and >>>> appears to be working, but it isn't updating CWOP or any of the other >>>> weather systems: >>>> >>>> Here's the syslog" >>>> roy@roy-STCK1A8LFC:/etc/weewx$ tail -f /var/log/syslog >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: manager: Daily summary >>>> version is 2.0 >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: message repeated 2 times: [ >>>> manager: Daily summary version is 2.0] >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Clock error is >>>> -0.45 seconds (positive is fast) >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Getting archive >>>> packets since 2019-08-25 12:00:00 EDT (1566748800) >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of >>>> console successful >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Retrieving 0 >>>> page(s); starting index= 0 >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: engine: Starting main >>>> packet loop. >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of >>>> console successful >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Requesting 200 >>>> LOOP packets. >>>> Aug 25 12:05:20 roy-STCK1A8LFC weewx[7510]: vantage: Gentle wake up of >>>> console successful >>>> Aug 25 12:05:30 roy-STCK1A8LFC wpa_supplicant[1179]: wlan1: >>>> CTRL-EVENT-SCAN-STARTED >>>> >>>> When I first ran it, the woftware download 2 months of data from the >>>> console, and it did update one time when I restarted the software, but now >>>> it doesn't seem to be updating CWOP or the web page on the PC. >>>> >>>> ??? >>>> >>>> rsl >>>> >>>> -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/eafc3a4d-8125-4af4-9256-3f21ac2ce293%40googlegroups.com.
