search for: ups_status

...y risky situation if we get another power failure immediately) 3) The UPS therefore reports low battery status to newhidups for the first few cycles (actually maybe just once!), 4) The UPS reaches enough reserves and no longer reports low battery Question: Looking at process_status_info(), ups_status seems to be used cumulatively, and alternative states clear each other, but who clears low battery from ups_status? I have observed upsc report a status of OL+LB+CHRG on a well charged battery several times, and I have just accidentally created a short power interruption for a fully loaded UPS...

...LB) before... > > or did I get you wrong? First, I fully understand that a UPS may report "Charging" because of a small amount of power drawn. However, in that case I would expect the UPS to report PowerSummary.PresentStatus.Charging with a value of one, and that should then show in ups_status. Second, I have encountered at least one situation in which the UPS reports "OL DISCHRG", but then immediately reports both Discharging and Charging as zero, and ups_status is therefore never cleared. I don't know the details of timing that lead to this situation, but it reproducibly...

Peter, Here are the transitions that I have tested with your latest changes (on the APC/Back-UPS ES 650): 1) OL ==> OB DISCHRG followed by OB DISCHRG ==> OL (no CHRG inbetween) 2) OL CHRG ==> OL 3) OL CHRG ==> OL CHRG LB (by manipulating battery.charge.low) 4) OL CHRG LB ==> OL CHRG (i.e. transition from below) 5) OB DISCHRG ==> FSD OB DISCHRG LB followed by proper shutdown In

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

...TEXP) 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's RemainingTimeLimitExpired that's causing the LB condition. Below is a bit more of the driver log which shows RemainingTimeLimitExpired changing to 1 and then back to 0 again. What does that variable mean? Ah, when I said earlier that I didn...

...n-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 4100 bytes Desc: image001.gif URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130715/0af8aaec/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: ups_status.zip Type: application/x-zip-compressed Size: 884 bytes Desc: ups_status.zip URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130715/0af8aaec/attachment.bin>

...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's RemainingTimeLimitExpired that's causing the LB condition. Below is a bit more of the driver log which shows RemainingTimeLimitExpired changing to 1 and then back to 0 again. What does that variable mean? Thanks again for your help, Gra...

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

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

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