pyusb and/or driver issues

42 views
Skip to first unread message

Yotta

unread,
Jun 28, 2016, 3:06:17 PM6/28/16
to wfrog-users
Ironing out the last few errors with my new wfrog server;
OS - Kubuntu 16.04 LTS
Station - Oregon Scientific WMR88A
Driver - WMRS200

My weather station seems to work intermittently, with all sensors working for ~2-3hrs, then sensors dropping out one after the other except barometric pressure. Looking at 'wflogger.log' showed a repeated error with the initial configuration (ignore the timestamp I updated pyusb again to reproduce the error): 

> 2016-06-28 13:26:01,850 WARNING [station.wmrs200] Record: FF 30 60 01 10 1A 0D 1C 06 10 02 FC 00  - bad checksum
> 2016-06-28 13:26:16,855 ERROR [station.wmrs200] Exception reading interrupt: [Errno 110] Operation timed out
> Traceback (most recent call last):
>   File "/usr/lib/wfrog/wfdriver/station/wmrs200.py", line 168, in _run
>    raise e
> USBError: [Errno 110] Operation timed out

This was previously discussed with a suggestion to roll back pyusb here: https://groups.google.com/forum/#!searchin/wfrog-users/errno$20110/wfrog-users/BYvUbk_mOZo/itMXBwwAAwAJ I was using 'pyusb-1.0.0b' so rolled back to 'pyusb-0.4.3' which is working fine on my other weather server. This included installing libusb-dev as usb.h was required to build pyusb-0.4.3.Unfortunately it has completely shut down the USB now with a similar error to before but no sensors working:

> 2016-06-28 10:21:01,205 WARNING [station.wmrs200] Record: FF 30 60 01 10 15 0A 1C 06 10 02 F4 00  - bad checksum
> 2016-06-28 10:21:16,210 ERROR [station.wmrs200] Exception reading interrupt: error sending control message: Broken pipe
> Traceback (most recent call last):
>   File "/usr/lib/wfrog/wfdriver/station/wmrs200.py", line 168, in _run
>     raise e
> USBError: error sending control message: Broken pipe

Looking into what a broken pipe meant turned up that its often due to an errornous usb command, so figure the issue may not be with pyusb.

I think it's getting historical data but failing when it tries to grab the live data for everything besides the barometer. I expect its an issue with using a driver that was not specifically built for this station.

Does this seem reasonable? Is it difficult to create your own drivers?
Reply all
Reply to author
Forward
0 new messages