[Nut-upsdev] Re: newhidups and APC Back-UPS CS 350

Thomas Jarosch thomas.jarosch at intra2net.com
Wed Aug 17 13:08:19 UTC 2005 

On Tuesday 16 August 2005 15:30, you wrote:
> 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...

Would be nice if HEAD represents the current development.
Tags for every release are a good thing, too,
but I better step out of this discussion.

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

Here's the dump:
Detected an UPS: American Power Conversion/Back-UPS CS 350 FW:807.q5.I USB 
FW:q5

Path: UPS.PowerSummary.iSerialNumber
Path: UPS.PowerSummary.iManufacturer
Path: UPS.PowerSummary.iOEMInformation
Path: UPS.PowerSummary.iDeviceChemistry
Path: UPS.PowerSummary.Rechargeable
Path: UPS.PowerSummary.CapacityMode
Path: UPS.PowerSummary.DesignCapacity
Path: UPS.PowerSummary.FullChargeCapacity
Path: UPS.PowerSummary.RemainingCapacity
Path: UPS.PowerSummary.RemainingCapacity
Path: UPS.PowerSummary.CapacityGranularity1
Path: UPS.PowerSummary.CapacityGranularity2
Path: UPS.PowerSummary.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.ConfigVoltage
Path: UPS.PowerSummary.Voltage
Path: UPS.PowerSummary.AudibleAlarmControl
Path: UPS.PowerSummary.PresentStatus.Charging
Path: UPS.PowerSummary.PresentStatus.Charging
Path: UPS.PowerSummary.PresentStatus.Discharging
Path: UPS.PowerSummary.PresentStatus.Discharging
Path: UPS.PowerSummary.PresentStatus.ACPresent
Path: UPS.PowerSummary.PresentStatus.ACPresent
Path: UPS.PowerSummary.PresentStatus.BatteryPresent
Path: UPS.PowerSummary.PresentStatus.BatteryPresent
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PowerSummary.PresentStatus.ShutdownRequested
Path: UPS.PowerSummary.PresentStatus.ShutdownRequested
Path: UPS.PowerSummary.PresentStatus.ShutdownImminent
Path: UPS.PowerSummary.PresentStatus.ShutdownImminent
Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired
Path: UPS.PowerSummary.PresentStatus.CommunicationLost
Path: UPS.PowerSummary.PresentStatus.CommunicationLost
Path: UPS.PowerSummary.PresentStatus.NeedReplacement
Path: UPS.PowerSummary.PresentStatus.NeedReplacement
Path: UPS.PowerSummary.PresentStatus.OverLoad
Path: UPS.PowerSummary.PresentStatus.OverLoad
Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated
Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated
Path: UPS.PowerSummary.PresentStatus.ff860080
Path: UPS.PowerSummary.PresentStatus.ff860080
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.PowerSummary.PresentStatus.00000000
Path: UPS.Battery.Test
Path: UPS.Battery.Test
Path: UPS.Battery.APCBattCapBeforeStartup
Path: UPS.Battery.ff86001a
Path: UPS.Battery.ff86001b
Path: UPS.Battery.APCBattReplaceDate
Path: UPS.Battery.ManufacturerDate
Path: UPS.Battery.RemainingCapacity
Path: UPS.Battery.RemainingTimeLimit
Path: UPS.Battery.RunTimeToEmpty
Path: UPS.Battery.Temperature
Path: UPS.Battery.ConfigVoltage
Path: UPS.Battery.Voltage
Path: UPS.Battery.ff860024
Path: UPS.Battery.ff860018
Path: UPS.Input.Voltage
Path: UPS.Input.ConfigVoltage
Path: UPS.Input.APC860052
Path: UPS.Input.ff860061
Path: UPS.Input.ff860024
Path: UPS.Output.PercentLoad
Path: UPS.Output.00840044
Path: UPS.Output.Frequency
Path: UPS.Output.Voltage
Path: UPS.Output.ConfigVoltage
Path: UPS.Output.HighVoltageTransfer
Path: UPS.Output.LowVoltageTransfer
Path: UPS.Output.APCDelayBeforeStartup
Path: UPS.Output.APCShutdownAfterDelay
Path: UPS.Output.DelayBeforeShutdown
Path: UPS.Output.DelayBeforeStartup
Path: UPS.Output.DelayBeforeReboot
Path: UPS.Output.APCForceShutdown
Path: UPS.Output.APCDelayBeforeShutdown
Path: UPS.iProduct
Path: UPS.iSerialNumber
Path: UPS.iManufacturer
Path: UPS.00840001
Path: UPS.APC_UPS_FirmwareRevision
Path: UPS.APC_USB_FirmwareRevision
Path: UPS.APCPanelTest
Path: UPS.ManufacturerDate
Path: UPS.ff860027
Path: UPS.ff860028
Path: UPS.AudibleAlarmControl
Path: UPS.PresentStatus.Charging
Path: UPS.PresentStatus.Charging
Path: UPS.PresentStatus.Discharging
Path: UPS.PresentStatus.Discharging
Path: UPS.PresentStatus.ACPresent
Path: UPS.PresentStatus.ACPresent
Path: UPS.PresentStatus.BatteryPresent
Path: UPS.PresentStatus.BatteryPresent
Path: UPS.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PresentStatus.BelowRemainingCapacityLimit
Path: UPS.PresentStatus.ShutdownRequested
Path: UPS.PresentStatus.ShutdownRequested
Path: UPS.PresentStatus.ShutdownImminent
Path: UPS.PresentStatus.ShutdownImminent
Path: UPS.PresentStatus.RemainingTimeLimitExpired
Path: UPS.PresentStatus.RemainingTimeLimitExpired
Path: UPS.PresentStatus.CommunicationLost
Path: UPS.PresentStatus.CommunicationLost
Path: UPS.PresentStatus.NeedReplacement
Path: UPS.PresentStatus.NeedReplacement
Path: UPS.PresentStatus.OverLoad
Path: UPS.PresentStatus.OverLoad
Path: UPS.PresentStatus.VoltageNotRegulated
Path: UPS.PresentStatus.VoltageNotRegulated
Path: UPS.PresentStatus.ff860080
Path: UPS.PresentStatus.ff860080
Path: UPS.PresentStatus.00000000
Path: UPS.PresentStatus.00000000
Path: UPS.PresentStatus.00000000
Path: UPS.PresentStatus.00000000
Path: UPS.PresentStatus.00000000
Path: UPS.PresentStatus.00000000
Path: UPS.ff860001.ff860023
Path: UPS.ff860001.ff860026
Path: UPS.ff860001.ff860025
Path: UPS.PowerConverter.ff860024

Should there be multiple entries like

Path: UPS.PowerSummary.PresentStatus.Charging
Path: UPS.PowerSummary.PresentStatus.Charging

?

I also don't see any events if I enter the test mode.
The output stays like this:

upsdrv_updateinfo...
Waiting for notifications...
 none (-22)

...

upsdrv_updateinfo...
Waiting for notifications...
 none (-22)

Cheers,
Thomas

More information about the Nut-upsdev mailing list