MeteoBridge - Vantage USB logger connection issue **solved**

[scottgw]

I am struggling to get my MeteoBridge to communicate with my Vantage Pro2 console via a Davis USB data logger. I have no trouble getting the console to talk to WeatherLink on my PC via the USB cable I run to the MeteoBridge - historical data is downloaded without any issues. The system tab of MeteoBridge give me the following set of messages which loop for a few minutes before stopping. I have tried every possible combination of powering down and reinstalling the data logger without success.

Any suggestions appreciated!
Scott

wnetd (17.10.2014 16:42:05): process started.
test5m (17.10.2014 16:42:08): logger stalled, will be restarted now
logger (17.10.2014 16:42:09): No historical data loaded.
logger (17.10.2014 16:42:09): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:42:09): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:42:38): No historical data loaded.
logger (17.10.2014 16:42:38): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:42:39): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:43:08): No historical data loaded.
logger (17.10.2014 16:43:08): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:43:09): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:43:38): No historical data loaded.
logger (17.10.2014 16:43:38): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:43:39): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:44:08): No historical data loaded.
logger (17.10.2014 16:44:08): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:44:09): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:44:38): No historical data loaded.
logger (17.10.2014 16:44:38): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:44:39): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:45:08): No historical data loaded.
logger (17.10.2014 16:45:08): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:45:09): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:45:38): No historical data loaded.
logger (17.10.2014 16:45:38): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:45:39): connect station 0 (Vantage via USB serial).
logger (17.10.2014 16:46:08): No historical data loaded.
logger (17.10.2014 16:46:08): data logger (version 5.0, build 5034) started.
logger (17.10.2014 16:46:09): station 0 (Vantage), can't open device /dev/ttyMH: No such file or directory
logger (17.10.2014 16:46:39): No historical data loaded.

System details:
Platform: TP-LINK TL-MR3020
RAM: 29364 kB total, 5748 kB free (80% used)
Software Version: Linux 3.3.8 mips (BE), FW 1.4, MeteoBridge 2.4 (5034)

[wvdkuil]

If you previously used Weatherlink only, the USB logger is probably set to usbexpress mode, which is a Davis-only way of communicating with the USB logger. See page 15 of the manual (not page 15 of the pdf) http://www.davisnet.com/product_documen ... 0_6555.pdf
with the warning about USB-express mode.

Do not know for sure if that is your problem, but multiple other weather programs have issues with that mode. And Weatherlink will still communicate normally with the reset logger.

Wim

[admin]

Are you using the mandatory USB hub in between?

[scottgw]

I wasn't made aware of the USB hub requirement by the Davis salesperson. Have now inserted one. No difference. No data loaded. I have checked that the logger is running in serial mode using weather link - it registers as serial comm post 4, so I think that is all as it should be.

[admin]

You can grant me access to your meteobridge as explained in the link below.
Please set password to "needhelp" and send the login link to "info(at)meteobridge.com".

viewtopic.php?f=57&t=9885

[Clément]

Hello,

I also have a problem of connection...
Software Version: Linux 3.3.8 mips (BE), FW 1.4, MeteoBridge 2.4 (5034)

Code: Select all

wnetd (17.10.2014 14:02:52): process started.
test5m (17.10.2014 14:02:55): logger stalled, will be restarted now
logger (17.10.2014 14:02:56): Historical data loaded (18 records).
logger (17.10.2014 14:02:56): data logger (version 5.0, build 5034) started.
logger (17.10.2014 14:02:56): connect station 0 (Vantage via USB serial).
logger (17.10.2014 14:02:57): station 0 (Vantage), wakeup sent.
logger (17.10.2014 14:02:58): station 0 (Vantage), internal logger activated.
logger (17.10.2014 14:02:58): station 0 (Vantage), syncing.
logger (17.10.2014 14:03:08): station 0 (Vantage), gettime request sent.
logger (17.10.2014 14:03:08): station 0 (Vantage), no Vantage time offset.
logger (17.10.2014 14:03:08): station 0 (Vantage), eeprom request sent.
logger (17.10.2014 14:03:08): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (17.10.2014 14:03:08): station 0 (Vantage), transmitter 1 active as station type (#0) "ISS".
logger (17.10.2014 14:03:08): station 0 (Vantage), transmitter 4 active as station type (#4) "Wind".
logger (17.10.2014 14:03:08): station 0 (Vantage), firmware version request sent.
logger (17.10.2014 14:03:08): station 0 (Vantage), firmware version 3.15
logger (17.10.2014 14:03:08): station 0 (Vantage), no reading of Vantage's internal logger.
logger (19.10.2014 09:09:26): child process received timeout signal (14).
logger (19.10.2014 09:10:12): data logger stopped.
logger (19.10.2014 09:10:12): Historical data loaded (18 records).
logger (19.10.2014 09:10:12): data logger (version 5.0, build 5034) started.
logger (19.10.2014 09:10:22): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:10:52): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:11:22): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:11:52): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:12:22): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:12:52): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:13:22): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:13:52): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:14:22): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:14:52): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (19.10.2014 09:20:52): child process received timeout signal (14).
logger (19.10.2014 09:20:53): data logger stopped.
logger (19.10.2014 09:20:53): Historical data loaded (18 records).
logger (19.10.2014 09:20:53): data logger (version 5.0, build 5034) started.

After reboot everything goest back to normal for one day or two.
The datalogger never worked with Weatherlink.
Note that there is no USB HUB as mentioned on the release page. Several other MeteoBridge work well without that HUB.

[admin]

@Clement: The errors you receive are very typical for a missing USB hub. Please believe me, you need one.

@Scott: There was a bug that aborts logger process, when an alarm was defined that had an empty raise or clear condition. Latest update from today does fix this.

[Clément]

Ok, I thought it was not necessary anymore as written in the changelog.
Have you an explanation about why some MeteoBridges don't have this issue?

[admin]

Have you an explanation about why some MeteoBridges don't have this issue?

All based on the Atheros chipset (D-Link and TP-Link) have the issue. It has been fixed for some
FTDI usb serial adapters, but not for the cp210x inside the Davis USB logger. When used on wired
LAN the problem does occur less often than when on WiFi, but it never works really stable without.

If you want to avoid the USB hub, you need to go with the Asus WL-330N3G platform, which
is not Atheros based. As Atheros does not provide too much information and you have to go under
NDA I don't think there will be a fix in the near future. But come on... adding a passive hub
might not be nice to look at but it adds just minimal costs and isn't a big thing at all