WMR 300 & Meteobridge Help please **solved**

[s type72]

Good evening.

I have a WMR300 along with a meteobridge that has been working well for over 6 months since new, about 3 months ago I would get an occasional freeze which I could solve with a reboot. This freezing varies in frequency.
All data logging with the main control screen continued normally. Just the meteobridge has stopped broadcasting.
This problem has worsened however to this week it has failed 3 times.
Any help would be extremely appreciated.
I have copied the system log and can post if you believe it appropriate.

Thanks in advance,
Steve

[admin]

Are you using a USB hub in-between WMR300 and Meteobridge?

[s type72]

Hi,

No never needed one, over first six month everything has worked perfectly.

Does this information help:

logger (22.11.2018 13:20:49): child process received timeout signal (14). logger (22.11.2018 13:20:50): disconnect station 0 (WMR-300): exit logger (22.11.2018 13:20:50): data logger stopped.
logger (22.11.2018 13:20:50): historical data loaded (18 records).
logger (22.11.2018 13:20:50): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 13:20:51): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 13:20:55): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 13:20:55): services paused.
logger (22.11.2018 13:22:52): give up waiting for sensors after 120 secs.
logger (22.11.2018 13:22:52): services activated.
logger (22.11.2018 13:31:21): child process received timeout signal (14).
logger (22.11.2018 13:31:21): disconnect station 0 (WMR-300): exit
logger (22.11.2018 13:31:22): data logger stopped.
logger (22.11.2018 13:31:22): historical data loaded (18 records).
logger (22.11.2018 13:31:22): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 13:31:23): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 13:31:26): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 13:31:26): services paused.
logger (22.11.2018 13:33:23): give up waiting for sensors after 120 secs.
logger (22.11.2018 13:33:23): services activated.
logger (22.11.2018 13:41:53): child process received timeout signal (14).
logger (22.11.2018 13:41:53): disconnect station 0 (WMR-300): exit
logger (22.11.2018 13:41:54): data logger stopped.
logger (22.11.2018 13:41:54): historical data loaded (18 records).
logger (22.11.2018 13:41:54): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 13:41:55): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 13:41:58): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 13:41:58): services paused.
logger (22.11.2018 13:43:55): give up waiting for sensors after 120 secs.
logger (22.11.2018 13:43:55): services activated.
logger (22.11.2018 13:52:25): child process received timeout signal (14).
logger (22.11.2018 13:52:25): disconnect station 0 (WMR-300): exit
logger (22.11.2018 13:52:25): data logger stopped.
logger (22.11.2018 13:52:26): historical data loaded (18 records).
logger (22.11.2018 13:52:26): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 13:52:26): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 13:52:30): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 13:52:30): services paused.
logger (22.11.2018 13:54:27): give up waiting for sensors after 120 secs.
logger (22.11.2018 13:54:27): services activated.
logger (22.11.2018 14:02:56): child process received timeout signal (14).
logger (22.11.2018 14:02:56): disconnect station 0 (WMR-300): exit
logger (22.11.2018 14:02:57): data logger stopped.
logger (22.11.2018 14:02:57): historical data loaded (18 records).
logger (22.11.2018 14:02:57): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 14:02:58): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 14:03:01): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 14:03:01): services paused.
logger (22.11.2018 14:04:58): give up waiting for sensors after 120 secs.
logger (22.11.2018 14:04:58): services activated.
logger (22.11.2018 14:13:28): child process received timeout signal (14).
logger (22.11.2018 14:13:28): disconnect station 0 (WMR-300): exit
logger (22.11.2018 14:13:29): data logger stopped.
logger (22.11.2018 14:13:29): historical data loaded (18 records).
logger (22.11.2018 14:13:29): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 14:13:30): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 14:13:33): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 14:13:33): services paused.
logger (22.11.2018 14:15:30): give up waiting for sensors after 120 secs.
logger (22.11.2018 14:15:30): services activated.
logger (22.11.2018 14:24:00): child process received timeout signal (14). logger (22.11.2018 14:24:00): disconnect station 0 (WMR-300): exit logger (22.11.2018 14:24:00): data logger stopped.
logger (22.11.2018 14:24:00): historical data loaded (18 records).
logger (22.11.2018 14:24:00): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 14:24:01): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 14:24:04): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 14:24:04): services paused.
logger (22.11.2018 14:26:01): give up waiting for sensors after 120 secs.
logger (22.11.2018 14:26:01): services activated.
logger (22.11.2018 14:34:31): child process received timeout signal (14).
logger (22.11.2018 14:34:31): disconnect station 0 (WMR-300): exit
logger (22.11.2018 14:34:32): data logger stopped.
logger (22.11.2018 14:34:32): historical data loaded (18 records).
logger (22.11.2018 14:34:32): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 14:34:33): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 14:34:36): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 14:34:36): services paused.
logger (22.11.2018 14:36:33): give up waiting for sensors after 120 secs.
logger (22.11.2018 14:36:33): services activated.
logger (22.11.2018 14:45:03): child process received timeout signal (14).
logger (22.11.2018 14:45:03): disconnect station 0 (WMR-300): exit
logger (22.11.2018 14:45:04): data logger stopped.
logger (22.11.2018 14:45:04): historical data loaded (18 records).
logger (22.11.2018 14:45:04): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 14:45:04): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 14:45:08): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 14:45:08): services paused.
logger (22.11.2018 14:47:05): give up waiting for sensors after 120 secs.
logger (22.11.2018 14:47:05): services activated.
logger (22.11.2018 14:55:34): child process received timeout signal (14).
logger (22.11.2018 14:55:35): disconnect station 0 (WMR-300): exit
logger (22.11.2018 14:55:35): data logger stopped.
logger (22.11.2018 14:55:35): historical data loaded (18 records).
logger (22.11.2018 14:55:35): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 14:55:36): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 14:55:39): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 14:55:39): services paused.
logger (22.11.2018 14:57:36): give up waiting for sensors after 120 secs.
logger (22.11.2018 14:57:36): services activated.
logger (22.11.2018 15:06:06): child process received timeout signal (14).
logger (22.11.2018 15:06:06): disconnect station 0 (WMR-300): exit
logger (22.11.2018 15:06:07): data logger stopped.
logger (22.11.2018 15:06:07): historical data loaded (18 records).
logger (22.11.2018 15:06:07): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 15:06:08): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 15:06:11): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 15:06:11): services paused.
logger (22.11.2018 15:08:08): give up waiting for sensors after 120 secs.
logger (22.11.2018 15:08:08): services activated.
logger (22.11.2018 15:16:38): child process received timeout signal (14).
logger (22.11.2018 15:16:38): disconnect station 0 (WMR-300): exit
logger (22.11.2018 15:16:38): data logger stopped.
logger (22.11.2018 15:16:38): historical data loaded (18 records).
logger (22.11.2018 15:16:38): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 15:16:39): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 15:16:42): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 15:16:42): services paused.
logger (22.11.2018 15:18:39): give up waiting for sensors after 120 secs.
logger (22.11.2018 15:18:39): services activated.

