[Nut-upsuser] BNT-1000AP

[Jaco Kroon]

Hi guys,

Seems like I was *wrong* about the "good enough".  As soon as we unplug 
the power input the battery charge goes to -274.0 % (was +93.0% just 
before we pulled the power).  How do I go about fixing that?

On a second run I obtained this:

battery.charge: -265.0
driver.name: powercom
driver.parameter.batteryPercentage: {5.0000,0.3268,-825.00,0.93022,0}
driver.parameter.frequency: {0.00041994,0.0}
driver.parameter.manufacturer: BlackKnight
driver.parameter.modelname: BNT-1000AP
driver.parameter.port: /dev/ttyS1
driver.parameter.type: KIN1500AP
driver.version: 2.0.5
driver.version.internal: $ Revision: 0.5 $
input.frequency: 0.00
input.voltage: -0.1
input.voltage.nominal: 230
output.frequency: 47.63
output.voltage: 211.3
ups.load: 183.6
ups.mfr: BlackKnight
ups.model: BNT-1000AP
ups.model.type: KIN1500AP
ups.serial: Unknown
ups.status: OB

Which indicates (to me at least) that the input stuff is in fact correct 
(well, other than the fact that the initial values was out by a factor 
of approximately two.  However, the battery percentage is way incorrect 
still.

Jaco

Jaco Kroon wrote:
> Arjen de Korte wrote:
>>> Hi guys,
>>>
>>> We've got a BNT-1000AP (powercom) BlackKnight UPS that works with the
>>> KIN1500AP model in the powercom driver.  Well, almost.  It seems the
>>> input frequency and the battery charge is swapped around:
>>>
>>> # upsc blackknight at localhost
>>> battery.charge: 46.5
>>> driver.name: powercom
>>> driver.parameter.manufacturer: BlackKnight
>>> driver.parameter.modelname: BNT-1000AP
>>> driver.parameter.port: /dev/ttyS1
>>> driver.parameter.type: KIN1500AP
>>> driver.version: 2.0.5
>>> driver.version.internal: $ Revision: 0.5 $
>>> input.frequency: 95.25
>>> input.voltage: 220.9
>>> input.voltage.nominal: 230
>>> output.frequency: 95.25
>>> output.voltage: 219.0
>>> ups.load: 23.8
>>> ups.mfr: BlackKnight
>>> ups.model: BNT-1000AP
>>> ups.model.type: KIN1500AP
>>> ups.serial: Unknown
>>> ups.status: OL
>>>
>>> Is there any way to confirm that?
>> Unless you can confirm your findings by measuring the frequency and
>> battery charge through an external means, probably not. Chances are that
>> the only problem is, that the (hardcoded) coefficients in the driver to
>> calculate these values are wrong for the BNT-1000AP. Preferably we would
>> like to see the values reported by the UPS and one from a calibrated
>> instrument for several frequencies and battery charge levels. Unless you
>> can get hold of such instrument, there is probably nothing you can do to
>> help us here. Just a suspicion that these may be swapped just isn't
>> enough.
> 
> Well, I can tell you that the frequency should in fact be close to 50Hz 
> (well, in theory it should be exactly, but we don't live in a perfect 
> world).  Changing the coefficients by trial and error I managed to get 
> it close to what I would expect, and close enough to be good enough for 
> knowing when we hit battery low:
> 
> # upsc blackknight at localhost
> battery.charge: 93.0
> driver.name: powercom
> driver.parameter.batteryPercentage: {5.0000,0.3268,-825.00,0.93022,0}
> driver.parameter.frequency: {0.00041994,0.0}
> driver.parameter.manufacturer: BlackKnight
> driver.parameter.modelname: BNT-1000AP
> driver.parameter.port: /dev/ttyS1
> driver.parameter.type: KIN1500AP
> driver.version: 2.0.5
> driver.version.internal: $ Revision: 0.5 $
> input.frequency: 47.63
> input.voltage: 226.7
> input.voltage.nominal: 230
> output.frequency: 47.63
> output.voltage: 226.7
> ups.load: 23.8
> ups.mfr: BlackKnight
> ups.model: BNT-1000AP
> ups.model.type: KIN1500AP
> ups.serial: Unknown
> ups.status: OL
> 
> Now, from experience, I've never actually seen a battery at 100 %, but 
> usually between 91 and 98 % ... so I'm rather happy with that, and the 
> frequency is close to 50Hz ... I'm not going to worry too much about 
> that not being accurate - unless someone can tell me why I should be.
> 
> Now, the values I've changed are as follows:
> 
>      frequency = {0.00041994,0.0}
>      batteryPercentage = {5.0000,0.3268,-825.00,0.93022,0}
> 
> The values are based on the defaults in the powercom man page, and I've 
> doubled the first value for frequency, and I doubled the second last 
> value in the batteryPercentage list.
> 
> I haven't seen any documentation (haven't looked too hard yet either) as 
> to what each of values mean, so the it was done entirely on trial and 
> error.  What is the "scientific" way of approaching this?  I've 
> basically got access to a multi-meter, but I can't measure frequencies 
> with that, so I don't know how much worth that is.  Also, how do you 
> actually measure what the actual battery charge is?
> 
> I reckon the above is good enough for my purposes.  Thanks for prodding 
> me to fiddle with those coefficient values though.