search for: ff000001

...matches HID descriptor retrieved (Reportlen = 27) Report descriptor retrieved (Reportlen = 27) Found HID device Report Descriptor size = 27 Report Descriptor: (200 bytes) => 06 00 FF 09 01 A1 01 09 02 15 00 26 FF 00 75 08 Detected a UPS: OMRON/87XXUPS Using subdriver: GENERIC HID 0.1 Looking up ff000001 Looking up ff000002 entering string_to_path() parsing ff000001 Looking up ff000001 parsing ff000002 Looking up ff000002 Path depth = 2 0: UPage(ff00), Usage(1) 1: UPage(ff00), Usage(2) Can't find object ff000001.ff000002 Path: ff000001.ff000002, Type: Input Looking up ff000001 Looking up 000000...

...r retrieved (Reportlen = 27) Report descriptor retrieved (Reportlen = 27) Found HID device Report Descriptor size = 27 Report Descriptor: (200 bytes) => 06 00 FF 09 01 A1 01 09 02 15 00 26 FF 00 75 08 Detected a UPS: Cypress Semiconductor/USB to Serial Using subdriver: GENERIC HID 0.1 Looking up ff000001 Looking up ff000002 entering string_to_path() parsing ff000001 Looking up ff000001 parsing ff000002 Looking up ff000002 Path depth = 2 0: UPage(ff00), Usage(1) 1: UPage(ff00), Usage(2) Can't find object ff000001.ff000002 Path: ff000001.ff000002, Type: Input Looking up ff000001 Looking up 000000...

...Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x60, Offset: 0, Size: 24, Value: 3.9321e+06 0.345522 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x60, Offset: 0, Size: 24, Value: 3.9321e+06 0.346515 Can't retrieve Report b1: Broken pipe 0.346528 Path: ff000001.ff000001, Type: Output, ReportID: 0xb1, Offset: 0, Size: 248 0.347502 Can't retrieve Report b2: Broken pipe 0.347514 Path: ff000001.ff000001, Type: Input, ReportID: 0xb2, Offset: 0, Size: 248 0.348506 Can't retrieve Report 81: Broken pipe 0.348520 Path: ff000001.ff000001, Type:...

...h: 00850068 -> RunTimeToEmpty > 0.422253 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x > 60, Offset: 0, Size: 24, Value: 3.9321e+06 > 0.422264 Entering libusb_get_report > 0.423983 Can't retrieve Report b1: Broken pipe > 0.424034 hid_lookup_path: ff000001 -> not found in lookup table > 0.424060 hid_lookup_path: ff000001 -> not found in lookup table > 0.424076 Path: ff000001.ff000001, Type: Output, ReportID: 0xb1, Offset: 0 > , Size: 248 > 0.424089 Entering libusb_get_report > 0.425933 Can't retrieve Report b2: Br...

I?m a new user of NUT and the OpenUPS - in the past I?ve used APC hardware and apcupsd on Centos 6. I?ve built NUT 2.7.2 from source but used the OpenUPS HID driver v0.4 that?s in github. I?m using firmware version 1.5 on the openups which is the latest published version; I?ve also tried 1.7 which Mini-box sent to me but reverted to the published version. Their support seems a bit slow! I?ve got

...; 09 21 00 01 00 01 22 1b 00 HID descriptor length 27 Report Descriptor size = 27 Report Descriptor: (27 bytes) => 06 00 ff 09 01 a1 01 09 02 15 00 26 ff 00 75 08 95 08 81 82 09 02 95 08 91 82 c0 Using subdriver: EXPLORE HID 0.1 Entering libusb_get_report Report[get]: (2 bytes) => 01 00 Path: ff000001.ff000002, Type: Input, ReportID: 0x00, Offset: 0, Size: 8, Value: 0.000000 Report[buf]: (2 bytes) => 01 00 Path: ff000001.ff000002, Type: Output, ReportID: 0x00, Offset: 0, Size: 8, Value: 0.000000 Report descriptor retrieved (Reportlen = 27) Found HID device Detected a UPS: Cypress Semiconducto...

