Output Load threshold Exceeded on Smart-UPS 3000

[BillP]

Twice in past 48 hours unit has shutdown.  Events Log claims cause is "Output Load Threshold Exceeded" and "Insufficient Runtime Available" and "Overload", but Data Log seems to show normal numbers, so I'm puzzled.  Attached devices have not changed for at least 12 months.  Logs are attached.  Please advise.

Model = SUA3000l

Serial = JS0602017319 (first character might be "U")

Batteries replaced October 2014 and are rarely needed, and then only for short periods like tripped breakers.

[BillP]

Hi,

What version of PowerChute Business Edition Agent is installed and do you have the PowerChute Business Edition Server and Console installed? 

[BillP]

Thank you for your reply.

Smart-UPS Firmware Revision = 655.12.I

Agent version = 9.0.3.604

Host is Hyper-V 2008 Core.  Only Agent is installed on host.  Server and Console were not installed, but I have just now installed them on a Hyper-V Guest.  Status is green.  Ran reports and got following results:

Risk Assessment > only warning is UPS Age.

Voltage Analysis > 240-247.  

Power Event Analysis > No data.

Power Event Summary > No data.

[BillP]

Hi,

The power event summaries would not show anything since the PowerChute Server had just been installed. The PowerChute web Agent event log showed the events lasting for a few seconds so that could be why the data log is not recording the issue. The data log appears to be set to record every 20 minutes which is the default setting. 

In the web interface how do you have PowerChute configured? What events are set to trigger a system shut down?

[BillP]

Hi,

The following events are configured to trigger shutdown:

Communication Lost While On Battery

UPS Internal Temperature Threshold Exceeded

Low Battery

Overload

[BillP]

Hi Bill,

Any ideas?

Thanks, Richard

[BillP · Accepted solution]

Hi,

The log shows that both low battery and overload occurred so that is why the system powered down. The data log does not show the event but that most likely is because the data log is set to only capture every 20 minutes so the event/s were missed.