File: richcomm_usb.8

package info (click to toggle)
nut 2.4.3-1.1squeeze2
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 5,816 kB
  • ctags: 5,658
  • sloc: ansic: 45,735; sh: 11,290; makefile: 668; python: 448; perl: 179
file content (35 lines) | stat: -rw-r--r-- 1,296 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
.TH RICHCOMM_USB 8 "Sat Dec 27 2008" "" "Network UPS Tools (NUT)"
.SH NAME
richcomm_usb \- Driver UPS equipment using Richcomm dry\(hycontact to USB
solution

.SH NOTE
This man page only documents the specific features of the richcomm_usb 
driver.  For information about the core driver, see \fBnutupsdrv\fR(8).

.SH SUPPORTED HARDWARE
The Richcomm dry\(hycontact to USB solution is a generic interface that is
used to upgrade an existing (RS-232) contact closure UPS interface to USB.
As such, all the limitations of the underlying contact closure interface
apply.  This means that you will only get the essentials in ups.status: OL,
OB, and LB.  See also \fBgenericups\fR(8).

.SH BUGS
Most contact\(hyclosure UPSes will not power down the load if the line power 
is present.  This can create a race when using slave \fBupsmon\fR(8) 
systems.  See the \fBupsmon\fR(8) man page for more information.

The solution to both of these problems is to upgrade to a smart protocol 
UPS of some kind that allows detection and proper load cycling on command.

.SH AUTHORS
Peter van Valderen <p.v.valderen at probu.nl>
Dirk Teurlings <dirk at upexia.nl>

.SH SEE ALSO

.SS The core driver:
\fBnutupsdrv\fR(8)

.SS Internet resources:
The NUT (Network UPS Tools) home page: http://www.networkupstools.org/