I took the log. Here's what happened.
Broadcast Message from nut@rasp
(somewhere) at 16:18 ...
UPS BNT500AP@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@rasp
(somewhere) at 17:33 ...
UPS BNT500AP@localhost on battery
occurred when UPS.PowerSummary.PresentStatus.ACPresent turned to 0 on this line:
10921.069403 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input,
ReportID: 0x0a, Offset: 2, Size: 1, Value: 0
Broadcast Message from nut@rasp
(somewhere) at 17:33 ...
UPS BNT500AP@localhost on line power
There were 3 more "on battery" events at 2:31:
43194.030619 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Feature,
ReportID: 0x0a, Offset: 2, Size: 1, Value: 0
Here I also see a suspisious frequency value 70. How is this possible?
43194.046966 Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x1e,
Offset: 0, Size: 8, Value: 70
At 2:58:
44790.984549 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input,
ReportID: 0x0a, Offset: 2, Size: 1, Value: 0
Here all voltages and frequencies are OK, so I don't understand why ACPresent
is 0.
44790.374516 Path: UPS.Input.Voltage, Type: Feature, ReportID: 0x1d, Offset:
0, Size: 16, Value: 232
44790.375512 Path: UPS.Input.Frequency, Type: Feature, ReportID: 0x1e,
Offset: 0, Size: 8, Value: 50
44790.376535 Path: UPS.Output.Voltage, Type: Feature, ReportID: 0x21,
Offset: 0, Size: 16, Value: 232
44790.377511 Path: UPS.Output.Frequency, Type: Feature, ReportID: 0x22,
Offset: 0, Size: 8, Value: 50
and at 6:15:
56597.541128 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input,
ReportID: 0x0a, Offset: 2, Size: 1, Value: 0
At 6:15 I also got "Low battery" event that triggered Raspberry pi shutdown,
but I don't see a reason for that in the driver log.
When it happened, the UPS started beeping every 2 seconds and I could silence
it by pressing the power button, as written in user manual. I was only able to
silence it by shutting down completely. By the way, the first time it happened
also at about the same time.
I'm not able to post the log, because even compressed it is more than 1 MB.
-----Original Message-----
From: Charles Lepple [mailto:[email protected]]
Sent: Saturday, June 08, 2013 10:49 PM
To: Mārtiņš Puķītis
Cc: 'nut-upsuser lists.alioth.debian.org'
Subject: Re: [Nut-upsuser] several problems with Powercom BNT-500AP
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 running at the same time. (That's even more difficult
to decipher from one log alone.)
You can either just restart the driver, or restart upsd after stopping
everything.
In either case, I was thinking that it would be useful to know where *in the
longer log* the events occur. Then we can look to see if the UPS is returning
bad information, or if the driver is experiencing an error condition.
--
Charles Lepple
clepple@gmail
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
