1TRIPPLITE_USB(8) NUT Manual TRIPPLITE_USB(8)
2
6 tripplite_usb - Driver for older Tripp Lite USB UPSes (not PDC HID)
7
9 tripplite_usb -h
10 tripplite_usb -a UPS_NAME [OPTIONS]
12
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 ID
17 0001, and the newer units (such as those with "LCD" in the model name)
18 with product ID 2001 require the usbhid-ups(8) driver instead. Please
19 report success or failure to the nut-upsuser mailing list. A key piece
20 of information is the protocol number, returned in ups.debug.0. Also,
21 be sure to turn on debugging (-DDD) for more informative log messages.
22 If your Tripp Lite UPS uses a serial port, you may wish to investigate
23 the tripplite(8) or tripplite_su(8) driver.
24 This driver has been tested with the following models:
26 · INTERNETOFFICE700
28 · OMNIVS1000
30 · OMNIVS1500XL (some warnings)
32 · SMART700USB
34 · SMART1500RM2U
36 · SMART2200RMXL2U
38 · SMART3000RM2U
40 If you have used Tripp Lite’s PowerAlert software to connect to your
42 UPS, there is a good chance that tripplite_usb will work if it uses one
43 of the following protocols:
44 · Protocol 0004
46 · Protocol 1001
48 · Protocol 2001
50 · Protocol 3003
52 On the other hand, if the web page for your UPS on the Tripp-Lite
54 website says "HID-compliant USB port also enables direct integration
55 with built-in power management and auto-shutdown features of Windows
56 and MAC OS X", then you should use the usbhid-ups(8) driver instead.
57
59 This driver supports the following optional settings in the ups.conf(5)
60 file (or with -x on the command line):
61 offdelay
63 This setting controls the delay between receiving the "kill"
64 command (-k) and actually cutting power to the computer.
65 bus
67 This regular expression is used to match the USB bus (as seen in
68 /proc/bus/usb/devices or lsusb(8); including leading zeroes).
69 product
71 A regular expression to match the product string for the UPS. This
72 would be useful if you have two different Tripp Lite UPS models
73 connected to the system, and you want to be sure that you shut them
74 down in the correct order.
75 Note
77 This regex is matched against the full USB product string as seen
78 in lsusb(8). The ups.model in the upsc(1) output only lists the
79 name after TRIPP LITE, so to match a SMART2200RMXL2U, you could use
80 the regex .*SMART2200.*.
81 productid
83 The productid is a regular expression which matches the UPS PID as
84 four hexadecimal digits. So far, the only devices that work with
85 this driver have PID 0001.
86 serial
88 It does not appear that these particular Tripp Lite UPSes use the
89 iSerial descriptor field to return a serial number. However, in
90 case your unit does, you may specify it here.
91 For more information on regular expressions, see regex(7)
93
95 ups.delay.shutdown
96 This variable is the same as the offdelay setting, but it can be
97 changed at runtime by upsrw(8).
98 ups.id
100 Some SMARTPRO models feature an ID that can be set and retrieved.
101 If your UPS supports this feature, this variable will be listed in
102 the output of upsrw(8).
103 outlet.1.switch
105 Some Tripp Lite units have a switchable outlet (usually outlet #1)
106 which can be turned on and off by writing 1 or 0, respectively, to
107 outlet.1.switch with upsrw(8). If your unit has multiple switchable
108 outlets, substitute the outlet number for 1 in the variable name.
109 Be sure to test this first - there is no other way to be certain
110 that the number used by the driver matches the label on the unit.
111
113 The driver was not developed with any official documentation from Tripp
114 Lite, so certain events may confuse the driver. If you observe any
115 strange behavior, please re-run the driver with -DDD to increase the
116 verbosity.
117 So far, the Tripp Lite UPSes do not seem to have a serial number or
119 other globally unique identifier accessible through USB. Thus, when
120 monitoring several Tripp Lite USB UPSes, you should use either the bus
121 or product configuration options to uniquely specify which UPS a given
122 driver instance should control.
123 For instance, you can easily monitor an OMNIVS1000 and a SMART1500RM2U
125 at the same time, since they have different USB Product ID strings. If
126 you have two SMART1500RM2U units, you would have to find which USB bus
127 number each unit is on (via lsusb(8)), which may result in ambiguities
128 if the available USB ports are on the same bus.
129 Some of the SMART*2U models have an ID number, but because this ID is
131 not exposed as a USB string descriptor, there is no easy way to use
132 this ID to distinguish between multiple UPS units on a single machine.
133 The UPS would need to be claimed by the driver in order to read this
134 ID.
135
137 Written by Charles Lepple, based on the tripplite(8) driver by Rickard
138 E. (Rik) Faith and Nicholas Kain. Please do not email the authors
139 directly - use the nut-upsdev mailing list.
140 A Tripp Lite OMNIVS1000 was graciously donated to the NUT project by
142 Bradley Feldman (http://www.bradleyloritheo.com)
143
145 The core driver:
146 nutupsdrv(8)
147 Other drivers for Tripp-Lite hardware:
149 tripplite(8), tripplitesu(8), usbhid-ups(8)
150 Other tools:
152 regex(7), lsusb(8)
153
155 The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
156Network UPS Tools 09/15/2011 TRIPPLITE_USB(8)