search for: hidgetdatavalue

...not contain input or output items. To read an input or an output item, the appropriate report type must be requested even if it has the same report ID as a different report type. So, going back to the subject of this patch: since HIDDumpTree() iterates over all items, requesting their values via HIDGetDataValue(), and since HIDGetDataValue() is only capable of retrieving Feature reports, it makes absolutely no sense to pass a non-feature report to HIDGetDataValue(). Hence, we should skip non-feature reports in this loop _unless_ HIDGetDataValue() is changed to be capable of retriving non-feature reports....

On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > Input and Output reports are used for interrupt endpoints rather than > control endpoints. HIDGetItemData() only ever requests feature > report IDs, and requesting non-feature report IDs as feature IDs may > lead to undesirable results and errors. This one made me scratch my head a bit. I don't think it's unreasonable

...nut]# /usr/local/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.3.0-1352 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352) Warning: This is an experimental driver. Some features may not function correctly. Using subdriver: TrippLite HID 0.2 (experimental) HIDGetDataValue: Value too large for defined data type This began with r1072... I wanted to include a debug output but it does not seems to end: [root at teevee ~]# /usr/local/bin/usbhid-ups -D -a smart1000lcd Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352) Warning: This is an experim...

Hi, There is many (20 per day on average) messages like: kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110 usbhid-ups[6768]: HIDGetDataValue: Connection timed out What can be done do correct that problem? best regards, Franck my configuration: debian etch nut 2.2.1 (recompiled source from testing to use latest version before posting here) updated from newhidups to usbhid-ups libusb-0.1-4 0.1.12-5 asus A7N8X-E (lates...

...th time and complexity. ------------------------------------------------------------------------ Symptom: when connecting to an APC Back-UPS 500, everything works fine until r1209; from r1210, I get lots of error messages such as Can't retrieve Report 22: Value too large for defined data type HIDGetDataValue: Value too large for defined data type For reference, attached are five files: r1209 and r1210: respective output of '/usr/bin/usbhid-ups -DD -a apc' u1209 and u1210: respective output of 'upsc apc' descriptor-apc.hex: the APC's report descriptor dump Further notes: it seems...

...id_ups_walk(HU_WALKMODE_INIT) == FALSE) { > + hd = NULL; > + return; > + } > } > #ifdef DEBUG > interval(); > @@ -716,7 +721,7 @@ > /* Process pending events (HID notifications on Interrupt pipe) */ > for (i = 0; i < evtCount; i++) { > > - if (HIDGetDataValue(udev, event[i], &value, 2) != 1) > + if (HIDGetDataValue(udev, event[i], &value, poll_interval) != 1) > continue; > > if (nut_debug_level >= 1) { > @@ -807,7 +812,7 @@ > > void upsdrv_initups(void) > { > - int i; > + int i, mode = MODE_OPEN;...

leave it for another day to be sure. > It would help running the driver in debug mode > > /path/to/usbhid-ups -DDD -a upsname > > The interesting parts will have 'HIDGetDataValue' in them and a few > lines before that will tell us which report it attempted to retrieve. I've done that and included the syslog output in the same file. The logfile is attached and contains about 15 minutes worth of information, which is how long it took for the first re-connect event...

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,