Nut upsuser - Sep 2007 - UPS shows 120%

I just got NUT 2.0.1 running on my Debian system at home.? I have a
new CPS UPS connected via USB.? Everything is working fine, except
the UPS is showing a value of 120% charged.? Any idea what causes
this?? Here's the upsc output for my UPS:

battery.charge:
120
battery.charge.low: 10
battery.charge.warning: 20
battery.runtime: 1320
battery.runtime.low: 300
battery.type:
PbAcid
battery.voltage: 20.2
battery.voltage.nominal: 12.0
driver.name: newhidups
driver.parameter.port: auto
driver.version: 2.0.4
driver.version.data: APC/CyberPower HID
0.9
driver.version.internal: 0.28
input.transfer.high: 140
input.transfer.low: 90
input.voltage: 121.0
input.voltage.nominal: 120
output.voltage: 122.0
ups.beeper.status: enabled
ups.delay.shutdown: -1
ups.load:
24.0
ups.mfr: CPS
ups.model: UPS BF700
ups.status: OL

> I just got NUT 2.0.1 running on my Debian system at home.
No, you have nut-2.0.4 running according to upsc. :-) The newhidups driver
in nut-2.0.1 only supported MGE devices.
> I have a new CPS UPS connected via USB.  Everything is working fine,
> except the UPS is showing a value of 120% charged.
This probably means that the HID path
'UPS.PowerSummary.RemainingCapacity'
has a very different meaning for CyberPower devices, than it has for APC
where it indicates the battery charge. It also means, that we might have
to make a separate subdriver to deal with this (I was already afraid of
that from looking at the very different HID paths it uses).
> Any idea what causes this?
Apparently, CyberPower doesn't follow the HID Power Devices specification.
That's sad, but we can probably work around that.
> Here's the upsc output for my UPS:
>
> battery.charge: 120
That is indeed suspicious.
> battery.charge.low: 10
> battery.charge.warning: 20
> battery.runtime: 1320
> battery.runtime.low: 300
> battery.type: PbAcid
> battery.voltage: 20.2
Seems to be a little high for a 12V battery system as reported below.
> battery.voltage.nominal: 12.0
> driver.name: newhidups
> driver.parameter.port: auto
> driver.version: 2.0.4
> driver.version.data: APC/CyberPower HID 0.9
> driver.version.internal: 0.28
> input.transfer.high: 140
> input.transfer.low: 90
> input.voltage: 121.0
> input.voltage.nominal: 120
> output.voltage: 122.0
> ups.beeper.status: enabled
> ups.delay.shutdown: -1
> ups.load: 24.0
> ups.mfr: CPS
> ups.model: UPS BF700
> ups.status: OL
What we need is the output from the driver running in debug mode

    newhidups -DD -a <upsname>

in order to write a new subdriver. Preferably from a somewhat more recent
version of NUT, but if nut-2.0.4 is all you have, that will do.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57

Phil Scarr wrote:
>>> I have a new CPS UPS connected via USB.  Everything is working
fine,
>>> except the UPS is showing a value of 120% charged.
>> This probably means that the HID path
'UPS.PowerSummary.RemainingCapacity'
>> has a very different meaning for CyberPower devices, than it has for
APC
>> where it indicates the battery charge. It also means, that we might
have
>> to make a separate subdriver to deal with this (I was already afraid of
>> that from looking at the very different HID paths it uses).
In retrospect, the value may be actually correct. This parameter tells
you the actual amount of charge the battery can hold in relation to the
design capacity. If this is indeed a new (battery) system, the first can
be *higher* than the latter, depending on the rate of discharge that was
used in measuring the actual capacity.

[...]
> Path: UPS.PowerSummary.ConfigVoltage, Type: Feature, Value: 12.000000
> Path: UPS.PowerSummary.Voltage, Type: Feature, Value: 21.400000
This here is actually the only surprise I see. This looks way too high
for a 12V battery and too low for a 24V battery (it could be a 3 x 6V
battery system, but I have never seen such a configuration). Can you
measure the battery voltage?

I still believe it would be better to create a separate subdriver for
CyberPower, if only for the reason that it is easier to maintain if each
VendorID has it's own subdriver.

Best regards, Arjen

PS  Please keep the mailinglist posted.

First of all, keep the mailinglist posted. I won't provide any help
off-list.
> How do I go about measuring the battery voltage?  Do I have to crack
> the case to get to it?  If so, I'm reluctant.  :-/
According to the CyberPower website, the batteries are user replaceable.
This means they should be readily accessible.

Best regards, Arjen