User's Manual UPS control system
Table Of Contents
- Apcupsd User's Manual
- Release Notes
- How To Use This Manual
- Basic User's Guide
- Planning Your Installation
- Building and Installing apcupsd
- After Installation
- Configuration Examples
- Testing Apcupsd
- Troubleshooting Your Installation
- Monitoring and Tuning your UPS
- Maintaining Your UPS
- Frequently-Asked Questions
- Apcupsd Bugs
- Advanced topics
- Customizing Event Handling
- Master/Slave Configurations
- Controlling Multiple UPSes on one Machine
- Support for SNMP UPSes
- Alternate Ways To Run The Network Information Server
- apcupsd System Logging
- Installation: Windows
- Windows Version of apcupsd
- Installation: Serial-Line UPSes
- Overview of Serial-Interface UPSes
- Connecting a Serial-Line UPS to a USB Port
- Connecting a APC USB UPS to either a PC USB or Serial Port
- Cables
- Smart-Custom Cable for SmartUPSes
- Smart Signalling Cable for BackUPS CS Models
- Voltage-Signalling Cable for "dumb" UPSes
- Other APC Cables that apcupsd Supports
- Voltage Signalling Features Supported by Apcupsd for Various Cables
- Voltage Signalling
- Back-UPS Office 500 signals
- Analyses of APC Cables
- Win32 Implementation Restrictions for Simple UPSes
- Internal Apcupsd Actions for Simple Cables
- RS232 Wiring and Signal Conventions
- Pin Assignment for the Serial Port (RS-232C), 25-pin and 9-pin, Female End
- Ioctl to RS232 Correspondence
- Testing Serial-Line UPSes
- Troubleshooting Serial Line communications
- Recalibrating the UPS Runtime
- DATA Logging
- Technical Reference
- Configuration Directive Reference
- apcupsd Status Logging
- Shutown Sequence and its Discontents
- APC smart protocol
- Apcupsd --- RPM Packaging FAQ
- Credits
- Kernel Config
./configure \
--prefix=$HOME/apcupsd/bin \
--sbindir=$HOME/apcupsd/bin \
--enable-cgi \
--with-cgi-bin=$HOME/apcupsd/bin \
--with-log-dir=$HOME/apcupsd/bin \
--with-pid-dir=$HOME/apcupsd/bin \
--sysconfdir=$HOME/apcupsd/bin \
--with-lock-dir=$HOME/apcupsd/bin \
--with-pwrfail-dir=$HOME/apcupsd/bin \
--with-serial-dev=/dev/ttyS1 \
--enable-pthreads \
--with-nis-port=7001 \
--disable-install-distdir
Note, in this case, we use considerably more configuration options
to ensure that the system files are placed in a different directory
($HOME/apcupsd/bin). We have also selected a different serial port and a
different NIS (Network Information Server) port. And finally, we have used
the --disable-install-distdir option, which prevents make install
from doing the final system installation (i.e. the modification of the halt
script) since this was previously done.
Important Steps after Installation of the Second Copy:
After the make install of the second copy of apcupsd there are a number
important steps to complete. You must either remove or modify the file
$HOME/apcupsd/bin/apccontrol, so that it will not shutdown Computer
A when the battery of UPS 2 is low. One suggestion is to copy exam-
ples/safe.apccontrol into $HOME/apcupsd/bin/apccontrol. Alternatively,
you could edit the $HOME/apcupsd/bin/apccontrol and delete all state-
ments that attempt to shutdown the machine. Another important step is to
find a way to shutdown Computer B when UPS 2’s battery is low. Probably
the simplest way to do this is to edit $HOME/apcupsd/bin/apcupsd.conf
on Computer A so that this second copy of apcupsd becomes a network
master. Then install a standard slave configuration on Computer B. Please
remember that if UPS 1’s batteries are exhausted before UPS 2’s batteries,
Computer B may not be properly shutdown. And at the current time, there
is no simple means to make the two copies of apcupsd running on Com-
puter A communicate. Thus there are certain risks in such a configuration.
However, these configurations can be very useful for powering electronic
equipment and such.
If Computer B is vitally important, it would probably be better to purchase
112