meteohub.de

Hi,

Everytime when I reboot de MeteoHub (after a update for example) I have issues to re-connect my Davis Logger and Meteostick.
I have to unplug the devices and reboot the MeteoHub (sometimes multiple times) and re-connect my devices.... or change the device settings (from USB to TTY)
This behaviour also occurs after updating the meteostick with a new firmware.

See log

ogger (20.11.2015 10:30:52): data logger (version 5.0l, build 146) started.
logger (20.11.2015 10:30:55): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:30:55): connect station 1 (Meteostick Vantage via USB serial).
logger (20.11.2015 10:30:55): connect station 2 (System Data via Plug-in).
logger (20.11.2015 10:30:55): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:30:55): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:30:55): station 0 (Vantage), syncing.
logger (20.11.2015 10:31:06): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:31:16): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:31:26): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:31:36): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:31:38): parent process received termination signal (15).
logger (20.11.2015 10:31:38): child process received termination signal (15).
logger (20.11.2015 10:31:38): disconnect station 1 (Meteostick Vantage): wrap-up
logger (20.11.2015 10:31:38): disconnect station 2 (System Data): wrap-up
logger (20.11.2015 10:31:39): data logger stopped.
logger (20.11.2015 10:32:19): data logger (version 5.0l, build 146) started.
logger (20.11.2015 10:32:20): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:32:20): connect station 1 (Meteostick Vantage via USB serial).
logger (20.11.2015 10:32:20): connect station 2 (System Data via Plug-in).
logger (20.11.2015 10:32:20): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:32:20): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:32:20): station 0 (Vantage), syncing.
logger (20.11.2015 10:32:31): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:32:41): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:32:51): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:33:01): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:33:31): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:33:31): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:33:31): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:33:31): station 0 (Vantage), syncing.
logger (20.11.2015 10:33:41): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:33:51): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:34:01): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:34:11): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:34:41): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:34:41): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:34:41): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:34:41): station 0 (Vantage), syncing.
logger (20.11.2015 10:34:51): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:35:01): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:35:11): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:35:21): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:35:51): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:35:51): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:35:51): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:35:51): station 0 (Vantage), syncing.
logger (20.11.2015 10:36:01): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:36:11): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:36:21): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:36:31): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:36:40): kernel module 'cp2101 cp210x' reloaded, module messages: Error: Module cp210x is in use FATAL: Module cp2101 not found.
logger (20.11.2015 10:37:01): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:37:01): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:37:01): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:37:01): station 0 (Vantage), syncing.
logger (20.11.2015 10:37:11): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:37:21): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:37:31): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:37:41): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:37:50): kernel module 'cp2101 cp210x' reloaded, module messages: Error: Module cp210x is in use FATAL: Module cp2101 not found.
logger (20.11.2015 10:38:11): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:38:11): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:38:11): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:38:11): station 0 (Vantage), syncing.
logger (20.11.2015 10:38:21): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:38:31): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:38:41): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:38:51): disconnect station 0 (Vantage): timeout
logger (20.11.2015 10:38:59): parent process received termination signal (15).
logger (20.11.2015 10:38:59): child process received termination signal (15).
logger (20.11.2015 10:39:00): kernel module 'cp2101 cp210x' reloaded, module messages: Error: Module cp210x is in use FATAL: Module cp2101 not found.
logger (20.11.2015 10:39:00): disconnect station 1 (Meteostick Vantage): wrap-up
logger (20.11.2015 10:39:00): disconnect station 2 (System Data): wrap-up
logger (20.11.2015 10:39:01): data logger stopped.
logger (20.11.2015 10:39:39): data logger (version 5.0l, build 146) started.
logger (20.11.2015 10:39:40): connect station 0 (Vantage via USB serial).
logger (20.11.2015 10:39:40): connect station 1 (Meteostick Vantage via USB serial).
logger (20.11.2015 10:39:40): connect station 2 (System Data via Plug-in).
logger (20.11.2015 10:39:40): station 0 (Vantage), wakeup sent.
logger (20.11.2015 10:39:40): station 0 (Vantage), internal logger activated.
logger (20.11.2015 10:39:40): station 0 (Vantage), syncing.
logger (20.11.2015 10:39:50): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:40:00): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:40:10): station 0 (Vantage), gettime request sent.
logger (20.11.2015 10:40:20): disconnect station 0 (Vantage): timeout

There are two type of names for the same USB ports

Example: USB serial /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyMH21

