search for: ffff0015

...: 0x52, Offset: 0, Size: 8, Value: 0 0.073273 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1 0.073997 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8208 0.074644 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.075266 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.075310 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.075908 refresh_report_buffer: expected...

...: Feature, Value: 65535.000000 Path: UPS.OutletSystem.Outlet.ffff0091, Type: Feature, Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff0092, Type: Feature, Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, Value: 1.000000 Path: UPS.ffff0010[1].ffff007d, Type: Feature Path: UPS.ffff0015[1].ffff00c0, Type: Feature Path: UPS.ffff0015[1].ffff00d2, Type: Feature Path: UPS.ffff0015[1].ffff00c1, Type: Feature Path: UPS.ffff0015[1].ffff00c2, Type: Feature Path: UPS.ffff0015[1].ffff00c3, Type: Feature Path: UPS.ffff0015[1].ffff00c5, Type: Feature Path: UPS.ffff0015[1].ffff00c4, Type: Feat...

...et: 0, Size: 8, Value: 0 1.046862 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1 1.063599 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 4103 1.080216 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 1.097025 refresh_report_buffer: expected 5 bytes, but got 2 instead 1.097394 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 1.113716 Path: UPS.ffff0015.[...

..., Offset: 0, Size: 8, Value: 1 0.186429 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8210 0.188432 Path: UPS.TLCustom.[1].ffff00df, Type: Feature, ReportID: 0x9f, Offset: 0, Size: 32, Value: 3 0.190439 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.192393 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.192571 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.194518 refresh_report_buffe...

...TLWatchdog, Type: Feature, ReportID: 0x52, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.ffff0010.[1].ffff007d, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8197.000000 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255.000000 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255.000000 Path: UPS.ffff0015.[1].ffff00c1, Type: Feature, ReportID: 0x97, Offset: 0, Size: 16, Value: 255.000000 Path: UPS....

...: 0x52, Offset: 0, Size: 8, Value: 0 0.069779 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1 0.070327 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8208 0.070953 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.071418 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.071462 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.072034 refresh_report_buffer: expected...

...fff0092, Type: Feature, ReportID: 0x52, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0x9d, Offset: 0, Size: 8, Value: 1.000000 Path: UPS.ffff0010.[1].ffff007d, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 4099.000000 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255.000000 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255.000000 Path: UPS.ffff0015.[1].ffff00c1, Type: Feature, ReportID: 0x97, Offset: 0, Size: 16, Value: 255.000000 Path: U...

...et: 0, Size: 8, Value: 0 1.104124 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1 1.121003 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 4103 1.137767 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 1.154468 refresh_report_buffer: expected 5 bytes, but got 2 instead 1.154581 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 1.171262 Path: UPS.ffff0015.[...

...gt; b6 01 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1.000000 Report[r]: (3 bytes) => 6c 05 20 Path: UPS.ffff0010.[1].ffff007d, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8197.000000 Report[r]: (2 bytes) => 96 ff Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255.000000 Report[r]: (2 bytes) => b4 ff Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255.000000 Report[r]: (3 bytes) => 97 ff ff Path: UPS.ffff0015.[1].ffff00c1, Type: Featu...

On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > Hi Charles. I patched, reconfigured, remake'd, remake install'd - but > no change. however, some more likely helpful information below for > you. Thank you Odd. Are you sure that the new version of usbhid-ups got installed to the same path you are running? Also, there is no protection against

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

...Offset: 0, Size: 8, Value: 1 0.154100 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8210 0.154618 Path: UPS.TLCustom.[1].ffff00df, Type: Feature, ReportID: 0x9f, Offset: 0, Size: 32, Value: 3 0.155062 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.155518 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.155541 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.156015 refresh_report_buf...

..., Offset: 0, Size: 8, Value: 1 0.168989 Path: UPS.TLCustom.[1].CommunicationProtocolVersion, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8210 0.170988 Path: UPS.TLCustom.[1].ffff00df, Type: Feature, ReportID: 0x9f, Offset: 0, Size: 32, Value: 3 0.172986 Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255 0.174949 refresh_report_buffer: expected 5 bytes, but got 2 instead 0.175115 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255 0.176949 refresh_report_buffe...

...n, it pops up with > libusb_get_string_invalid argument over and over again, mixed in the > debug output. seems to be several issues reported in the log, but they > arent easily interpreted. Does the libusb_get_string error occur only every 30 seconds or so? > 1.164089 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, > ReportID: 0x9b, Offset: 0, Size: 16, Value: 3 > 1.172696 libusb_get_report: Value too large for defined data type > 1.172928 Can't retrieve Report c2: Value too large for defined data type The entries with hex numbers in the path aren't i...

...o tell the UPS to shut down immediately - it's the command that upsdrvctl runs, but with more debugging.) For future reference, was this UPS manufactured recently? The NUT source code mentions that the TLCustom prefix is 0xffff0010, but the HID descriptor dump shows a few items under "UPS.ffff0015". Hopefully the delays haven't been moved to those values, since we don't have good information on the corresponding names. Also, it may be worthwhile to reach out to Tripp Lite support. A few years ago, the NUT project got a large spreadsheet of testing results (mostly upsc output, r...

...b6 01 Path: UPS.OutletSystem.Outlet.ffff00c7, Type: Feature, ReportID: 0xb6, Offset: 0, Size: 8, Value: 1.000000 Report[get]: (3 bytes) => 6c 05 20 Path: UPS.ffff0010.[1].ffff007d, Type: Feature, ReportID: 0x6c, Offset: 0, Size: 16, Value: 8197.000000 Report[get]: (2 bytes) => 96 ff Path: UPS.ffff0015.[1].ffff00c0, Type: Feature, ReportID: 0x96, Offset: 0, Size: 8, Value: 255.000000 Report[get]: (5 bytes) => b4 ff 00 00 00 Path: UPS.ffff0015.[1].ffff00d2, Type: Feature, ReportID: 0xb4, Offset: 0, Size: 32, Value: 255.000000 Report[get]: (3 bytes) => 97 ff ff

...mixed in the >> debug output. seems to be several issues reported in the log, but they >> arent easily interpreted. > > Does the libusb_get_string error occur only every 30 seconds or so? Yes - thats correct. perhaps more like every 15 sec. > >> 1.164089 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, >> ReportID: 0x9b, Offset: 0, Size: 16, Value: 3 >> 1.172696 libusb_get_report: Value too large for defined data type >> 1.172928 Can't retrieve Report c2: Value too large for defined data type > > The entries with hex numbers in...

...the libusb_get_string error occur only every 30 seconds or so? > > > Yes - thats correct. perhaps more like every 15 sec. I was incorrect. they occur every 6 seconds. and there are two of them each time. hopefully that narrows it down! > >> >>> 1.164089 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, >>> ReportID: 0x9b, Offset: 0, Size: 16, Value: 3 >>> 1.172696 libusb_get_report: Value too large for defined data type >>> 1.172928 Can't retrieve Report c2: Value too large for defined data >>> type >> >>...

...2 Path: UPS.PowerConverter.Input.[3].PresentStatus.Used, Type: Feature, ReportID: 0x3b, Offset: 0, Size: 8, Value: 0 9.391537 Path: UPS.PowerConverter.Input.[3].PresentStatus.Used, Type: Input, ReportID: 0x3b, Offset: 0, Size: 8, Value: 0 9.425303 Path: UPS.PowerConverter.ffff0014.ffff0015, Type: Feature, ReportID: 0x40, Offset: 0, Size: 8, Value: 1 9.451294 Path: UPS.PowerConverter.ffff0014.PresentStatus.Used, Type: Feature, ReportID: 0x41, Offset: 0, Size: 8, Value: 0 9.451517 Path: UPS.PowerConverter.ffff0014.PresentStatus.Used, Type: Input, ReportID: 0x41, Offset: 0...

...8, Value: 1 5.131046 Report[get]: (2 bytes) => 3a 01 5.131202 Path: UPS.PowerConverter.Input.[3].ffff0047, Type: Feature, ReportID: 0x3a, Offset: 0, Size: 8, Value: 1 5.230660 Report[get]: (5 bytes) => 40 01 04 01 01 5.231096 Path: UPS.PowerConverter.ffff0014.ffff0015, Type: Feature, ReportID: 0x40, Offset: 0, Size: 8, Value: 1 5.330530 Report[get]: (2 bytes) => 41 00 5.331054 Path: UPS.PowerConverter.ffff0014.PresentStatus.Used, Type: Feature, ReportID: 0x41, Offset: 0, Size: 8, Value: 0 5.331220 Report[buf]: (2 bytes) => 41 00...