Hi all,
I have set up my MB Pro to read the data from my Vantage Pro2 through the WeatherLink IP module (over the LAN), rather than through the Meteostick (i.e., wireless) functionality. The MB Pro is configured to allow the WeatherLink IP module to upload data to WeatherLink.com every minute.
Everything works fine and all relevant information is also uploaded to Meteoplug with no visible gaps, but I have noticed the following messages in the MB Pro's system log:
logger (03.04.2016 11:40:11): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (03.04.2016 11:40:11): disconnect station 0 (Vantage): read failed
logger (03.04.2016 11:40:41): connect station 0 (Vantage via TCP/IP).
logger (03.04.2016 11:40:41): wakeup sent.
logger (03.04.2016 11:40:41): internal logger activated.
logger (03.04.2016 11:40:41): syncing.
logger (03.04.2016 11:40:52): gettime request sent.
logger (03.04.2016 11:40:52): no Vantage time offset.
logger (03.04.2016 11:40:52): eeprom request sent.
logger (03.04.2016 11:40:53): rain collector size 0.2 mm per tick.
logger (03.04.2016 11:40:53): transmitter 1 active as station type (#0) "ISS".
logger (03.04.2016 11:40:53): firmware version request sent.
logger (03.04.2016 11:40:54): firmware version 3.12
logger (03.04.2016 11:40:54): no reading of Vantage's internal logger.
The above series of messages appears at least 3 or 4 times a day (maybe more), i.e., there are at least 3 or 4 read failures every day (which lead to a re-connection process).
Is this some bug? Why would the MB Pro fail to connect to the WeatherLink IP module? It should be noted that I never got those messages in the past.
Thanks,
chrysnic
MB Pro failure to read WeatherLink IP data **solved**
Moderator: Mattk
Re: MB Pro failure to read WeatherLink IP data
Are WLIP and MB PRO located in the same LAN? Is MB PRO operated on Ethernet or WiFi?
Re: MB Pro failure to read WeatherLink IP data
Yes, the WLIP and MB Pro are located in the same LAN. The MB Pro is operated on Ethernet.
Thanks.
Thanks.
Re: MB Pro failure to read WeatherLink IP data
I am revisiting this to provide an update. Indeed, after observing the log over the last 10 days, the "Connection reset by peer" messages occur several times each day. Sometimes, they occur in bursts, as shown in the log below (4 connection resets in a short period of time):
logger (12.04.2016 10:25:09): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:25:09): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:25:39): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:25:39): wakeup sent.
logger (12.04.2016 10:25:39): internal logger activated.
logger (12.04.2016 10:25:39): syncing.
logger (12.04.2016 10:25:50): gettime request sent.
logger (12.04.2016 10:25:50): no Vantage time offset.
logger (12.04.2016 10:25:50): eeprom request sent.
logger (12.04.2016 10:25:51): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:25:51): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:25:51): firmware version request sent.
logger (12.04.2016 10:25:52): firmware version 3.12
logger (12.04.2016 10:25:52): no reading of Vantage's internal logger.
logger (12.04.2016 10:27:41): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:27:41): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:28:11): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:28:11): wakeup sent.
logger (12.04.2016 10:28:11): internal logger activated.
logger (12.04.2016 10:28:11): syncing.
logger (12.04.2016 10:28:21): gettime request sent.
logger (12.04.2016 10:28:21): no Vantage time offset.
logger (12.04.2016 10:28:21): eeprom request sent.
logger (12.04.2016 10:28:22): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:28:22): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:28:22): firmware version request sent.
logger (12.04.2016 10:28:23): firmware version 3.12
logger (12.04.2016 10:28:23): no reading of Vantage's internal logger.
logger (12.04.2016 10:53:13): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:53:13): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:53:43): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:53:43): wakeup sent.
logger (12.04.2016 10:53:43): internal logger activated.
logger (12.04.2016 10:53:43): syncing.
logger (12.04.2016 10:53:54): gettime request sent.
logger (12.04.2016 10:53:54): no Vantage time offset.
logger (12.04.2016 10:53:54): eeprom request sent.
logger (12.04.2016 10:53:55): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:53:55): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:53:55): firmware version request sent.
logger (12.04.2016 10:53:56): firmware version 3.12
logger (12.04.2016 10:53:56): no reading of Vantage's internal logger.
logger (12.04.2016 10:55:45): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:55:45): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:56:15): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:56:15): wakeup sent.
logger (12.04.2016 10:56:15): internal logger activated.
logger (12.04.2016 10:56:15): syncing.
logger (12.04.2016 10:56:26): gettime request sent.
logger (12.04.2016 10:56:26): no Vantage time offset.
logger (12.04.2016 10:56:26): eeprom request sent.
logger (12.04.2016 10:56:27): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:56:27): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:56:27): firmware version request sent.
logger (12.04.2016 10:56:28): firmware version 3.12
logger (12.04.2016 10:56:28): no reading of Vantage's internal logger.
As I said, the WLIP and MB Pro are located in the same LAN, and the MB Pro is operated on Ethernet. The activity on the LAN is very low (the other clients are inactive most of the time).
Thanks,
chrysnic
logger (12.04.2016 10:25:09): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:25:09): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:25:39): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:25:39): wakeup sent.
logger (12.04.2016 10:25:39): internal logger activated.
logger (12.04.2016 10:25:39): syncing.
logger (12.04.2016 10:25:50): gettime request sent.
logger (12.04.2016 10:25:50): no Vantage time offset.
logger (12.04.2016 10:25:50): eeprom request sent.
logger (12.04.2016 10:25:51): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:25:51): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:25:51): firmware version request sent.
logger (12.04.2016 10:25:52): firmware version 3.12
logger (12.04.2016 10:25:52): no reading of Vantage's internal logger.
logger (12.04.2016 10:27:41): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:27:41): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:28:11): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:28:11): wakeup sent.
logger (12.04.2016 10:28:11): internal logger activated.
logger (12.04.2016 10:28:11): syncing.
logger (12.04.2016 10:28:21): gettime request sent.
logger (12.04.2016 10:28:21): no Vantage time offset.
logger (12.04.2016 10:28:21): eeprom request sent.
logger (12.04.2016 10:28:22): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:28:22): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:28:22): firmware version request sent.
logger (12.04.2016 10:28:23): firmware version 3.12
logger (12.04.2016 10:28:23): no reading of Vantage's internal logger.
logger (12.04.2016 10:53:13): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:53:13): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:53:43): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:53:43): wakeup sent.
logger (12.04.2016 10:53:43): internal logger activated.
logger (12.04.2016 10:53:43): syncing.
logger (12.04.2016 10:53:54): gettime request sent.
logger (12.04.2016 10:53:54): no Vantage time offset.
logger (12.04.2016 10:53:54): eeprom request sent.
logger (12.04.2016 10:53:55): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:53:55): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:53:55): firmware version request sent.
logger (12.04.2016 10:53:56): firmware version 3.12
logger (12.04.2016 10:53:56): no reading of Vantage's internal logger.
logger (12.04.2016 10:55:45): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (12.04.2016 10:55:45): disconnect station 0 (Vantage): read failed
logger (12.04.2016 10:56:15): connect station 0 (Vantage via TCP/IP).
logger (12.04.2016 10:56:15): wakeup sent.
logger (12.04.2016 10:56:15): internal logger activated.
logger (12.04.2016 10:56:15): syncing.
logger (12.04.2016 10:56:26): gettime request sent.
logger (12.04.2016 10:56:26): no Vantage time offset.
logger (12.04.2016 10:56:26): eeprom request sent.
logger (12.04.2016 10:56:27): rain collector size 0.2 mm per tick.
logger (12.04.2016 10:56:27): transmitter 1 active as station type (#0) "ISS".
logger (12.04.2016 10:56:27): firmware version request sent.
logger (12.04.2016 10:56:28): firmware version 3.12
logger (12.04.2016 10:56:28): no reading of Vantage's internal logger.
As I said, the WLIP and MB Pro are located in the same LAN, and the MB Pro is operated on Ethernet. The activity on the LAN is very low (the other clients are inactive most of the time).
Thanks,
chrysnic
Re: MB Pro failure to read WeatherLink IP data
Can you rule out that another PC is also trying to access the WLIP in your LAN?
Meteobridge will give the WLIP a chance to upload to the weatherlink network
and disconnects from it. This temporary drop of the connection could be used by
another PC in the LAN to establish a connection with the WLIP and this will then
block Meteobridge to reconnect. Just a guess....
Meteobridge will give the WLIP a chance to upload to the weatherlink network
and disconnects from it. This temporary drop of the connection could be used by
another PC in the LAN to establish a connection with the WLIP and this will then
block Meteobridge to reconnect. Just a guess....
Re: MB Pro failure to read WeatherLink IP data
There is no other PC trying to access the WLIP. This is why the situation seems strange. The reason why I suspect it may be some kind of MB Pro bug (that was introduced after an upgrade, perhaps) is because I have the exact same LAN setup as always, and I never used to get these sort of messages (not even a single message).
Thank you for your time and help.
Thank you for your time and help.
Re: MB Pro failure to read WeatherLink IP data
This is not related to any recent firmware upgrade as also now seeing same errors with FW2.5 July 31, build 6790. I believe FW 2.8 April 26, build 9808 is also showing the same error but after logging back in messages became reset, will confirm overnight. Both these units have WLIP loggers & MB (not pro), issue not evident with MB Pro via RF
Re: MB Pro failure to read WeatherLink IP data
Same issue occurring with July 2015 & April 26, 2016 firmware, both on MB (TP-Link MR3020)
Re: MB Pro failure to read WeatherLink IP data
Have now moved a system on to a totally separate network comprising only a WLIP, MB & M2M cellular router. All access is remote via MB login & WLIP data download, can also access the router and WLIP via DNS.
Still getting this very continual cycle of "Connection reset by peer" message as per example/s above.
Still getting this very continual cycle of "Connection reset by peer" message as per example/s above.
Re: MB Pro failure to read WeatherLink IP data
Message logs (zipped) attached for MB's on main network (16d29-71a) and standalone network (16d29-72e1).
Main network MB is a MR3020 running 2.5 July 2015, build 6790
Secondary network MB is a MR3020 running 2.8 April 28, build 9814
Both WLIP's are uploading to WeatherLink, main is Console & VP2 ISS, secondary is an Envoy & Vue
Main network MB is a MR3020 running 2.5 July 2015, build 6790
Secondary network MB is a MR3020 running 2.8 April 28, build 9814
Both WLIP's are uploading to WeatherLink, main is Console & VP2 ISS, secondary is an Envoy & Vue
- Attachments
-
- MB-log16d29a.zip
- (2.46 KiB) Downloaded 287 times
Re: MB Pro failure to read WeatherLink IP data
An update, this cycle just doesn't stop, is this normal?
- Main network station MB, WLIP
logger (04.05.2016 12:39:56): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 12:39:56): disconnect station 0 (Vantage): read failed
logger (04.05.2016 12:40:26): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 12:40:26): wakeup sent.
logger (04.05.2016 12:40:26): internal logger activated.
logger (04.05.2016 12:40:26): syncing.
logger (04.05.2016 12:40:36): gettime request sent.
logger (04.05.2016 12:40:36): no Vantage time offset.
logger (04.05.2016 12:40:36): eeprom request sent.
logger (04.05.2016 12:40:37): rain collector size 0.2 mm per tick.
logger (04.05.2016 12:40:37): transmitter 2 active as station type (#0) "ISS".
logger (04.05.2016 12:40:37): firmware version request sent.
logger (04.05.2016 12:40:37): firmware version 1.90
logger (04.05.2016 12:40:37): no reading of Vantage's internal logger.
logger (04.05.2016 13:07:26): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 13:07:26): disconnect station 0 (Vantage): read failed
logger (04.05.2016 13:07:56): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 13:07:56): wakeup sent.
logger (04.05.2016 13:07:56): internal logger activated.
logger (04.05.2016 13:07:56): syncing.
logger (04.05.2016 13:08:07): gettime request sent.
logger (04.05.2016 13:08:07): no Vantage time offset.
logger (04.05.2016 13:08:07): eeprom request sent.
logger (04.05.2016 13:08:08): rain collector size 0.2 mm per tick.
logger (04.05.2016 13:08:08): transmitter 2 active as station type (#0) "ISS".
logger (04.05.2016 13:08:08): firmware version request sent.
logger (04.05.2016 13:08:08): firmware version 1.90
logger (04.05.2016 13:08:08): no reading of Vantage's internal logger.
logger (04.05.2016 13:21:40): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 13:21:40): disconnect station 0 (Vantage): read failed
logger (04.05.2016 13:22:10): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 13:22:10): wakeup sent.
logger (04.05.2016 13:22:10): internal logger activated.
logger (04.05.2016 13:22:10): syncing.
logger (04.05.2016 13:22:21): gettime request sent.
logger (04.05.2016 13:22:21): no Vantage time offset.
logger (04.05.2016 13:22:21): eeprom request sent.
logger (04.05.2016 13:22:22): rain collector size 0.2 mm per tick.
logger (04.05.2016 13:22:22): transmitter 2 active as station type (#0) "ISS".
logger (04.05.2016 13:22:22): firmware version request sent.
logger (04.05.2016 13:22:22): firmware version 1.90
logger (04.05.2016 13:22:22): no reading of Vantage's internal logger.
-Secondary standalone network MB, WLIP, M2M router (only)
logger (04.05.2016 14:24:37): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 14:24:37): disconnect station 0 (Vantage): read failed
logger (04.05.2016 14:25:07): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 14:25:07): wakeup sent.
logger (04.05.2016 14:25:07): internal logger activated.
logger (04.05.2016 14:25:07): syncing.
logger (04.05.2016 14:25:18): gettime request sent.
logger (04.05.2016 14:25:18): time offset of Vantage: -1 minutes
logger (04.05.2016 14:25:18): eeprom request sent.
logger (04.05.2016 14:25:19): rain collector size 0.2 mm per tick.
logger (04.05.2016 14:25:19): transmitter 3 active as station type (#0) "ISS".
logger (04.05.2016 14:25:19): firmware version request sent.
logger (04.05.2016 14:25:20): firmware version 1.90
logger (04.05.2016 14:25:20): no reading of Vantage's internal logger.
logger (04.05.2016 14:28:13): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 14:28:13): disconnect station 0 (Vantage): read failed
logger (04.05.2016 14:28:43): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 14:28:43): wakeup sent.
logger (04.05.2016 14:28:43): internal logger activated.
logger (04.05.2016 14:28:43): syncing.
logger (04.05.2016 14:28:54): gettime request sent.
logger (04.05.2016 14:28:54): time offset of Vantage: -1 minutes
logger (04.05.2016 14:28:54): eeprom request sent.
logger (04.05.2016 14:28:55): rain collector size 0.2 mm per tick.
logger (04.05.2016 14:28:55): transmitter 3 active as station type (#0) "ISS".
logger (04.05.2016 14:28:55): firmware version request sent.
logger (04.05.2016 14:28:56): firmware version 1.90
logger (04.05.2016 14:28:56): no reading of Vantage's internal logger.
logger (04.05.2016 14:29:00): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 14:29:00): disconnect station 0 (Vantage): read failed
logger (04.05.2016 14:29:30): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 14:29:30): wakeup sent.
logger (04.05.2016 14:29:30): internal logger activated.
logger (04.05.2016 14:29:30): syncing.
logger (04.05.2016 14:29:41): gettime request sent.
logger (04.05.2016 14:29:42): time offset of Vantage: -1 minutes
logger (04.05.2016 14:29:42): eeprom request sent.
logger (04.05.2016 14:29:42): rain collector size 0.2 mm per tick.
logger (04.05.2016 14:29:42): transmitter 3 active as station type (#0) "ISS".
logger (04.05.2016 14:29:42): firmware version request sent.
logger (04.05.2016 14:29:43): firmware version 1.90
logger (04.05.2016 14:29:43): no reading of Vantage's internal logger.
- Main network station MB, WLIP
logger (04.05.2016 12:39:56): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 12:39:56): disconnect station 0 (Vantage): read failed
logger (04.05.2016 12:40:26): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 12:40:26): wakeup sent.
logger (04.05.2016 12:40:26): internal logger activated.
logger (04.05.2016 12:40:26): syncing.
logger (04.05.2016 12:40:36): gettime request sent.
logger (04.05.2016 12:40:36): no Vantage time offset.
logger (04.05.2016 12:40:36): eeprom request sent.
logger (04.05.2016 12:40:37): rain collector size 0.2 mm per tick.
logger (04.05.2016 12:40:37): transmitter 2 active as station type (#0) "ISS".
logger (04.05.2016 12:40:37): firmware version request sent.
logger (04.05.2016 12:40:37): firmware version 1.90
logger (04.05.2016 12:40:37): no reading of Vantage's internal logger.
logger (04.05.2016 13:07:26): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 13:07:26): disconnect station 0 (Vantage): read failed
logger (04.05.2016 13:07:56): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 13:07:56): wakeup sent.
logger (04.05.2016 13:07:56): internal logger activated.
logger (04.05.2016 13:07:56): syncing.
logger (04.05.2016 13:08:07): gettime request sent.
logger (04.05.2016 13:08:07): no Vantage time offset.
logger (04.05.2016 13:08:07): eeprom request sent.
logger (04.05.2016 13:08:08): rain collector size 0.2 mm per tick.
logger (04.05.2016 13:08:08): transmitter 2 active as station type (#0) "ISS".
logger (04.05.2016 13:08:08): firmware version request sent.
logger (04.05.2016 13:08:08): firmware version 1.90
logger (04.05.2016 13:08:08): no reading of Vantage's internal logger.
logger (04.05.2016 13:21:40): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 13:21:40): disconnect station 0 (Vantage): read failed
logger (04.05.2016 13:22:10): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 13:22:10): wakeup sent.
logger (04.05.2016 13:22:10): internal logger activated.
logger (04.05.2016 13:22:10): syncing.
logger (04.05.2016 13:22:21): gettime request sent.
logger (04.05.2016 13:22:21): no Vantage time offset.
logger (04.05.2016 13:22:21): eeprom request sent.
logger (04.05.2016 13:22:22): rain collector size 0.2 mm per tick.
logger (04.05.2016 13:22:22): transmitter 2 active as station type (#0) "ISS".
logger (04.05.2016 13:22:22): firmware version request sent.
logger (04.05.2016 13:22:22): firmware version 1.90
logger (04.05.2016 13:22:22): no reading of Vantage's internal logger.
-Secondary standalone network MB, WLIP, M2M router (only)
logger (04.05.2016 14:24:37): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 14:24:37): disconnect station 0 (Vantage): read failed
logger (04.05.2016 14:25:07): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 14:25:07): wakeup sent.
logger (04.05.2016 14:25:07): internal logger activated.
logger (04.05.2016 14:25:07): syncing.
logger (04.05.2016 14:25:18): gettime request sent.
logger (04.05.2016 14:25:18): time offset of Vantage: -1 minutes
logger (04.05.2016 14:25:18): eeprom request sent.
logger (04.05.2016 14:25:19): rain collector size 0.2 mm per tick.
logger (04.05.2016 14:25:19): transmitter 3 active as station type (#0) "ISS".
logger (04.05.2016 14:25:19): firmware version request sent.
logger (04.05.2016 14:25:20): firmware version 1.90
logger (04.05.2016 14:25:20): no reading of Vantage's internal logger.
logger (04.05.2016 14:28:13): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 14:28:13): disconnect station 0 (Vantage): read failed
logger (04.05.2016 14:28:43): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 14:28:43): wakeup sent.
logger (04.05.2016 14:28:43): internal logger activated.
logger (04.05.2016 14:28:43): syncing.
logger (04.05.2016 14:28:54): gettime request sent.
logger (04.05.2016 14:28:54): time offset of Vantage: -1 minutes
logger (04.05.2016 14:28:54): eeprom request sent.
logger (04.05.2016 14:28:55): rain collector size 0.2 mm per tick.
logger (04.05.2016 14:28:55): transmitter 3 active as station type (#0) "ISS".
logger (04.05.2016 14:28:55): firmware version request sent.
logger (04.05.2016 14:28:56): firmware version 1.90
logger (04.05.2016 14:28:56): no reading of Vantage's internal logger.
logger (04.05.2016 14:29:00): station 0 (Vantage), reading weather station failed: Connection reset by peer
logger (04.05.2016 14:29:00): disconnect station 0 (Vantage): read failed
logger (04.05.2016 14:29:30): connect station 0 (Vantage via TCP/IP).
logger (04.05.2016 14:29:30): wakeup sent.
logger (04.05.2016 14:29:30): internal logger activated.
logger (04.05.2016 14:29:30): syncing.
logger (04.05.2016 14:29:41): gettime request sent.
logger (04.05.2016 14:29:42): time offset of Vantage: -1 minutes
logger (04.05.2016 14:29:42): eeprom request sent.
logger (04.05.2016 14:29:42): rain collector size 0.2 mm per tick.
logger (04.05.2016 14:29:42): transmitter 3 active as station type (#0) "ISS".
logger (04.05.2016 14:29:42): firmware version request sent.
logger (04.05.2016 14:29:43): firmware version 1.90
logger (04.05.2016 14:29:43): no reading of Vantage's internal logger.
Re: MB Pro failure to read WeatherLink IP data
Also an update on my side: after a month of log observations, I confirm what Mattk mentions in his post above, i.e., the cycle does not stop.
Re: MB Pro failure to read WeatherLink IP data
The cycle certainly does not stop and from what I have observed the cycle can be anything from several minutes but no longer than 1 hour. This cycle (from what I observed/logged) does not appear to be failing to read data but obviously is an overhead that the unit could do without? I also have a MB Pro on the same network as one of the MB's showing this cycle, the MB Pro is receiving via RF (Davis) and has no indication of this cycle at all (totally clean) so this tends to point to something being triggered with the WLIP logger? Also have another MB on a dedicated cellular router which also displays this cycle so this would/could tend to indicate the trigger is incoming from the WWW? We know WeatherLink.com and the MB Server have connections into the local networks, who knows what else there might be?chrysnic wrote:Also an update on my side: after a month of log observations, I confirm what Mattk mentions in his post above, i.e., the cycle does not stop.
Re: MB Pro failure to read WeatherLink IP data
To be honest I don't really have an idea here. The message indicates that reading from the TCP connection does fail,
so there is a problem in receiving data from the WLIP. May be the WLIP is blocking for some reason. Does behavior change when you tell on "station" tab that WLIP should not be given the chance every X minutes or so to upload data to weatherlink?
Maybe this takes unusual long and results into this kind of problem? Or WLIP cuts the line to MB after a while
to enforce having its data uploaded to weatherlink, which Davis might have an interest in and changed the behavior
of the WLIP that way. Playing with this parameter might give us more insight...
so there is a problem in receiving data from the WLIP. May be the WLIP is blocking for some reason. Does behavior change when you tell on "station" tab that WLIP should not be given the chance every X minutes or so to upload data to weatherlink?
Maybe this takes unusual long and results into this kind of problem? Or WLIP cuts the line to MB after a while
to enforce having its data uploaded to weatherlink, which Davis might have an interest in and changed the behavior
of the WLIP that way. Playing with this parameter might give us more insight...
Re: MB Pro failure to read WeatherLink IP data
OK, I have just configured the MB Pro to NOT upload to WeatherLink ("no WL upload" setting on "Station" tab). I will observe the log and report in 24 hours or so.
chrysnic
chrysnic