ERROR weewx.drivers.vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead

201 views
Skip to first unread message

G400

unread,
Feb 21, 2021, 4:55:15 PM2/21/21
to weewx-user
ERROR weewx.drivers.vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead

Davis Vantage Pro2 and Vantage Envoy wireless (connected to RPI via USB - serial link)
Values received on Davis Vantage console looks ok, but getting above errors parsing data from Envoy
Any idea what is causing this?

Tom Keffer

unread,
Feb 21, 2021, 8:23:02 PM2/21/21
to weewx-user
Hard to say without seeing the log. See the wiki article Help! Posting to weewx-user for how to get a log.

--
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/fc460e02-30de-4d3a-8120-02bc99025983n%40googlegroups.com.

G400

unread,
Feb 22, 2021, 4:02:24 AM2/22/21
to weewx-user
Hi,
About 30 min log is attached

I see a lot of these errors:

Feb 22 09:06:04 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:08 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:12 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: LOOP try #4; error: Expected to read 99 chars; got 0 instead
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] ERROR weewx.drivers.vantage: LOOP max tries (4) exceeded.
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] INFO weewx.engine: Main loop exiting. Shutting engine down.
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] INFO weewx.engine: Shutting down StdReport thread
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] DEBUG weewx.engine: StdReport thread has been terminated
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] CRITICAL __main__: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.
Feb 22 09:06:16 aad-raspberry-01 weewx[1286] CRITICAL __main__:     ****  Waiting 60 seconds then retrying...
Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: retrying...
Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: Using configuration file /etc/weewx/weewx.conf
Feb 22 09:07:16 aad-raspberry-01 weewx[1286] INFO __main__: Debug is 1
Feb 22 09:07:16 aad

mylog.zip

Tom Keffer

unread,
Feb 22, 2021, 7:07:54 AM2/22/21
to weewx-user
You did not restart weewx, so the log does not show the startup sequence.

There could be another problem, but, at the minimum, it appears that the memory in your logger is corrupt. See the section WeeWX generates HTML pages, but it does not update them in the wiki on how to clear the logger.

However, the symptoms are not quite classic. The timestamps in your logger are quite old: over a year old. Usually, corrupt memory shows more recent timestamps than that.

It's also still possible there is something else wrong. If clearing the logger does not help, then post the log again, but this time make sure to restart weewx and make sure the log includes that startup sequence.

-tk

--
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.
Reply all
Reply to author
Forward
0 new messages