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
9. To verify that your UPS is communicating with your computer and
will do the right thing when the power goes out, read and follow the
instructions in the Testing (see Testing Apcupsd) section.
10. If you run into problems, read the Troubleshooting (see
Troubleshooting Your Installation) section of this manual.
11. If you still need help, send a message to the developer’s email list
apcupsd-users at lists.sourceforge.net describing your problem, what
version of apcupsd you are using, what operating system you are using,
and anything else you think might be helpful.
12. Read the manual sections on monitoring and maintaining your UPS.
Supported Operating Systems, UPSes and Cables
Please note that due to the lack of Unix USB API standards, the USB code
in apcupsd works only on Linux and *BSD systems. In addition, at the
current release (3.10.17) the USB support for *BSD systems can at best be
considered BETA due to fragile kernel drivers. Drivers for other OSes can
be written, but it requires someone with a knowledge of the OS and the
USB to do so. (This lack of a Unix USB API interface is one of the big
failings of Unix. It occurs in other areas such as the GUI. Many people tout
the diversity as an advantage, but it is in fact a weakness.)
The apcupsd maintainers develop it under Fedora (Red Hat); that port is,
accordingly, the most up to date and best tested. There are enough Debian
Linux users that that port is also generally pretty fresh. Slackware Linux is
also fully supported.
apcupsd has also been ported to FreeBSD, NetBSD, OpenBSD, HP/UX,
Solaris, Alpha Unix and the Cygwin Unix emulation under Windows. It is
quite likely to work on those systems, though the port may occasionally get
stale and require minor tweaking.
In Operating System Specifics you’ll find operating-system-specific tips for
building and configuring apcupsd.
You can generally count on your UPS being supported if it has either
an Ethernet-connected SNMP interface or a USB interface with an APC-
supplied cable.
The “UPSTYPE Keyword” field is the value you will put in your
/etc/apcupsd/apcupd.conf file to tell apcupsd what type of UPS you have.
16