v3.6.0 - WMR 300 - WeeWxIOError: [Errno 110]

270 views
Skip to first unread message

Miguel Iniesta

unread,
Oct 8, 2016, 3:16:04 PM10/8/16
to weewx-user
Hello,

Running v3.6.0 on ubuntu 16.04. Connected to a WMR300 station produces error WeeWxIOError: [Errno 110]
Please, find log attached.

Any help please.
Thank you,
Miguel
201610082057-syslog

mwall

unread,
Oct 8, 2016, 3:49:44 PM10/8/16
to weewx-user
On Saturday, October 8, 2016 at 3:16:04 PM UTC-4, Miguel Iniesta wrote:
Running v3.6.0 on ubuntu 16.04. Connected to a WMR300 station produces error WeeWxIOError: [Errno 110]
Please, find log attached.

miguel,

could you try again, but with debug=1 in the weewx configuration file?

that will not fix the problem, but it will provide more clue as to why weewx cannot communicate with the wmr300

m

Miguel Iniesta

unread,
Oct 8, 2016, 5:23:07 PM10/8/16
to weewx-user
The log attached has been obtained with debug = 1.

Thanks,

mwall

unread,
Oct 8, 2016, 6:02:58 PM10/8/16
to weewx-user
On Saturday, October 8, 2016 at 5:23:07 PM UTC-4, Miguel Iniesta wrote:
The log attached has been obtained with debug = 1.


ok, lets go back a step.  which versions do you have for pyusb and libusb?

dpkg -l | grep libusb
dpkg -l | grep python-usb

then try this:

cd /home/weewx
sudo PYTHONPATH=bin python bin/weewx/drivers/wmr300.py

and post the log.

this will load the driver and attempt to capture loop packets, with debug_comm and debug_counts enabled.  it should help us figure out where the timeout exception is coming from.

i suspect that the problem is the encapsulation/naming of a usb error.  it also appears that ubuntu 16.x is missing bus.dirname and dev.filename like recent centos.

m

Miguel Iniesta

unread,
Oct 9, 2016, 5:25:54 AM10/9/16
to weewx-user
Please, find attached versions and log as required.

Thank you.
201610091123-log.txt

Miguel Iniesta

unread,
Oct 9, 2016, 6:03:30 AM10/9/16
to weewx-user
Python-usb was not installed because Weewx has been installed using the tool setup py
Afer install it, the version is:

ii  python-usb                                 1.0.0~b2-2

mwall

unread,
Oct 9, 2016, 9:55:13 AM10/9/16
to weewx-user
On Sunday, October 9, 2016 at 6:03:30 AM UTC-4, Miguel Iniesta wrote:
Python-usb was not installed because Weewx has been installed using the tool setup py
Afer install it, the version is:

ii  python-usb                                 1.0.0~b2-2


thank you miguel.

please install the attached 0.13rc1

mv bin/weewx/drivers/wmr300.py bin/weewx/drivers/wmr300-0.12.py
cp ~/Downloads/wmr300-0.13rc1.py bin/weewx/drivers/wmr300.py

then start weewx and post the log.

v0.13 adds retries to the usb read/write methods, and it is more selective about usb error propagation.

m
wmr300-0.13rc1.py

Miguel Iniesta

unread,
Oct 9, 2016, 11:34:06 AM10/9/16
to weewx-user
Please, fin log attached.
Thank you.
201610091721-syslog-env

mwall

unread,
Oct 9, 2016, 5:37:06 PM10/9/16
to weewx-user
miguel,

did you have the wmr300 station working with a previous version of weewx, or on different hardware?  or is this your first time to use the wmr300 with weewx?

please change line 986 in wmr300.py v0.13rc1 from this:

        self.timeout = 100

to this:

        self.timeout = 3000

then try running weewx again.

m

Miguel Iniesta

unread,
Oct 10, 2016, 2:00:05 PM10/10/16
to weewx-user
Hello,
Same error.
I have been running v3.5.0 on a raspberry connected to the wmr300 for over a month. After some crashes and a failed upgrade, the raspberry it is not working fine. At every restart it returns to a point in time some months earlier. Changes after that date are lost. Very strange.
So I decided to install v3.6.0 on a laptop running Ubuntu 16.04. The errors reported come from this hardware.
Since it doesn't work, I am going to try to fix the Raspberry reinstalling the OS and test v3.6.0 on it.
I will let you know.

Thank you very much for your support.

Miguel Iniesta

unread,
Oct 11, 2016, 7:42:26 AM10/11/16
to weewx-user
Hello m,

Good news. v3.6.0 is working fine on the Raspberry after reinstalling Raspbian.
It's been running for over 12 hours without any error so far.
Therefore, it can be infer that Errno110 was hw related (laptop usb ports) or an Ubuntu 16.04 issue on this laptop.
I have tested the usb ports on a pendrive and a smartphone and they seem to work ok. I will test some more devices to try to sort it out.

Thank you,
Reply all
Reply to author
Forward
0 new messages