The ttyUSB are not fixed to a physical port so after rebooting they can and often will be connected to a different physical port.
It happens often on a raspberry with its two ports , also with other weatherprograms as this has costs me a lot of wasted time with another weatherprogram.

Meteohub has also ports with MH in the name and they are tied to a physical port.

If you use those with MH in the name there should be less problems.

Wim

Wim,

I will give it a try to use MH112 and MH113 instead of USB0 and USB1.

I'm using a Raspberry PI 2 which has 4 usb ports.
When I drop down the menu (Under weatherstation --> Device) I have USB0, USB1,USB2,USB3 and MH112 and MH113.
I assume there must also a MH114 and MH115?

Regards,
Martijn

I notice also this entries in the log.

logger (20.11.2015 13:15:25): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 05 a8 ff c1 00 89 54) -77db
logger (20.11.2015 13:16:18): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 01 5e ff c1 00 b8 86) -77db
logger (20.11.2015 13:17:10): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 03 af ff c1 00 15 fc) -77db
logger (20.11.2015 13:18:55): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 03 c8 ff c3 00 7b 61) -79db
logger (20.11.2015 13:19:48): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 02 b0 ff c3 00 16 86) -76db
logger (20.11.2015 13:20:40): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 04 03 ff c3 00 b1 0e) -77db
logger (20.11.2015 13:21:33): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 02 6b ff c3 00 a0 9a) -77db
logger (20.11.2015 13:22:25): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.5)uvi (41 04 d2 ff c1 00 09 db) -79db

assenzuid wrote:Wim,

I will give it a try to use MH112 and MH113 instead of USB0 and USB1.

I'm using a Raspberry PI 2 which has 4 usb ports.
When I drop down the menu (Under weatherstation --> Device) I have USB0, USB1,USB2,USB3 and MH112 and MH113.
I assume there must also a MH114 and MH115?

Regards,
Martijn

Yes more ports can be shown, but only if a device is attached.
So your weather station is connected to either 112 or 113.
Wim

Wim,

I can confirm that this is working.
Chancing it to MH112 and MH113, perform a reboot and it's works directly.

Only strange log entry is:
logger (20.11.2015 19:57:56): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.0)uvi (41 02 8d ff c1 00 65 8b) -83db

Thanks.
Martijn

UV > 20 in the winter looks strange, unless you are in Australia. I can move the bounds up
in correspondence to a melting atmosphere. No kidding, do you really have that intense UV
or is it more a misreading?

No, The sensor reports 0
See attachment.

I noticed it a few weeks ago already after a firmware update, I will check if there is a new MeteoStick firmware and will load it on to the meteostick.

logger (24.11.2015 21:19:35): station 1 (Meteostick Vantage), suspicious (blocked) uv reading: uv(last) 20.1(0.0)uvi (41 04 57 ff c1 00 68 a6) -77db

After changing the Settings from USB0 and USB1 to MH112 and MH113 I have still the issue.

logger (24.11.2015 21:02:25): data logger (version 5.0l, build 146) started.
logger (24.11.2015 21:02:26): connect station 0 (Vantage via USB serial).
logger (24.11.2015 21:02:26): connect station 1 (Meteostick Vantage via USB serial).
logger (24.11.2015 21:02:26): connect station 2 (System Data via Plug-in).
logger (24.11.2015 21:02:26): station 0 (Vantage), wakeup sent.
logger (24.11.2015 21:02:26): station 0 (Vantage), internal logger activated.
logger (24.11.2015 21:02:26): station 0 (Vantage), syncing.
logger (24.11.2015 21:02:36): station 0 (Vantage), gettime request sent.
logger (24.11.2015 21:02:46): station 0 (Vantage), gettime request sent.
logger (24.11.2015 21:02:56): station 0 (Vantage), gettime request sent.
logger (24.11.2015 21:03:06): disconnect station 0 (Vantage): timeout
logger (24.11.2015 21:03:36): connect station 0 (Vantage via USB serial).

At USB0 the Meteostick is connected, otherwise I can't update the MeteoStick's firmware.
USB1 a Davis Datalogger.

disconnect Vantage console from power, USB and remove batteries. wait a minute.
put n batteries (if any), connect with power and then connect with USB.
Console hangs up sometimes, when data logger is inserted during console operation.

I'm using a Weather Envoy data logger (USB connected) with my MeteoHub

same procedure. Envoy is just a console where they forgot to solder the display

Okay, will give it an try