October 5, 201411 yr I tried searching but I didn't find anything. I was wondering if you guys are aware of this bug within APC UPS
October 5, 201411 yr That's a very old posting (over 4 years ago, referencing an e-mail from 2 years earlier), so I doubt it's still an issue with newer units. My BR1500 is about 3 years old and does NOT have this problem ... but I can't speak for certain about other similar models, except to note that it would be very unusual for a problem they were well aware of that long ago to not yet be resolved.
October 5, 201411 yr Author I just bought an APC, and installed the apcupsd-3.14.3-i486-1kjz.tgz pkg using unmenu. Also using unmenu > System Info > UPS Status, I get this information. As you can see my BATTDATE is 13 years befor my MANDATE. I then searched the forums with the search term "BATTDATE : 2001-09-25" and found quite a few posts with logs containing the same thing, but no mention of it being acknowledged as an issue/bug. That led to me searching the web for the same, and finding the information in the link in my first post. APC : 001,039,1024 DATE : Sun Oct 05 10:20:54 EDT 2014 HOSTNAME : Tower RELEASE : 3.14.3 VERSION : 3.14.3 (20 January 2008) slackware UPSNAME : Tower CABLE : Custom Cable Smart MODEL : Back-UPS RS1000G UPSMODE : Stand Alone STARTTIME: Sat Oct 04 06:48:57 EDT 2014 STATUS : ONLINE LINEV : 122.0 Volts LOADPCT : 9.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 84.0 Minutes MBATTCHG : 10 Percent MINTIMEL : 5 Minutes MAXTIME : 300 Seconds SENSE : Medium LOTRANS : 088.0 Volts HITRANS : 147.0 Volts ALARMDEL : Always BATTV : 27.3 Volts LASTXFER : Unacceptable line voltage changes NUMXFERS : 4 XONBATT : Sun Oct 05 06:23:01 EDT 2014 TONBATT : 0 seconds CUMONBATT: 7 seconds XOFFBATT : Sun Oct 05 06:23:02 EDT 2014 SELFTEST : NO STATFLAG : 0x07000008 Status Flag MANDATE : 2014-05-17 SERIALNO : 3B1420X26737 BATTDATE : 2001-09-25 NOMINV : 120 Volts NOMBATTV : 24.0 Volts NOMPOWER : 600 Watts FIRMWARE : 868.L3 -P.D USB FW: APCMODEL : Back-UPS RS1000G END APC : Sun Oct 05 10:21:22 EDT 2014 It probably isn't an issue, I just thought at first that my battery was 13 years old. I apologize for not providing more information in my first post.
October 5, 201411 yr Looking at one of my other units, it also shows the 2001-9-25 date !! This is on a unit I've never changed the battery on. I suspect the APC software only updates the battery date when you "tell" it you've replaced the battery, and I don't see a way to do this with the apcupsd package (it's not listed in the config file). The Windows control software has a way to update the date you changed the battery, but no such luck with the package we use. But as you've already concluded, it's not a problem -- just a bit of a nuisance [and now that I know about it, it'll bug me as well ]
Archived
This topic is now archived and is closed to further replies.