search for: hid_lookup_usage

...; Before exponent: 0, 0/0) =>> After conversion: 0.000000 (0), 0/0) Report : (8 bytes) => 02 00 E8 03 00 00 00 00 hu_find_infoval: searching for value = 0 hu_find_infoval: found !shutdownimm (value: 0) process_status_info: !shutdownimm entering string_to_path() parsing UPS Looking up UPS hid_lookup_usage: found 840004 parsing PowerSummary Looking up PowerSummary hid_lookup_usage: found 840024 parsing PresentStatus Looking up PresentStatus hid_lookup_usage: found 840002 parsing BelowRemainingCapacityLimit Looking up BelowRemainingCapacityLimit hid_lookup_usage: found 850042 Path depth = 4 0: UPage(8...

...0.035580 hid_lookup_path: 00ff0057 -> not found in lookup table ..skip.. 0.036073 hid_lookup_path: 00840004 -> UPS 0.036084 hid_lookup_path: 00840024 -> PowerSummary 0.036095 hid_lookup_path: 00ff0056 -> not found in lookup table ..skip.. 0.054472 hid_lookup_usage: UPS -> 00840004 0.054476 hid_lookup_usage: PowerSummary -> 00840024 0.054480 hid_lookup_usage: DelayBeforeStartup -> 00840056 0.054488 string_to_path: depth = 3 0.054494 hid_lookup_usage: UPS -> 00840004 0.054499 hid_lookup_usage: PowerSummary -> 0...

...runtime.low --> LB reported by NUT, UPS beeper indicates LB. The lowbatt option changes the value in upsc, but otherwise doesn't do anything, I saw it get reset back to 10 after running upscmd. So I guess it would be best to use ignorelb and override.<variable>? --- 0.624002 hid_lookup_usage: UPS -> 00840004 0.624002 hid_lookup_usage: PowerSummary -> 00840024 0.624002 hid_lookup_usage: RemainingCapacityLimit -> 00850029 0.624002 string_to_path: depth = 3 0.624002 Report[buf]: (2 bytes) => 11 0a 0.624002 PhyMax = 0, PhyMin = 0, LogMax = 100...

...Report Descriptor size = 358 Report Descriptor: (200 bytes) => 05 84 09 04 A1 00 09 16 A1 00 09 17 85 0B 75 0 8 Detected a UPS: unknown/unknown Using subdriver: MGE HID 0.8 Looking up 00840004 Looking up 00840016 Looking up 00840017 entering string_to_path() parsing UPS Looking up UPS hid_lookup_usage: found 840004 parsing PowerConverter Looking up PowerConverter hid_lookup_usage: found 840016 parsing PowerConverterID Looking up PowerConverterID hid_lookup_usage: found 840017 Path depth = 3 0: UPage(84), Usage(4) 1: UPage(84), Usage(16) 2: UPage(84), Usage(17) Entering libusb_get_repo...

...g > 0.278176 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, > Offset: 0, Size: 16, Value: 2.201e-05 > 0.278274 Input/OutputVoltage = 2.201e-05 -> assuming correction factor > = 1e+07 > 0.278384 send_to_all: SETINFO input.voltage "220.1" > 0.278517 hid_lookup_usage: UPS -> 00840004 > 0.278621 hid_lookup_usage: Output -> 0084001c > 0.278769 hid_lookup_usage: Voltage -> 00840030 > 0.278913 string_to_path: depth = 3 > 0.279025 Report[buf]: (3 bytes) => 2b 9e 08 > 0.279133 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin =...

...g > 0.278176 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x20, > Offset: 0, Size: 16, Value: 2.201e-05 > 0.278274 Input/OutputVoltage = 2.201e-05 -> assuming correction factor > = 1e+07 > 0.278384 send_to_all: SETINFO input.voltage "220.1" > 0.278517 hid_lookup_usage: UPS -> 00840004 > 0.278621 hid_lookup_usage: Output -> 0084001c > 0.278769 hid_lookup_usage: Voltage -> 00840030 > 0.278913 string_to_path: depth = 3 > 0.279025 Report[buf]: (3 bytes) => 2b 9e 08 > 0.279133 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin =...

...ing up 00840012\n", 20) = 20 > write(2, "Looking up ff860016\n", 20) = 20 > write(2, "entering string_to_path()\n", 26) = 26 > write(2, "parsing UPS\n", 12) = 12 > write(2, "Looking up UPS\n", 15) = 15 > write(2, "hid_lookup_usage: found 840004\n", 31) = 31 > write(2, "parsing Battery\n", 16) = 16 > write(2, "Looking up Battery\n", 19) = 19 > write(2, "hid_lookup_usage: found 840012\n", 31) = 31 > write(2, "parsing APCBattReplaceDate\n", 27) = 27 > write(2,...

...e, Neil. Extract from mge-shut -DDDDDDD ------------------------------ 12.207366 entering hid_get_value(UPS.PowerConverter.Output.Voltage) 12.207371 entering lookup_path(UPS.PowerConverter.Output.Voltage) 12.207375 parsing UPS 12.207384 Looking up UPS 12.207387 hid_lookup_usage: found 840004 12.207389 parsing PowerConverter 12.207392 Looking up PowerConverter 12.207395 hid_lookup_usage: found 840016 12.207397 parsing Output 12.207408 Looking up Output 12.207411 hid_lookup_usage: found 84001c 12.207414 parsing Voltage 12....

...Size); memcpy(raw_buf, p_raw_buf_test, ReportSize); return rc; } else return 0; } From this I now get Detected a UPS: UIS Ablerex/Ablerex USB Interface 049e Using subdriver: EXPLORE HID 0.1 parsing 00860004 parsing Flow hid_lookup_usage: found 84001e parsing FlowID hid_lookup_usage: found 84001f Path depth = 3, Path: 00860004.Flow.FlowID, Node1/2/3:, 860004, 84001e, 84001f 0: Usage(00860004) 1: Usage(0084001e) 2: Usage(0084001f) Buffer is stale. refreshing Noting in the buffer for rbuf->data[0] Noting in the buffer for rbuf-&gt...

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

