On Dec 11, 2014, at 5:43 AM, j...@telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: > 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002, Type: Input, ReportID: 0x02, Offset: 0, > Size: 1, Value: 0 > 0.347015 Report[buf]: (2 bytes) => 02 00 > 0.347036 Path: 008c0001.008c0002, Type: Feature, ReportID: 0x02, Offset: > 0, Size: 1, Value: 0 > 0.347055 Entering libusb_get_report > 0.350988 Report[get]: (2 bytes) => 03 0c > 0.351102 Path: 008c0001.008c0004, Type: Input, ReportID: 0x03, Offset: 0, > Size: 8, Value: 12 > 0.351138 Report[buf]: (2 bytes) => 03 0c > 0.351166 Path: 008c0001.008c0004, Type: Feature, ReportID: 0x03, Offset: > 0, Size: 8, Value: 12 > 0.351196 Entering libusb_get_report > 0.354990 Report[get]: (2 bytes) => 04 00 > 0.355104 Path: 008c0001.008c0005, Type: Feature, ReportID: 0x04, Offset: > 0, Size: 8, Value: 0
Unfortunately, your device does not respond to the interrupt pipe, so in order to test whether these values change, you will need to stop (Ctrl-C is sufficient) and re-run the driver with line power turned off. > 0.355333 upsdrv_updateinfo... > 0.607995 libusb_get_interrupt: Connection timed out > 0.608075 Got 0 HID objects... ... > Keeps going the same all the time... This part is disappointing, but we have a "pollonly" workaround. You can try it now, but I don't think it works with the "explore" sub-driver, since pollonly iterates over a list of known HID Path IDs, and we haven't added that yet. Before we set that up, I think we need to verify that the values actually change based on power conditions. -- 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
