search for: timelimitexp

On Jan 11, 2015, at 11:48 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: >> 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, an...

.../usbhid-ups -a maxell -DD at a time >> when low battery is reported: > > hmm, are you sure 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,...

...h: 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.PowerSummary.PresentStatus.Charging, Type: Feature, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, Value: 0.000000 Path: UPS.PowerSummary....

...ively.) > output of /usr/local/libexec/nut/usbhid-ups -a maxell -DD at a time when low battery is reported: hmm, are you sure 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...

...ng for value =3D 0 > > > > hu_find_infoval: found !replacebatt (value: 0) > > > > process_status_info: !replacebatt > > entering string_to_path() > > Looking up UPS > > Looking up PowerSummary > > Looking up PresentStatus > > Looking up RemainingTimeLimitExpired > > Report : (8 bytes) =3D> 00 00 9C F3 00 03 10 D2 > > hu_find_infoval: searching for value =3D 0 > > > > hu_find_infoval: found !timelimitexp (value: 0) > > > > process_status_info: !timelimitexp > > entering string_to_path() > > Looking up U...

.../* ups is off */ #define STATUS_CAL 0x00800 /* calibration */ #define STATUS_OVERHEAT 0x01000 /* overheat; Belkin, TrippLite */ #define STATUS_COMMFAULT 0x02000 /* UPS fault; Belkin, TrippLite */ #define STATUS_DEPLETED 0x04000 /* battery depleted; Belkin */ #define STATUS_TIMELIMITEXP 0x08000 /* time limit expired; APC */ #define STATUS_BATTERYPRES 0x10000 /* battery present; APC */ #define STATUS_FULLYCHARGED 0x20000 /* battery full; CyberPower */ #define STATUS_AWAITINGPOWER 0x40000 /* awaiting power; Belkin, TrippLite */ #define STATUS_VRANGE 0x80000...

Hello Nutters, I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason described in the FAQ (but I'm not 100% sure). In the trace output I can see that

Arjen de Korte wrote: > > + * drivers/apc-hid.c: > + - Commented out the 'fullycharged' status. If anyone can explain the > + use of this, please step forward. This flag is defined on p.36 of the "Universal Serial Bus Usage Tables for HID Power Devices", Release 1.0 November 1, 1997, a USB standards document available on the web. The document defines this

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

...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.PowerSummary.PresentStatus.Charging, Type: Feature, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Feature, Value: 0.000000 Path: UPS.PowerSummary.Pres...

...; > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: > > Feature, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: > > Input, Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: > > Feature, Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.Pr...