On Thu, Apr 3, 2008 at 10:18 PM, Charles Lepple <<a href="mailto:clepple@gmail.com">clepple@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, Apr 3, 2008 at 3:49 PM, Matt Fischer <<a href="mailto:tadowguy@gmail.com">tadowguy@gmail.com</a>> wrote:<br>
> The Compatibility page lists the OMNIVS1000 as supported, but the<br>
> tripplite_usb driver doesn't seem to recognize my UPS. Below is the debug<br>
> dump from attempting to load the driver. I am using the nut package from<br>
> Debian: 2.2.1-2.1 and I was wondering if this was a known issue?<br>
><br>
> maroon:/lib/nut# /lib/nut/tripplite_usb -DDDDD -a usbups<br>
> Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-)<br>
> Warning: This is an experimental driver.<br>
> Some features may not function correctly.<br>
><br>
> debug level is '5'<br>
[...]<br>
</div><div class="Ih2E3d">> Checking device (09AE/1007) (002/008)<br>
> - VendorID: 09ae<br>
> - ProductID: 1007<br>
> - Manufacturer: Tripp Lite<br>
> - Product: TRIPP LITE UPS<br>
> - Serial Number: FW-2263 E<br>
> - Bus: 002<br>
> Trying to match device<br>
> Device does not match - skipping<br>
<br>
</div>Well, they did it again - Tripp Lite changed the product ID while<br>
keeping the model name the same.<br>
<br>
You can try using some of the options on the tripplite_usb man page to<br>
force loading the driver, but if it is closer in lineage to the OMNI<br>
LCD models (or whatever they're called), then you might have better<br>
luck with the usbhid-ups driver.<br>
<br>
Also, please let us know roughly when this OMNIVS1000 was manufactured<br>
(as well as which driver works, and with what options), so that we can<br>
update the compatibility list.<br>
<br>
thanks,<br>
<br>
--<br>
<font color="#888888">- Charles Lepple<br>
</font></blockquote></div><br>Doing a reply to all (including the list) since I forgot the first time (personally, I blame gmail).<br><br>This unit was just pulled out of the box yesterday and was ordered a
few months back, so it's pretty new. I don't see anything about dates
on the box, but I see a "Series# AGOM6032" on the box which perhaps
helps. <br>
<br>I had poor results with both drivers, but I got farther with
usbhid-ups using -x productid=1007. It looks like that driver
retrieved some info and then went into an infinite loop (all details attached in uncompressed files). The tripplite driver failed after sending a watchdog command
and gave up.<br><br>note: I had to kill the usbhid-ups driver with kill -9 after a bit, if you want me to let it run longer, let me know, but I think it's just spinning.<br><br><br>