×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
So, what do YOU do? How do you come to the determination of needed battery
time? Do you just want to handle one time through, or more?
At a prior employer, I wrote the UPS power handling programs. One ran
when the UPS was running (i.e. discharging the batteries). It
decremented a 'battery time left' data area for each minute it was on.
(dlyjob) If it reached the 'gotta stop now' limit, it forced a shutdown.
There was a second program that was a NEP that incremented the data area
once every 5 minutes, but only if the discharge program was not active.
This way if there were multiple outages, the 'remaining capacity'
count was reasonable (but low, on the side of caution.)
The flaw in the ointment was when the S/38, er, System i was powered
down for a long time after the UPS was exhausted. The data area would
read 'low' but the actual batteries were fully charged. Never automated
that, but had a note on the console to check the UPS capacity and adjust
the data area when IPLing.
--buck
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
