Nut upsuser - Dec 2009 - usbhid-ups disconnects with Eaton Ellipse 1000S

My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse
0463:ffff).

I have been using the usb interface with the usbhid-ups driver, but I
found that sometimes (too much times) the driver doesn't respond and NUT
doesn't receive changes nor notifications from the UPS.

The kernel lose the connections with USB device, in the kernel logs
appears:

Dec 30 11:24:12 rei kernel: [561646.660027] usb 6-2: usbfs:
USBDEVFS_CONTROL 
failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75
Dec 30 11:30:12 rei kernel: [562006.456470] usb 6-2: usbfs: USBDEVFS_CONTROL
failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75
Dec 30 11:48:16 rei kernel: [563090.692015] usb 6-2: usbfs: USBDEVFS_CONTROL
failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110
Dec 30 11:54:16 rei kernel: [563450.480662] usb 6-2: usbfs: USBDEVFS_CONTROL
failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110

And as can be seen in the logs, the devices disappears and reappers (assigned a
new addresss):

Dec 28 13:31:11 rei kernel: [396465.447223] usb 6-1: USB disconnect, address 12
Dec 28 13:31:12 rei kernel: [396466.996013] usb 6-1: new low speed USB device
using ohci_hcd and address 15
Dec 28 13:31:13 rei kernel: [396467.960737] usb 6-1: configuration #1 chosen
from 1 choice
Dec 28 13:31:13 rei kernel: [396467.965533] usb 6-1: New USB device found,
idVendor=0463, idProduct=ffff
Dec 28 13:31:13 rei kernel: [396467.965549] usb 6-1: New USB device strings:
Mfr=1, Product=2, SerialNumber=4
Dec 28 13:31:13 rei kernel: [396467.965552] usb 6-1: Product: ELLIPSE
Dec 28 13:31:13 rei kernel: [396467.965555] usb 6-1: Manufacturer: EATON
Dec 28 13:31:13 rei kernel: [396467.965557] usb 6-1: SerialNumber: 000000000
Dec 28 13:43:54 rei kernel: [397228.950392] usb 6-1: USB disconnect, address 15
Dec 28 13:43:56 rei kernel: [397230.500080] usb 6-1: new low speed USB device
using ohci_hcd and address 18
Dec 28 13:43:57 rei kernel: [397231.444215] usb 6-1: configuration #1 chosen
from 1 choice
Dec 28 13:43:57 rei kernel: [397231.449076] usb 6-1: New USB device found,
idVendor=0463, idProduct=ffff
Dec 28 13:43:57 rei kernel: [397231.449097] usb 6-1: New USB device strings:
Mfr=1, Product=2, SerialNumber=4
Dec 28 13:43:57 rei kernel: [397231.449101] usb 6-1: Product: ELLIPSE
Dec 28 13:43:57 rei kernel: [397231.449103] usb 6-1: Manufacturer: EATON
Dec 28 13:43:57 rei kernel: [397231.449106] usb 6-1: SerialNumber: 000000000

If I try to reestart the driver:
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.2
Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2)

No matching HID UPS found
Driver failed to start (exit status=1)

Doing it manually with verbose:
# /lib/nut/usbhid-ups -a Ellipse -DDDD
[...]
Checking device (0463/FFFF) (006/023)
- VendorID: 0463
- ProductID: ffff
- Manufacturer: EATON
- Product: ELLIPSE
- Serial Number: 000000000
- Bus: 006
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...
  Couldn't retrieve descriptors
[...]

When this happens the last solution is unplug and plug again the USB cable of
the UPS and restart NUT.

Now I'm using the serial interface with the mge-shut driver. (without
problems for Now). I discarded USB problem because I have a USB Drive attached
to the same bus without any problem.

Citeren Marc Franquesa <mark op l3jane.net>:
> My UPS is a Eaton Ellipse 1000S (But its identified as MGE Ellipse
> 0463:ffff).
That's because part of the company MGE that originally acquired the  
vendorid 0463 is now owned by Eaton. They still use the 'old' vendorid  
for the .
> I have been using the usb interface with the usbhid-ups driver, but I
> found that sometimes (too much times) the driver doesn't respond and
NUT
> doesn't receive changes nor notifications from the UPS.
This is a known problem with the Ellipse series UPS. Eaton send me one  
for testing and it has the same problem as what you describe. I'm  
trying to work around the problem, but so far without success. Note  
that for instance an MGE Evolution that is running in parallel to this  
system hardly ever sees a glitch, so this pretty much rules out  
problems with kernel, libusb and/or usbhid-ups.
> Now I'm using the serial interface with the mge-shut driver.  
> (without problems for Now). I discarded USB problem because I have a  
> USB Drive attached to the same bus without any problem.
If you upgrade to nut-2.4.1, you could try adding the 'pollonly' flag  
to 'ups.conf' entry for this UPS. The problems seem to be related to  
the use of the interrupt pipe on this UPS. If that doesn't work, I  
would also recommend to use the serial interface with the Ellipse  
series (even if this would require a USB to serial converter).

Best regards, Arjen
-- 
Please keep list traffic on the list

Hi, its only a minor wrinkle, but repeated %s in NOTIFYMSG seem to 
be ignored. In /etc/ups/upsmon.conf I specified:

NOTIFYMSG NOCOMM "UPS %s is unavailable +++ Onduleur %s indisponible"

but the message I received said:

Broadcast Message from upsd at sandrane
         (somewhere) at 18:33 ...

UPS Eaton-66781 at localhost is unavailable +++ Onduleur (null) 
indisponible

Roger