Problem with Smart-UPS 1500 SUA1500I

[Anonymous user]

Hello everyone!

I have a Smart-UPS 1500 SUA1500I with a problem.

I replaced the batteries with a APC genuine RBC7 pack.

The UPS shows a fully charged battery.

If I disconnect the UPS ( no load attached to the UPS ) from the mains the battery indicator drops from 5 leds ( full ) to 1 led.

I measured the battery's voltage and it is ok, 26,5 V

Please help me.

[BillP]

Hi,

Have you performed a runtime calibration? See Schneider Electric FAQ FA284198

[Anonymous user]

Hi Bill,

Happy New Year !

Thanks for your reply.

I cannot perform a runtime calibration because if I disconnect the UPS ( with no load attached to the it ) from the mains the battery indicator on the UPS goes from fully charged ( 5 LED ) to fully discharged ( 1 LED ) in that second.

[BillP]

Hi Florin - 

You can try running a manual calibration. To do this you would want to attach a load that can safely be dropped when the UPS runs out of battery power. This load should be 30% or more and not vary more than 5%. Unplug the UPS from utility power and let it run until it drops the load. You will likely find that the battery indicator on the UPS immediately drops to 1 LED, but then runs for the expected amount of runtime. Do not turn the UPS off before the load drops. Once the load drops, plug the UPS back in and allow it to charge back up to 100%. You should now see that the battery charge indicator counts down as expected when the UPS switches to battery. If you continue to have issues I would advise contacting tech support.

Liam

[Anonymous user]

Hi Liam,

Yesterday I managed to find a suitable load to perform the manual calibration that you sugested. I found a room heater with 3 heating elements, each 400 watt. The heater had the option to select the number of heating elements active.

I set the room heater in 400 watt and then performed the manual calibration. The manual calibration ran for almost 50 minutes. 

The UPS is fine now.

Thank you very much for your help.

[SamirD_apc · Accepted solution]

Great to hear a recalibration solved this issue. 🙂