You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reported a problem with the USB driver and an Eaton 5PX UPS. usbhid-ups failed to start, because it timeouts while receiving the descriptor. The USB_TIMEOUT constant in libusb.c is set to 4 seconds, instead of the standard 5 seconds.
Set the low level USB timeout back to the standard
5 seconds. This was set to 4 seconds, for performance
reasons, but is now causing issues with some devices
(reported by Stefan "stevenbg", GitHub issue #23)
I confirm this issue.
You did well find and point the faulty param.
and as commented, this was not the default value for perf reasons (sigh!)
On 5PX, this is related to a small increase in the report descriptor
(describes the data struct)
which, by side effect caused the main issue you found (timeout on init, and
failure to init comm. with the device).
I have fixed it in the latest master, which will be available in the next
release (probably a soon to come 2.6.6...)
Note that I've also opened a tracker for adding a new "communication
timeout" option (GitHub issue #24)
Hello,
I reported a problem with the USB driver and an Eaton 5PX UPS. usbhid-ups failed to start, because it timeouts while receiving the descriptor. The USB_TIMEOUT constant in libusb.c is set to 4 seconds, instead of the standard 5 seconds.
Here is the original thread: http://www.mail-archive.com/nut-upsuser@lists.alioth.debian.org/msg07676.html
Here is the constant I'm talking about: https://github.com/networkupstools/nut/blob/master/drivers/libusb.c#L38
The text was updated successfully, but these errors were encountered: