Nut upsuser - Nov 2012 - APC UPS: replacement battery always triggers shutdown

?I've been using nut on an APC Back-UPS 750 for several years with no
problem, seeing the walled "UPS on battery power"
messages during short 1-2 minute outages. This is connected with the original
USB cable that came with the unit.

After replacing the battery recently, nut always triggers a shutdown when AC
power is cut off, even if only for 1 minute.

I see that the data fields reported by nut have not changed (details below) and
the runtime is stuck at 0, even with 35% charge. This runtime is an incorrect
reading as I verified that stopping nut and cutting off AC power does indeed
keep my computer running. It is only nut that thinks the runtime is 0 and
triggers
the shutdown.

FAQs #37, #38 on networkupstools.org are related to this issue:
? ? ?
? ?
http://www.networkupstools.org/docs/FAQ.html#_i_replaced_the_battery_in_my_apc_smart_ups_and_now_it_thinks_the_battery_is_low_all_the_time_how_do_you_fix_this

I followed this procedure (charging the battery fully, letting it drain off a
token load while UPS is grounded on a surge protector) but it did not help.

Perhaps I missed something running this procedure; if anyone has suggestions for
solving this they'd be greatly appreciated.
I'm using nut-2.6.4-1 on debian linux (testing distribution, kernel
3.1.0-1).

thanks,
--jack

Here are the details I see:
=> upsc apc
battery.charge: 35
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2008/01/25 ? ? ? ? ? ? ? ? ? ? ?
?<<<<<<<<<< battery bought 11/01/2012 ??
battery.runtime: 0 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
?<<<<<<<<<< runtime = 0 with 35% charge above?
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 11.8
battery.voltage.nominal: 12.0
device.mfr: American Power Conversion
device.model: Back-UPS ES 750
device.serial: 3B0804X42777 
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.version: 2.6.4
driver.version.data: APC HID 0.95
driver.version.internal: 0.37
input.sensitivity: medium
input.transfer.high: 139
input.transfer.low: 92
input.voltage: 119.0
input.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 841.I2 .D
ups.firmware.aux: I2 
ups.load: 42
ups.mfr: American Power Conversion
ups.mfr.date: 2008/01/25
ups.model: Back-UPS ES 750
ups.productid: 0002
ups.realpower.nominal: 450
ups.serial: 3B0804X42777 
ups.status: OL CHRG LB ? ? ? ? ? ? ? ? ? ? ? ? ?
?<<<<<<<<<<<<<<< see FAQ #37, 38
ups.test.result: No test initiated
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121111/446dec55/attachment.html>

On Sun, Nov 11, 2012 at 07:21:35AM -0800, JS wrote:
> I followed this procedure (charging the battery fully, letting it drain off
a token load while UPS is grounded on a surge protector) but it did not help.
> 
> Perhaps I missed something running this procedure; if anyone has
suggestions for solving this they'd be greatly appreciated.
I've been in the same situation after replacing the battery in SC620I model.

Then I found http://old.nabble.com/SmartUPS-and-new-battery-td20678966.html
and followed the procedure:

1. Shutdown the apcupsd daemon.
2. Run apctest
3. Choose option 6 to enter terminal mode
4. Enter Y (UPS should respond SM)
5. Enter 1 (one, not el; wait 4 seconds)
6. Enter 1 (one, not el; UPS should respond PROG)
7. Enter 0 (zero, not oh; UPS should respond with current constant)
8. Enter + (plus) or - (minus) to increment/decrement the value
9. Enter R to reprogram constant value (UPS should respond Bye)
10. Enter Y (UPS should respond SM)
11. Enter 0 (zero, not oh; UPS should respond with the new constant)
12. Enter Esc to exit terminal mode
13. Choose option 7 to exit apctest. 

The value to store in the register 0 differs by the model. There is a table
posted in the middle of the thread. I hope your model is listed there.
If you cannot find your model, you may want to try experimenting with different
values.

In my case, after updating register 0, my UPS is back to 42 min runtime.

Hope this helps.

Kastus