Click here to see reports of other supported models from Tripp Lite.
|
When a user reports that a variable/command is not right then it will be highlighted by a red underline. Bad values/ranges/etc… will get a red dashed outline or red solid left border. The accompanying explaining comment - if provided - will be emphasized through a red dotted border on the left. |
2.4.3
Report #1 with driver tripplite_usb (detailed comments available)
This device is known to work with driver tripplite_usb.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.charge
|
|
|
battery.test.status
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.voltage
|
|
|
ups.debug.V
|
|
|
ups.debug.load_banks
|
|
|
ups.delay.shutdown
|
This variable can be set through upsrw to a string value. |
|
ups.firmware
|
|
|
ups.firmware.aux
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.power.nominal
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
shutdown.return
Report #2 with driver tripplite_usb (detailed comments available)
This device is known to work with driver tripplite_usb.
You can grab a dummy-ups compliant .dev file to simulate this device clicking here.
Some more detailed comments are available after the "Known supported…" sections.
Known supported variables
This device is known to support the following variables (values are just examples):
|
battery.charge
|
|
|
battery.test.status
|
After the UPS has come back to a full charge I get a red light on the front of the UPS and I get this. I made the bad battery message go away by running a ‘Self Test’ by holding down the Mute button for two seconds while the unit is powered on and everything connected to it is running. |
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.voltage
|
|
|
ups.debug.V
|
|
|
ups.debug.load_banks
|
|
|
ups.delay.shutdown
|
This variable can be set through upsrw to a string value. |
|
ups.firmware
|
|
|
ups.firmware.aux
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.power.nominal
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
shutdown.return
