APC SMT3000RM2U replace battery LED came back after replacing battery

[Anonymous user]

Hi,

We have a 2 year old UPS "SMT3000RM2U" S/N: JS1052002648. We got 2 months ago the LED notifying us to change the battery. So we got a new one from APC, replaced it, after about 24 hours, made a self test and it was OK. After a week or so, the LED came back. try to do a self test, nothing, fails.

some of the info:

Device Status: On line (Green Mode), Replace battery

UPS Load 44.2%

Runtime Remaining 20

Minutes Internal Temperature 19.8°C / 67.6°F

Load Power 44.80% VA

Load Current 12.1 Amps

Manufacture Date Dec 2010

Battery Installation Date Feb 2013

Noticed that the Predicted Replacement Date Still says Mar 2011

Any ideas?

Thanks

[BillP]

Hello.

After reviewing this, to me, it seems like a battery problem. But then the fact that it is within a normal temperature range and the predicted replacement date still says 2011, makes me think the battery isn't actually bad.

I assume it reports 100% charged? If it is, run another self test, and if it still fails, let me know. It was also suggested to look to a firmware upgrade of the UPS incase we think this is something strange with the UPS firmware considering the predicted replace battery date did not update either.

[Anonymous user]

Thanks for the reply. I already tried another test and it failed again.

I will try to find a firmware updateif available

[BillP]

Alrighty. In our knowledge base, you can verify what the latest version is. Go to  http://www.apc.com/site/support/index.cfm/faq/ and search for FA164737. you can upgrade your UPS via the Firmware Upgrade Wizard (via serial cable on your model most likely) or via a network management card. I can't tell if you're using a management card or PowerChute Business Edition. Either method requires the UPS output to turn off to do the upgrade so plan accordingly.

[Anonymous user]

Hi,

Had to schedule it for the past weekend since my production switches are connected to it. Firmware updated, the error disappeared and the predicted date changed to 2017. All OK now.

Big Thanks

[BillP · Accepted solution]

Glad to hear!