Displaying 19 results from an estimated 19 matches for "ffff00c5".
Did you mean:
ffff0015
2015 Jun 07
2
libusb_get_string: invalid argument
...0x97, Offset: 0, Size: 16, Value: 255
1.130459 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature,
ReportID: 0x98, Offset: 0, Size: 8, Value: 255
1.147339 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature,
ReportID: 0x99, Offset: 0, Size: 16, Value: 255
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
1.173268 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature,
ReportID: 0xc2,...
2015 Jun 08
0
libusb_get_string: invalid argument
...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 important - th...
2015 Jun 08
2
libusb_get_string: invalid argument
...>> 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 path aren...
2006 Nov 15
1
Tripp Lite OMNI900LCD
...0
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: Feature
Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 104.000000
Path: UPS.BatterySystem.Battery.Voltage, Type: Feature, Value: 130.000000
Path: UPS.PowerConverter.Input.Voltage, Type: Feature, Value: 112.800003
Path: UPS.PowerConverter.I...
2006 Aug 07
0
Re: your Tripp-Lite AVR550U
...00d2, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c1, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c2, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c3, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c5, Type: Feature, Value: 2.000000
> Can't retrieve Report 154 (-32/32): Broken pipe
> Path: UPS.ffff0015.00ff0001.ffff00c4, Type: Feature
> entering identify_ups(0x09ae, 0x1003)
>
> upsdrv_updateinfo...
> dstate_init: sock /var/state/ups/newhidups-auto open on fd 5
> upsdrv_...
2006 Jul 08
1
Re: your Tripp-Lite AVR550U
...00d2, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c1, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c2, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c3, Type: Feature, Value: 255.000000
> Path: UPS.ffff0015.00ff0001.ffff00c5, Type: Feature, Value: 2.000000
> Can't retrieve Report 154 (-32/32): Broken pipe
> Path: UPS.ffff0015.00ff0001.ffff00c4, Type: Feature
> entering identify_ups(0x09ae, 0x1003)
>
> upsdrv_updateinfo...
> dstate_init: sock /var/state/ups/newhidups-auto open on fd 5
> upsdrv_...
2008 Mar 03
1
Tripplite Smart1000LCD problem with revision > r1071
..., Type: Feature, ReportID: 0x97,
Offset: 0, Size: 16, Value: 255.000000
Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID: 0x98,
Offset: 0, Size: 8, Value: 255.000000
Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID: 0x99,
Offset: 0, Size: 16, Value: 255.000000
Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID: 0x9b,
Offset: 0, Size: 16, Value: 3.000000
Can't retrieve Report 154: Broken pipe
Path: UPS.ffff0015.[1].ffff00c4, Type: Feature, ReportID: 0x9a,
Offset: 0, Size: 32
Can't retrieve Report 49: Value too large for defined data type
Path: UPS.PowerSummary.Voltage, Typ...
2007 Dec 05
2
Crash when I start driver
...ype: Feature, ReportID: 0x97, Offset:
0, Size: 16, Value: 255.000000
Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID: 0x98, Offset:
0, Size: 8, Value: 255.000000
Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID: 0x99, Offset:
0, Size: 16, Value: 255.000000
Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID: 0x9b, Offset:
0, Size: 16, Value: 2.000000
Can't retrieve Report 154 (32): Broken pipe
Path: UPS.ffff0015.[1].ffff00c4, Type: Feature, ReportID: 0x9a, Offset:
0, Size: 32
Can't find object UPS.PowerSummary.RemainingCapacityLimit
Can't find object UPS.PowerSum...
2008 Jan 26
1
USBDEVFS_CONTROL error ?
...Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID: 0x98, Offset: 0, Size: 8, Value: 255.000000
Report[r]: (3 bytes) => 99 ff ff
Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID: 0x99, Offset: 0, Size: 16, Value: 255.000000
Report[r]: (3 bytes) => 9b 03 00
Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID: 0x9b, Offset: 0, Size: 16, Value: 3.000000
Report[r]: (3 bytes) => 9a 9a 9a
Path: UPS.ffff0015.[1].ffff00c4, Type: Feature, ReportID: 0x9a, Offset: 0, Size: 32, Value: 154.000000
Can't retrieve Report 49 (75): Value too large for defined data type
Path: UPS.PowerSum...
2017 Dec 18
2
Tripp-Lite BCPERS450 shutdown/restart problems
..., ReportID: 0x97, Offset: 0, Size: 16, Value: 255
0.077150 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID: 0x98, Offset: 0, Size: 8, Value: 255
0.077710 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID: 0x99, Offset: 0, Size: 16, Value: 255
0.078289 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID: 0x9b, Offset: 0, Size: 16, Value: 3
0.079011 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature, ReportID: 0xc2, Offset: 0, Size: 32, Value: 14
0.079620 libusb_get_report: error sending control message: Operation not permitted
0.079665 Can't retrieve Report c1: Op...
2015 Jun 09
0
libusb_get_string: invalid argument
...0x97, Offset: 0, Size: 16, Value: 255
1.188284 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature,
ReportID: 0x98, Offset: 0, Size: 8, Value: 255
1.205022 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature,
ReportID: 0x99, Offset: 0, Size: 16, Value: 255
1.221761 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature,
ReportID: 0x9b, Offset: 0, Size: 16, Value: 3
1.230623 libusb_get_report: Value too large for defined data type
1.231014 Can't retrieve Report c2: Value too large for defined data type
1.231393 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature,
ReportID: 0xc2,...
2015 Jun 09
0
libusb_get_string: invalid argument
...et_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
>>
>>
>> The...
2006 Jul 24
3
Tripp Lite Smart1000LCD driver problem
Thanks Kjell for the help with the build problem. Thanks for your input,
too, Charles.
Now I have a new problem that I think has already been solved. I have
Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver
to communicate correctly. I found a thread on the development list from
last December where Jonathan Freedman described had a problem with this
UPS in a thread
2015 Jun 09
2
libusb_get_string: invalid argument
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
2020 Jan 01
2
Tripp Lite SMART1500LCD will not stay shut down when power is disconnected
...0x97, Offset: 0, Size: 16, Value: 255
0.197763 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID:
0x98, Offset: 0, Size: 8, Value: 255
0.199686 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID:
0x99, Offset: 0, Size: 16, Value: 255
0.200527 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID:
0x9b, Offset: 0, Size: 16, Value: 3
0.202435 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature, ReportID:
0xc2, Offset: 0, Size: 32, Value: 11
0.204391 libusb_get_report: could not claim interface 0: Device or
resource busy
0.204547 Can't retrieve Rep...
2017 Dec 20
3
Tripp-Lite BCPERS450 shutdown/restart problems
..., ReportID: 0x97, Offset: 0, Size: 16, Value: 255
0.073152 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID: 0x98, Offset: 0, Size: 8, Value: 255
0.073668 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID: 0x99, Offset: 0, Size: 16, Value: 255
0.078695 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID: 0x9b, Offset: 0, Size: 16, Value: 3
0.079245 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature, ReportID: 0xc2, Offset: 0, Size: 32, Value: 14
0.079703 libusb_get_report: could not claim interface 0: Device or resource busy
0.079755 Can't retrieve Report c1: Devi...
2007 May 11
11
tripp lite smart2200RMXL2U error reading protocol
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
2017 Aug 21
5
TrippLite SMART1500LCD no delay before ups shutdown.
...97, Offset: 0, Size: 16, Value: 255
0.157092 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature,
ReportID: 0x98, Offset: 0, Size: 8, Value: 255
0.157584 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature,
ReportID: 0x99, Offset: 0, Size: 16, Value: 255
0.158067 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature,
ReportID: 0x9b, Offset: 0, Size: 16, Value: 3
0.158553 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature,
ReportID: 0xc2, Offset: 0, Size: 32, Value: 11
0.159017 libusb_get_report: could not claim interface 0: Device
or resource busy
0.159023 Can't retrieve...
2019 Dec 08
3
Tripp Lite SMART1500LCD repeatedly disconnecting and reconnecting
...0x97, Offset: 0, Size: 16, Value: 255
0.180988 Path: UPS.ffff0015.[1].ffff00c2, Type: Feature, ReportID:
0x98, Offset: 0, Size: 8, Value: 255
0.182984 Path: UPS.ffff0015.[1].ffff00c3, Type: Feature, ReportID:
0x99, Offset: 0, Size: 16, Value: 255
0.184983 Path: UPS.ffff0015.[1].ffff00c5, Type: Feature, ReportID:
0x9b, Offset: 0, Size: 16, Value: 3
0.186987 Path: UPS.ffff0015.[1].ffff00d6, Type: Feature, ReportID:
0xc2, Offset: 0, Size: 32, Value: 11
0.188951 libusb_get_report: No error
0.189102 Can't retrieve Report c1: Operation not permitted
0.189243...