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 battery_min, battery_max
67 These floating-point values correspond to the "empty" (10%) and
68 "full" (100%) voltages of the battery. They are used for an
69 approximation of the battery state-of-charge. The calculated
70 battery.charge value will be clamped to the range of 10% through
71 100%, so the resting voltage of the charged battery can be used for
72 battery_max, and the higher float charge voltage should not cause
73 problems.
74 bus
76 This regular expression is used to match the USB bus (as seen in
77 /proc/bus/usb/devices or lsusb(8); including leading zeroes).
78 product
80 A regular expression to match the product string for the UPS. This
81 would be useful if you have two different Tripp Lite UPS models
82 connected to the system, and you want to be sure that you shut them
83 down in the correct order.
84 Note
86 This regex is matched against the full USB product string as seen
87 in lsusb(8). The ups.model in the upsc(1) output only lists the
88 name after TRIPP LITE, so to match a SMART2200RMXL2U, you could use
89 the regex .*SMART2200.*.
90 productid
92 The productid is a regular expression which matches the UPS PID as
93 four hexadecimal digits. So far, the only devices that work with
94 this driver have PID 0001.
95 serial
97 It does not appear that these particular Tripp Lite UPSes use the
98 iSerial descriptor field to return a serial number. However, in
99 case your unit does, you may specify it here.
100 For more information on regular expressions, see regex(7)
102
104 ups.delay.shutdown
105 This variable is the same as the offdelay setting, but it can be
106 changed at runtime by upsrw(8).
107 ups.id
109 Some SMARTPRO models feature an ID that can be set and retrieved.
110 If your UPS supports this feature, this variable will be listed in
111 the output of upsrw(8).
112 outlet.1.switch
114 Some Tripp Lite units have a switchable outlet (usually outlet #1)
115 which can be turned on and off by writing 1 or 0, respectively, to
116 outlet.1.switch with upsrw(8). If your unit has multiple switchable
117 outlets, substitute the outlet number for 1 in the variable name.
118 Be sure to test this first - there is no other way to be certain
119 that the number used by the driver matches the label on the unit.
120
122 The driver was not developed with any official documentation from Tripp
123 Lite, so certain events may confuse the driver. If you observe any
124 strange behavior, please re-run the driver with -DDD to increase the
125 verbosity.
126 So far, the Tripp Lite UPSes do not seem to have a serial number or
128 other globally unique identifier accessible through USB. Thus, when
129 monitoring several Tripp Lite USB UPSes, you should use either the bus
130 or product configuration options to uniquely specify which UPS a given
131 driver instance should control.
132 For instance, you can easily monitor an OMNIVS1000 and a SMART1500RM2U
134 at the same time, since they have different USB Product ID strings. If
135 you have two SMART1500RM2U units, you would have to find which USB bus
136 number each unit is on (via lsusb(8)), which may result in ambiguities
137 if the available USB ports are on the same bus.
138 Some of the SMART*2U models have an ID number, but because this ID is
140 not exposed as a USB string descriptor, there is no easy way to use
141 this ID to distinguish between multiple UPS units on a single machine.
142 The UPS would need to be claimed by the driver in order to read this
143 ID.
144
146 Written by Charles Lepple, based on the tripplite(8) driver by Rickard
147 E. (Rik) Faith and Nicholas Kain. Please do not email the authors
148 directly - use the nut-upsdev mailing list.
149 A Tripp Lite OMNIVS1000 was graciously donated to the NUT project by
151 Bradley Feldman (http://www.bradleyloritheo.com)
152
154 The core driver:
155 nutupsdrv(8)
156 Other drivers for Tripp-Lite hardware:
158 tripplite(8), tripplitesu(8), usbhid-ups(8)
159 Other tools:
161 regex(7), lsusb(8)
162
164 The NUT (Network UPS Tools) home page: http://www.networkupstools.org/
165Network UPS Tools 2.7.3. 12/29/2015 TRIPPLITE_USB(8)