Nut upsuser - Sep 2007 - Powercom USB UPS is not support

Hi, fellow NUT gurus;

 

I am having a big issue with our new Powercom Imperial Digital UPS. The
UPS is come with a serial over USB port and plug into the usb port on
the computer. I am having problem to setup our fedora 7 linux machine
talks to the ups.  The kernel 2.6.22.1 seems to be able to detect the
ups is plug into one of its usb port. But it just couldn't establish a
connection with the UPS. I have attached the screen dump below. Could
you please help...... 



The all ups configure files are being configure. We are running
nut-2.2.0 version and have tried to use the newhid-ups mgetech-usb
drivers. I think we need to modify the powercom driver with a usb
version such powercom-usb.

 

**** Kernel detected ups connected to one of its usb port *****

 

[root at tcm-file itsupport]# dmesg | grep hiddev96

hiddev96: USB HID v1.00 Device [POWERCOM CO., LTD. USB to Serial] on
usb-0000:00:1a.1-1

 

[root at tcm-file itsupport]# /sbin/lsusb

Bus 004 Device 001: ID 0000:0000

Bus 006 Device 001: ID 0000:0000

Bus 001 Device 001: ID 0000:0000

Bus 007 Device 001: ID 0000:0000

Bus 005 Device 001: ID 0000:0000

Bus 003 Device 001: ID 0000:0000

Bus 002 Device 004: ID 0d9f:0002 Powercom Co., Ltd

Bus 002 Device 001: ID 0000:0000

 

**** NUT-2.2.0 detected the PowerCom UPS but failure to establish a
connection with it****

 

[root at tcm-file itsupport]# /sbin/usbhid-ups -a myups -u root -x
vendorid=0d9f -x explore -D

Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30
(2.2.0-)

 

debug level is '4'

 

Trying to match device

Device does not match - skipping

Checking device (0D9F/0002) (002/004)

- VendorID: 0d9f

- ProductID: 0002

- Manufacturer: POWERCOM CO., LTD.

- Product: USB to Serial

- Serial Number: unknown

- Bus: 002

Trying to match device

Device matches

HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 25 00

i=0, extra[i]=09, extra[i+1]=21

HID descriptor, method 2: (9 bytes) => 09 21 00 01 00 01 22 25 00

HID descriptor retrieved (Reportlen = 37)

Report descriptor retrieved (Reportlen = 37)

Found HID device

Report Descriptor size = 37

Report Descriptor: (37 bytes) => 06 a0 ff 09 01 a1 01 09 01 15 00 26 ff
00

75 08 95 08 81 02 09 02 75 08 95 08 91 02 09 03 75 08 95 05 b1 02 c0

Detected a UPS: POWERCOM CO., LTD./USB to Serial

Using subdriver: EXPLORE HID 0.1

parsing ffa00001

parsing ffa00001

Path depth = 2

0: Usage(ffa00001)

1: Usage(ffa00001)

Can't find object ffa00001.ffa00001

Path: ffa00001.ffa00001, Type: Input, ReportID: 0x00, Offset: 0, Size: 8

parsing ffa00001

parsing ffa00002

Path depth = 2

0: Usage(ffa00001)

1: Usage(ffa00002)

Can't find object ffa00001.ffa00002

Path: ffa00001.ffa00002, Type: Output, ReportID: 0x00, Offset: 0, Size:
8

parsing ffa00001

parsing ffa00003

Path depth = 2

0: Usage(ffa00001)

1: Usage(ffa00003)

Entering libusb_get_report

Report[r]: (2 bytes) => 00 00

=>> Before exponent: 0, 0/0)

=>> After conversion: 0.000000 (0), 0/0)

Path: ffa00001.ffa00003, Type: Feature, ReportID: 0x00, Offset: 0, Size:
8, Value: 0.000000

upsdrv_updateinfo...

dstate_init: sock /var/run/nut/usbhid-ups-myups open on fd 6

upsdrv_updateinfo...

Waiting for notifications...

upsdrv_updateinfo...

Waiting for notifications...

upsdrv_updateinfo...

Waiting for notifications...

upsdrv_updateinfo...

Waiting for notifications...

 

Thanks for all for your help.

 

Paul

MCSE/MCSA/MCE

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20070903/2bf6c484/attachment.htm

I'm crossposting this to nut-upsdev, where this thread really belongs.
Please remove the nut-upsuser list from your reply, this doesn't belong
there.

Paul Wu wrote:
> I am having a big issue with our new Powercom Imperial Digital UPS. The
> UPS is come with a serial over USB port and plug into the usb port on
> the computer. I am having problem to setup our fedora 7 linux machine
> talks to the ups.  The kernel 2.6.22.1 seems to be able to detect the
> ups is plug into one of its usb port. But it just couldn?t establish a
> connection with the UPS. I have attached the screen dump below. Could
> you please help??
> 
> The all ups configure files are being configure. We are running
> nut-2.2.0 version and have tried to use the newhid-ups mgetech-usb
> drivers. I think we need to modify the powercom driver with a usb
> version such powercom-usb.
It surely looks like it.
> [root at tcm-file itsupport]# /sbin/usbhid-ups -a myups -u root -x
> vendorid=0d9f -x explore -D
> Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.2.0-)
> 
> debug level is '4'
> 
> Trying to match device
> Device does not match - skipping
> Checking device (0D9F/0002) (002/004)
> - VendorID: 0d9f
> - ProductID: 0002
> - Manufacturer: POWERCOM CO., LTD.
> - Product: USB to Serial
> - Serial Number: unknown
> - Bus: 002
> Trying to match device
> Device matches
> HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 25 00
> i=0, extra[i]=09, extra[i+1]=21
> HID descriptor, method 2: (9 bytes) => 09 21 00 01 00 01 22 25 00
> HID descriptor retrieved (Reportlen = 37)
> Report descriptor retrieved (Reportlen = 37)
> Found HID device
This is becoming a FAQ nowadays. :-)

A report descriptor of just 37 bytes is far to small for a HID Power
Device, so there is no chance that it will work with the usbhid-ups
driver. It maps exactly one Feature, Input, and Output report. You might
try your luck with linking powercom.c with megatec_usb.c in the same way
as megatec.c is linked with megatec_usb.c and see how you get along. As
a side note, megatec_usb.c should really be named serial_usb.c, since
the megatec protocol is dealt with in the megatec.c file.

Something like
> powercom_usb_SOURCES = powercom.c megatec_usb.c libusb.c
> powercom_usb_CFLAGS = $(AM_CFLAGS) $(LIBUSB_CFLAGS) -DMEGATEC_SUBDRV
> powercom_usb_LDADD = $(LDADD_DRIVERS) $(LIBUSB_LDFLAGS)
in Makefile.am. You'll need to run configure again and maybe you need to
make other changes to this file as well. Remember to specify '-x
vendorid=0d9f -x productid=0002' on the startup commandline for the
powercom_usb driver. Please let us know how you get along.

Best regards, Arjen