Hi Michael,
I don't have an IP-logger myself.
Last year I was remote testing a Raspberry PI model B with a Davis
IP-logger in Germany (from Suriname) .
Don't know if the IP was static or dynamic. I don't think I had
loop_on_init = True in the config file.
I was playing with the various timings and also changed the wake-up and
other logic.
I checked my old logs. The remote system got broken pipe errors with
version 3.0.6 and the errors were gone with version 3.0.5.
Unfortunately I don't have copies anymore of those versions to check the
differences.
Luc
On Wednesday, 12 July 2017 03:02:11 UTC-3, Mike wrote:
>
> Thanks for the informations.
>
> @@ Luc
>
> Are you getting a dynamic ot static IP from your ISP?
> Do you use loop_on_init = True in your conf file?
>
> Thanks again
> Michael
>
> Am Montag, 10. Juli 2017 05:47:09 UTC+7 schrieb Tom Keffer:
>>
>> Michael,
>>
>> loop_on_init only affects how an error in the driver is handled on
>> startup.
>>
>> Normally, if an error is encountering when weewx is starting up
>> ("initializing"), the program exits. The assumption is that the user has a
>> configuration problem, so there is no point in trying the same thing
>> over-and-over again.
>>
>> However, if loop_on_init is set to true, then weewx will restart from the
>> top and keep trying.
>>
>> In either case, once a successful startup is achieved, if an error
>> occurs, weewx will restart from the top.
>>
>> On to your WLIP problems. The Davis serial protocol is very "chatty,"
>> with lots of state transitions. This makes it very difficult to run it over
>> a WAN. It should work just fine with either static or dynamic IP
>> assignments. However, it will be very sensitive to firewall settings.
>>
>> I do not own an IP logger, so it's very hard for me to debug them
>> remotely.
>>
>> -tk
>>
>> On Sat, Jul 8, 2017 at 3:16 PM, Luc Heijst <[email protected]> wrote:
>>
>>> Hi Mike,
>>>
>>> I debugged the vantage driver for the ip-datalogger in March 2016 and
>>> came across the same errors you have now.
>>> I discovered the ip-datalogger needed other timings than the serial and
>>> usb dataloggers.
>>>
>>> This is what I found in my old notes:
>>>
>>> # Serial delays (when using serial or USB):
>>> command_delay = 0.2
>>>
>>> # TCP delays (when using the WeatherLinkIP):
>>> command_delay = 1.0
>>> tcp_send_delay = 0.2
>>>
>>> The default values of the current driver are:
>>> command_delay = 0.5
>>> tcp_send_delay = 0.5
>>>
>>> Maybe the command_delay time is too short for the ip-datalogger.
>>> Default it is 0.5 s and it should be 1.0 s (according to my notes one
>>> year ago)
>>> You can try to increase the command_delay time by putting in the
>>> [Vantage] section of weewx.conf:
>>> command_delay = 1.0
>>>
>>> Maybe it helps.
>>>
>>> Luc
>>>
>>>
>>> --
>>> 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].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
--
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].
For more options, visit https://groups.google.com/d/optout.
