search for: belowremainingcapacitylimit

...? > > The file drivers/usbhid-ups.c is looking for any of the following > conditions to declare LB: > > ? STATUS(LOWBATT) > ? STATUS(TIMELIMITEXP) > ? STATUS(SHUTDOWNIMM) > > The mapping to HID Path names will depend on the model, but > STATUS(LOWBATT) can come from ...BelowRemainingCapacityLimit, which is > 0 in both instances in your log. STATUS(TIMELIMITEXP) maps to > ...RemainingTimeLimitExpired, which I don't see, and > STATUS(SHUTDOWNIMM) would cause an ups.alarm message to show up in upsc. > Thanks very much for replying, Charles. I've done a bit more investigat...

...that this log matches the time of the LB event? The file drivers/usbhid-ups.c is looking for any of the following conditions to declare LB: ? STATUS(LOWBATT) ? STATUS(TIMELIMITEXP) ? STATUS(SHUTDOWNIMM) The mapping to HID Path names will depend on the model, but STATUS(LOWBATT) can come from ...BelowRemainingCapacityLimit, which is 0 in both instances in your log. STATUS(TIMELIMITEXP) maps to ...RemainingTimeLimitExpired, which I don't see, and STATUS(SHUTDOWNIMM) would cause an ups.alarm message to show up in upsc. -- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachmen...

...UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x07, Offset: 1, Size: 1, Value: 0 163.221614 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x07, Offset: 0, Size: 1, Value: 0 163.221643 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 165.108555 upsdrv_updateinfo... 165.231693 Got 1 HID objects... 165.231811 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x0d, Offset: 0, Size: 16, Value: 142 165.231841 Quick up...

...143052 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 3, Size: 1, Value: 0 0.143200 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x32, Offset: 4, Size: 1, Value: 0 0.143346 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x32, Offset: 5, Size: 1, Value: 0 0.143492 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x32, Offset: 6, Size: 1, Value: 1 0.143636 Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Input, ReportID: 0x32, Offset: 7, Size:...

Peter, Apparently, some Belkin UPSes still have problems with this. When we receive this report through the interrupt pipeline it is ignored (the special case in usbhid-ups.c) and even after that it looks like there are still some problems with it: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html Wouldn't it be an option to just to ignore this completely and

...8, Value: 1 5.777970 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x01, Offset: 0, Size: 1, Value: 1 5.777987 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x01, Offset: 0, Size: 1, Value: 1 5.777997 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x01, Offset: 1, Size: 1, Value: 0 5.778006 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x01, Offset: 1, Size: 1, Value: 0 5.778014 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x01, Offset: 2, S...

...: 1, Value: 1 0.039344 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0 0.039448 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0b, Offset: 2, Size: 1, Value: 0 0.039554 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0b, Offset: 3, Size: 1, Value: 0 0.039658 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x0b, Offset: 4, Size: 1, Value: 1 0.039763 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0b, Offset: 5, Siz...

...0.132770 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0 0.132774 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0b, Offset: 2, Size: 1, Value: 0 0.132778 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0b, Offset: 3, Size: 1, Value: 0 0.132782 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x0b, Offset: 4, Size: 1, Value: 1 0.132786 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0b, Of...

...re, ReportID: 0x12, Offset: 0, Size: 8, Value: 1 0.621398 Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 0.621499 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 0.626402 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 0.626439 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 0.626450 Path: UPS.PowerSummary.ShutdownImminent, Type: Input, ReportID: 0x14, Offset: 8, Size: 8, Value: 0...

Oops... changing that to --with-user=nut solved one problem. I have the driver, upsd and upsmon running now. Thank you! Now I'm back to another issue, every 2 seconds I get in the logs: May 3 13:45:23 myhost upsd[2587]: Connected to UPS [eaton]: usbhid-ups-eaton It seems happy to do this forever. On Tue, May 3, 2016 at 8:17 AM, Charles Lepple <clepple at gmail.com> wrote: > On

...procedure anyway. It might be useful for logging remote UPS'es, so it might be worth logging by 'upslog', that's why I didn't outright remove it. In a normal situation, NUT won't wait until ShutdownImminent is signaled, rather it will initiate a shutdown sequence as soon as BelowRemainingCapacityLimit or RemainingTimeLimitExpired is set. As soon as we have found that (and we have OB LB), it is irrelevant what the UPS sends, since there is no way to stop (or speedup) a shutdown sequence from that moment on. > Other cases are handled by > the hardware through the BYPASS (overload), the RB (...

...tus.Discharging Path: UPS.PowerSummary.PresentStatus.Discharging Path: UPS.PowerSummary.PresentStatus.ACPresent Path: UPS.PowerSummary.PresentStatus.ACPresent Path: UPS.PowerSummary.PresentStatus.BatteryPresent Path: UPS.PowerSummary.PresentStatus.BatteryPresent Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit Path: UPS.PowerSummary.PresentStatus.ShutdownImminent Path: UPS.PowerSummary.PresentStatus.ShutdownImminent Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired...

...2, Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, ReportID: 0x16, Offset: 1, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x16, Offset: 0, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x16, Offset: 4, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.Charging, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 0.000000 Path: UPS.PowerSummary.Discharging, Type: Feature, ReportID: 0x06, Offset: 8, Size: 8, Value: 0.000000 Path: UPS.PowerSummary...

...pe: Feature, Value: 20.900000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value: 1.000000 Path: UPS.Pow...

...7865 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 3, Size: 1, Value: 0 0.147867 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x32, Offset: 4, Size: 1, Value: 0 0.147869 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x32, Offset: 5, Size: 1, Value: 0 0.147872 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x32, Offset: 6, Size: 1, Value: 1 0.147874 Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Input, ReportID: 0x32, Offset: 7, Si...

...x12, Offset: 0, Size: 8, Value: 1 > 0.050153 Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 > 0.050693 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 > 0.051529 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 > 0.051760 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 > 0.052150 Path: UPS.PowerSummary.ShutdownImminent, Type: Input, ReportID: 0x14, Offset: 8, Size: 8,...

...ype: Feature, Value: 21.200001 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, Value: 1.000000 Path: UPS.PowerSu...

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

...0.263059 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0 0.263067 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x0b, Offset: 2, Size: 1, Value: 0 0.263075 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0b, Offset: 3, Size: 1, Value: 0 0.263082 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x0b, Offset: 4, Size: 1, Value: 1 0.263090 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0b, Offs...

...et: 0, Size: 8, Value: 1 >> 0.050153 Path: UPS.PowerSummary.ACPresent, Type: Input, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 >> 0.050693 Path: UPS.PowerSummary.ACPresent, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 1 >> 0.051529 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 >> 0.051760 Path: UPS.PowerSummary.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 0 >> 0.052150 Path: UPS.PowerSummary.ShutdownImminent, Type: Input, ReportID: 0x14, Offset: 8, Siz...