[Nut-upsdev] tripplite smart2000rmxl2u product id 3014

[Ken Teh]

I have it sort of working.  I was able to run the usbhid-ups driver with the productid as you suggested but I have to run everything as root.  Here's a quick summary of results:

(1) The distro's 52.nut rules file generates error messages in the syslog.  So, I rewrote them.  But this had no effect.  I was able to see a mapped device /dev/hiddevXX with owner/permissions I specified but the  nut driver and programs still do not run without the '-u root' option.  Does the driver open a device file in /dev or does it walk the usb tree somewhere else?  In /sys?

(2) Running everything as root, I was able to generate notify events when I take the UPS on line power and off line power.

(3) I also checked with a upsmon slave and everything works as expected.

Today was the smoke test day.  I took the UPS off line power, partially drained the battery with a electric heater, and monitored the battery charge with upsc.  It kept dropping down to 1 and stayed there like forever.  upsmon never went through executing the low battery notify event or the shutdown.  I noticed that the UPS LEDs indicated adequate power (it was still green) so this leads me to the next questions:

(1) It seems that the driver does not read the UPS correctly.  At least it does not read the battery charge correctly.

(2) What actually triggers the shutdown and low battery events in upsmon?  Is it the battery charge or something else?

I'd appreciate a quick response and suggestions on moving forward.  If I cannot resolve this quickly, I will have to give up on nut and use something else.

Thanks!

Ken




Arjen de Korte wrote:
> Citeren teh at phy.anl.gov:
> 
>> Adding the -x productid=3014 as you suggested did not work.  Here's what
>> the driver dumps out.
>>
>> [root at fugue ups]# bin/usbhid-ups -a ups01 -DD -x productid=3014
>> Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2)
>>
>> debug level is '2'
>> upsdrv_initups...
>>
>> ...<snip>...
>>
>> Checking device (09AE/3014) (002/002)
>> - VendorID: 09ae
>> - ProductID: 3014
>> - Manufacturer: unknown
>> - Product: unknown
>> - Serial Number: unknown
>> - Bus: 002
>> 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)
>> HID descriptor length 1145
>> Unable to get Report descriptor: Operation not permitted
>> No appropriate HID device found
>> No matching HID UPS found
>> [root at fugue ups]#
>>
>> Why does it fail to claim the device?  Is another driver or process own
>> it?  If so, which?
> 
> Add '-u root' to the startup commandline to rule out a permissions 
> problem. Chances are that you need to setup hotplug/udev to allow the 
> driver access to the UPS when it drops privileges. Since this is a new 
> VID:PID combination, this won't work as it is. Running the driver as 
> root successfully should confirm this.
> 
> Best regards, Arjen