I just installed MB V3.1 on DIR-505. It updated to V3.3 during a reboot. Ran for 1.5 days uploading data to WU without issue both wired and wireless config MB to Router. Now stopped accessing data from Davis VP2 with Weatherlink USB logger V3.15 FW. In MB Weatherstation Tab, Davis Vantage Pro 2: USB has red 'X'. I have powered down the VP2, removed/reseated Data logger, rebooted VP, tried different USB cables btwn VP2/MB, tried: no USB hub/direct connect, powered, and non-powered USB 2.0 hubs. Reflashed MB back to V3.1, 3.2 and 3.3. Nothing works, but the Weatherlink SW is able to get VP2 data from VP2 data logger under all above scenarios.
MB gave a message about needing USB 2.0 hub even with USB hub in use.
Log after latest MB flash/reboot (sticking with MB V3.1 and hardwired to LAN router):
logger (25.07.2017 02:34:03): Historical data loaded (19 records).
logger (25.07.2017 02:34:03): data logger (version 5.0t, build 10776) started.
logger (25.07.2017 02:34:03): connect station 0 (Vantage via USB serial).
logger (25.07.2017 02:34:04): wakeup sent.
logger (25.07.2017 02:34:04): internal logger activated.
logger (25.07.2017 02:34:04): syncing.
logger (25.07.2017 02:34:14): gettime request sent.
logger (25.07.2017 02:34:14): no Vantage time offset.
logger (25.07.2017 02:34:14): eeprom request sent.
logger (25.07.2017 02:34:14): rain collector size 0.01 inch per tick.
logger (25.07.2017 02:34:14): transmitter 1 active as station type (#0) "ISS".
logger (25.07.2017 02:34:14): firmware version request sent.
logger (25.07.2017 02:34:14): firmware version 3.15
logger (25.07.2017 02:34:14): no reading of Vantage's internal logger.
logger (25.07.2017 02:50:40): child process received timeout signal (14).
logger (25.07.2017 02:51:15): disconnect station 0 (Vantage): exit
logger (25.07.2017 02:51:16): data logger stopped.
logger (25.07.2017 02:51:16): Historical data loaded (19 records).
logger (25.07.2017 02:51:16): data logger (version 5.0t, build 10776) started.
logger (25.07.2017 02:51:21): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
logger (25.07.2017 02:51:51): station 0 (Vantage), can't open device /dev/ttyMH: Input/output error
Live Data Tab reports uploading to WU successfully at 02:45:08 and then sensor update times start to climb as the connection is lost. Back to red X on VP2: USB on weather station tab.
Data can still be read via same USB cable in Weather link SW.
Any suggestions? Bad DIR-505? Bad Weather Link Data logger (Davis support say no because it works with Weather link software)?
Meteobridge (DIR-505) stopped access to Davis Data Logger VP2
Moderator: Mattk
Re: Meteobridge (DIR-505) stopped access to Davis Data Logger VP2
I would suggest to buy a spare D-505. Any part can die, but most devices either work for a very short period or they work for many years.
Install Meteobridge on another device, just to test if that device works again with the hub attached, probably it will work OK.
Wim
Install Meteobridge on another device, just to test if that device works again with the hub attached, probably it will work OK.
Wim
Re: Meteobridge (DIR-505) stopped access to Davis Data Logger VP2
Thanks for the quick response! I ordered another DIR-505. What other device can I try? I would assume it has to be a weather station. If so, the VP2 is the only listed device I have.
What is strange is that it connects at some point upon re flashing/rebooting, because it gets the historical data from somewhere after deleting it and reflasshing the MB. I assume the data comes from the Davis logger.
I doubt that it is a USB connector hardware issue because I can flash the MB from a USB stick and it reads the stick and writes a log file.
Is there any way to revert the DIR-505 back to its original functionality to test?
What is strange is that it connects at some point upon re flashing/rebooting, because it gets the historical data from somewhere after deleting it and reflasshing the MB. I assume the data comes from the Davis logger.
I doubt that it is a USB connector hardware issue because I can flash the MB from a USB stick and it reads the stick and writes a log file.
Is there any way to revert the DIR-505 back to its original functionality to test?
Re: Meteobridge (DIR-505) stopped access to Davis Data Logger VP2
The historical data is safely stored also at the meteoplug server.JetJockey wrote: Tue Jul 25, 2017 4:07 pm What is strange is that it connects at some point upon re flashing/rebooting, because it gets the historical data from somewhere after deleting it and reflasshing the MB. I assume the data comes from the Davis logger.
http://meteobridge.com/wiki/index.php/Live_Data => Historical Data =>
Meteobridge also keeps track of some historical data like min/max values of the day, month, year and all time. As this information would be lost during a powercycle or reboot, Meteobridge does store this information on the Meteobridge Internet server in regular intervals. After a restart of your Meteobridge devices data is restored from there so that statistics have a chance to be correct even over a longer time period.
No.Is there any way to revert the DIR-505 back to its original functionality to test?
We need to be sure it is not the DIR-505, and if not so, you have a spare one.
You tested if the other component, the USB hub, could be the culprit
And you tested multiple versions of the Meteobridge software.
Never heard of a faulty Davis logger, so lets see if a new D-505 works OK.
Wim
Re: Meteobridge (DIR-505) stopped access to Davis Data Logger VP2
Please also read this
https://www.manula.com/manuals/pws/davi ... gger-modes
If by accident you connected the USB logger to Weatherlink and set the mode to USB-xpress you have to reset it back to serial!
No other devices /weather-programs than Weatherlink, understand the USB-xpress mode.
So check your Weatherlink program !
===
If all is working correctly, you can use Weatherlink on your PC, but do not connect it using a usb cable. You can always run 1 extra weather-program next to the Meteobridge. Use the pass-through function of the Meteobridge and tell your Weatherlink program to access the logger at the ip-adress opf the meteobridge (192.168.xxx.yyy at port 22222.
Wim
https://www.manula.com/manuals/pws/davi ... gger-modes
If by accident you connected the USB logger to Weatherlink and set the mode to USB-xpress you have to reset it back to serial!
No other devices /weather-programs than Weatherlink, understand the USB-xpress mode.
So check your Weatherlink program !
===
If all is working correctly, you can use Weatherlink on your PC, but do not connect it using a usb cable. You can always run 1 extra weather-program next to the Meteobridge. Use the pass-through function of the Meteobridge and tell your Weatherlink program to access the logger at the ip-adress opf the meteobridge (192.168.xxx.yyy at port 22222.
Wim
Re: Meteobridge (DIR-505) stopped access to Davis Data Logger VP2
Thanks for all of the ideas!
Davis support was great. They couldn't do much when the WL, VP2, and logger all work as expected without MB. They offered to go over the equipment out of warranty for $70 if I returned it.
I currently have WL collecting data via USB (serial) until MB is fixed. WL shows serial/Com5 and is getting data to WU. Win 7 Device manager shows CP210x USB to UART Bridge on Com5 working properly.
When MB was working and sending data to WU, I had WL getting data from MB pass through on port 22222. Something definitely changed causing MB to stop seeing Davis Logger, although the query for VP2 firmware returned correct V3. 15.
Guess that explains where the historical data came from! Agree that it shouldn't be the Davis logger since it and WL function normally.
I ordered 2 DIR-505s and due to arrive Thursday! I'll post the results with new DIR-505 then. Again, thanks to all for all of the help!
Davis support was great. They couldn't do much when the WL, VP2, and logger all work as expected without MB. They offered to go over the equipment out of warranty for $70 if I returned it.
I currently have WL collecting data via USB (serial) until MB is fixed. WL shows serial/Com5 and is getting data to WU. Win 7 Device manager shows CP210x USB to UART Bridge on Com5 working properly.
When MB was working and sending data to WU, I had WL getting data from MB pass through on port 22222. Something definitely changed causing MB to stop seeing Davis Logger, although the query for VP2 firmware returned correct V3. 15.
Guess that explains where the historical data came from! Agree that it shouldn't be the Davis logger since it and WL function normally.
I ordered 2 DIR-505s and due to arrive Thursday! I'll post the results with new DIR-505 then. Again, thanks to all for all of the help!