[Nut-upsdev] Developing the UPS side of the UPS-NUT equation (via usbhid)

Rob Groner rgroner at RTD.com
Thu Mar 13 13:44:13 UTC 2014

Hmm...well, after it gets the report descriptor, NUT then gets each of the reports defined in there, so that's good.  But after that, there are no more messages (no more reports being requested...the NUT debug info just shows "libusb_get_interrupt: Connection timed out" repeatedly).  I put in some enticing values into the report descriptor, like shutdownimminent and discharging and charging, hoping that would get NUT interested enough to ask for those status, but not so far.  I'm missing something obvious.  I'm going to dig into NUT to see if I can find where it decides what reports to get during the "Quick update".

-----Original Message-----
From: Nut-upsdev [mailto:nut-upsdev-bounces+rgroner=rtd.com at lists.alioth.debian.org] On Behalf Of Charles Lepple
Sent: Wednesday, March 12, 2014 8:24 PM
To: nut-upsdev at lists.alioth.debian.org Developers
Subject: Re: [Nut-upsdev] Developing the UPS side of the UPS-NUT equation (via usbhid)

On Mar 12, 2014, at 5:18 PM, Rob Groner wrote:

> Is there some minimum amount of functionality I need to provide in this report descriptor in order for NUT to work correctly?  I assume it's not requesting reports because there is nothing it wants to know about.

That sounds vaguely familiar, but I think NUT will still poll the interrupt pipe if present. The requests over EP0 are probably only made if there are HID usage paths mapped to NUT variable names.

Charles Lepple
clepple at gmail

Nut-upsdev mailing list
Nut-upsdev at lists.alioth.debian.org

More information about the Nut-upsdev mailing list