Meteohub 4.9k (build 1068) Stops Logging and Sending Data

[ApexWx]

Hello,

I am a newbie with regards to the Meteohub (and Linux)--just started using the DC01 a couple of weeks ago (purchased from Ambient Weather which sells the unit as "Weather Hub 4" in the US).

Anyway, I really like the "always on" functionality of Meteohub, and love the compact size of this device (plus the "green" aspects, too), but I have had a persistent problem. I'm using Meteohub with a Davis Instrument Vantage Pro 2 using a USB-Serial logger.

Meteohub will be logging data and sending info to the various weather networks, but then it suddenly stops logging data or transmitting to the wx networks. Looking at what I think are relevant logs, I get the following.

First, the "meteohub log" records the following, which is typical after the unit spontaneously ceases to log and transmit data:

logger (29.06.2012 23:05:32): child process received timeout signal (14).
logger (29.06.2012 23:06:19): disconnect station 1 (Vantage).
logger (29.06.2012 23:06:22): data logger stopped.
logger (29.06.2012 23:06:23): data logger (version 4.9k, build 1069) started.
logger (29.06.2012 23:07:45): connect station 1 (Vantage via USB serial).
logger (29.06.2012 23:21:35): child process received timeout signal (14).
logger (29.06.2012 23:22:22): disconnect station 1 (Vantage).
logger (29.06.2012 23:22:25): data logger stopped.
logger (29.06.2012 23:22:26): data logger (version 4.9k, build 1069) started.
logger (29.06.2012 23:23:48): connect station 1 (Vantage via USB serial).
logger (29.06.2012 23:37:38): child process received timeout signal (14).
logger (29.06.2012 23:38:25): disconnect station 1 (Vantage).
logger (29.06.2012 23:38:27): data logger stopped.
logger (29.06.2012 23:38:29): data logger (version 4.9k, build 1069) started.
logger (29.06.2012 23:39:51): connect station 1 (Vantage via USB serial).
logger (29.06.2012 23:53:41): child process received timeout signal (14).
logger (29.06.2012 23:54:28): disconnect station 1 (Vantage).
logger (29.06.2012 23:54:30): data logger stopped.
logger (29.06.2012 23:54:32): data logger (version 4.9k, build 1069) started.
logger (29.06.2012 23:55:53): connect station 1 (Vantage via USB serial).
logger (30.06.2012 00:09:43): child process received timeout signal (14).
logger (30.06.2012 00:10:30): disconnect station 1 (Vantage).
logger (30.06.2012 00:10:33): data logger stopped.
logger (30.06.2012 00:10:34): data logger (version 4.9k, build 1069) started.
logger (30.06.2012 00:11:56): connect station 1 (Vantage via USB serial).
logger (30.06.2012 00:25:46): child process received timeout signal (14).
logger (30.06.2012 00:26:33): disconnect station 1 (Vantage).
logger (30.06.2012 00:26:35): data logger stopped.
logger (30.06.2012 00:26:37): data logger (version 4.9k, build 1069) started.
logger (30.06.2012 00:27:59): connect station 1 (Vantage via USB serial).
logger (30.06.2012 00:41:49): child process received timeout signal (14).
logger (30.06.2012 00:42:36): disconnect station 1 (Vantage).

To me, there seems to be some sort of hang-up that is causing a loop here as Meteohub tries to contact the station, but gets a "timeout" and disconnects then repeats the process. I have tweaked the time out length for "dropped" sensor setting from 300 up to 600 seconds (for example), but that doesn't seem to be the fix.

Also, it does state on the "alarm log" that it isn't getting a reading from the outdoor temp sensor, but my check of that sensor shows that it is running normally and gets good quality check feedback from the CWOP network that it transmits data to. However, that sensor could be connected in some way since that shows up on the alarm log.

Currently, the only fix is to reboot Meteohub, but that rather defeats the point of having the "always on" connection to the weather networks.

So, I've been looking over the forum, but don't see a precise analog to my problem, so I will seek the wisdom of more experienced users with the caveat that while I am comfortable with tech, I am also new to this system (and Linux--as mentioned above), so I might ask for some step-by-step details to resolve the problem, so anyone offering assistance, I ask for your patience as I work to resolve the problem.

All assistance is greatly appreciated!

[wvdkuil]

When you search this forum for USB+cable+problems you wiill be surprised to see the number of problems with USB cables and serial to usb converters.
So first swap the cable for a short and good cable.
Try to rearrange your setup so that the cable is not close to any interference prone device.

Lets see if the problem disappears.

Wim van der Kuil
http://www.weerstation-Leuven.be

[wvdkuil]

From another post by admin: USB HID problems on DC01 - read for WORK-AROUND

Update: It turns out that the USB kernel drivers for oxnas chipset in DC01 do not support USB 1.x low speed USB HID devices. As I don't know if/how to patch these linux kernel drivers, I recommend to use a passive, cheap USB 2.0 HUB to be placed between DC01 USB port and the USB cable of the weather station. Any USB 2.0 hub for a couple of dollars will do.

Maybe this can help?

[ApexWx]

Thanks for the advice--I see now that the cable may well be the culprit. I have a USB 2.0 hub on order (I live in a rural area, so e-commerce is the quickest route) and will hook it up on arrival early next week. I'm also reconfiguring the hook up so that the USB cable is away from the hub and the wireless station console just a bit to try and cut down on any interference. I may have a short cable somewhere about (seems I remember getting one with a piece of equipment some time ago) and will try that out, too.

Thanks for the advice and I will update once I try the solution/work-around suggestions.

[ApexWx]

Greetings,

I have just received and installed the USB 2.0 hub and will monitor to see if the problem resolves. I'll post a note here once sufficient time has passed to know if the suggested solution proved successful.

Thanks again to my respondents.

[ApexWx]

Greetings,

The USB 2.0 hub appears to have done the trick. Meteohub has been operating continuously without time-outs or other lost data for over a day now.

I greatly appreciate the assistance.