[Nut-upsuser] New powercom device?

Charles Lepple clepple at gmail.com
Tue Aug 15 13:13:12 UTC 2017


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 )


More information about the Nut-upsuser mailing list