Arjen, Arnaud, All, Here I propose 2 new status flags for inclusion into NUT: HB - HighBattery TEST - Battery test is running rationale: Eltek AL175 alarm module provides this info, therefore rationale: I dicide to add them. Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru> Index: nut--trunk/docs/new-drivers.txt ==================================================================--- nut--trunk.orig/docs/new-drivers.txt 2007-01-09 12:39:06.000000000 +0300 +++ nut--trunk/docs/new-drivers.txt 2007-01-16 20:18:20.000000000 +0300 @@ -160,7 +160,9 @@ OL - On line OB - On battery (inverter is providing load power) LB - Low battery + HB - High battery RB - The battery needs to be replaced + TEST - Battery test is running BYPASS - UPS bypass circuit is active - no battery protection is available CAL - UPS is currently performing runtime calibration (on battery) OFF - UPS is offline and is not supplying power to the load -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20070116/134d73ea/attachment.pgp
Kirill Smelkov wrote:> Here I propose 2 new status flags for inclusion into NUT: > > HB - HighBatteryWhat is this? Is this a notification that the battery is full, or that the battery voltage is too high? At the very least, this should be a little more descriptive. Yet I'm not quite sure if this is not similar to RB (Replace Battery).> TEST - Battery test is runningWe already have CAL, which is essentially the same thing. Unless this is totally different, I don't support adding this to the ups.status. For the operation of upsmon, a battery test and runtime calibration are the same thing - you'd risk a shorter than normal runtime when the mains is out (if the battery is not fully charged). For now, I don't support either of these two flags. Best regards, Arjen