Hi, Is there any further information on this UPS interface? I have an Upsonic UPS that is reporting the same interface, but I cannot make it work or get any sensible information from it. Thanks Jon --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000706-2, 25/01/2007 Tested on: 26/01/2007 11:00:14 AM avast! is copyright (c) 2000-2007 ALWIL Software.

...eems to call libusb and get invalid responses. I notice in > the latest output that the length of the data and the length being > requested seem different (I put a couple of extra debugging statements in). > > Using subdriver: EXPLORE HID 0.1 > parsing 00860004 > parsing Flow > hid_lookup_usage: found 84001e > parsing FlowID > hid_lookup_usage: found 84001f > Path depth = 3 > 0: Usage(00860004) > 1: Usage(0084001e) > 2: Usage(0084001f) > Entering libusb_get_report. ReportSize: 13 > typesafe_control_msg: size: 13 > Can't retrieve Report 1 (75): Value too larg...

Hi Folks, I just bought two APC UPSes, an EX 1300 and an ES 550 for two different sites and installed NUT for the first time on two machines (one Centos 4.1, the other Ubuntu 7.04). So far I'm well impressed -- excellent work by the dev team! The EX 1300 is working beautifully with NUT on the Centos box, but I'm having a bit of a problem with the ES 550: even while loaded, the ups.load

...warning: pointer targets in return differ in signedness libhid.c: In function 'HIDGetEvents': libhid.c:368: warning: implicit declaration of function 'malloc' libhid.c:368: warning: incompatible implicit declaration of built-in function 'malloc' libhid.c: In function 'hid_lookup_usage': libhid.c:715: warning: implicit declaration of function 'atoi' make[1]: *** [libhid.o] Error 1 gcc -I../include -O -Wall -Wsign-compare -c energizerups.c energizerups.c:24:23: error: asm/types.h: No such file or directory energizerups.c:31:26: error: linux/hiddev.h: No such file or di...

...ke up (it could not even be killed with "kill -KILL"). I had to reboot each time to be able to attach another driver. I commented out this call, which seems to be useless anyway. 4) nut-cvs-patch-NUMPATH-2005-08-24 ---------------------------------------- This patch extends the function hid_lookup_usage() so that path names can also be looked up by numerical values. This is just a convenience - it allows one to put stuff like "UPS.PowerConverter.ff860024" in the apc-hid.h while testing device variables whose purpose is yet unknown. 5) nut-cvs-patch-DEP-2005-08-24 -----------------------...