search for: remainingtimelimitexpired

...gt; ? 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 investigating. I added a diagnostic printf("%x", ups_status) at the point where LB is set....

...> ? 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 investigating. I added a diagnostic printf("%x", ups_status) at the point where LB is set. It shows that it'...

...seful 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 (replace battery or > inter...

...", 0, 1, "UPS.PowerSummary.PresentStatus.ShutdownImminent", NULL, "%.0f", HU_FLAG_OK, &shutdownimm_info[0] }, + /* The following two are returned with long notification from Back-UPS ES 650 */ + { "ups.status", 0, 1, "UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired", NULL, + "%.0f", HU_FLAG_OK, NULL }, + { "ups.status", 0, 1, "UPS.PowerSummary.PresentStatus.BatteryPresent", NULL, + "%.0f", HU_FLAG_OK, NULL }, /* Input page */ { "input.voltage", 0, 0, "UPS.Input.Voltage", NULL, &qu...

...with the variables, although the current change doesn't affect > status evaluation in any way either. Rather than using a NULL item mapping I am now using the hex_conversion mapping to accept the two items: UPS.PowerSummary.PresentStatus.BatteryPresent and UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired that are however still ignored, as it happened with the 2.0.2 changes. If the experts think it would be worthwhile to actually make the two items available (although they are not particularly useful), please let me know how they might be mapped, and I will add and test such a mapping. Here fol...

...he 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 attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20150109/...

...entStatus.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 Path: UPS.PowerSummary.PresentStatus.NeedReplacement Path: UPS.PowerSummary.PresentStatus.NeedReplacement Path: UPS.PowerSummary.PresentStatus.OverLoad Path: UPS.PowerSummary.PresentStatus.OverLoad Path: UPS.PowerSummary.PresentStatus.0...

...39554 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, Size: 1, Value: 0 0.039870 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 1, Value: 1 0.039970 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0...

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

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

...entStatus.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 Path: UPS.PowerSummary.PresentStatus.NeedReplacement Path: UPS.PowerSummary.PresentStatus.NeedReplacement Path: UPS.PowerSummary.PresentStatus.OverLoad Path: UPS.PowerSummary.PresentStatus.OverLoad Path: UPS.PowerSummary.PresentStatus.0...

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

...PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0a, Offset: 4, Size: 1, Value: 0 0.130620 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x0a, Offset: 4, Size: 1, Value: 0 0.130625 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0a, Offset: 5, Size: 1, Value: 0 0.130630 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x0a, Offset: 5, Size: 1, Value: 0 0.130634 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0...

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

...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, Offset: 5, Size: 1, Value: 0 0.132790 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 1, Value: 1 0.132795 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x0b, Offset: 1, Size: 1,...

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

...29778 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x0b, Offset: 3, Size: 1, Value: 0 0.029815 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x0b, Offset: 4, Size: 1, Value: 1 0.029850 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x0b, Offset: 5, Size: 1, Value: 0 0.029886 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 1, Value: 1 0.029921 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x0b, Offset: 1, Size: 1, Value: 0...

...h: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x16, Offset: 5, Size: 1, Value: 0 > 0.059435 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x16, Offset: 5, Size: 1, Value: 0 > 0.059909 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x16, Offset: 6, Size: 1, Value: 0 > 0.060331 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x16, Offset: 6, Size: 1, Value: 0 > 0.060733 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, ReportID:...

...: 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, Offset: 5, Size: 1, Value: 0 0.263098 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature, ReportID: 0x0b, Offset: 0, Size: 1, Value: 1 0.263105 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Feature, ReportID: 0x0b, Offset: 1, Size: 1,...

....PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x16, Offset: 5, Size: 1, Value: 0 >> 0.059435 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x16, Offset: 5, Size: 1, Value: 0 >> 0.059909 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x16, Offset: 6, Size: 1, Value: 0 >> 0.060331 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Feature, ReportID: 0x16, Offset: 6, Size: 1, Value: 0 >> 0.060733 Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, Rep...