Davis VP2 time out

[jerry...@gmail.com]

I have been running 5.1 for over a month on macOS 10.15.7 (frozen in time, no longer updated) interfacing to a VP2 via WifiLogger2.  Nothing has changed recently.  No Python updates. Everything was fine until yesterday, then the weewx.sdb stopped updating.  Got the following error.  Any thoughts?  Corrupted SDB file?

All ethernet interfaces are functioning.

LOOP:   2024-10-30 18:04:09 PDT (1730336649) 'altimeter': 'None', 'appTemp': '56.08810321307781', 'barometer': '30.13', 'cloudbase': '901.6874663631168', 'consBatteryVoltage': '4.79', 'dateTime': '1730336649', 'dayET': '0.0', 'dayRain': '0.0', 'dewpoint': '55.133775148002286', 'ET': 'None', 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0', 'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7': '0', 'extraAlarm8': '0', 'forecastIcon': '8', 'forecastRule': '1', 'heatindex': '58.689', 'humidex': '63.89747284993446', 'inDewpoint': '49.7056632424887', 'inHumidity': '54.0', 'insideAlarm': '0', 'inTemp': '66.9', 'maxSolarRad': '0.07726802694009056', 'monthET': '0.0', 'monthRain': '0.0', 'outHumidity': '87.0', 'outsideAlarm1': '0', 'outsideAlarm2': '0', 'outTemp': '59.0', 'pressure': 'None', 'rain': '0.0', 'rainAlarm': '0', 'rainRate': '0.0', 'soilLeafAlarm1': '0', 'soilLeafAlarm2': '0', 'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0', 'stormRain': '0.0', 'sunrise': '1730298900', 'sunset': '1730337120', 'txBatteryStatus': '0', 'usUnits': '1', 'windchill': '59.0', 'windDir': '261.0', 'windGust': '8.0', 'windGustDir': '261.0', 'windrun': 'None', 'windSpeed': '8.0', 'windSpeed10': '7.0', 'yearET': '0.0', 'yearRain': '0.0'

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

Unable to wake up console... sleeping

Unable to wake up console... retrying

^CTraceback (most recent call last):

  File "/Users/rycweather/weewx-venv/lib/python3.12/site-packages/weewxd.py", line 127, in main

    engine.run()

  File "/Users/rycweather/weewx-venv/lib/python3.12/site-packages/weewx/engine.py", line 204, in run

    for packet in self.console.genLoopPackets():

  File "/Users/rycweather/weewx-venv/lib/python3.12/site-packages/weewx/drivers/vantage.py", line 557, in genLoopPackets

    for _loop_packet in self.genDavisLoopPackets(self.loop_batch):

  File "/Users/rycweather/weewx-venv/lib/python3.12/site-packages/weewx/drivers/vantage.py", line 596, in genDavisLoopPackets

    raise weewx.RetriesExceeded(msg)

weewx.RetriesExceeded: LOOP max batch errors (3) exceeded.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File "/Users/rycweather/weewx-venv/./bin/weewxd", line 8, in <module>

    sys.exit(main())

             ^^^^^^

  File "/Users/rycweather/weewx-venv/lib/python3.12/site-packages/weewxd.py", line 154, in main

    time.sleep(wait_time)

KeyboardInterrupt

[Tom Keffer]

Impossible to say without a log. See: https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user#include-the-log

Also, any reason to think it's a WeeWX problem, rather than a WiFiLogger2 problem?

--
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 visit https://groups.google.com/d/msgid/weewx-user/fc8488a1-30bf-49fb-ba9d-590fc7c64b0an%40googlegroups.com.

[Charlie Fortner]

I have a WiFiLogger that interfaces with my VP2. Like Tom suggests, this is probably a WiFiLogger problem. I've had similar issues when WFL misbehaves. Reboot the WFL and see if it reconnects.

Charlie