Nut upsuser - Oct 2010 - Powercom WOW-525U nut configuration

please subscribe to the nut user mailing list (
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser)
and post the output of "/path/to/usbhid-ups -DDDDD -a
<your_ups_name_in_ups.conf>"

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

2010/9/11 nsaw
> Good day,
>
> I'm nsaw from Indonesia. I have Powercom WOW-525u UPS with usb cable as
> pc communication. I have trouble using it under nut. My system is Arch
> Linux (updated). I tried usbhid-ups and powercom. I was hoping that you
> would like to help me solve this problem. Thank you very much for your
> attention.
>
> lsusb output:
>
> Bus 004 Device 008: ID 0d9f:0001 Powercom Co., Ltd
> Device Descriptor:
>  bLength                18
>  bDescriptorType         1
>  bcdUSB               1.00
>  bDeviceClass            0 (Defined at Interface level)
>  bDeviceSubClass         0
>  bDeviceProtocol         0
>  bMaxPacketSize0         8
>  idVendor           0x0d9f Powercom Co., Ltd
>  idProduct          0x0001
>  bcdDevice            1.00
>  iManufacturer           1
>  iProduct                2
>  iSerial                 3
>  bNumConfigurations      1
>  Configuration Descriptor:
>    bLength                 9
>    bDescriptorType         2
>    wTotalLength           34
>    bNumInterfaces          1
>    bConfigurationValue     1
>    iConfiguration          0
>    bmAttributes         0x40
>      (Missing must-be-set bit!)
>      Self Powered
>    MaxPower                0mA
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        0
>      bAlternateSetting       0
>      bNumEndpoints           1
>      bInterfaceClass         3 Human Interface Device
>      bInterfaceSubClass      0 No Subclass
>      bInterfaceProtocol      0 None
>      iInterface              0
>        HID Device Descriptor:
>          bLength                 9
>          bDescriptorType        33
>          bcdHID               1.00
>          bCountryCode            0 Not supported
>          bNumDescriptors         1
>          bDescriptorType        34 Report
>          wDescriptorLength     175
>         Report Descriptors:
>           ** UNAVAILABLE **
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x81  EP 1 IN
>        bmAttributes            3
>          Transfer Type            Interrupt
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0008  1x 8 bytes
>        bInterval             250
> Device Status:     0x0000
>  (Bus Powered)
>
> dmesg output:
>
> usbcore: registered new interface driver usbserial
> USB Serial support registered for generic
> generic-usb 0003:0D9F:0001.0009: hiddev0,hidraw2: USB HID v1.00 Device
> [HID 0d9f:0001] on usb-0000:02:0b.0-1/input0
> usbcore: registered new interface driver usbserial_generic
> usbserial: USB Serial Driver core
>
> dmesg output every time I tried to start upsd:
>
> usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255
> ret -110
> usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255
> ret -110
> usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255
> ret -110
> usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255
> ret -110
> usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255
> ret -110
> usb 4-1: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 255
> ret -110
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20101013/01f3f649/attachment.htm>

Citeren Arnaud Quette <arnaud.quette at free.fr>:
> please subscribe to the nut user mailing list (
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser)
> and post the output of "/path/to/usbhid-ups -DDDDD -a
> <your_ups_name_in_ups.conf>"
Forget the above, this is not a HID PDC device. Currently PowerCOM  
uses (at least) the following VendorID:ProductID combinations:

0d9f:0001 - probably USB to serial implementation (unknown)
0d9f:0002 - Cypress M8 USB to serial (use a /dev/ttyUSBx serial port  
and 'powercom' serial driver)
0d9f:00a2 - serial over HID PDC (use usbhid-ups)
0d9f:00a3 - serial over HID PDC (use usbhid-ups)
0d9f:00a4 - serial over HID PDC (use usbhid-ups)
0d9f:00a5 - serial over HID PDC (use usbhid-ups)
0d9f:00a6 - serial over HID PDC (use usbhid-ups)

We've seen reports for the 0d9f:0001 from PowerCOM before, but no  
reports from people that succeeded in setting this up with NUT. You'd  
need to find out what protocol is use and how the USB to serial  
implementation works.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)