Can Claim Usb Device Could Not Detach Kernel DriverCan Claim Usb Device Could Not Detach Kernel Driver

What to do when your Fine Offset station locks up The Fine Offset stations are known to periodically stop communicating via USB. The weather station console continues to communicate with the sensors, and weather data are displayed properly on the weather station console. However, any communication over USB stops. Installer Tome 3.mpqe Error 108. Since the lockup happens in the station firmware, no weather station software is immune. It happens with weewx, Cumulus, pywws, wview, EasyWeather, etc. Jim Easterbrook (author of pywws) surmises that the lockup happens when a computer attempts to communicate with the station while the station is reading data from the sensors (every 48 or 60 seconds) or writing to console memory (every archive interval). It is possible that the lockup is due to hardware configuration.

Libusb_detach_kernel_driver (libusb_device. Engenius Wireless Lan Usb2.0 Adapter Driver. A device represents a USB device that is currently. If a kernel driver is active, you cannot claim the.

Some people experience the lockup with certain computers but not others, some report fewer lockups after switching to a powered hub or to a different USB cable. It would appear to be a problem with stations manufactured after 2010 or so; older stations seem to be immune. It might coincide with a change in radio communication protocols between console and sensors.

The USB lockups were first noted in 2011. What does it look like? When the lockup happens, you will see a gap in weather data. In the weewx log you will see messages such as this: Jun 7 21:50:33 localhost weewx[2460]: fousb: get archive interval failed attempt 1 of 3: could not detach kernel driver from interface 0: No data available The 'could not detach kernel driver from interface. No data available' is the sign of a lockup. How to fix it The only way to get things working again is to power cycle the station.

That means remove the batteries, disconnect the USB connection, then reinstall the batteries and reconnect the USB. There is no need to restart weewx. Since the station receives power from USB, removing the batteries without disconnecting USB will not power cycle the station. Workarounds for unattended operation Obviously, this firmware bug makes the FineOffset stations unsuitable for unattended operation. However, there are some workarounds: Use correct settings The best settings for a Fine Offset station using weewx 2.6.x and earlier are: [FineOffsetUSB] polling_mode = PERIODIC polling_interval = 60 [StdArchive] archive_interval = 300 record_generation = software Also, set the station's archive interval to 5 minutes (300 seconds): sudo wee_device --set-interval=5 These settings are not a guarantee against lockups, but they will reduce the chance. With weewx 2.6.x and earlier, using polling_mode = ADAPTIVE or record_generation = hardware will increase the chance of a lockup. Use a switched hub Connect the station, without batteries, to a USB hub that has per-port switching.

When a lockup is detected, power cycle the station by turning the power off/on in the USB hub. Bowa Arc 350 User Manual. This feature is included in the fousb.py driver in weewx as of r2225 or weewx 2.6.4.

When weewx detects a lockup, it tells the USB hub to power cycle the station. To enable this feature, add the following to weewx.conf: [FineOffsetUSB] power_cycle_hub = 001:016 power_cycle_port = 1 power_cycle_port indicates the port to which the station is attached.

On a four-port hub this will be 1, 2, 3, or 4. Note that the port number may not be the same as the socket number. This is a known problem with the DUB-H7. You'll have to experiment to find the right port number. Power_cycle_hub uniquely identifies the hub to which the station is attached. It has the format XXX:YYY where XXX is the bus and YYY is the device, for example 001:016.

Coments are closed
Scroll to top