[Nut-upsuser] blazer_ser battery.high / battery.low

Charles Lepple clepple at gmail.com
Mon Jun 2 22:58:48 UTC 2014

On Jun 2, 2014, at 6:48 PM, Charles Lepple wrote:

> On Jun 2, 2014, at 12:25 PM, Andreas Lausch / TBT wrote:
>> Hi,
>> thanks for the reply.
>> On 2014-05-29 05:21, Charles Lepple wrote:
>>>> Now my questions:
>>>> 1. should the blazer_ser's high voltage be the voltage during charging
>>>> or right after I've unplugged it from the mains?
>>> sounds like during charging (or more accurately, during float charging at the end of the cycle):
>>> http://www.networkupstools.org/docs/man/blazer.html#_extra_arguments
>> Are you sure? If I put the 27.4 (reported voltage @ 100%) in the config,
>> battery.charge drops immediately when unplugged, because the reported
>> battery.voltage then is only 26.xV. (But I'm not sure the battery was at
>> 100% when I saw the 26.xV)
> I'm pretty sure I wouldn't rely on a charge percentage derived this way ;-)
> As mentioned in the other thread about the tripplite_usb driver, apart from having two sets of calibration constants, one for OL and one for OB, there is no good way to have a one-size-fits-all calibration.
> My answer was based on the documentation, but you could make a case for the on-battery voltage.

A little more explanation under the "Battery Charge" heading:

"If you specify both battery.voltage.high and battery.voltage.low in ups.conf(5), but don’t enter runtimecal, it will guesstimate the state of charge by looking at the battery voltage alone. This is not reliable under load..."

Does your UPS report load? If so, there is the "runtimecal" option.


Charles Lepple
clepple at gmail

More information about the Nut-upsuser mailing list