mge-utalkSection: Network UPS Tools (NUT) (8)Updated: Wed Mar 10 2004 |
mge-utalkSection: Network UPS Tools (NUT) (8)Updated: Wed Mar 10 2004 |
Pulsar Evolution (Serial port),
Pulsar ESV+,
Pulsar ES+,
Pulsar EL,
Pulsar EX,
Pulsar EXtreme C,
Pulsar / Comet EXtreme,
Comet / Galaxy (Serial card)
This driver supports the following optional settings in the ups.conf(5):
Not all MGE UPS models provide all possible information. mge-utalk checks on startup which variables and commands are available from the UPS, and re-reads these regularly. Thus, startup is a bit slow, but this should not matter much.
mge-utalk.h defines a struct array that tells the driver how to read variables from the UPS and publish them as NUT data.
"ups.status" variable is not included in this array, since it contains information that requires several calls to the UPS and more advanced analysis of the reponses. The function get_ups_status does this job.
Note that MGE enumerates the status "bits" from right to left, i.e., if buf[] contains the reponse to command "Ss" (read system status), then buf[0] contains "bit" Ss.1.7 (General alarm), while buf[7] contains "bit" Ss.1.0 (Load unprotected).
enable_ups_comm() is called before each attempt to read/write data from/to the UPS to re synchronise the communication.
Older models, such as ES/ESV ones, might report repetitive "data stale" errors. This is due to the fact that these models doesn't support too much polling. To solve this problem, add "pollinterval=20" in ups.conf, and change the value of MAXAGE to 25 in upsd.conf, and DEADTIME to 25 in upsmon.conf.