search for: libusb_get_report

...02 85 90 0.046950 09 00 15 00 26 ff 00 75 08 95 3f 91 02 c0 c0 0.047210 Using subdriver: APC HID 0.95 0.049181 Report[get]: (2 bytes) => 01 02 0.049296 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 2 0.050313 libusb_get_report: error sending control message: Protocol error 0.050426 Can't retrieve Report 02: Protocol error 0.050545 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8 0.051230 libusb_get_report: error sending control message: Protocol error...

...75 08 26 ff 3.268319 00 65 00 b1 82 09 97 85 29 75 20 27 ff ff ff 7f 66 01 10 b1 82 05 84 09 30 3.268342 85 07 75 10 27 ff ff 00 00 67 21 d1 f0 00 55 07 b1 83 c0 c0 3.268674 Using subdriver: EXPLORE HID 0.1 3.268690 173 HID objects found 3.268706 Entering libusb_get_report 3.299546 Report[get]: (4 bytes) => 20 01 01 01 3.299579 Path: UPS.BatterySystem.Battery.BatteryID, Type: Feature, ReportID: 0x20, Offset: 0, Size: 8, Value: 1 3.299782 Entering libusb_get_report 3.327540 Report[get]: (2 bytes) => 21 00 3.327573 Path: U...

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

I recently installed NUT 2.4.3 and found that the USB drivers were logging an insane amount of data to syslog: usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report: No error usbhid-ups | daemon debug | Apr 16 18:29:40 | libusb_get_report...

On Dec 11, 2014, at 5:43 AM, janc at 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: I...

...23 75 08 95 01 b1 82 85 02 09 02 15 00 25 01 75 01 81 82 75 07 81 83 85 02 09 0.339161 02 75 01 b1 82 75 07 b1 83 85 03 09 04 15 00 26 ff 00 75 08 81 82 85 03 09 0.339191 04 b1 82 85 04 09 05 15 00 26 ff 00 75 08 b1 82 c0 0.339253 Using subdriver: EXPLORE HID 0.1 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, Off...

...75 75 08 95 01 b1 82 85 02 09 02 15 00 25 01 75 01 81 82 75 07 81 83 85 02 09 0.349312 02 75 01 b1 82 75 07 b1 83 85 03 09 04 15 00 26 ff 00 75 08 81 82 85 03 09 0.349344 04 b1 82 85 04 09 05 15 00 26 ff 00 75 08 b1 82 c0 0.349399 Using subdriver: EXPLORE HID 0.1 0.349427 Entering libusb_get_report 0.353126 Report[get]: (2 bytes) => 01 00 0.353225 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 0.353267 Entering libusb_get_report 0.357112 Report[get]: (2 bytes) => 02 00 0.357152 Path: 008c0001.008c0002, Type: Input, ReportID: 0x02, Off...

..., Size: 8, Value: 100.000000 ... With 2.4.3: # /sbin/usbhid-ups -D -a auto Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 0.000000 debug level is '1' 0.001172 upsdrv_initups... 0.279899 Using subdriver: Belkin HID 0.12 0.284577 libusb_get_report: No error 0.284609 Can't retrieve Report 01: Operation not permitted 0.284628 Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8 0.289575 libusb_get_report: No error 0.289590 Can't retrieve Report 02: Operation not permi...

...message constantly in log > Message-ID: <BLU175-W2C7D7E6609924EE1F4C43B5450 at phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > I'm using Nas4Free, and I'm getting the following message all the time in the Daemon log: > > usbhid-ups[42466]: libusb_get_report: Unknown Error > > I'm running Nas4Free 9.2.0.1 Shigawire > Driver usbhid-ups > Nut Version is 2.7.1 > Internal verion 0.38 > > UPS Info from Nas4Free > > Manufacturer:CP1500PFCLCD > Model:CRCA102*AF1 > > The model UPS I'm running is a Cyber Power...

...v/bus/usb/002/007 $ id nut uid=57(nut) gid=57(nut) groups=57(nut),18(dialout) However, if I try to run usbhid-ups as user "nut", I get: $ sudo -u nut ./usbhid-ups -a usb Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: TrippLite HID 0.4 libusb_get_report: could not claim interface 0: Device or resource busy Got disconnected by another driver: Device or resource busy Can't initialize data from HID UPS Whereas if I run it as root: $ sudo ./usbhid-ups -a usb -u root Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.3...

