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

After which, you can do a:
make
And to install apcupsd, do:
make install
Finally, you should follow the Win32 (see Installation on Windows) instal-
lation instruction, skipping the part that describes unZipping the binary
release.
After Installation
Checking Your Configuration File
Once you have installed apcupsd, either from a binary package or
by building from source, your next step should be to inspect your
/etc/apcupsd/apcupsd.conf file to make sure it is valid.
You can read the complete reference on configuration directives (see
Configuration Directive Reference), but if you are setting up a normal stan-
dalone configuration you should only need to check (and possibly fix) the
first three items listed below.
Your UPSTYPE should be the UPS’s protocol type: dumb, apcsmart, usb,
net, snmp, or ether. Your UPSCABLE should be the type of cable you are
using. You should have gotten both from the table of types (see type table);
usually they will both be the string “usb”.
If you have a USB device, it is better not to specify a DEVICE direc-
tive by commenting it out. Apcupsd will automatically search for your
device in the standard places. If you specify a DEVICE, it should be the
name of the device (or device range) that apcupsd is to use to commu-
nicate with the UPS. If you’re using a USB UPS under Linux, you may
leave the device name field blank and apcupsd will search all the stan-
dard locations for the UPS. You may also explicitly specify the device lo-
cation as either /dev/usb/hid/hiddev[0-15] (on non-Red-Hat systems) or
/dev/usb/hiddev[0-15] (on Red Hat systems), but this is not recommended.
49










