1
.TH mge-utalk 8 "Wed Mar 10 2004" "" "Network UPS Tools (NUT)"
1
.TH mge\-utalk 8 "Mon Mar 07 2005" "" "Network UPS Tools (NUT)"
3
mge-utalk \- Driver for MGE UPS SYSTEMS UTalk protocol hardware
3
mge\(hyutalk \- Driver for MGE UPS SYSTEMS UTalk protocol hardware
5
This man page only documents the hardware-specific features of the
6
mge-utalk driver. For information about the core driver, see
5
This man page only documents the hardware\(hyspecific features of the
6
mge\(hyutalk driver. For information about the core driver, see
9
9
.SH SUPPORTED HARDWARE
10
mge-utalk supports the following models:
10
mge\(hyutalk supports the following models:
12
12
Pulsar Evolution (Serial port),
17
18
Pulsar / Comet EXtreme,
18
19
Comet / Galaxy (Serial card)
31
32
.IP "OffDelay=\fIvalue\fR"
32
33
Delay before shutdown, in seconds (default 120 seconds)
36
Set this flag if you are running Linux on an Oldworld Macintosh box
37
(all beige Apple Macintosh). This might also be needed for other
38
OSs (like *BSD) running on PowerMac.
34
40
.SH IMPLEMENTATION DETAILS
36
Not all MGE UPS models provide all possible information. mge-utalk
42
Not all MGE UPS models provide all possible information. mge\(hyutalk
37
43
checks on startup which variables and commands are available from
38
the UPS, and re-reads these regularly. Thus, startup is a bit slow,
44
the UPS, and re\(hyreads these regularly. Thus, startup is a bit slow,
39
45
but this should not matter much.
41
mge-utalk.h defines a struct array that tells the driver how to read
47
mge\(hyutalk.h defines a struct array that tells the driver how to read
42
48
variables from the UPS and publish them as NUT data.
44
50
"ups.status" variable is not included in this array, since it
55
61
from/to the UPS to re synchronise the communication.
58
.SS "Repetitive stale status - Loss of communication"
64
.SS "Repetitive stale status \(hy Loss of communication"
60
66
Older models, such as ES/ESV ones, might report repetitive "data stale"
61
67
errors. This is due to the fact that these models doesn't support too
68
.IP "Option -d (setting sddelay)"
69
Ignored for now, the driver should wait this long before
70
it itself shuts down. As Russell writes:
72
sddelay is supposed to be how long the _driver_ waits for the
73
shutdown, not necessarily the UPS. It's there so you can make the
74
driver stick around for awhile until the computer gets turned off.
75
If it exits, you should reboot, since something failed.
77
74
.IP "Sort out OFF/OL issues"
78
75
OFF is set according to Ls.2.7, but maybe this interpretation is in
79
76
conflict with the NUT interpretation of the OFF flag?
81
.IP "Sort out status_set(FSD) issue"
82
This flag is set when the UPS is in Shutdown Imminent state. But Russell
83
says the driver should set it... To be clarified.
85
.IP "Add selectable plug number for commands"
78
.IP "Add PowerSave support (selectable plug number for commands)"
86
79
ON/OFF/REBOOT commands can act either on outlet 1, 2 or main (1 + 2). This
87
features depends on the UPS model.
80
features depends on the UPS model. This would also allow to support
81
UM\(hySwitch (smart outlet).
90
Hans Ekkehard Plesser, Nicholas Reilly, Arnaud Quette, Dave Abbott,
84
Arnaud Quette, Hans Ekkehard Plesser, Martin Loyer, Patrick Agrain,
85
Nicholas Reilly, Dave Abbott, Marek Kralewski