logger (22.11.2018 15:27:09): child process received timeout signal (14). logger (22.11.2018 15:27:09): disconnect station 0 (WMR-300): exit logger (22.11.2018 15:27:10): data logger stopped.
logger (22.11.2018 15:27:10): historical data loaded (18 records).
logger (22.11.2018 15:27:10): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 15:27:11): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 15:27:14): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 15:27:14): services paused.
logger (22.11.2018 15:29:11): give up waiting for sensors after 120 secs.
logger (22.11.2018 15:29:11): services activated.
logger (22.11.2018 15:37:41): child process received timeout signal (14).
logger (22.11.2018 15:37:41): disconnect station 0 (WMR-300): exit
logger (22.11.2018 15:37:42): data logger stopped.
logger (22.11.2018 15:37:42): historical data loaded (18 records).
logger (22.11.2018 15:37:42): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 15:37:42): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 15:37:46): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 15:37:46): services paused.
logger (22.11.2018 15:39:43): give up waiting for sensors after 120 secs.
logger (22.11.2018 15:39:43): services activated.
logger (22.11.2018 15:48:12): child process received timeout signal (14).
logger (22.11.2018 15:48:13): disconnect station 0 (WMR-300): exit
logger (22.11.2018 15:48:13): data logger stopped.
logger (22.11.2018 15:48:13): historical data loaded (18 records).
logger (22.11.2018 15:48:13): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 15:48:14): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 15:48:17): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 15:48:17): services paused.
logger (22.11.2018 15:50:14): give up waiting for sensors after 120 secs.
logger (22.11.2018 15:50:14): services activated.
logger (22.11.2018 15:58:44): child process received timeout signal (14).
logger (22.11.2018 15:58:44): disconnect station 0 (WMR-300): exit
logger (22.11.2018 15:58:45): data logger stopped.
logger (22.11.2018 15:58:45): historical data loaded (18 records).
logger (22.11.2018 15:58:45): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 15:58:46): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 15:58:49): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 15:58:49): services paused.
logger (22.11.2018 16:00:46): give up waiting for sensors after 120 secs.
logger (22.11.2018 16:00:46): services activated.
logger (22.11.2018 16:09:16): child process received timeout signal (14).
logger (22.11.2018 16:09:16): disconnect station 0 (WMR-300): exit
logger (22.11.2018 16:09:16): data logger stopped.
logger (22.11.2018 16:09:16): historical data loaded (18 records).
logger (22.11.2018 16:09:16): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 16:09:17): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 16:09:20): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 16:09:20): services paused.
logger (22.11.2018 16:11:17): give up waiting for sensors after 120 secs.
logger (22.11.2018 16:11:17): services activated.
logger (22.11.2018 16:19:47): child process received timeout signal (14).
logger (22.11.2018 16:19:47): disconnect station 0 (WMR-300): exit
logger (22.11.2018 16:19:48): data logger stopped.
logger (22.11.2018 16:19:48): historical data loaded (18 records).
logger (22.11.2018 16:19:48): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 16:19:49): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 16:19:52): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 16:19:52): services paused.
logger (22.11.2018 16:21:49): give up waiting for sensors after 120 secs.
logger (22.11.2018 16:21:49): services activated.

