[Nut-upsuser] Re Powercom Vanguard driver for nut

Gordon Longland gordon at compsos.com.au
Sat Jul 21 11:52:21 UTC 2012


Hi 

Have been trying to get nut and Powercom Vanguard 2000 ups communicating

 
in the /lib/udev/rules.d/52-nut-usbups.rules file we have this entry

#  PowerCOM VGD - Vanguard  - usbhid-ups
ATTR{idVendor}=="0d9f", ATTR{idProduct}=="0004", MODE="664", GROUP="nut"

 
In the /etc/ups/ups.conf

[UPS]
        driver = usbhid-ups
        port = /var/lib/ups/hiddev0
        productid = 0004

When running the command

upsdrvctl -u nut -DDDDD start

 
It returns

Network UPS Tools - UPS driver controller 2.2.2
Starting UPS: UPS
exec: /sbin/usbhid-ups -a UPS -u nut
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)

 
Nut version

nut-2.2.2-3.el5

on kernel

2.6.18-308.11.1.el5PAE

 
If we try using the powercom driver it complains it is a usbhid-ups and if we try some of the powercom settings in the ups.conf the usbhid-ups driver rejects them as unknown (ie) model = , linevoltage = ....

 
lsusb -vd 0d9f:0004|sed -ne '/^\w/p;/\bi/p'  returns

Protocol spec without prior Class and Subclass spec at line 4297
Bus 005 Device 002: ID 0d9f:0004 Powercom Co., Ltd
Device Descriptor:
  idVendor           0x0d9f Powercom Co., Ltd
  idProduct          0x0004
  iManufacturer           3 POWERCOM Co.,LTD
  iProduct                1 HID UPS Battery
  iSerial                 2 004-0D9F-000
    iConfiguration          0
      iInterface              0

 
Run the driver directly on debug level 4

/sbin/usbhid-ups -DDDD -a UPS

 
debug level is '4'
upsdrv_initups...
Checking device (0000/0000) (008/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 008
Trying to match device
Device does not match - skipping
Checking device (0D9F/0004) (005/002)
- VendorID: 0d9f
- ProductID: 0004
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 005
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (005/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 005
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (006/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 006
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (003/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 003
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (001/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (002/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 002
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (007/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 007
Trying to match device
Device does not match - skipping
Checking device (0000/0000) (004/001)
- VendorID: 0000
- ProductID: 0000
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 004
Trying to match device
Device does not match - skipping
No appropriate HID device found
No matching HID UPS found
 
The log shows

Jul 21 21:32:29 server upsd[3760]: Can't connect to UPS [UPS] (usbhid-ups-UPS): No such file or directory
Jul 21 21:32:30 server upsmon[3764]: Poll UPS [UPS at localhost] failed - Driver not connected
Jul 21 21:34:35 server upsmon[3764]: UPS UPS at localhost is unavailable

 
Is there something simple we are missing? Why does it add the UPS stanza to the driver (usbhid-ups-UPS) name and then fail?

Is there a patch for the usbhid-ups driver to recognise the Vanguard series?


TIA
 
Regards  

 
Compsos

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120721/f9e99b90/attachment.html>


More information about the Nut-upsuser mailing list