search for: needreplac

I took the log. Here's what happened. Broadcast Message from nut at rasp (somewhere) at 16:18 ... UPS BNT500AP at localhost battery needs to be replaced occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a, Offset: 6, Size: 1, Value: 1 It happened for 9 times, but the message appeared only on first. Broadcast Message from nut at rasp (somewhere) at 17:33 ... UPS BNT500AP a...

...000000 0.577942 Report[buf]: (2 bytes) => 07 0d 0.577954 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0.000000 0.577963 Report[buf]: (2 bytes) => 07 0d 0.577975 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x07, Offset: 6, Size: 1, Value: 0.000000 0.577984 Report[buf]: (2 bytes) => 07 0d 0.577996 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x07, Offset: 6, Size: 1, Value: 0.000000 0.578005 Report[buf]: (2 bytes) =...

...000000 0.577942 Report[buf]: (2 bytes) => 07 0d 0.577954 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0.000000 0.577963 Report[buf]: (2 bytes) => 07 0d 0.577975 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x07, Offset: 6, Size: 1, Value: 0.000000 0.577984 Report[buf]: (2 bytes) => 07 0d 0.577996 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x07, Offset: 6, Size: 1, Value: 0.000000 0.578005 Report[buf]: (2 bytes) =...

....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.RemainingTimeLimit Path: UPS.PowerSummary.AudibleAlarmControl Path: UPS.Battery.APCBattReplaceDate Path: UPS.Battery.Manufactu...

...: > I took the log. Here's what happened. > Broadcast Message from nut at rasp > (somewhere) at 16:18 ... > UPS BNT500AP at localhost battery needs to be replaced > > occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: > 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a, Offset: 6, Size: 1, Value: 1 > It happened for 9 times, but the message appeared only on first. Correct, upsmon throttles the REPLBATT event: http://www.networkupstools...

...quot;new commands" pointed in your archive (thanks for isolating these changes!): - Usage ID : 85:68 is already supported with UPS.PowerSummary.RunTimeToEmpty - Usage ID :85:4B is already supported with 1 of the 2 below (can't check the HID report structure) UPS.PowerSummary.PresentStatus.NeedReplacement UPS.PresentStatus.NeedReplacement This leaves the 2 "Outlet Group" commands, which is probably the actual reason why you contacted us: Usage ID : 84:01 Report ID : 50 Write : 1 Description : Outlet Group1 ON Usage ID : 84:01 Report ID : 49 Write : 0 Description : Outlet Group2 OFF...

....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.00000000 Path: UPS.PowerSummary.PresentStatus.00000000 Path: UPS.PowerSummary.PresentStatus.00000000 Path: UPS.P...

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

...Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 21, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Input, ReportID: 0x32, Offset: 22, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x32, Offset: 23, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Feature, ReportID: 0x32, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x32, Offset: 9, Size:...

...1, Value: 1 0.066736 Path: UPS.PowerSummary.PresentStatus.Charging, Type: Input, ReportID: 0x32, Offset: 2, Size: 1, Value: 1 to 0.066756 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 3, Size: 1, Value: 0 0.066777 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x32, Offset: 4, Size: 1, Value: 0 0.066798 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x32, Offset: 5, Size: 1, Value: 0 0.066819 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Input, ReportID: 0x32, Offset:...

....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.00000000 Path: UPS.PowerSummary.PresentStatus.00000000 ....................... a total of 46 PresentStatus.00000...

...mary.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: 0x0a, Offset: 6, Size: 1, Value: 0 0.130638 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, ReportID: 0x0a, Offset: 6, Size: 1, Value: 0 0.130643 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x0a...

...: > I took the log. Here's what happened. > Broadcast Message from nut at rasp > (somewhere) at 16:18 ... > UPS BNT500AP at localhost battery needs to be replaced > > occurred when for the first time value "1" was read as "UPS.PowerSummary.PresentStatus.NeedReplacement", on this line: > 6409.240690 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x0a, Offset: 6, Size: 1, Value: 1 > It happened for 9 times, but the message appeared only on first. Correct, upsmon throttles the REPLBATT event: http://www.networkupstools...

...8262 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 21, Size: 1, Value: 0 0.028286 Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Input, ReportID: 0x32, Offset: 22, Size: 1, Value: 0 0.028310 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x32, Offset: 23, Size: 1, Value: 0 0.028333 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x32, Offset: 18, Size: 1, Value: 0 0.028357 Path: UPS.PowerSummary.PresentStatus.FullyCharged, Type: Feature, ReportID:...

On Jan 2, 2008 3:34 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Wed Jan 2 20:34:26 2008 > New Revision: 1210 > > Log: > Parsing continues if the HID path for a report ends in 0x00000000 (these will not be made available). Commonly used as placeholders. > > It looks like (but correct me if I'm wrong) that reports

On Jun 8, 2013, at 12:57 PM, M?rti?? Pu??tis wrote: > I'll take a longer driver log. This page (http://www.networkupstools.org/support.html) says that to take a driver log NUT should be stopped, so I won't be able to tell when these events occurred within a driver log. Hmm, I didn't realize it said that, but I think that's to prevent having two copies of the same driver

...> Feature, Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.CommunicationLost, Type: > > Feature, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Feature, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, Value: > > 0.000000 > > Path: UPS.PowerSummary.PresentStatus.Overlo...

..., Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.Discharging, Type: Input, ReportID: 0x32, Offset: 21, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.FullyDischarged, Type: Input, ReportID: 0x32, Offset: 22, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.NeedReplacement, Type: Input, ReportID: 0x32, Offset: 23, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Feature, ReportID: 0x32, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x32, Offset: 9, Size: 1,...

Thanks for the support. Here's list of when transition to battery with return to utility power within a few seconds occurred in last few days: Wednesday 1:41 11:48 11:54 12:59 13:42 14:42 18:13 18:14 Thursday 5:23 Friday 5:12 7:39 7:43 Saturday 7:34 Here's list of when messages that battery needs replacement occurred: Wednesday 20:34 Thursday 9:07 23:09 Friday 18:25 Saturday 7:32 19:47

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