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

Power Off (killpower) of UPS Does Not Work:
Currently (as of 3.10.6) the code to power off the UPS works only if you have
a Linux kernel version 2.4.22 or greater, or you have applied the patches in
the examples directory to your kernel.
apcupsd Cannot Reconnect After a Reboot:
If apcupsd does not connect to the USB port when you reboot, it is probably
the appropriate kernel modules are not getting loaded correctly.
You can check this by bringing up your system, fiddling around until you
get apcupsd to work with the UPS, then doing cat /proc/modules andnd
save the output some place. Then reboot your computer and before you do
anything else, do the cat /proc/modules again. Most likely you will find
some of the usb modules are missing in the second listing.
There are two solutions:
• Ensure that you have the hotplug program loaded. It should fix the
problem. This is a bit of magic, so we are not exactly sure how it
works. The rpm I (Kern) have loaded is: hotplug-2001
02 14-15
You might want to read the man page on hotplug, and it might be
necessary to cp /etc/hotplug/usb.rc /etc/init.d/hotplug to get
it fully working.
• You can explicitly force the appropriate usb modules to be loaded by
adding:
/sbin/modprobe <missing-module-name>
in the /etc/rc.d/init.d/apcupsd script just after the start) case (at
about line 17). This will force the modules to be loaded before apcupsd
is invoked.
Monitoring and Tuning your UPS
After you have verified that your UPS is working correctly, you will probably
want to query the state of its health occasionally. The tools apcupsd gives
71










