On 8/15/2017 6:13 AM, Charles Lepple wrote: > On Aug 10, 2017, at 12:19 AM, Harlan Stenn wrote: >> >> 0.447497 HID descriptor length 37 >> 0.450449 Report Descriptor size = 37 >> 0.451062 Using subdriver: PowerCOM HID 0.5 >> 0.451996 3 HID objects found >> 0.453502 Path: ffa00001.ffa00001, Type: Input, ReportID: 0x00, >> Offset: 0, Size: 8, Value: 0 >> 0.453677 Path: ffa00001.ffa00002, Type: Output, ReportID: 0x00, >> Offset: 0, Size: 8, Value: 0 >> 0.454070 Path: ffa00001.ffa00003, Type: Feature, ReportID: 0x00, >> Offset: 0, Size: 8, Value: 0 > > Unfortunately, this won't be able to be supported by the usbhid-ups > driver - it looks like they are using USB HID to emulate a serial > port. (A true USB HID Power Device Class report descriptor is > generally several hundred bytes long, versus the 37 shown here). > > Is it possible that you just need to load the usbserial kernel > module, and bind it to the UPS' 0d9f:0002 ID? Then the /dev/ttyUSB* > port can be passed to the "powercom" driver. (This is suggested by > http://networkupstools.org/stable-hcl.html?manufacturer=Powercom&connection=USB > )
OK, thanks! I read up about the stuff in the last paragraph, and it's not clear to me what I need to do to test this out. % ls /lib/modules/`uname r`/kernel/drivers/usb/serial/ ch341.ko cp210x.ko ftdi_sio.ko % lsusb Bus 004 Device 003: ID 0d9f:0002 Powercom Co., Ltd Black Knight PRO / WOW Uninterruptible Power Supply (Cypress HID->COM RS232) Bus 004 Device 001: ... root hub ... % The debian docs say: Look at the output of lsusb, and if it identifies the serial device, try installing the appropriate driver using modprobe. Then tell it about the new nyumber using "echo VENDOR PRODUCT >/sys/bus/usb-serial/drivers/DRIVER" So any pointers on what I should do next would be appreciated. H _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
