WeeWx error "Vantage: LOOP read error. Try ... "

149 views
Skip to first unread message

Joachim Puttkammer

unread,
Dec 27, 2020, 6:35:38 AM12/27/20
to weewx-user
Hi, suddenly the Raspi Py did not read out any data (console Vantage Pro 2).
ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
Removing and reconnecting the USB connector and rebooting the Raspi did not help.
Command wee_device --clear and then  sudo service weewx restart solved the problem.
Unfortunately, measurement data was lost in the process.
Is there another solution without data loss? ( for the future)

Joachim

gjr80

unread,
Dec 27, 2020, 7:12:19 AM12/27/20
to weewx-user
Hi,

You can try using 

$ wee_device —dump

before clearing the loggers memory, this will dump all available archive records to database. It may or may not get any records from the logger that have not previously been downloaded, but it is about the best you can do at this stage.

Gary

Claudio

unread,
Dec 27, 2020, 11:12:00 AM12/27/20
to weewx-user
try to set your date and time before start weewx

Rob Cranfill

unread,
Dec 27, 2020, 8:42:05 PM12/27/20
to weewx-user
I've been running weewx for years, and now all of a sudden I am having this problem over and over again. 

Now, this is a new build on this same RPI - I had a SSD crash - but it seems substantially the same as before, yet here I am.

I realize this has to do with the OS's time not being.... "correct", whatever that means. So why does this confuse me?

pi@pi3b:~ $ wee_device --info | grep time
      Onboard time:                 2020-12-27 17:37:04
pi@pi3b:~ $ date
Sun 27 Dec 2020 05:37:09 PM PST

Is this really the cause of my problems?

Dec 27 17:36:22 pi3b systemd[1]: Starting LSB: weewx weather system...
Dec 27 17:36:22 pi3b weewx[7655] INFO __main__: Initializing weewx version 4.2.0
Dec 27 17:36:22 pi3b weewx[7655] INFO __main__: Using Python 3.7.3 (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
Dec 27 17:36:22 pi3b weewx[7655] INFO __main__: Platform Linux-5.4.79-v7+-armv7l-with-debian-10.7
Dec 27 17:36:22 pi3b weewx[7655] INFO __main__: Locale is 'en_US'
Dec 27 17:36:22 pi3b weewx[7655] INFO __main__: PID file is /var/run/weewx.pid
Dec 27 17:36:22 pi3b weewx[7659] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Dec 27 17:36:22 pi3b weewx[7659] INFO __main__: Debug is 1
Dec 27 17:36:22 pi3b weewx[7644]: Starting weewx weather system: weewx.
Dec 27 17:36:22 pi3b systemd[1]: Started LSB: weewx weather system.


Dec 27 17:36:27 pi3b weewx[7659] ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
Dec 27 17:36:31 pi3b weewx[7659] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead
Dec 27 17:36:35 pi3b weewx[7659] ERROR weewx.drivers.vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead
^C

Rob Cranfill

unread,
Dec 27, 2020, 8:43:13 PM12/27/20
to weewx-user
And I have tried "sudo wee_device --dump" and "sudo wee_device --clear-memory" several times.....

Tom Keffer

unread,
Dec 27, 2020, 8:51:54 PM12/27/20
to weewx-user
Do you have multiple instances of weewxd running? It's normal to see two PIDs, one of the original process, one of the fork, but I'm seeing three.

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/cf2f1912-7af8-4c96-bf44-d4e1b40af229n%40googlegroups.com.

Rob Cranfill

unread,
Dec 28, 2020, 2:50:16 PM12/28/20
to weewx-user
Tom,

I don't *think* I did (have multiple instances running), and have since tried running weewx from the command line (after stopping the service, of course and verifying no 'weewx' processes), with the same result. I'll keep mucking with it, and if I still have probs will start a new thread.

Thanks,
 Rob

Claudio

unread,
Dec 28, 2020, 3:03:50 PM12/28/20
to weewx-user
I had the same error when time was wrong, check time on console and raspberry
Reply all
Reply to author
Forward
0 new messages