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
Project Discussions: APCUPSD Mailing List
Thanks to American Power Conversion (APC) who helped in giving techni-
cal information on their UPSes.
A special thanks to APC who gave me (Riccardo) a Smart UPS1400 INET
when my old Back UPS v/s 650’s battery died. Thank you guys, your help
has been invaluable.
Thanks to all the users that send bug reports and suggestions:we need your
help.
Thanks to every one I forgot here. If you feel Ihave forgot your name, please
don’t hesitate to tell me.
Miquel van Smoorenburg, The Doctor What, Pavel Korensky, and Russell
Kroll <rkroll at exploits.org> for the CGI programs. Jonathan Benson
<jbenson at technologist.com> for adapting the upsstatus.cgi program to
work with apcupsd
The gd 1.2 Image Library used in our CGI programs is copyright 1994,
1995, Quest Protein Database Center, Cold Spring Harbor Labs. Permission
granted to copy and distribute this work provided that this notice remains
intact. Credit for the library must be given to the Quest Protein Database
Center, Cold Spring Harbor Labs, in all derived works. This does not affect
your ownership of the derived work itself, and the intent is to assure proper
credit for Quest, not to interfere with your use of gd.
gd 1.2 was written by Thomas Boutell and is currently distributed by
boutell.com, Inc.
Parts of the VNC project by ATT (cool code) were used as templates for
our Win32 code, see: http://www.uk.research.att.com/vnc
Disclaimer: NO WARRANTY
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE
IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMIT-
TED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED
IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PAR-
TIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MER-
CHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
204