...les, and settings). The values for the usages are grouped in Reports, each with a one-byte ID. For instance, the UPS.PowerSummary.PresentStatus.* usages are all one bit long, and they are grouped in the 16-bit ReportID 0x40. Usually, the Usage IDs are unique. For whatever reason, they use the same ff000001.ff000001 ID for several reports, so I suspect that these reports are accessed directly by their Report ID, instead of looking up the HID Usage IDs to find a report ID. That may mean that there is another protocol to get report 0xB1, for instance - it might involve writing something to one of the o...

...; - Manufacturer: OMRON > - Product: USB UPS > - Serial Number: unknown > - Bus: 001 > Trying to match device > Device matches > HID descriptor length 27 > Report Descriptor size = 27 > Using subdriver: EXPLORE HID 0.1 > Can't retrieve Report 0: Broken pipe > Path: ff000001.ff000002, Type: Input, ReportID: 0x00, Offset: 0, Size: 8 > Can't retrieve Report 0: Broken pipe > Path: ff000001.ff000002, Type: Output, ReportID: 0x00, Offset: 0, Size: 8 > Report descriptor retrieved (Reportlen = 27) > =46ound HID device > Detected a UPS: OMRON/USB UPS > up...

...ettings). The values for the usages are grouped in Reports, each with a one-byte ID. For instance, the UPS.PowerSummary.PresentStatus.* usages are all one bit long, and they are grouped in the 16-bit ReportID 0x40. > > Usually, the Usage IDs are unique. For whatever reason, they use the same ff000001.ff000001 ID for several reports, so I suspect that these reports are accessed directly by their Report ID, instead of looking up the HID Usage IDs to find a report ID. > > That may mean that there is another protocol to get report 0xB1, for instance - it might involve writing something to on...

...09 02 15 00 26 ff 00 0.058887 75 08 95 08 81 82 09 02 95 08 91 82 c0 0.059102 Using subdriver: Liebert HID 0.3 0.059195 Entering libusb_get_report 0.060809 libusb_get_report: I/O error 0.060914 Can't retrieve Report 00: I/O error 0.060993 Path: ff000001.ff000002, Type: Input, ReportID: 0x00, Offset: 0, Size: 8 0.061057 Entering libusb_get_report 0.061850 libusb_get_report: I/O error 0.061954 Can't retrieve Report 00: I/O error 0.062024 Path: ff000001.ff000002, Type: Output, ReportID: 0x00, Offset: 0, Size: 8...

Charles, Did you get chance to look at the data I sent you, please? I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! Also from the trace I sent you, it appears that after the ?RunTimeToEmpty? query, the interface tries to

R version 2.7.0 RC (2008-04-20 r45403) When using semi-transparent filled plotting symbols, the border of the symbol has a different (darker) colour than the interior: plot(0, 0, pch=19, col="#FF000022") (Saving this as a PDF and looking at it magnified may make it easier to see.) This is pretty annoying, since when plotting partially overlapping points, the border colour dominates,

Charles, Thanks again for your help, and sorry I didn?t :cc - noted for the future! I?m suspicious that the OpenUPS doesn?t behave properly in a number of ways, of which the USB traffic is the one of immediate concern. It seems to me that NUT can read from it but probably not write to it: and the OpenUPS doesn?t flag ?low battery? conditions correctly either. It does shut itself down at a

...ff 09 01 a1 01 09 02 15 > 00 26 ff 00 > 0.058887 75 08 95 08 81 82 09 02 95 08 91 82 c0 > 0.059102 Using subdriver: Liebert HID 0.3 > 0.059195 Entering libusb_get_report > 0.060809 libusb_get_report: I/O error > 0.060914 Can't retrieve Report 00: I/O error > 0.060993 Path: ff000001.ff000002, Type: Input, ReportID: 0x00, Offset: > 0, Size: 8 > 0.061057 Entering libusb_get_report > 0.061850 libusb_get_report: I/O error > 0.061954 Can't retrieve Report 00: I/O error > 0.062024 Path: ff000001.ff000002, Type: Output, ReportID: 0x00, Offset: > 0, Size: 8 >...