Cannot connect to VP2 datalogger

All about the standard Meteobridge devices based on mobile routers from TP-Link, D-Link, ASUS

Moderator: Mattk

Post Reply
Clément
Senior Boarder
Senior Boarder
Posts: 41
Joined: Sun Nov 24, 2013 11:04 am
Contact:

Cannot connect to VP2 datalogger

Post by Clément » Thu Nov 30, 2017 10:34 pm

Hello,

It seems that the Meteobridge has some difficulties to connect to my VP2 datalogger...
Here is the log:

Code: Select all

wnetd (30.11.2017 21:23:28): process started.
system (30.11.2017 21:23:28): start of logging process initiated.
logger (30.11.2017 21:23:28): no historical data loaded.
logger (30.11.2017 21:23:28): data logger (version 5.0w, build 11648) started.
logger (30.11.2017 21:23:29): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:23:29): wakeup sent.
logger (30.11.2017 21:23:29): internal logger activated.
logger (30.11.2017 21:23:29): syncing.
logger (30.11.2017 21:23:32): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (30.11.2017 21:23:32): services paused.
logger (30.11.2017 21:23:39): gettime request sent.
logger (30.11.2017 21:23:59): message above repeats 2 times.
logger (30.11.2017 21:24:09): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:24:39): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:24:39): wakeup sent.
logger (30.11.2017 21:24:39): internal logger activated.
logger (30.11.2017 21:24:39): syncing.
logger (30.11.2017 21:24:49): gettime request sent.
logger (30.11.2017 21:25:09): message above repeats 2 times.
logger (30.11.2017 21:25:19): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:25:29): give up waiting for sensors after 120 secs.
logger (30.11.2017 21:25:29): services activated.
logger (30.11.2017 21:25:49): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:25:49): wakeup sent.
logger (30.11.2017 21:25:49): internal logger activated.
logger (30.11.2017 21:25:49): syncing.
logger (30.11.2017 21:25:59): gettime request sent.
logger (30.11.2017 21:26:19): message above repeats 2 times.
logger (30.11.2017 21:26:29): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:26:59): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:26:59): wakeup sent.
logger (30.11.2017 21:26:59): internal logger activated.
logger (30.11.2017 21:26:59): syncing.
logger (30.11.2017 21:27:09): gettime request sent.
logger (30.11.2017 21:27:29): message above repeats 2 times.
logger (30.11.2017 21:27:39): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:28:09): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:28:09): wakeup sent.
logger (30.11.2017 21:28:09): internal logger activated.
logger (30.11.2017 21:28:09): syncing.
logger (30.11.2017 21:28:19): gettime request sent.
logger (30.11.2017 21:28:39): message above repeats 2 times.
logger (30.11.2017 21:28:49): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:28:51): usb port reset.
logger (30.11.2017 21:29:19): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:29:19): wakeup sent.
logger (30.11.2017 21:29:19): internal logger activated.
logger (30.11.2017 21:29:19): syncing.
logger (30.11.2017 21:29:29): gettime request sent.
logger (30.11.2017 21:29:49): message above repeats 2 times.
logger (30.11.2017 21:29:59): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:30:01): usb port reset.
logger (30.11.2017 21:30:29): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:30:29): wakeup sent.
logger (30.11.2017 21:30:29): internal logger activated.
logger (30.11.2017 21:30:29): syncing.
logger (30.11.2017 21:30:39): gettime request sent.
logger (30.11.2017 21:30:59): message above repeats 2 times.
logger (30.11.2017 21:31:09): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:31:11): usb port reset.
logger (30.11.2017 21:31:39): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:31:39): wakeup sent.
logger (30.11.2017 21:31:39): internal logger activated.
logger (30.11.2017 21:31:39): syncing.
logger (30.11.2017 21:31:49): gettime request sent.
logger (30.11.2017 21:32:09): message above repeats 2 times.
logger (30.11.2017 21:32:19): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:32:21): usb port reset.
logger (30.11.2017 21:32:49): connect station 0 (Vantage via USB serial).
logger (30.11.2017 21:32:49): wakeup sent.
logger (30.11.2017 21:32:49): internal logger activated.
logger (30.11.2017 21:32:49): syncing.
logger (30.11.2017 21:32:59): gettime request sent.
logger (30.11.2017 21:33:19): message above repeats 2 times.
logger (30.11.2017 21:33:29): disconnect station 0 (Vantage): timeout
logger (30.11.2017 21:33:31): usb port reset.
MB running on MR3020, V3.4, Firmware 1.5.

Any ideas?

Thanks...

Colin
Fresh Boarder
Fresh Boarder
Posts: 17
Joined: Mon Aug 17, 2015 12:30 pm

Re: Cannot connect to VP2 datalogger

Post by Colin » Sat Dec 02, 2017 4:28 am

For what it is worth and because of lack of response from other members I will put my views forward.
I had a very similar problems with my VP2 and Meteobridge not talking to each other. Went on for ages on an intermittent basis.
The fault was less frequent when I used a USB hub between the 2.
Admin logged onto my system and changed a setting on the weather network page. He set the retries to 'no retries' and the fault has disappeared.
Been good for months now.
Not saying that is the answer to your problem, just saying it is what fixed mine.
Hope it helps....

Clément
Senior Boarder
Senior Boarder
Posts: 41
Joined: Sun Nov 24, 2013 11:04 am
Contact:

Re: Cannot connect to VP2 datalogger

Post by Clément » Sat Dec 02, 2017 1:53 pm

Hello Colin,

Thank you for your answer.
Unfortunately, so far, your workaround has not fixed anything.

Regards.

User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 5025
Joined: Mon Oct 01, 2007 10:51 pm

Re: Cannot connect to VP2 datalogger

Post by admin » Sun Dec 03, 2017 12:59 pm

Your Vantage does not report any data over USB.

1) Make sure you have a USB 2.0 hub inbetween, this is mandatory.

2) Other reason might be that Console's USB port has hung up when inserting the USB logger into a powered-on Console:
Please remove USB connection, Power and batteries from the console, then put all in again.

3) Please also check that logger is still tightly fitting in the console, it might have swapped out.

Clément
Senior Boarder
Senior Boarder
Posts: 41
Joined: Sun Nov 24, 2013 11:04 am
Contact:

Re: Cannot connect to VP2 datalogger

Post by Clément » Mon Dec 04, 2017 3:12 pm

Thanks for the reply.

1) Yes.
2 and 3) I'll try it again...

Post Reply