Re: [weewx-user] LOOP try problem ...

I've changed to running on a RPi3 B. It's back up and running, however, the LOOP error still exists. After a time, however, I see that the system initializes and posts data again! NTP is running and keeping the time in sync, so I don't think it's a time issue. To say I'm baffled, would be

Re: [weewx-user] LOOP try problem ...

as tom noted, you need to configure the vp2 console device to 300 secs to get reports each 5 mins (or change weewx.conf file to 1800 secs if every 30 mins sufficient) this would not cause the read errors on the vp2, so is off-topic, but worth pointing out. cheers > On 18 Jun 2022, at 2:23 pm,

Re: [weewx-user] LOOP try problem ...

Hello Graham, Can you enlighten me just a bit more? Where is the "config error"? Thank you! On Friday, June 17, 2022 at 7:20:46 PM UTC-7 Graham Eddy wrote: > not the reported problem, but config error needs to be fixed nonetheless > > > On 18 Jun 2022, at 1:14 am, mup...@gmail.com wrote: > >

Re: [weewx-user] LOOP try problem ...

not the reported problem, but config error needs to be fixed nonetheless > On 18 Jun 2022, at 1:14 am, mup...@gmail.com wrote: > > Jun 17 08:09:38 weewx-RPi weewx[83743] ERROR weewx.engine: The archive > interval in the configuration file (300) does not match the station hardware > interval

Re: [weewx-user] LOOP try problem ...

I used the wee_device utility and cleared the archive records. Using the same utility, I've set the interval to 10 minutes. tail command reports that archive memory has been cleared. Now I wait ... On Friday, June 17, 2022 at 3:26:45 PM UTC-7 tke...@gmail.com wrote: > The default is 1800

Re: [weewx-user] LOOP try problem ...

The default is 1800 seconds. To change it, either see the guide that came with the logger, or use the utility wee_device with the --set-interval option. Did you try resetting the logger using the directions in the wiki section

Re: [weewx-user] LOOP try problem ...

I did change back to hardware record generation. The hardware archive interval is being set for me. Not sure how I'd change it, or what might be a better value. This is the Davis logger and I did take your recommendation and re-seat it. On Friday, June 17, 2022 at 12:09:34 PM UTC-7

Re: [weewx-user] LOOP try problem ...

This time, it is using hardware record generation. Did you change it? Also, the hardware archive interval is 1/2 hour, which may be longer than what you want / expect. When downloading archive records from the logger, it is starting from page zero, index zero, which is usually indicative of an

Re: [weewx-user] LOOP try problem ...

Thank you for your response. I have set debug=1. I had tried changing to software record generation to see what might change. It is now back to hardware. This is the log file upon restart: sudo tail -f /var/log/syslog Jun 17 08:08:11 weewx-RPi weewx[76976] ERROR weewx.drivers.vantage: LOOP

Re: [weewx-user] LOOP try problem ...

It appears that "debug" is not on, so the information in the log will be limited. However, I would guess that weewxd is having trouble connecting with your Vantage. Try setting debug=1 in weewx.conf, then restarting weewxd. Post the log from startup through the first reporting cycle. Also, any

[weewx-user] LOOP try problem ...

Hello, Just checked my log to see how things were operating and found this: Jun 16 17:45:20 weewx-RPi weewx[76976] ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded. Jun 16 17:45:20 weewx-RPi weewx[76976] INFO weewx.engine: Main loop exiting. Shutting engine down. Jun 16 17:45:20