[Nut-upsdev] tripplite_usb and Omni1000

[Justin Maggard]

Did you update your hotplug scripts to support NUT on USB?  In the source 
tree, look in scripts/hotplug.

>From: "Brandon Siegel" <bsiegel at fastmail.fm>
>To: Nut-upsdev at lists.alioth.debian.org
>Subject: Re: [Nut-upsdev] tripplite_usb and Omni1000
>Date: Fri, 17 Mar 2006 18:58:40 -0500
>
>Just an update:
>
>I tried adding "-x productid=2005" to the commandline of tripplite_usb
>to force it to match, and this is the output:
>
>Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.1.0)
>Warning: This is an experimental driver.
>Some features may not function correctly.
>
>debug level is '5'
>Checking device (0000/0000) (002/001)
>- VendorID: 0000
>- ProductID: 0000
>- Manufacturer: unknown
>- Product: unknown
>- Serial Number: unknown
>- Bus: 002
>Trying to match device
>Device does not match - skipping
>Checking device (09AE/2005) (001/002)
>- VendorID: 09ae
>- ProductID: 2005
>- Manufacturer: unknown
>- Product: unknown
>- Serial Number: unknown
>- Bus: 001
>Trying to match device
>Device matches
>failed to claim USB device, trying 2 more time(s)...
>detaching kernel driver from USB device...
>failed to detach kernel driver from USB device...
>trying again to claim USB device...
>failed to claim USB device, trying 1 more time(s)...
>detaching kernel driver from USB device...
>failed to detach kernel driver from USB device...
>trying again to claim USB device...
>failed to claim USB device, trying 0 more time(s)...
>detaching kernel driver from USB device...
>failed to detach kernel driver from USB device...
>trying again to claim USB device...
>Unable to get HID descriptor (error sending control message: Operation
>not permitted)
>Checking device (0000/0000) (001/001)
>- VendorID: 0000
>- ProductID: 0000
>- Manufacturer: unknown
>- Product: unknown
>- Serial Number: unknown
>- Bus: 001
>Trying to match device
>Device does not match - skipping
>No appropriate HID device found
>No matching USB/HID UPS found
>
>
>
>On Fri, 17 Mar 2006 18:51:35 -0500, "Brandon Siegel"
><bsiegel at fastmail.fm> said:
> > As I understand it from looking through the archives of this mailing
> > list and the source for the driver, tripplite_usb should work for this
> > device. I tried to go through the source as best I could to see if I
> > could add support myself, but got a bit lost.
> >
> > Anyhow, here's hoping that someone has some experience with this model.
> > My system is using the latest CVS checkout of the Development branch (as
> > of this message), and libusb(-dev) packages version 0.1.11-6. The system
> > uses GCC 4.0 to compile. Here is the output of ./tripplite_usb -DDDDD
> > /dev/usb/hiddev0:
> >
> > Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.1.0)
> > Warning: This is an experimental driver.
> > Some features may not function correctly.
> >
> > debug level is '5'
> > Checking device (0000/0000) (002/001)
> > - VendorID: 0000
> > - ProductID: 0000
> > - Manufacturer: unknown
> > - Product: unknown
> > - Serial Number: unknown
> > - Bus: 002
> > Trying to match device
> > Device does not match - skipping
> > Checking device (09AE/2005) (001/002)
> > - VendorID: 09ae
> > - ProductID: 2005
> > - Manufacturer: unknown
> > - Product: unknown
> > - Serial Number: unknown
> > - Bus: 001
> > Trying to match device
> > Device does not match - skipping
> > Checking device (0000/0000) (001/001)
> > - VendorID: 0000
> > - ProductID: 0000
> > - Manufacturer: unknown
> > - Product: unknown
> > - Serial Number: unknown
> > - Bus: 001
> > Trying to match device
> > Device does not match - skipping
> > No appropriate HID device found
> > No matching USB/HID UPS found
> >
> > Also, as I was reading through the source, I found a notation that some
> > events were unknown as to their function. Here are the functions of the
> > ones I could figure out (for the OMNI1000 LCD):
> >
> > 8400d0: 0 when on battery, 1 when on wall power
> > 84004b: 0 when on wall power and battery (sorry, not much help on this
> > one)
> > 840045: 1 when on battery and also 1 immediately after wall power is
> > restored, but changes to 0 after about 5-10 seconds
> > 840044: 0 when on battery and also 0 immediately after wall power is
> > restored, but changes to 1 after about 5-10 seconds
> >
> > I noticed that immediately after wall power was restored, the LCD
> > displayed voltage level of 122 volts. I suspect it is possible that the
> > changing of those last two after a few seconds may involve automatic
> > voltage regulation, or perhaps when the battery is charging.
> >
> > This is all I can give you for now. If you can think of anything else
> > for me to try that will help you, please let me know.
> >
> > --Brandon Siegel
> >
> > _______________________________________________
> > 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