search for: 00840004

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

...nstant commands: beeper.toggle - Toggle the UPS beeper -- not working test.battery.start.quick - Start a quick battery test -- works ok. No load and shutdown commands. Trying svn trunk version, with the same results. Debug output shows the problem: 0.035558 hid_lookup_path: 00840004 -> UPS 0.035569 hid_lookup_path: 00840024 -> PowerSummary 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_pat...

...of free memory > and swap. I stopped many daemons, and the problem persisted. > > I tried stracing /lib/nut/newhidups: > > write(2, "Path: UPS.Battery.ff86001b, Type"..., 59) = 59 > write(2, "entering path_to_string()\n", 26) = 26 > write(2, "Looking up 00840004\n", 20) = 20 > write(2, "Looking 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\...

...ID descriptor retrieved (Reportlen = 358) Report descriptor retrieved (Reportlen = 358) Found HID device 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...

...ed 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, LogMin = 1 0.6...

I have a new-ish APC Back-UPS XS 1500G connected via USB. It's giving me a "ups.alarm: No battery installed!" error. I also installed and configured apcupsd to give that a try and it's giving me the same error. I suspect this is a driver problem because while NUT claims the battery isn't plugged in, it's giving me battery runtime/charge info. Both can't be valid

...do a "zgrep" on previous logs to find similarities. If logs come in as Zip files, or inline, it certainly isn't the end of the world, but it lengthens the search. </soapbox> This seems to be the source of the "no battery" alarm: > 0.571436 hid_lookup_path: 00840004 -> UPS > 0.571438 hid_lookup_path: 00840024 -> PowerSummary > 0.571440 hid_lookup_path: 00840002 -> PresentStatus > 0.571443 hid_lookup_path: 008500d1 -> BatteryPresent > 0.571446 Path: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Inpu...

...messages : > > 0.419974 Entering libusb_get_report > 0.421967 Report[get]: (4 bytes) => 60 c4 ff 3b > 0.422056 PhyMax = 0, PhyMin = 0, LogMax = 16777215, LogMin = 0 > 0.422069 Unit = 00001001, UnitExp = 0 > 0.422080 Exponent = 0 > 0.422093 hid_lookup_path: 00840004 -> UPS > 0.422107 hid_lookup_path: 00840024 -> PowerSummary > 0.422121 hid_lookup_path: 00850068 -> RunTimeToEmpty > 0.422146 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: > 0x60, Offset: 0, Size: 24, Value: 3.9321e+06 That looks like a calibration...

....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 = 0 > 0.279240 U...

....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 = 0 > 0.279240 U...

...d 840016 12.207397 parsing Output 12.207408 Looking up Output 12.207411 hid_lookup_usage: found 84001c 12.207414 parsing Voltage 12.207416 Looking up Voltage 12.207419 hid_lookup_usage: found 840030 12.207422 Path depth = 4 12.207425 0: Usage(00840004) 12.207427 1: Usage(00840016) 12.207430 2: Usage(0084001c) 12.207433 3: Usage(00840030) 12.207438 entering shut_get_report(id: 12, len: 1800) 12.207441 entering shut_packet_send (8) 12.207444 shut_checksum = a9 12.207449 sent: (11 bytes) => 81...

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

...e not reporting the presence of such a battery: > >???? 0.428188??? Report[buf]: (2 bytes) => 0c 05 >???? 0.428215??? PhyMax = 0, PhyMin = 0, LogMax = 1, LogMin = 0 >???? 0.428240??? Unit = 00000000, UnitExp = 0 >???? 0.428264??? Exponent = 0 >???? 0.428290??? hid_lookup_path: 00840004 -> UPS >???? 0.428316??? hid_lookup_path: 00840024 -> PowerSummary >???? 0.428344??? hid_lookup_path: 008500d1 -> BatteryPresent >???? 0.428373??? Path: UPS.PowerSummary.BatteryPresent, Type: Input, ReportID: 0x0c, Offset: 4, Size: 1, Value: 0 > Yes the presence of the batter...

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

...ummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x02, Offset: 8, Size: 8, Value: 0 32.407367 hu_find_infoval: found !replacebatt (value: 0) 32.407369 process_boolean_info: !replacebatt There is also this LCM (Life Cycle Monitoring) part: 22.677035 hid_lookup_path: 00840004 -> UPS 22.677037 hid_lookup_path: ffff0018 -> LCMSystem 22.677039 hid_lookup_path: ffff001a -> LCMAlarm 22.677045 hid_lookup_path: 00ff0001 -> not found in lookup table 22.677049 hid_lookup_path: 00840002 -> PresentStatus 22.677052 hid_lookup_path: ffff0...

...[D4] Entering libusb_get_report 0.549533 [D3] Report[get]: (3 bytes) => 1a 02 15 0.549550 [D5] PhyMax = 0, PhyMin = 0, LogMax = 9216, LogMin = 2304 0.549561 [D5] Unit = 00000000, UnitExp = 0 0.549569 [D5] Exponent = 0 0.549576 [D5] hid_lookup_path: 00840004 -> UPS 0.549583 [D5] hid_lookup_path: 00840012 -> Battery 0.549591 [D5] hid_lookup_path: 00840030 -> Voltage 0.549603 [D1] Path: UPS.Battery.Voltage, Type: Feature, ReportID: 0x1a, Offset: 0, Size: 16, Value: 5378 Suggest me, please, how I can interpret the batt...

Hi On 10/03/2014 03:42 PM, Charles Lepple wrote:> On Oct 3, 2014, at 7:50 AM, paul.chavent at fnac.net wrote: > > > This is what I was referring to (from the belkin-hid log): > >???? 1.325782??? Report[buf]: (5 bytes) => 05 53 00 48 00 >???? 1.325799??? Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x05, Offset: 16, Size: 16, Value: 0 >????

On 28 May 2014, at 21:59, Charles Lepple <clepple at gmail.com> wrote: >> What would log it? > > The driver. OK. >> I could try running the driver with debugging and see if that shows anything of interest. > > That should help. Unfortunately for non-debug operation, it appears that most of the usbhid-ups instcmd messages are buried at debug level 3 or 5. That

I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu drivers

Hi all, After some research I've found that this device should run with the blazer_usb driver. Jun 3 16:15:38 pegasus kernel: ugen0.4: <vendor 0x0001> at usbus0 Jun 3 16:15:38 pegasus kernel: uhid0: <vendor 0x0001 product 0x0000, class 0/0, rev 1.00/1.00, addr 4> on usbus0 However, even after shoehorning it; [crees at pegasus]/usr/local/libexec/nut% sudo ./blazer_usb -a zigor