[Nut-upsuser] Re: Xserve, USB, NUT

Ted nups at bjmoose.com
Sat Jan 7 10:24:21 UTC 2006

Further info, here's the debug output from newhidups:
Checking device (051D/0002) (002/003-051d-0002-00-00)
 - VendorID: 051d
 - ProductID: 0002
 - Manufacturer: American Power Conversion
 - Product: Smart-UPS 1500 FW:601.3.D USB FW:1.5
 - Serial Number: AS0544120062
 - Bus: 002
Trying to match device
Device matches
failed to claim USB device...
HID descriptor retrieved (Reportlen = 61939)
Unable to get Report descriptor (-1) 

Apparently while 2.0.2 can grab the device from OS X, 2.0.3 version does 

Ted writes: 

> Did that (with 2.0.2) - got the newhidups driver to come up, but it had no 
> APC recognition of anything, it saw the UPS but upsc did not report any 
> status, just vendor, serial, description.  
> Then I tried the latest 2.0.3 on the site, had to add the libusb path for 
> newhidups to build (a clue I was on the same version as you were), and put 
> that in.  However now, without any change to the config files that worked 
> for 2.0.2, it does not find the UPS at all.  
> Now it says:
> # /usr/local/ups/bin/upsdrvctl start
> Network UPS Tools - UPS driver controller 2.0.3-pre2
> Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3-pre2)  
> No matching USB/HID UPS found
> Driver failed to start (exit status=1)
> #  
> Any idea how to get it going from here?  As I said the config files are 
> untouched from what worked to get it to at least upsc seeing it in 2.0.2.  
> Peter Selinger writes:  
>> Ted Bardusch wrote:
>>> OK, I've installed libusb and gd (for the cgi stuff).  I have the UPS  
>>> connected, and built NUT with newhidups.  but now I need to know what  
>>> to set the ups.conf port to.  Any ideas on that?
>> Please see the newhidups(8) man page, section IMPLEMENTATION.  
>>  The  driver  ignores the "port" value in ups.conf. Unlike previous ver-
>>  sions of this driver, it is now possible to control multiple UPS  units
>>  simultaneously  with  this driver. They can be distinguished by setting
>>  some combination of the "vendor", "product", "serial", "vendorid",  and
>>        "productid" options. For instance:  
>>             [mge]
>>                  driver = newhidups
>>                  port = auto
>>                  vendorid = 0463
>>             [tripplite]
>>                  driver = newhidups
>>                  port = auto
>>                  vendorid = 09ae  
>> Arnaud: this is now a frequenly asked question. Should we add the info
>> on the newhidups "port" value to INSTALL, section 7?  
>> Greetings to all from Hanoi (Vietnam). -- Peter
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

More information about the Nut-upsuser mailing list