tripplite_usb - Driver for older Tripp Lite USB UPSes (non-PDC HID) This man page only documents the hardware-specific features of the tripplite_usb driver. For information about the core driver, see nutupsdrv(8). This driver should work with older Tripp Lite UPSes which are detected as USB HID-class devices, but are not true HID Power-Device Class devices. So far, the devices supported by tripplite_usb have product ID 0001, and the newer units (such as those with "LCD" in the model name) with product ID 2001 will work with the usbhid-ups driver instead. Please report success or failure to the nut-upsuser mailing list. A key piece of information is the protocol number, returned in ups.debug.0. Also, be sure to turn on debugging ("-DDD") for more informative log messages. If your Tripp Lite UPS uses a serial port, you may wish to investigate the tripplite(8) or tripplite_su(8) driver. This driver has been tested with the following models: This driver supports the following optional setting in the ups.conf(5) file (or with "-x" on the command line): This setting controls the delay between receiving the "kill" command ("-k") and actually cutting power to the computer. This regular expression is used to match the USB bus (as seen in "/proc/bus/usb/devices" or lsusb(8); including leading zeroes). A regular expression to match the product string for the UPS. This would be useful if you have two different Tripp Lite UPS models connected to the system, and you want to be sure that you shut them down in the correct order. Note that this regex is matched against the full USB product string as seen in lsusb(8). The "ups.model" in the "upsc" output only lists the name after "TRIPP LITE", so to match a SMART2200RMXL2U, you could use the regex ".*SMART2200.*". The productid is a regular expression which matches the UPS PID as four hexadecimal digits. So far, the only devices that work with this driver have PID 0001. It does not appear that these particular Tripp Lite UPSes use the iSerial descriptor field to return a serial number. However, in case your unit does, you may specify it here. For more information on regular expressions, see regex(7) This variable is the same as the "offdelay" setting, but it can be changed at runtime by upsrw(8). The driver was not developed with any official documentation from Tripp Lite, so certain events may confuse the driver. If you observe any strange behavior, please re-run the driver with "-DDD" to increase the verbosity. So far, the Tripp Lite UPSes do not seem to have any serial number or other unique identifier accessible through USB. Thus, when monitoring several Tripp Lite USB UPSes, you should use either the "bus" or "product" configuration options to uniquely specify which UPS a given driver instance should control. For instance, you can easily monitor an OMNIVS1000 and a SMART1500RM2U at the same time, since they have different USB Product ID strings. If you have two SMART1500RM2U units, you would have to find which USB bus number each unit is on (via "lsusb"), which may result in ambiguities if the available USB ports are on the same bus. Some of the SMART*2U models seem to have an ID number that could be used in a future version of this driver to monitor multiple similar UPSes. Charles Lepple <clepple+nut@ghz.cc>, based on the tripplite driver by Rickard E. (Rik) Faith <faith@alephnull.com> and Nicholas Kain <nicholas@kain.us>. A Tripp Lite OMNIVS1000 was graciously donated to the NUT project by: Relevant Evidence, LLC. http://www.relevantevidence.com Email: info@relevantevidence.com

The core driver:
nutupsdrv(8), regex(7), usbhid-ups(8)

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