Charlie, thanks for posting this!  I'm switching from my ancient vantage 
pro, connected via lantronix serial<->ethernet to a shiny new vantage pro 2 
with the WiFiLogger 2 <https://wifilogger.net> (firmware 2.33).  I ran into 
the same problem:

Sep 22 10:56:59 ubu-mini-weather weewx[178549] INFO weewx.manager: Starting 
backfill of daily summaries

Sep 22 10:57:00 ubu-mini-weather weewx[178549] INFO weewx.engine: Starting 
main packet loop.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #1; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #2; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #3; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP try #4; error: Expected 99 characters; got zero instead

Sep 22 10:58:02 ubu-mini-weather weewx[178549] ERROR weewx.drivers.vantage: 
LOOP max tries (4) exceeded.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] INFO weewx.engine: Main loop 
exiting. Shutting engine down.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting LOOP data.

Sep 22 10:58:02 ubu-mini-weather weewx[178549] CRITICAL __main__:     ****  
Waiting 60 seconds then retrying...
After several frustrating hours of trying to fix it, I searched the forum 
and found your post.  Sure enough, changing the WiFiLogger configuration 
Setup > System > General Settings > TCP Port to Pause (there was no 
"auto-pause") fixed the problem, and it's running great now.  Going through 
the log, I still find a couple of the loop errors, but they're rare now, 
and the retry gets it right.

A couple of checklist items for anybody else doing this.  The weewx config 
items are all in the Vantage section of weewx.conf.  The wfl items are set 
using a browser to access the web server built into the wfl.

   - Make sure the WiFiLogger (wfl) port number (setup->wiFi setup->tcp 
   port settings, default 22222)  matches weewx.conf items tcp_port and port. 
    Actually, the "port" item is probably not used, but I just set them both.
   - Make sure the wfl is at a fixed ip address on your lan, and that 
   weewx.conf "host" is set to that address.  You can fix the IP address 
   either in your router (preferable, IMHO) or on the wfl itself (Setup->WiFi 
   Setup->Connect to Router->Advanced Options).
   - I'm using loop type 2 (loop_request = 2 in weewx.conf), but I'm not 
   sure this matters.
   - Make sure the archive intervals match.  In weewx.conf it's 
   archive_interval in the StdArchive section.  On the wfl it's Setup->Weather 
   Station Setup->Set Archive Interval, BUT the units are seconds in 
   weewx.conf, minutes in wfl.  So, mine are 10 minutes on the wfl, 600 in 
   weewx.conf.
   
I haven't had it running for long, but it's very nice to have a wireless 
connection to the Davis console, and to stick my old Lantronix on a shelf.

Thanks again for posting the fix, Charlie.
On Sunday, November 25, 2018 at 7:40:18 PM UTC-8 [email protected] wrote:

>
> On Saturday, November 24, 2018 at 7:37:26 PM UTC-5, [email protected] 
> wrote:
>>
>> WeeWx sees the WiFi logger and can get the archive packets, but not the 
>> LOOP packets. It always times out. 
>>
>
> It looks like the time out problems were caused by the TCP settings of the 
> WiFiLogger, not weewx.
>
> I know this isn't a WiFiLogger forum, but in the interest of anyone that 
> stumbles upon this same problem here's how I fixed things: In the 
> WiFiLogger I changed Setup > System > General Settings > TCP Port to 
> Auto-Pause. This is with WiFiLogger firmware 1.23. The timeout problems now 
> seem to be gone and weewx can get the LOOP packets as normal.
>
>
>
> Charlie
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/95d9b830-a255-4b73-b25e-2113b67ba237n%40googlegroups.com.

Reply via email to