...9;d be interested in a trace without the patch, to > > see if we're still on the overflow side. > > trunk (rev.3529) "with no patch" log attached. > > Btw I've checked all logs I've sent so far - all of them contain: > > 1.199490 libusb_get_report: Unknown error > 1.199512 Can't retrieve Report 0c: Input/output error > > Seems you are talking about Dmitry's case (overflow). > > > you're right: your issues are the same, but BSD doesn't report EOVERFLOW > has it should. > while Dmitry is r...

Hello! First time posting to this list. I recently purchased a Tripp-Lite OMNIPLUS1000LCD from Costco (USA). I have it attached via USB to a Dell computer with Ubuntu 8.04 server (all updates on it). I've gone through a lot of research on google and this list and can't figure out why my UPS will not connect using nut/usbhid-ups. My setup in ups.conf is: ------- [OMNI1000LCD]

Peter, I have been doing some more testing and I find that if I modify the libusb.c file to set a report size in libusb_get_report to 16 the error messages go away. This is the code as it currently stands: static int libusb_get_report(usb_dev_handle *udev, int ReportId, unsigned char *raw_buf, int ReportSize ) { int ReportSize_test = 16; unsigned char raw_buf_test[ReportSize_test + 1]; int rc; unsigned char...

...id argument The driver should only call libusb_get_string() for informational purposes, so it should only affect ups.mfr and ups.model in upsc. > > And if I run upsd with high level of debug, after working OK for a while, I see these ?broken pipe? messages : > > 0.419974 Entering libusb_get_report > 0.421967 Report[get]: (4 bytes) => 60 c4 ff 3b > 0.422056 PhyMax = 0, PhyMin = 0, LogMax = 16777215, LogMin = 0 > 0.422069 Unit = 00001001, UnitExp = 0 > 0.422080 Exponent = 0 > 0.422093 hid_lookup_path: 00840004 -> UPS > 0.422107 hid_lookup_path: 0084002...

...I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. To that end, the .ac.txt and .bat.txt files both show 24.0 V: 0.081935 Entering libusb_get_report 0.082018 Report[get]: (2 bytes) => 09 f0 0.082029 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 0.082035 Entering libusb_get_report 0.082115 Report[get]: (2 bytes) => 0a f0 0.082124 Path: UPS.PowerSummary.Voltage, Type: Featu...

...I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V: > > 0.081935 Entering libusb_get_report > 0.082018 Report[get]: (2 bytes) => 09 f0 > 0.082029 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 > 0.082035 Entering libusb_get_report > 0.082115 Report[get]: (2 bytes) => 0a f0 > 0.082124...

...SmartOnline SU1000XLA. [sups] driver = usbhid-ups port = auto vendorid = 09ae productid = 4004 4337# upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver: TrippLite HID 0.4 libusb_get_report: could not claim interface 0: Device or resource busy Got disconnected by another driver: Device or resource busy Can't initialize data from HID UPS Driver failed to start (exit status=1) I did an 'fuser -m -v /dev/usb/hiddev0' just prior, and the file was unused by any other process,...

I just noticed what I think is another incorrectly reported value. I found that on the second screen of upsstats.cgi, the one with bar graphs, that the reported battery voltage is 16.0V even though the battery charge is at 100% and the UPS is on AC power. I would have thought it should be more than 25V.

...HID descriptor length 34 0.195165 Report Descriptor size = 34 0.195484 Report Descriptor: (34 bytes) => 06 a0 ff 09 a5 a1 01 09 a6 09 a7 15 00 25 0.196073 ff 75 08 95 08 81 02 09 a9 15 00 25 ff 75 08 95 08 91 02 c0 0.196506 Using subdriver: EXPLORE HID 0.1 0.197232 Entering libusb_get_report 0.200187 Can't retrieve Report 00: Broken pipe 0.200434 Path: ffa000a5.ffa000a6, Type: Input, ReportID: 0x00, Offset: 0, Size: 8 0.201022 Entering libusb_get_report 0.204196 Can't retrieve Report 00: Broken pipe 0.204443 Path: ffa000a5.ffa000a7, Type: Input, ReportID: 0...

...cation driver 0.31 Trying to configure the UPS from FreeNAS failed so I try to investigate which is the problem. Running "usr/local/libexec/nut/usbhid-ups -a SAI" I get this: Network UPS Tools - Generic HID driver 0.37 (2.6.5) USB communication driver 0.31 Using subdriver: APC HID 0.95 libusb_get_report: Unknown error Can't initialize data from HID UPS With -DD to get more information I found the problem: 0.723737 Path: UPS.Battery.ff860018, Type: Feature, ReportID: 0x48, Offset: 0, Size: 32, Value: 0 0.726114 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, Offset: 0, Size: 32,...