search for: ffa00003

...089, value=0}) = -1 EINVAL (Invalid argument) 653 ioctl(3, HIDIOCGUSAGE, {report_type=3, report_id=ffffffff, field_index=0, usage_index=0, usage_code=8400ff, value=0}) = -1 EINVAL (Invalid argument) 653 ioctl(3, HIDIOCSUSAGE, {report_type=3, report_id=0, field_index=0, usage_index=0, usage_code=ffa00003, value=95}) = 0 653 ioctl(3, HIDIOCSREPORT, {report_type=3,report_id=0,num_fields=0}) = 0 653 ioctl(3, HIDIOCSUSAGE, {report_type=3, report_id=0, field_index=0, usage_index=1, usage_code=ffa00003, value=4}) = 0 653 ioctl(3, HIDIOCSREPORT, {report_type=3,report_id=0,num_fields=0}) = 0 653 io...

...a00001.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 ups...

...a00001.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 ups...

...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 0.454462 Report descriptor retrieved (Reportlen = 37) 0.454818 Found HID device 0.454943 Detected a UPS: POWERCOM CO., LTD./USB to Serial 0.456645 find_nut_info: unknown info type: load.off.delay 0.457544 find_nut_info: unk...

...//openbsd.7691.n7.nabble.com/general-question-about-usb-stack-and-ups-td234700.html it looks like there are just two 8-byte reports, one to the UPS (Type: Output), and one back to the PC. 0.040766 hid_lookup_path: ffa00001 -> not found in lookup table 0.040781 hid_lookup_path: ffa00003 -> not found in lookup table 0.040796 Path: ffa00001.ffa00003, Type: Input, ReportID: 0x00, Offset: 0, Size: 8 0.040810 Entering libusb_get_report 0.041661 libusb_get_report: Input/output error 0.041697 Can't retrieve Report 00: Input/output error 0.0...

...21 11 01 00 01 22 20 00 HID descriptor length 32 Report Descriptor size = 32 Report Descriptor: (32 bytes) => 06 a0 ff 09 01 a1 01 09 03 15 00 25 01 75 08 95 08 81 02 09 04 15 00 25 01 75 08 95 08 91 02 c0 Using subdriver: EXPLORE HID 0.1 Can't retrieve Report 0: Broken pipe Path: ffa00001.ffa00003, Type: Input, ReportID: 0x00, Offset: 0, Size: 8 Can't retrieve Report 0: Broken pipe Path: ffa00001.ffa00004, Type: Output, ReportID: 0x00, Offset: 0, Size: 8 Report descriptor retrieved (Reportlen = 32) Found HID device Detected a UPS: ATCL FOR UPS/ATCL FOR UPS upsdrv_initinfo... upsdrv_updat...

Hi, I just bought a cheap UPS and apparently I'm hitting the same issue that's described here: http://comments.gmane.org/gmane.comp.monitoring.nut.user/6146 Mine is a different brand: "Kanji" which appears to be the argentinian dealler for some generic chinese manufacturer. My model is also 800VA and identified in the same way, so maybe is the same UPS under a different brand:

...river: 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...

...>> 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 > gen...

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070205/5ad69acc/attachment.pgp