On Dec 4, 2014, at 7:01 AM, j...@telefonica.net wrote: > 0.339848 Report[get]: (2 bytes) => 01 00 > 0.339928 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, > Size: 8, Value: 0 > 0.343852 Report[get]: (2 bytes) => 02 00 > 0.343931 Path: 008c0001.008c0002, Type: Input, ReportID: 0x02, Offset: 0, > Size: 1, Value: 0 > 0.343975 Report[buf]: (2 bytes) => 02 00 > 0.344002 Path: 008c0001.008c0002, Type: Feature, ReportID: 0x02, Offset: 0, > Size: 1, Value: 0 > 0.347849 Report[get]: (2 bytes) => 03 0c > 0.347947 Path: 008c0001.008c0004, Type: Input, ReportID: 0x03, Offset: 0, > Size: 8, Value: 12 > 0.347987 Report[buf]: (2 bytes) => 03 0c > 0.348014 Path: 008c0001.008c0004, Type: Feature, ReportID: 0x03, Offset: 0, > Size: 8, Value: 12 > 0.351848 Report[get]: (2 bytes) => 04 00 > 0.351943 Path: 008c0001.008c0005, Type: Feature, ReportID: 0x04, Offset: 0, > Size: 8, Value: 0
Hmm, I misread that. I assumed it was just a pair of 8-byte buffers (the way most of the HID USB-to-serial converters are laid out), but "Size: 8" is in bits. The interesting part is that "008c..." is the HID Usage Page for bar code scanners. You can try running usbhid-ups in "explore" mode, as explained here: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s04.html#hid-subdrivers The driver keeps looping and reading the values, and you can see whether they correspond to various power states (on battery vs on AC, low battery, etc.) -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser