Nut upsuser - Jun 2013 - Cannot connect to a Eaton Ellipse Pulsar ASR/6000VA usbs

Hi all, I am trying to communicate to this Eaton Ellipse (see above) using
nut from a Debian Squeeze system on Armel architecture. But have not
succeeded so far.

Version: Linux b3 2.6.39.4-11 #1 Tue Apr 3 21:45:12 FET 2012 armv5tel
GNU/Linux

Nut version is  2.4.3-1.1squeeze2 this information if from dpkg.

NUT installation method:from debian package for armel.

The problem is I cannot communicate to this device from the usbhid-ups
driver.

The configuration is as follows.

# Network UPS Tools: example nut.conf
MODE=standalone
driver = usbhid-ups
port = auto

# Network UPS Tools: example ups.conf
[eaton]
       driver = usbhid-ups
         port = auto
vendor = 0463


# Network UPS Tools: Example upsd.users
[monuser]
password = password  #password changed to demo
upsmon master
action = SET
instcmds = ALL

# Network UPS Tools: example upsmon configuration
# --------------------------------------------------------------------------
RUN_AS_USER root
#
# --------------------------------------------------------------------------
MONITOR eaton at localhost 1 admin password master #password changed to demo7
#

MINSUPPLIES 1

# --------------------------------------------------------------------------
# SHUTDOWNCMD "<command>"
SHUTDOWNCMD "/usr/lib/web-admin/backend.pl power_off"

# --------------------------------------------------------------------------
# POLLFREQ <n>
POLLFREQ 5

# --------------------------------------------------------------------------
# POLLFREQALERT <n>
POLLFREQALERT 5

# --------------------------------------------------------------------------
# HOSTSYNC - How long upsmon will wait before giving up on another upsmon
HOSTSYNC 15

# --------------------------------------------------------------------------
DEADTIME 15

# --------------------------------------------------------------------------
# POWERDOWNFLAG - Flag file for forcing UPS shutdown on the master system
POWERDOWNFLAG /etc/killpower
# --------------------------------------------------------------------------

# RBWARNTIME - replace battery warning time in seconds
RBWARNTIME 43200

# --------------------------------------------------------------------------
# NOCOMMWARNTIME - no communications warning time in seconds
NOCOMMWARNTIME 300

# --------------------------------------------------------------------------
# FINALDELAY - last sleep interval before shutting down the system
FINALDELAY 5



This is the output from the debug of usbhid-ups

louis at b3:/dev/bus/usb/001$ sudo /lib/nut/usbhid-ups -u root -a eaton -DDDDD
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
   0.000000 debug level is '5'
   0.003364 upsdrv_initups...
   0.005048 Checking device (0463/FFFF) (001/003)
   0.408515 - VendorID: 0463
   0.409052 - ProductID: ffff
   0.409551 - Manufacturer: EATON
   0.410030 - Product: ELLIPSE
   0.410509 - Serial Number: BD9L32081
   0.410988 - Bus: 001
   0.411461 Trying to match device
   0.412030 Device does not match - skipping
   0.412577 Checking device (05E3/0608) (001/002)
   0.413887 - VendorID: 05e3
   0.414354 - ProductID: 0608
   0.414837 - Manufacturer: unknown
   0.415316 - Product: USB2.0 Hub
   0.415383 - Serial Number: unknown
   0.415711 - Bus: 001
   0.415775 Trying to match device
   0.416074 Device does not match - skipping
   0.416153 Checking device (1D6B/0002) (001/001)
   0.416539 - VendorID: 1d6b
   0.416839 - ProductID: 0002
   0.417118 - Manufacturer: Linux 2.6.39.4-11 ehci_hcd
   0.417184 - Product: Marvell Orion EHCI
   0.417462 - Serial Number: orion-ehci.0
   0.417526 - Bus: 001
   0.417749 Trying to match device
   0.417874 Device does not match - skipping
   0.417943 No appropriate HID device found
   0.418015 No matching HID UPS found
louis at b3:/dev/bus/usb/001$

However lsusb gives:
louis at b3:/dev/bus/usb/001$ lsusb
Bus 001 Device 003: ID 0463:ffff MGE UPS Systems UPS
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
louis at b3:/dev/bus/usb/001$

and after running the udev rule the rights are:

louis at b3:/dev/bus/usb/001$ ls -l
totaal 0
crw-rw-r-- 1 root root 189, 0 jun 19 21:41 001
crw-rw-r-- 1 root root 189, 1 jun 19 21:41 002
crw-rw-r-- 1 root nut  189, 2 jun 19 21:41 003
louis at b3:/dev/bus/usb/001$

Monuser is part of group nut:

louis at b3:~$ groups monuser
monuser : monuser nut

I don't understand the problem here. I first thought it was a rights
problem, but certainly not on the usb device. The rights seem sufficient.

Any help appreciated, foremost I do not know where to look next.

Kind regard, Louis
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130619/5cb5a7cd/attachment.html>

On Jun 19, 2013, at 4:51 PM, Louis Chaillet wrote:
> # Network UPS Tools: example ups.conf
> [eaton]
>        driver = usbhid-ups
>          port = auto
> 	vendor = 0463
Identifying the vendor or product is not strictly required, but if you provide
'vendor', it must match the 'Manufacturer:' value
('EATON', in your case).

To match against the hex values, use 'vendorid' (or
'productid').

Reference:
http://www.networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments

-- 
Charles Lepple
clepple at gmail