Feature requests for PowerChute Serial Shutdown

[breinersj]

I'd like to suggest a couple of enhancements (i.e., improved functionality) for PowerChute Serial Shutdown software - currently version 1.2.0.301.

1) Create a mechanism for accelerating the pace of periodic logging on the occurrence of designated events or condition... for instance, an input voltage drop should trigger acceleration of Data Logging from every 15 minutes to every 1 minute. Given the limited size capability (2000 events) of the event log and purported "performance issues" for frequent data logs, being able to set triggers for events and for increased data collection would allow more efficient storage and scrutiny of logs.

2) Add additional event triggers - e.g., input AC voltage spikes or drops (beyond user-settable thresholds) and option to trigger event logging at the start of battery load increases. In the attached log clipping, there were no events triggered by an unexpected (and seemingly unnecessary, given the input AC voltage) battery load shown in the attached graphic - which triggered an audible alert (waking me from a sound sleep), but did not log any events.

3) Make sure that event entries specify precisely what condition(s) triggered an event (this suggested "enhancement" may actually already be implemented, but since no event entries were created in this case, I include it here for good measure, in case not).

All in all, I'm reasonably satisfied with PCSS, as it provides a reasonable tool for monitoring UPS status, but could be at least a little bit better.

SJB

[RyanG32]

Typically instead of listing it on the data logs the PCBE PCSS software logs events 

Please see list of all events created by PowerChute Business Edition and PowerChute Serial Shutdown that will be logged in the Windows Event Viewer in this article

https://www.se.com/us/en/faqs/FA228995/

Low Voltage and High Voltage usually triggers AVR Boost and AVR Trim if it goes beyond UPS will go on Battery.

[breinersj]

I would note that there is an Event Log in the PCSS software - it just doesn't work (at least with my installation). Give that there is one offered by PCSS, I shouldn't have to rely inspection of Windows Logs to see PCSS-related events. The Data Log you mention does work as expected (input and output voltage, battery levels etc.) - my suggestion was offered to suggest that the data log could be more useful, if its logging frequency were subject to conditions triggered by time-sensitive events.