Réf. : Re: [Nut-upsdev] Re: newhidups and APC Back-UPS CS 350

arnaud.quette at mgeups.com arnaud.quette at mgeups.com
Tue Aug 16 13:30:49 UTC 2005

A note to begin:
The stable branch is based upon Testing. Testing only add
bugfixes and info update.
The Development release is where everything come in.

> Guess 2.0.3 is not based on HEAD, but on the "stable" branch.

guess right, according to the above, HEAD should point Development.
in fact, as I (ab)use branches, it currently points the 2.0.1 release
I've imported first. I'm wondering if I'll use HEAD for the latest Development,
the latest Testing or the latest whatever (as it should be). Low prio as
there was nobody else working with me...

> Any idea why newhidups might miss the ("on battery") events from the UPS?

there is no reason...
newhidups shouldn't miss status event. As it's generated by the unit
(notification), we should get it either when we wait for notification,
or by any polling we do (as it's a critical data).
When in debug mode (newhidups -DDDDD ...), you should see lines
mentionning "UPS.PowerSummary.PresentStatus.ACPresent" that
are looked up as "ups.status = OB".

Send back the DumpTree() output (at newhidups startup, you should
see a list of data available, ie):
Path: UPS.PowerSummary.PresentStatus.ACPresent
Path: UPS.PowerSummary.PresentStatus.BatteryPresent
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PowerSummary.PresentStatus.ShutdownImminent
And the part where it lookup between "...ACPresent" and "ups.status = OB"
to see if there's a problem.

Arnaud Quette
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
OpenSource Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
 ... and much more ...

More information about the Nut-upsdev mailing list