[Nut-upsuser] clearing the 'Replace Battery' on Eaton 5PX
Dan Langille
dan at langille.org
Thu Jan 2 18:19:06 GMT 2025
On Sun, Dec 22, 2024, at 4:49 PM, Dan Langille via Nut-upsuser wrote:
> On Sun, Dec 22, 2024, at 2:53 PM, Dan Langille via Nut-upsuser wrote:
>> I thought I could clear the Eaton 5PX battery message. I've failed.
>>
>> The following is based on
>> https://haefelfinger.ch/posts/2020/2020-09-23-reset-battery-alert-eaton-5p-ups/
>>
>> I shutdown the UPS. I disconnected it from power. I disconnected both
>> the main battery and the external battery pack. I pressed the power on
>> button several times, until the clicking stopped....
>>
>> I waited 10 minutes. Connect it all back up. The warning persists.
>>
>> The webpage for the UPS the battery status is OK. That must be charge
>> level (90%).
>>
>> If I check from the command line:
>>
>> [19:41 r730-01 dvl ~] % upsc ups02 | grep -i alarm
>> ups.alarm: Replace battery!
>> ups.status: ALARM OL CHRG RB
>>
>> I've gone though the front panel options and didn't see anything for
>> resetting this warning.
>>
>> I have found one suggestion: update firmware.
>
> Update firmware does not seem to be an option, based on reading.
>
> I did a restore-factory-settings through the front panel:
>
> https://community.spiceworks.com/t/eaton-5px-2200rt-replacement-battery-alarm-firmware-update/766015/4
>
> I repeated the "drain the capacitors" procedure at the top of my first email.
>
> Interesting: the network setting persisted - I could get the UPS via
> the web UI - it still used the same IP address.
>
> However, connecting to the serial console, I get:
>
> Local database initialisation
> - state_bind_error -
> * END state_bind_error *
> Local database initialisation
> - state_bind_error -
> * END state_bind_error *
> Local database initialisation
> ... repeat
>
> From the host connected to the UPS via the USB cable:
>
> $ upsc ups02
> Error: Driver not connected
>
> I suppose they might all be related. It's dinner time. I can come back
> to this on Monday.
Happy New Year!
This problem has been solved. It was a disconnected cable.
The data cable connecting the UPS to the server was disconnected at the UPS end.
I reconnected the cable and started the UPS service on the host. All came back up.
For bonus points:
[18:17 r730-01 dvl ~] % upsc ups02 | grep -i alarm
[18:17 r730-01 dvl ~] %
The battery alarm has cleared.
--
Dan Langille
dan at langille.org
More information about the Nut-upsuser
mailing list