search for: remainingtimelimit

...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 i...

...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. H...

...erSummary.RemainingCapacity, Type: Input, Value: 120.000000 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: 120.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, Value: 240.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 240.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: 300.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: 300.000000 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000 Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 21.200001 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Inp...

...ery.charge.low "10" 0.624002 send_to_all: SETFLAGS battery.charge.low RW STRING 0.624002 send_to_all: SETAUX battery.charge.low 10 0.624002 hid_lookup_usage: UPS -> 00840004 0.624002 hid_lookup_usage: Battery -> 00840012 0.624002 hid_lookup_usage: RemainingTimeLimit -> 0085002a 0.624002 string_to_path: depth = 3 0.624002 Report[buf]: (3 bytes) => 24 78 00 0.624002 PhyMax = 0, PhyMin = 0, LogMax = 65535, LogMin = 0 0.624002 Unit = 00001001, UnitExp = 0 0.624002 Exponent = 0 0.624002 Path: UPS.Battery.RemainingTime...

...that the UPS is not reporting the same value to NUT. Note that there are two different HID strings that map to battery.runtime.low: https://github.com/networkupstools/nut/blob/master/drivers/apc-hid.c#L309 I think that means that NUT will pick the first one that works (between "UPS.Battery.RemainingTimeLimit" and "UPS.PowerSummary.RemainingTimeLimit"), but there certainly have been discrepancies between the spec and what gets implemented. If you want, we can take a look at the debug output of the driver. Not sure how that works in the NAS, but it involves killing the usbhid-ups process,...

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

...uot;UPS.PowerSummary.WarningCapacityLimit", NULL, "%.0f", HU_FLAG_OK, NULL }, /* Read only */ { "battery.runtime", 0, 0, "UPS.PowerSummary.RunTimeToEmpty", NULL, "%.0f", HU_FLAG_OK, NULL }, - { "battery.runtime.low", 0, 0, "UPS.Battery.RemainingTimeLimit", NULL, "%.0f", HU_FLAG_OK, NULL }, + /* the following is writeable for the Back-UPS ES 650 */ + { "battery.runtime.low", ST_FLAG_RW | ST_FLAG_STRING, 5, "UPS.PowerSummary.RemainingTimeLimit", NULL, + "%.0f", HU_FLAG_OK | HU_FLAG_SEMI_STATIC, NULL }...

...erSummary.WarningCapacityLimit Path: UPS.PowerSummary.RemainingCapacityLimit Path: UPS.PowerSummary.ManufacturerDate Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.RunTimeToEmpty Path: UPS.PowerSummary.DelayBeforeShutdown Path: UPS.PowerSummary.DelayBeforeReboot Path: UPS.PowerSummary.RemainingTimeLimit Path: UPS.PowerSummary.RemainingTimeLimit Path: UPS.PowerSummary.ConfigVoltage Path: UPS.PowerSummary.Voltage Path: UPS.PowerSummary.AudibleAlarmControl ... This seems to indicate that I have the configuration files correct, but when I try to start but I get the following in the logs: Oct 4 08:4...

...Summary.RemainingCapacity, Type: Input, Value: 100.000000 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: 100.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, Value: 5722.000000 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, Value: 5722.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: 300.000000 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: 300.000000 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000 Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 20.900000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Inp...

On Mon, Mar 7, 2016 at 9:00 PM, Charles Lepple <clepple at gmail.com> wrote: > If you stop and start the driver, it should refresh. Hi Charles, thanks for the reply! Pardon the dead horse beating, but I just want to clarify/confirm two things: 1) I did my full power down test (including powering down UPS and NAS, and restarting them) after the change to 600s on the UPS. Shouldn't

...> ? 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...

...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.PresentS...

...owerSummary.RunTimeToEmpty, Type: Feature, Value: > > 900.000000 > > Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, Value: > > -1.000000 > > Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, Value: > > 16777215.000000 > > Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, Value: > > 120.000000 > > Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, Value: > > 120.000000 > > Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: > > 24.000002 > > Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 27.670...

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

...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.PresentS...

...", 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", NU...

...0, Size: 8, Value: 100 0.132443 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x08, Offset: 8, Size: 16, Value: 3690 0.132447 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x08, Offset: 8, Size: 16, Value: 3690 0.132450 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.132454 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.132561 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value...

...0x08, Offset: 0, Size: 8, Value: 100 0.025493 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x08, Offset: 8, Size: 16, Value: 8070 0.025531 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x08, Offset: 8, Size: 16, Value: 8070 0.025569 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.025607 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.028203 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 0.0...

..., Size: 8, Value: 100 0.262759 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x08, Offset: 8, Size: 16, Value: 3030 0.262767 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x08, Offset: 8, Size: 16, Value: 3030 0.262776 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.262784 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.262865 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value:...

...08, Offset: 0, Size: 8, Value: 100 0.035210 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Input, ReportID: 0x08, Offset: 8, Size: 16, Value: 15120 0.035309 Path: UPS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x08, Offset: 8, Size: 16, Value: 15120 0.035407 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Input, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.035506 Path: UPS.PowerSummary.RemainingTimeLimit, Type: Feature, ReportID: 0x08, Offset: 24, Size: 16, Value: 300 0.037734 Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, ReportID: 0x09, Offset: 0, Size: 8, Value: 24 0.0...