02.12.2015 Views

Network UPS Tools User Manual

Network UPS Tools User Manual

Network UPS Tools User Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Network</strong> <strong>UPS</strong> <strong>Tools</strong> <strong>User</strong> <strong>Manual</strong> 3 / 84<br />

2.8.1 Extra Settings<br />

Some drivers may require additional settings to properly communicate with your hardware. If it doesn’t detect your <strong>UPS</strong> by<br />

default, check the driver’s man page or help (-h) to see which options are available.<br />

For example, the usbhid-ups driver allows you to use USB serial numbers to distinguish between units via the "serial" configuration<br />

option. To use this feature, just add another line to your ups.conf section for that <strong>UPS</strong>:<br />

[sparky]<br />

driver = usbhid-ups<br />

port = auto<br />

serial = 1234567890<br />

2.8.2 Hardware Compatibility List<br />

The Hardware Compatibility List is available in the source directory (nut-X.Y.Z/data/driver.list), and is generally distributed with<br />

packages. For example, it is available on Debian systems as:<br />

/usr/share/nut/driver.list<br />

This table is also available online.<br />

If your driver has vanished, see the FAQ and Upgrading notes.<br />

2.8.3 Generic Device Drivers<br />

NUT provides several generic drivers that support a variety of very similar models.<br />

• The genericups driver supports many serial models that use the same basic principle to communicate with the computer.<br />

This is known as "contact closure", and basically involves raising or lowering signals to indicate power status.<br />

This type of <strong>UPS</strong> tends to be cheaper, and only provides the very simplest data about power and battery status. Advanced<br />

features like battery charge readings and such require a "smart" <strong>UPS</strong> and a driver which supports it.<br />

See the genericups(8) man page for more information.<br />

• The usbhid-ups driver attempts to communicate with USB HID Power Device Class (PDC) <strong>UPS</strong>es. These units generally<br />

implement the same basic protocol, with minor variations in the exact set of supported attributes. This driver also applies<br />

several correction factors when the <strong>UPS</strong> firmware reports values with incorrect scale factors.<br />

See the usbhid-ups(8) man page for more information.<br />

• The blazer_ser and blazer_usb drivers supports the Megatec / Q1 protocol that is used in many brands (Blazer, Energy<br />

Sistem, Fenton Technologies, Mustek and many others).<br />

See the blazer(8) man page for more information.<br />

• The snmp-ups driver handles various SNMP enabled devices, from many different manufacturers. In SNMP terms, snmpups<br />

is a manager, that monitors SNMP agents.<br />

See the snmp-ups(8) man page for more information.<br />

• The powerman-pdu is a bridge to the PowerMan daemon, thus handling all PowerMan supported devices. The PowerMan<br />

project supports several serial and networked PDU, along with Blade and IPMI enabled servers.<br />

See the powerman-pdu(8) man page for more information.<br />

• The apcupsd-ups driver is a bridge to the Apcupsd daemon, thus handling all Apcupsd supported devices. The Apcupsd<br />

project supports many serial, USB and networked APC <strong>UPS</strong>.<br />

See the apcupsd-ups(8) man page for more information.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!