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
Startup
Normally, apcupsd is automatically started when your system is rebooted.
This normally occurs because the startup script apcupsd is linked into the
appropriate places in /etc/rc.d. On most Linux systems, there is a program
called chkconfig(8) that will automatically link the startup script. This
program is invoked by the make install scripts, or it is explicitly done for
those systems that do not have chkconfig(8). If this is not the case, you can
either link it in appropriately yourself or explicitly call it from your rc.local
file. The appropriate manual way to startup apcupsd is by executing:
<path>/apcupsd start
where <path> is normally /etc/rc.d or /etc/rc.d/init.d depending on your
system (isn’t Unix wonderful? :-)). Using this script is important so that
any files remaining around after a power failure are removed. Likewise,
shutting down apcupsd should be done with the same script:
<path>/apcupsd stop
Windows Considerations
Please see the end of Windows chapter (see Installation on Windows) of this
manual for conderations pertaining to shutdown and killpower on Windows.
APC smart protocol
The APC UPS protocol was originally analyzed by Pavel Korensky with
additions from Andre H. Hendrick beginning in 1995, and we want to give
credit for good, hard work, where credit is due. After having said that, you
will see that Steven Freed built much of the orginal apcupsd information
file. [Comment inserted by Riccardo Facchetti]
The start of this chapter of the apcupsd manual in HTML format was pulled
from the Network UPS Tools (NUT) site. It has been an invaluable tool in
improving apcupsd, and I consider it the Bible of APC UPS programming.
In the course of using it, I have added information gleaned from apcupsd
186