logger (22.11.2018 16:30:19): child process received timeout signal (14). logger (22.11.2018 16:30:19): disconnect station 0 (WMR-300): exit logger (22.11.2018 16:30:19): data logger stopped.
logger (22.11.2018 16:30:19): historical data loaded (18 records).
logger (22.11.2018 16:30:19): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 16:30:20): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 16:30:24): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 16:30:24): services paused.
logger (22.11.2018 16:32:21): give up waiting for sensors after 120 secs.
logger (22.11.2018 16:32:21): services activated.
logger (22.11.2018 16:40:50): child process received timeout signal (14).
logger (22.11.2018 16:40:50): disconnect station 0 (WMR-300): exit
logger (22.11.2018 16:40:51): data logger stopped.
logger (22.11.2018 16:40:51): historical data loaded (18 records).
logger (22.11.2018 16:40:51): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 16:40:52): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 16:40:55): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 16:40:55): services paused.
logger (22.11.2018 16:42:52): give up waiting for sensors after 120 secs.
logger (22.11.2018 16:42:52): services activated.
logger (22.11.2018 16:51:22): child process received timeout signal (14).
logger (22.11.2018 16:51:22): disconnect station 0 (WMR-300): exit
logger (22.11.2018 16:51:23): data logger stopped.
logger (22.11.2018 16:51:23): historical data loaded (18 records).
logger (22.11.2018 16:51:23): data logger (version 5.1a, build 12487) started.
logger (22.11.2018 16:51:23): connect station 0 (WMR-300 via USB HID).
logger (22.11.2018 16:51:27): waiting for sensors (wind0, rain0, th0, thb0) to provide data. logger (22.11.2018 16:51:27): services paused.
logger (22.11.2018 16:53:24): give up waiting for sensors after 120 secs.
logger (22.11.2018 16:53:24): services activated.

Thanks again
Steve

[admin]

Unless you have a MB PRO or MR3020v3 you need one. Doesn't it display you a warning messages on the admin interface that you need that?

[s type72]

Hi,

I have looked at the unit, it is a TL--MR3020(UN) VER 1.9 supplied by meteobridge shop.

I used their instruction with further advice from weather34.com.

No errors, no problems for 6 months

TL-MR3020 (no USB hub)
RAM: 29364 kB total, 3520 kB free (88% used)
SW Version: Meteobridge 3.8 (Nov 26 2018, build 12523), FW 1.5
Uptime: 2 days, 1 hours, 45 minutes Buffer: 1 items (0%)

current info

Steve

[s type72]

Current message list:

wnetd (01.12.2018 06:59:53): process started.
system (01.12.2018 06:59:53): start of logging process initiated.
logger (01.12.2018 06:59:53): historical data loaded (19 records).
logger (01.12.2018 06:59:53): data logger (version 5.1a, build 12523) started.
logger (01.12.2018 06:59:54): connect station 0 (WMR-300 via USB HID).
logger (01.12.2018 06:59:54): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (01.12.2018 06:59:54): services paused.
logger (01.12.2018 06:59:56): sensors are now providing data.
logger (01.12.2018 06:59:56): services started.

This may run perfectly now for months/weeks or a few days!

very frustrating when I get the offline message, then a simple reboot sorts everything.

[weatherist34]

hi
i no longer use a wmr300(took a direct hit by lightning) but i used to get those errors listed occasionally *note it was never a frequent occurrence* when the ISS would lose communication with console momentarily. i never used a USB hub in between console and mr3030 but i would say if Boris is stating use one then thats the path to take .. i have with two local,students i help,they both use wmr300 without usb hub and i recall in the past they would get similar errors i could only fathem out it was console to ISS loss of packet momentarily , poor wireless signal between console and iss perhaps getting knocked out by localized noise or localized wireless signal,from another product using similar frequency.. bottom line i could never determine the cause and it was never frequent enough to truly confirm wether usb hub was needed or not or i could pinpoint it to directly being console to iss problem. so safe bet stick a usb hub in between to eleminate that or has a nearby product which uses a similar wireless frequency been installed recently . one occasion i do recall when we had 12 guests over for dinner all armed with there smart phones and tablets , remote car key,alarm gadgets my console stopped communicating with the ISS . sorry a bit long winded but hopefully throws up,some possibilities for you..brian

[admin]

I have looked at the unit, it is a TL--MR3020(UN) VER 1.9 supplied by meteobridge shop.

This unit needs a USB hub for stable operation. Reason is in the Atheros USB drivers that have a hick-up here and there on USB 1.x protocols. The USB hub pimps communication to USB 2.x and by that everything is fine. When you are a Linux expert you are invited to read about it in the openwrt forum, to fully understand this.

The Meteobridge does tell you in red letters to use a USB hub. What else can it do to prevent you from doing wrong? Ok, when you think to know better, it is out of options as it can hardly apply force

[s type72]

Hub now connected for the first time, fingers crossed.

Thanks for your advice.

Steve