tripplite_usb(8)

1TRIPPLITE_USB(8)            Network UPS Tools (NUT)           TRIPPLITE_USB(8)
2
3
4

NAME

6       tripplite_usb - Driver for older Tripp Lite USB UPSes (non-PDC HID)
7

NOTE

9       This man page only documents the hardware-specific features of the
10       tripplite_usb driver.  For information about the core driver, see
11       nutupsdrv(8).
12

SUPPORTED HARDWARE

14       This driver should work with older Tripp Lite UPSes which are detected
15       as USB HID-class devices, but are not true HID Power-Device Class
16       devices.  So far, the devices supported by tripplite_usb have product
17       ID 0001, and the newer units (such as those with "LCD" in the model
18       name) with product ID 2001 will work with the newhidups driver instead.
19       Please report success or failure to the nut-upsuser mailing list.  A
20       key piece of information is the protocol number, returned in
21       ups.debug.0.  Also, be sure to turn on debugging ("-DDD") for more
22       informative log messages.  If your Tripp Lite UPS uses a serial port,
23       you may wish to investigate the tripplite(8) or tripplite_su(8) driver.
24
25       This driver has been tested with the following models:
26
27       * OMNISV1000
28       * OMNISV1500XL (some warnings)
29       * SMART1500RM2U
30       * SMART2200RMXL2U
31       * SMART3000RM2U
32

EXTRA ARGUMENTS

34       This driver supports the following optional setting in the ups.conf(5)
35       file (or with "-x" on the command line):
36
37       offdelay
38           This setting controls the delay between receiving the "kill" com‐
39           mand ("-k") and actually cutting power to the computer.
40
41       bus This regular expression is used to match the USB bus (as seen in
42           "/proc/bus/usb/devices" or lsusb(8); including leading zeroes).
43
44       product
45           A regular expression to match the product string for the UPS.  This
46           would be useful if you have two different Tripp Lite UPS models
47           connected to the system, and you want to be sure that you shut them
48           down in the correct order.
49
50           Note that this regex is matched against the full USB product string
51           as seen in lsusb(8). The "ups.model" in the "upsc" output only
52           lists the name after "TRIPP LITE", so to match a SMART2200RMXL2U,
53           you could use the regex ".*SMART2200.*".
54
55       productid
56           The productid is a regular expression which matches the UPS PID as
57           four hexadecimal digits.  So far, the only devices that work with
58           this driver have PID 0001.
59
60       serial
61           It does not appear that these particular Tripp Lite UPSes use the
62           iSerial descriptor field to return a serial number.  However, in
63           case your unit does, you may specify it here.
64
65       For more information on regular expressions, see regex(7)
66

RUNTIME VARIABLES

68       ups.delay.shutdown
69           This variable is the same as the "offdelay" setting, but it can be
70           changed at runtime by upsrw(8).
71

KNOWN ISSUES AND BUGS

73       The driver was not developed with any official documentation from Tripp
74       Lite, so certain events may confuse the driver. If you observe any
75       strange behavior, please re-run the driver with "-DDD" to increase the
76       verbosity.
77
78       So far, the Tripp Lite UPSes do not seem to have any serial number or
79       other unique identifier accessible through USB. Thus, when monitoring
80       several Tripp Lite USB UPSes, you should use either the "bus" or "prod‐
81       uct" configuration options to uniquely specify which UPS a given driver
82       instance should control.
83
84       For instance, you can easily monitor an OMNIVS1000 and a SMART1500RM2U
85       at the same time, since they have different USB Product ID strings. If
86       you have two SMART1500RM2U units, you would have to find which USB bus
87       number each unit is on (via "lsusb"), which may result in ambiguities
88       if the available USB ports are on the same bus.
89
90       Some of the SMART*2U models seem to have an ID number that could be
91       used in a future version of this driver to monitor multiple similar
92       UPSes.
93

AUTHORS

95       Charles Lepple <clepple+nut@ghz.cc>, based on the tripplite driver by
96       Rickard E. (Rik) Faith <faith@alephnull.com> and Nicholas Kain
97       <nicholas@kain.us>.
98
99       A Tripp Lite OMNIVS1000 was graciously donated to the NUT project by:
100
101           Relevant Evidence, LLC.
102
103           http://www.relevantevidence.com
104
105           Email: info@relevantevidence.com
106