Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-standard USB_TIMEOUT in libusb.c is causing problems with Eaton 5PX UPS, usbhid-ups won't start #23

Closed
stevenbg opened this issue Apr 4, 2013 · 2 comments
Assignees
Labels

Comments

@stevenbg
Copy link

stevenbg commented Apr 4, 2013

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

@stevenbg stevenbg reopened this Apr 11, 2013
aquette added a commit that referenced this issue Apr 11, 2013
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)
@ghost ghost assigned aquette Apr 11, 2013
@aquette
Copy link
Member

aquette commented Apr 11, 2013

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)

Thanks and cheers

@aquette
Copy link
Member

aquette commented Apr 24, 2013

closed with commit 9758dcf.
I forgot to reference the present issue in the commit message...

@aquette aquette closed this as completed Apr 24, 2013
aquette added a commit to aquette/nut that referenced this issue Oct 13, 2017
Problems: Eaton G3 ePDU outlet.%i.name overwritten by fallback entry; device.count==1 not published
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants