[Nut-upsdev] RFC: new variable battery.status (was: [PATCH] upscode2: Report ABM Status)

Arnaud Quette aquette.dev at gmail.com
Mon Feb 13 17:58:07 UTC 2012


2012/2/6 thomas schorpp <thomas.schorpp at googlemail.com>:
> Hi,

Hi Thomas,

> I want the driver report the battery status from ABM charging controllers
> -patch attached- :

thanks for your patch.

since it introduces a new variable (battery.status.abm), I prefer to
step back and think to something useful more widely.

thus, I'm thinking about a generic "battery.status" that would have
the following possible values:
- charging
- floating (charging method with lower voltage)
- resting (not charging nor discharging)

a complementary status should be discharging, when none of the above applies.

For the time being, this only applies to Eaton manufactured UPSs.
But I'd like to get feedback from owners of other devices, that
support an equivalent technology.

This data would apply to upscode2, bcmxcp*, usbhid-ups ("MGE"
subdriver) and possibly snmp-ups.

For now, I've tracked your patch here:
https://alioth.debian.org/tracker/index.php?func=detail&aid=313541&group_id=30602&atid=411544

> http://www.google.de/url?sa=t&rct=j&q=advanced+battery+management+floating&source=web&cd=1&ved=0CDMQxQEwAA&url=http%3A%2F%2Fdocs.google.com%2Fviewer%3Fa%3Dv%26q%3Dcache%3AH0Fy9-ZmujgJ%3Alit.powerware.com%2Fll_download.asp%253Ffile%253DABM_datasheet_rev_A_re_working.pdf%2Badvanced%2Bbattery%2Bmanagement%2Bfloating%26hl%3Dde%26gl%3Dde%26pid%3Dbl%26srcid%3DADGEESj_h5zp2cVwCOSCZP0BgmzG3jNOC9cq_54FStVvgWoYVD6lauUNAqYpMSoVxYMf3dcNF2_9x_ZGCPNGnnlm6OVZuvi8VzKvbVfwVdNISlcSrdzqaeS3b8I2WApj9E_Yh38CGIww%26sig%3DAHIEtbRE44qDSR4VtSuK7qOOLZSRVz7XYA&ei=ytUvT6XyBILKtAbJk4ndDA&usg=AFQjCNH0GuqrYphp6h9t1jtWcAu0LzGsBw
>
> battery.capacity.nominal: 17.00
> battery.charge: 74.4
> battery.runtime: 1620
> battery.status.abm: RS (New)
> battery.voltage: 26.10*
> battery.voltage.maximum: 28.20
> battery.voltage.minimum: 20.00
> battery.voltage.nominal: 24.00
>
> Since my ancient Compaq T1000h got it, response STBM should be widely
> implemented:
> http://webcache.googleusercontent.com/search?q=cache:Pt8WJTtgaW0J:old.networkupstools.org/protocols/eaton/UC2concept-1002889j.odt+upscode+II+pdf&cd=1&hl=de&ct=clnk&gl=de
>
> BTW, possible bug: Wether my new lead AGM batteries are broken (Cold weather
> storage damage in GLS logistics transport?)
> http://media.rotek.at/a000/000/007/000000007_V000000_HAB_HIG_00_RT_A_de.pdf
>
> *or the charge estimation calculator of the driver is broken:
>
> battery.capacity.nominal: 17.00
> battery.charge: 93.9
> battery.runtime: 1620
> battery.status.abm: FT
> battery.voltage: 27.70
> battery.voltage.maximum: 28.20
> battery.voltage.minimum: 20.00
> battery.voltage.nominal: 24.00
> device.mfr: Compaq
> device.model: UPS 1000 VA FW -0026
> device.serial: E00230050
>
> My UPS does not support UPBS cmd, but its responses are not very useful
> anyway.

as mentioned in the manpage and source code, no battery.charge data is
returned from the device.
"the driver will guestimate a value based on the nominal battery
min/max and the current battery voltage."

so it may be due to both.
It may also be a percentage of the nominal level, which may be not
reachable after some time.

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/



More information about the Nut-upsdev mailing list