Jeff Boyce
2007-11-16 19:10:04 UTC
Greetings -
I have just replaced the battery in my APC Smart-UPS 1000 XL and have run
the battery calibration process, so that the apcupsd status shows the
current charge and runtime that I would expect to see. As suggested in the
apcupsd manual I ran the calibration process twice on the new battery.
Although looking through the message archives and the manual I have seen
different recommendations for running the calibration process. Some state
that the calibration must be run at exactly a 30 percent load, others state
a minimum of a 30 percent load, and I also saw reference to optimally
between a 30 and 35 percent load. Does anyone have a definitive answer on
best practice here, or can explain technically why a specific load should be
used? I ran my first calibration with a 26.6 percent load as I didn't have
enough non-critical electronic devices in the office to get a higher load.
Then the next day I brought in some additional devices and ran the
calibration the second time with a 32.5 percent load.
The only odd thing in my ups status now is the manufacture date and battery
date still show the date of my original battery, not the replacement. I
searched the archives and found one reference stating that the battery date
has to be reset manually, but there is no additional description of how this
would be done. I also did not find anything on the APC web site that might
give me a clue (didn't really expect it would). What would I need to do in
order to have the status show the correct battery date?
I have posted my UPS status below (it is currently being recharged and does
not have a load on it). Also listed is my apcupsd config file (running
version 3.10.17). I am running RHEL 3 with the kernel listed below. If it
takes updating my kernel to 2.6 something and updating apcupsd to the latest
version in order to get the correct battery date, then that is something
that I am not sure will happen. This UPS is supporting a Dell file server
for a small office which doesn't have a full time system administrator (the
part time administrator is a full-time ecologist), therefore we generally
operate under the philosophy of only applying necessary updates to the
system, and only of we are confident that it won't break something else, or
cause a cascade of updates. Does this mean that I am going to be out of
luck with the battery date?
PS. Thanks for the great UPS software. This has run flawlessly for the
past 3 plus years, and has saved our hardware numerous times.
Jeff Boyce
Linux Bison 2.4.21-50.ELsmp #1 SMP Tue May 8 17:18:29 EDT 2007 i686 i686
i386 GNU/Linux
APC : 001,051,1201
DATE : Fri Nov 16 10:06:53 PST 2007
HOSTNAME : Bison
RELEASE : 3.10.17
VERSION : 3.10.17 (18 March 2005) redhat
UPSNAME : UPS_IDEN
CABLE : Custom Cable Smart
MODEL : Smart-UPS 1000 XL
UPSMODE : Stand Alone
STARTTIME: Fri Nov 16 07:13:52 PST 2007
STATUS : ONLINE
LINEV : 114.4 Volts
LOADPCT : 0.0 Percent Load Capacity
BCHARGE : 042.0 Percent
TIMELEFT : 131.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME : 0 Seconds
MAXLINEV : 118.8 Volts
MINLINEV : 000.0 Volts
OUTPUTV : 114.4 Volts
SENSE : High
DWAKE : 000 Seconds
DSHUTD : 090 Seconds
DLOWBATT : 02 Minutes
LOTRANS : 106.0 Volts
HITRANS : 127.0 Volts
RETPCT : 000.0 Percent
ITEMP : 24.3 C Internal
ALARMDEL : 5 seconds
BATTV : 27.4 Volts
LINEFREQ : 60.0 Hz
LASTXFER : No transfers since turnon
NUMXFERS : 0
TONBATT : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI : 336
STATFLAG : 0x02000008 Status Flag
REG1 : 0x00 Register 1
REG2 : 0x00 Register 2
REG3 : 0x00 Register 3
MANDATE : 10/24/03
SERIALNO : AS0343231786
BATTDATE : 10/24/03
NOMOUTV : 120
NOMBATTV : 24.0
EXTBATTS : 0
FIRMWARE : 631.3.D
APCMODEL : FWD
END APC : Fri Nov 16 10:06:55 PST 2007
UPSCABLE smart
UPSTYPE smartups
DEVICE /dev/ttyS0
LOCKFILE /var/lock
ONBATTERYDELAY 6
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
KILLDELAY 0
NETSERVER on
NISIP 0.0.0.0
NISPORT 3551
EVENTSFILE /var/log/apcupsd.events
EVENTSFILEMAX 10
UPSCLASS standalone
UPSMODE disable
STATTIME 0
STATFILE /var/log/apcupsd.status
LOGSTATS off
DATATIME 0
___________________________________________________________________
Users of Arkeia can share their experiences and questions via this
mailing-list. Support programs are available to Arkeia commercial
version users: contact us at info-AHySt852JRvQT0dZR+***@public.gmane.org for more information.
If you wish to modify your subscription or if you want to subscribe
to other Arkeia mailing-lists, please, go to:
http://www.arkeia.com/community/
___________________________________________________________________
I have just replaced the battery in my APC Smart-UPS 1000 XL and have run
the battery calibration process, so that the apcupsd status shows the
current charge and runtime that I would expect to see. As suggested in the
apcupsd manual I ran the calibration process twice on the new battery.
Although looking through the message archives and the manual I have seen
different recommendations for running the calibration process. Some state
that the calibration must be run at exactly a 30 percent load, others state
a minimum of a 30 percent load, and I also saw reference to optimally
between a 30 and 35 percent load. Does anyone have a definitive answer on
best practice here, or can explain technically why a specific load should be
used? I ran my first calibration with a 26.6 percent load as I didn't have
enough non-critical electronic devices in the office to get a higher load.
Then the next day I brought in some additional devices and ran the
calibration the second time with a 32.5 percent load.
The only odd thing in my ups status now is the manufacture date and battery
date still show the date of my original battery, not the replacement. I
searched the archives and found one reference stating that the battery date
has to be reset manually, but there is no additional description of how this
would be done. I also did not find anything on the APC web site that might
give me a clue (didn't really expect it would). What would I need to do in
order to have the status show the correct battery date?
I have posted my UPS status below (it is currently being recharged and does
not have a load on it). Also listed is my apcupsd config file (running
version 3.10.17). I am running RHEL 3 with the kernel listed below. If it
takes updating my kernel to 2.6 something and updating apcupsd to the latest
version in order to get the correct battery date, then that is something
that I am not sure will happen. This UPS is supporting a Dell file server
for a small office which doesn't have a full time system administrator (the
part time administrator is a full-time ecologist), therefore we generally
operate under the philosophy of only applying necessary updates to the
system, and only of we are confident that it won't break something else, or
cause a cascade of updates. Does this mean that I am going to be out of
luck with the battery date?
PS. Thanks for the great UPS software. This has run flawlessly for the
past 3 plus years, and has saved our hardware numerous times.
Jeff Boyce
Linux Bison 2.4.21-50.ELsmp #1 SMP Tue May 8 17:18:29 EDT 2007 i686 i686
i386 GNU/Linux
APC : 001,051,1201
DATE : Fri Nov 16 10:06:53 PST 2007
HOSTNAME : Bison
RELEASE : 3.10.17
VERSION : 3.10.17 (18 March 2005) redhat
UPSNAME : UPS_IDEN
CABLE : Custom Cable Smart
MODEL : Smart-UPS 1000 XL
UPSMODE : Stand Alone
STARTTIME: Fri Nov 16 07:13:52 PST 2007
STATUS : ONLINE
LINEV : 114.4 Volts
LOADPCT : 0.0 Percent Load Capacity
BCHARGE : 042.0 Percent
TIMELEFT : 131.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME : 0 Seconds
MAXLINEV : 118.8 Volts
MINLINEV : 000.0 Volts
OUTPUTV : 114.4 Volts
SENSE : High
DWAKE : 000 Seconds
DSHUTD : 090 Seconds
DLOWBATT : 02 Minutes
LOTRANS : 106.0 Volts
HITRANS : 127.0 Volts
RETPCT : 000.0 Percent
ITEMP : 24.3 C Internal
ALARMDEL : 5 seconds
BATTV : 27.4 Volts
LINEFREQ : 60.0 Hz
LASTXFER : No transfers since turnon
NUMXFERS : 0
TONBATT : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI : 336
STATFLAG : 0x02000008 Status Flag
REG1 : 0x00 Register 1
REG2 : 0x00 Register 2
REG3 : 0x00 Register 3
MANDATE : 10/24/03
SERIALNO : AS0343231786
BATTDATE : 10/24/03
NOMOUTV : 120
NOMBATTV : 24.0
EXTBATTS : 0
FIRMWARE : 631.3.D
APCMODEL : FWD
END APC : Fri Nov 16 10:06:55 PST 2007
UPSCABLE smart
UPSTYPE smartups
DEVICE /dev/ttyS0
LOCKFILE /var/lock
ONBATTERYDELAY 6
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
KILLDELAY 0
NETSERVER on
NISIP 0.0.0.0
NISPORT 3551
EVENTSFILE /var/log/apcupsd.events
EVENTSFILEMAX 10
UPSCLASS standalone
UPSMODE disable
STATTIME 0
STATFILE /var/log/apcupsd.status
LOGSTATS off
DATATIME 0
___________________________________________________________________
Users of Arkeia can share their experiences and questions via this
mailing-list. Support programs are available to Arkeia commercial
version users: contact us at info-AHySt852JRvQT0dZR+***@public.gmane.org for more information.
If you wish to modify your subscription or if you want to subscribe
to other Arkeia mailing-lists, please, go to:
http://www.arkeia.com/community/
___________________________________________________________________