[Nut-upsdev] Re: [PATCH] upsstatus += HB, TEST

[Kirill Smelkov]

17 Январь 2007 04:02, Peter Selinger написал:
> Arjen de Korte wrote:
> > 
> > Kirill Smelkov wrote:
> > 
> > > Here I propose 2 new status flags for inclusion into NUT:
> > > 
> > >   HB    - HighBattery
> > 
> > What 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).
> 
> Perhaps this is just the negation of LB - Low Battery? In this case it
> is not needed as a separate flag.

AL175 documentation states:

(description of one of AL175 registers)
Battery voltage status:
0 - Normal
1 - Low Battery
2 - High Battery

So I think HB is ok.

 
> > >   TEST  - Battery test is running
> > 
> > We 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).
> 
> Perhaps this belongs in ups.test.result? Several drivers put "in
> progress" here while a test is in progress. 
Yes it is.
I have separate information:

- whether battery test is running (0/1), and
- battery test result (OK/FAIL)

So should i use CAL instead of TEST?

  
> > For now, I don't support either of these two flags.
> 
> Neither I. -- Peter

-- 
	Всего хорошего, Кирилл.

-------------- 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/20070117/816ac73c/attachment.pgp