[Nut-upsdev] tripp lite smart2200RMXL2U error reading protocol

Patrick Krepps cso at satcharters.com
Thu May 17 01:38:10 UTC 2007 

Hi Peter,

My apologies. I had seen your posting and thought you may have done some work 
on this. But I see you have real important stuff going on in you life! 
Congratulations on the (soon to be) new baby!

Don't worry about this, I can live with what I have. The problem was the unit 
showing to be on battery, even when on line power. My wife works at home and 
she knows how to power the servers down/up if we loose power during the day. 
As the UPS has a loud alarm, the "wife" version of NUT will get us by until 
you have time to take this back up. While this isn't perfect, it is better 
than what I had before - no UPS at all. The UPS has well over 20 minutes of 
capacity with the two systems connected. Most of the time power has been 
restored by the time she gets in here to check them.

BTW, if this is your first child, I have some advice - get all the sleep you 
can now, because you won't be getting much for the next few months. But in 
the end the lack of sleep is worth it.

Best of luck to you and your wife.

Patrick

On Wednesday 16 May 2007 19:43, you wrote:
> Hi Patrick,
>
> as you know, I haven't had much time to work on NUT. Now my wife is
> expecting our first baby in 1 week, so I don't think I will get back
> to it in the foreseeable future.
>
> I remember that there was something I was planning to do for your
> device, but I have forgotten what it was. Was it that your device was
> mostly working, but something had to be tweaked? I now have, it seems,
> thousands of unread, as well as read, NUT messages, so perhaps it's
> best if you remind me. I seem to remember that it was something
> relatively easy, which I had been putting off because I hoped to take
> care of it as part of a larger rewrite. Perhaps I can quickly do the
> easy thing without the rewrite.
>
> -- Peter
>
> Patrick Krepps wrote:
> > Hi Peter,
> >
> > I noticed you listed the SmartOnlineSU1500. Is that by chance the one you
> > were looking at for me a while back? I hadn't heard anything back from
> > you and I've been plaing around with DNS servers, so I hadn't tried NUT
> > in a few weeks. I am going to go get the latest SVN version and give it a
> > try. Is there anything you need from me?
> >
> > Thanks,
> > Patrick
> >
> > On Monday 14 May 2007 11:16, Peter Selinger wrote:
> > > OK, that is very similar to the other Tripplite-HID devices; the
> > > functionality of this device seems to be almost a superset of the
> > > OMNI1000LCD and of the SmartOnlineSU1500RTXL2ua.
> > >
> > > It should work without problems with the newhidups driver, if you just
> > > add the 0x3012 to the source code where Charles suggested.
> > >
> > > I have just done this in the latest SVN version (revision 901).
> > > Note that in SVN, the driver has been renamed to usbhid-ups from
> > > newhidups.
> > >
> > > -- Peter
> > >
> > > Lance Thomas wrote:
> > > > I'll look into the newest svn of nut.
> > > > Here is the output from:
> > > > newhidups -u root  -x vendorid=09ae -x explore auto
> > > >
> > > > Detected a UPS: Tripp Lite /TRIPP LITE SMART2200RMXL2U
> > > > Using subdriver: EXPLORE HID 0.1
> > > > Path: UPS.PowerSummary.iProduct, Type: Feature, Value: 2.000000
> > > > Path: UPS.PowerSummary.iSerialNumber, Type: Feature, Value: 3.000000
> > > > Path: UPS.PowerSummary.iManufacturer, Type: Feature, Value: 1.000000
> > > > Path: UPS.PowerSummary.Input.ConfigVoltage, Type: Feature, Value:
> > > > 120.000000
> > > > Path: UPS.PowerSummary.Input.Voltage, Type: Feature, Value:
> > > > 125.599998 Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature,
> > > > Value: 2.000000
> > > > Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, Value:
> > > > 4.000000 Path: UPS.PowerSummary.iOEMInformation, Type: Feature,
> > > > Value: 1.000000 Path: UPS.PowerSummary.CapacityMode, Type: Feature,
> > > > Value: 2.000000 Path: UPS.PowerSummary.RemainingCapacity, Type:
> > > > Input, Value: 100.000000 Path: UPS.PowerSummary.RemainingCapacity,
> > > > Type: Feature, Value: 100.000000
> > > > Path: UPS.PowerSummary.RemainingCapacityLimit, Type: Feature, Value:
> > > > 10.000000
> > > > Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, Value:
> > > > 100.000000
> > > > Path: UPS.PowerSummary.DesignCapacity, Type: Feature, Value:
> > > > 100.000000 Path: UPS.PowerSummary.WarningCapacityLimit, Type:
> > > > Feature, Value: 30.000000
> > > > Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, Value:
> > > > 1.000000
> > > > Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, Value:
> > > > 1.000000
> > > > Path: UPS.PowerSummary.Rechargeable, Type: Feature, Value: 1.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Input,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value:
> > > > 1.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Input
> > > > Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit,
> > > > Type: Input, Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input,
> > > > Value: 1.000000
> > > > Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value:
> > > > 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, Value:
> > > > 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Input,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value:
> > > > 1.000000
> > > > Path: UPS.PowerSummary.PresentStatus., Type: Feature
> > > > Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit,
> > > > Type: Feature, Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Feature,
> > > > Value: 1.000000
> > > > Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, Value:
> > > > 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.BatterySystem.Battery.ConfigVoltage, Type: Feature, Value:
> > > > 48.000000
> > > > Path: UPS.BatterySystem.Battery.Voltage, Type: Feature, Value:
> > > > 54.299999 Path: UPS.BatterySystem.Battery.PresentStatus., Type:
> > > > Feature Path: UPS.BatterySystem.Battery.PresentStatus., Type: Feature
> > > > Path:
> > > > UPS.BatterySystem.Battery.PresentStatus.BelowRemainingCapacityLimit,
> > > > Type: Feature
> > > > Path: UPS.BatterySystem.Battery.PresentStatus.FullyCharged, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.BatterySystem.Battery.PresentStatus.Charging, Type:
> > > > Feature, Value: 1.000000
> > > > Path: UPS.BatterySystem.Battery.PresentStatus.Discharging, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.BatterySystem.Battery.PresentStatus.FullyDischarged, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.BatterySystem.Battery.PresentStatus.NeedReplacement, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.BatterySystem.Battery.RemainingCapacity, Type: Feature,
> > > > Value: 100.000000
> > > > Path: UPS.BatterySystem.Test, Type: Feature, Value: 0.000000
> > > > Path: UPS.BatterySystem.Temperature, Type: Feature, Value: 307.000000
> > > > Path: UPS.Flow.ConfigVoltage, Type: Feature, Value: 120.000000
> > > > Path: UPS.Flow.ConfigFrequency, Type: Feature, Value: 60.000000
> > > > Path: UPS.Flow.ffff0097, Type: Feature, Value: 0.000000
> > > > Path: UPS.Flow.ConfigApparentPower, Type: Feature, Value: 2200.000000
> > > > Path: UPS.PowerConverter.Input.Voltage, Type: Feature, Value:
> > > > 125.099998 Path: UPS.PowerConverter.Input.Frequency, Type: Feature,
> > > > Value: 59.900002
> > > > Path: UPS.PowerConverter.Output.Voltage, Type: Feature, Value:
> > > > 125.599998
> > > > Path: UPS.PowerConverter.Output.Frequency, Type: Feature, Value:
> > > > 59.900002
> > > > Path: UPS.PowerConverter.Output.LowVoltageTransfer, Type: Feature,
> > > > Value: 83.000000
> > > > Path: UPS.PowerConverter.Output.HighVoltageTransfer, Type: Feature,
> > > > Value: 145.000000
> > > > Path: UPS.PowerConverter.PresentStatus.VoltageOutOfRange, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus.Buck, Type: Feature, Value:
> > > > 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus.Boost, Type: Feature, Value:
> > > > 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus.Overload, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus.Used, Type: Feature, Value:
> > > > 1.000000
> > > > Path: UPS.PowerConverter.PresentStatus.OverTemperature, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus.InternalFailure, Type:
> > > > Feature, Value: 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.PowerConverter.PresentStatus.AwaitingPower, Type: Feature,
> > > > Value: 0.000000
> > > > Path: UPS.PowerConverter.PresentStatus., Type: Feature
> > > > Path: UPS.OutletSystem.Outlet.DelayBeforeShutdown, Type: Feature,
> > > > Value: -1.000000
> > > > Path: UPS.OutletSystem.Outlet.DelayBeforeStartup, Type: Feature,
> > > > Value: -1.000000
> > > > Path: UPS.OutletSystem.Outlet.DelayBeforeReboot, Type: Feature,
> > > > Value: -1.000000
> > > > Path: UPS.OutletSystem.Outlet.PercentLoad, Type: Feature, Value:
> > > > 43.000000
> > > > Path: UPS.OutletSystem.Outlet.ffff0056, Type: Feature, Value:
> > > > -1.000000 Path: UPS.OutletSystem.Outlet.ffff0081, Type: Feature,
> > > > Value: 0.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.ffff0093, Type: Feature, Value: 0.000000
> > > > Path: UPS.OutletSystem.Outlet.ffff0095, Type: Feature, Value:
> > > > 7.000000 Path: UPS.OutletSystem.Outlet.ffff0096, Type: Feature,
> > > > Value: 7.000000 Path: UPS.OutletSystem.Outlet.ffff0098, Type:
> > > > Feature, Value: 0.000000 Can't retrieve Report 106 (25):
> > > > Inappropriate ioctl for device Path:
> > > > UPS.OutletSystem.Outlet.ffff0099, Type: Feature
> > > > Can't retrieve Report 107 (25): Inappropriate ioctl for device
> > > > Path: UPS.OutletSystem.Outlet.ffff009a, Type: Feature
> > > > Path: UPS.OutletSystem.Outlet.ffff00a7, Type: Feature, Value:
> > > > 0.000000 Path: UPS.OutletSystem.Outlet.ffff00a9, Type: Feature,
> > > > Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff00a2, Type:
> > > > Feature, Value: 0.000000 Can't retrieve Report 124 (25):
> > > > Inappropriate ioctl for device Path:
> > > > UPS.OutletSystem.Outlet.ffff00a8, Type: Feature
> > > > Can't retrieve Report 114 (25): Inappropriate ioctl for device
> > > > Path: UPS.OutletSystem.Outlet.ffff00a0, Type: Feature
> > > > Path: UPS.OutletSystem.Outlet.ffff00aa, Type: Feature, Value:
> > > > 0.000000 Path: UPS.OutletSystem.Outlet.ffff00a4, Type: Feature,
> > > > Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff00ab, Type:
> > > > Feature, Value: 0.000000 Path: UPS.OutletSystem.Outlet.ffff00ac,
> > > > Type: Feature, Value: 0.000000 Path: UPS.ffff0010[1].ffff0075, Type:
> > > > Feature
> > > > Path: UPS.ffff0010[1].ffff0076, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff007c, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e1, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff007d, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e0, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e2, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e3, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e4, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e5, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e6, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e7, Type: Feature
> > > > Path: UPS.ffff0010[1].ffff00e8, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00c0, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00c2, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00d2, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00d3, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00c1, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00c3, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00c5, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00d6, Type: Feature
> > > > Path: UPS.ffff0015[1].ffff00c4, Type: Feature
> > > > upsdrv_updateinfo...
> > > > dstate_init: sock /var/lib/nut/newhidups-auto open on fd 6
> > > > upsdrv_updateinfo...
> > > > Waiting for notifications...
> > > >
> > > > =>Got 1 HID Objects...
> > > > find_hid_info: unknown variable: UPS.PowerSummary.RemainingCapacity
> > > >
> > > > upsdrv_updateinfo...
> > > > Waiting for notifications...
> > > >
> > > > =>Got 24 HID Objects...
> > > > find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.
> > > >
> > > > find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus.
> > > >
> > > > >>> Peter Selinger <selinger at mathstat.dal.ca> 05/14/07 9:43 AM >>>
> > > >
> > > > Lance Thomas wrote:
> > > > > I tried the newhidups with the command:
> > > > > newhidups -u root -DDDD -x vendorid=09ae -x productid=3012 auto
> > > > >
> > > > > and it goes through finds the ups and tells me that this particular
> > > > > Tripp Lite device (09ae/3012) is not supported.  And then to try
> > > > > the tripplite_usb.
> > > >
> > > > And then it asks you to report the results to the mailing list, which
> > > > you have hereby done :)
> > > >
> > > > There are two things to do:
> > > >
> > > > (1) try the --explore option that Charles was talking about. This
> > > > will not make the driver work, but it will generate sufficient
> > > > debugging info for us to make the driver work. Please use -DD and not
> > > > -DDDD, as the latter generates too much useless information. Please
> > > > post the output.
> > > >
> > > > (2) If you can upgrade from 2.0.5 to a current SVN version of NUT
> > > >     (compiled from sources), then the driver might work directly.
> > > >
> > > > -- Peter
> > > >
> > > > > I forgot to mention that when we got this tripplite we took the
> > > >
> > > > standard
> > > >
> > > > > NEMA 5-20P input plug off and are using the NEMA 5-15P plug
> > > > > instead.
> > > >
> > > > I
> > > >
> > > > > don't think that would make a difference, but I thought I'd mention
> > > > > it just in case.
> > > > >
> > > > > ----
> > > > > Lance sent me the output of "lsusb -vvv" for this device off-list,
> > > > > and here is the key portion of that:
> > > > >
> > > > >         HID Device Descriptor:
> > > > >           bLength                 9
> > > > >           bDescriptorType        33
> > > > >           bcdHID               1.10
> > > > >           bCountryCode            0 Not supported
> > > > >           bNumDescriptors         1
> > > > >           bDescriptorType        34 Report
> > > > >           wDescriptorLength    1121
> > > > >           Report Descriptor: (length is 1121)
> > > > >             Item(Global): Usage Page, data= [ 0x84 ] 132
> > > > >                             Power Device Page
> > > > >             Item(Local ): Usage, data= [ 0x04 ] 4
> > > > >                             UPS
> > > > >             Item(Main  ): Collection, data= [ 0x01 ] 1
> > > > >                             Application
> > > > >             Item(Local ): Usage, data= [ 0x24 ] 36
> > > > >                             Power Summary
> > > > >             Item(Main  ): Collection, data= [ 0x00 ] 0
> > > > >                             Physical
> > > > >             Item(Global): Usage Page, data= [ 0x84 ] 132
> > > > >                             Power Device Page
> > > > >
> > > > > As Kjell mentioned, this looks like another one of those cases
> > > > > where the innards of the UPS got an overhaul, but they kept the
> > > > > model name.
> > > > >
> > > > > Lance: I forget, did you try the newhidups driver as well? That's
> > > > > the one that should eventually support this UPS (tripplite_usb only
> > > > > handles the older serial-protocol-over-USB models).
> > > > >
> > > > > You may have to pass the manufacturer and model options to
> > > > > newhidups as well, since we were not aware of this alternate
> > > > > vendor/product ID for this model of UPS.
> > > > >
> > > > > On 5/11/07, Lance Thomas <Lance.Thomas at fammed.wisc.edu> wrote:
> > > > > > 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 -a tripplite1
> > > > > >
> > > > > > with the following ups.conf:
> > > > > > [tripplite1]
> > > > > >         driver = tripplite_usb
> > > > > >         port = /proc/bus/usb/002/002
> > > > > >         productid = 3012
> > > > > >         bus = 002
> > > > > >         desc = "top ups"
> > > > > >
> > > > > > I get it to run and find the HID, but it returns the following
> > > >
> > > > errors
> > > >
> > > > > > before quitting:
> > > > > > Detected a UPS: Tripp Lite /TRIPP LITE SMART2200RMXL2U
> > > > > > send_cmd(msg_len=3, type='W')
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > send_cmd: send_try = 3, recv_try = 3
> > > > > >
> > > > > > Could not reset watchdog. Please send model information to
> > > >
> > > > nut-upsdev
> > > >
> > > > > > mailing list
> > > > > > send_cmd(msg_len=2, type='
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > libusb_get_interrupt() returned 4 instead of 8
> > > > > > send_cmd: send_try = 3, recv_try = 3
> > > > > >
> > > > > > Error reading protocol
> > > > > >
> > > > > >
> > > > > > Any suggestions?
> > > > > > _________________________________________________________________
> > > > > >___
> > > > > >
> > > > > > This email and any attachments may contain confidential
> > > > > > information
> > > > >
> > > > > and is
> > > > >
> > > > > > solely for the intended recipient(s).  Email communications are
> > > > > > not
> > > > >
> > > > > considered
> > > > >
> > > > > > secure.  If you are not the intended recipient(s) of this email
> > > > > > you
> > > > >
> > > > > are expected
> > > > >
> > > > > > to disregard the content, delete the message and notify the
> > > > > > original
> > > > >
> > > > > sender.
> > > > >
> > > > > > --University of Wisconsin, Department of Family Medicine--
> > > > > > _________________________________________________________________
> > > > > >___
> > > > > >
> > > > > > **UW DFM**
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Nut-upsdev mailing list
> > > > > > Nut-upsdev at lists.alioth.debian.org
> > > > > > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
> > > > >
> > > > > --
> > > > > - Charles Lepple
> > > > >
> > > > > _______________________________________________
> > > > > Nut-upsdev mailing list
> > > > > Nut-upsdev at lists.alioth.debian.org
> > > > > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Nut-upsdev mailing list
> > > > > Nut-upsdev at lists.alioth.debian.org
> > > > > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
> > > >
> > > > _______________________________________________
> > > > Nut-upsdev mailing list
> > > > Nut-upsdev at lists.alioth.debian.org
> > > > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
> > >
> > > _______________________________________________
> > > Nut-upsdev mailing list
> > > Nut-upsdev at lists.alioth.debian.org
> > > http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev

More information about the Nut-upsdev mailing list