Ok, if you are going to stick with a 600 second archive period then just change archive_interval = 300 to archive_interval = 600 under [StdArchive] in weewx.conf and you should not see that message again.
Gary On Tuesday, 8 January 2019 16:24:17 UTC+10, monmul wrote: > > Great, thanks, it seems to be working ok now.....and I will just stick > with the 600 sec. > > On Tuesday, 8 January 2019 19:18:12 UTC+13, gjr80 wrote: >> >> >> On Tuesday, 8 January 2019 08:14:28 UTC+10, monmul wrote: >>> >>> I notice an error in the archival interval - see below. Is this >>> important? >>> >>> Jan 8 11:07:08 Weatherpi weewx[750]: engine: The archive interval in >>> the configuration file (300) does not match the station hardware interval >>> (600). >>> Jan 8 11:07:08 Weatherpi weewx[750]: engine: Using archive interval of >>> 600 seconds (specified by hardware) >>> >> >> I presume you mean the 600/300 log entries above and not the LOOP errors >> below. The two entries above mean that the archive interval set in your >> console (600 seconds) does not match the archive interval under >> [StdArchive] in weewx.conf. When such a disagreement occurs weeWX >> defaults to using the console value, so in your case it uses 600 seconds >> and you will find that you have archive records being saved to database >> (and reports being generated) every 600 seconds (10 minutes). If you want >> to change this to 300 seconds (5 minutes) you will need to change the >> archive interval in your console. As with the wind direction offset this >> can be done through the console buttons or using the wee_device utility. >> For wee_device it's the same process as setting the wind direction >> offset, but this time you would use the --set-interval action >> <http://weewx.com/docs/hardware.htm#vantage_archive_interval46>. >> >> >>> Jan 8 11:07:14 Weatherpi weewx[750]: vantage: LOOP try #1; error: >>> Expected to read 99 chars; got 0 instead >>> Jan 8 11:07:19 Weatherpi weewx[750]: vantage: LOOP try #2; error: >>> Expected to read 99 chars; got 0 instead >>> Jan 8 11:07:28 Weatherpi weewx[750]: vantage: LOOP try #3; error: >>> Expected to read 99 chars; got 0 instead >>> Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP try #4; error: >>> Expected to read 99 chars; got 0 instead >>> Jan 8 11:07:33 Weatherpi weewx[750]: vantage: LOOP max tries (4) >>> exceeded. >>> Jan 8 11:07:33 Weatherpi weewx[750]: engine: Caught WeeWxIOError: Max >>> tries exceeded while getting LOOP data. >>> Jan 8 11:07:33 Weatherpi weewx[750]: **** Waiting 60 seconds then >>> retrying... >>> >> >> As for the LOOP errors, that indicates that your RPi is not able to >> communicate with your console. You have had it working and the vantage >> stations tend to just work so go through some basic checking (is it plugged >> in is something else interfering, unplug/plug in the station again, stop >> then start weeWX). Remember monitor the log, it will tell you what is going >> on. A useful approach can be to have two terminals open; one for issuing >> commands and one for monitoring the log with the command: >> >> $ tail -f -n 20 /var/log/syslog >> >> This shows you the last 20 lines of syslog then automatically displays >> any additional log entries as they occur. Makes it easy to see what happens >> when you issue commands. >> >> 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.
