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.7.2
Report #1
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.
Known supported variables
This device is known to support the following variables (values are just examples):
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.version
|
|
driver.version.internal
|
|
input.voltage.nominal
|
|
ups.debug.0
|
|
ups.debug.D
|
|
ups.debug.L
|
|
ups.debug.M
|
|
ups.debug.P
|
|
ups.debug.S
|
|
ups.debug.T
|
|
ups.debug.V
|
|
ups.debug.load_banks
|
|
ups.delay.shutdown
|
|
ups.firmware
|
|
ups.firmware.aux
|
|
ups.id
|
|
ups.mfr
|
|
ups.model
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.status
|
ups.status is always empty (protocol 3005 was not yet supported in 2.7.2); it should be fixed in newer versions of NUT. |
ups.vendorid
|
|
Report #2
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.
Known supported variables
This device is known to support the following variables (values are just examples):
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.version
|
|
driver.version.internal
|
|
input.voltage.nominal
|
|
outlet.1.desc
|
|
outlet.1.id
|
|
outlet.1.switch
|
|
outlet.1.switchable
|
|
outlet.2.desc
|
|
outlet.2.id
|
|
outlet.2.switchable
|
|
ups.debug.D
|
|
ups.debug.L
|
|
ups.debug.M
|
|
ups.debug.P
|
|
ups.debug.S
|
|
ups.debug.T
|
|
ups.debug.V
|
|
ups.debug.load_banks
|
|
ups.delay.shutdown
|
|
ups.firmware
|
|
ups.firmware.aux
|
|
ups.id
|
|
ups.mfr
|
|
ups.model
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.status
|
|
ups.vendorid
|
|
Report #3
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.
Known supported variables
This device is known to support the following variables (values are just examples):
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.version
|
|
driver.version.internal
|
|
input.voltage.nominal
|
|
outlet.1.desc
|
|
outlet.1.id
|
|
outlet.1.switch
|
|
outlet.1.switchable
|
|
outlet.2.desc
|
|
outlet.2.id
|
|
outlet.2.switchable
|
|
ups.debug.D
|
|
ups.debug.L
|
|
ups.debug.M
|
|
ups.debug.P
|
|
ups.debug.S
|
|
ups.debug.T
|
|
ups.debug.V
|
|
ups.debug.load_banks
|
|
ups.delay.shutdown
|
|
ups.firmware
|
|
ups.firmware.aux
|
|
ups.id
|
|
ups.mfr
|
|
ups.model
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.status
|
|
ups.vendorid
|
|
Report #4
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.
Known supported variables
This device is known to support the following variables (values are just examples):
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.version
|
|
driver.version.internal
|
|
input.voltage.nominal
|
|
outlet.1.desc
|
|
outlet.1.id
|
|
outlet.1.switch
|
|
outlet.1.switchable
|
|
outlet.2.desc
|
|
outlet.2.id
|
|
outlet.2.switchable
|
|
ups.debug.D
|
|
ups.debug.L
|
|
ups.debug.M
|
|
ups.debug.P
|
|
ups.debug.S
|
|
ups.debug.T
|
|
ups.debug.V
|
|
ups.debug.load_banks
|
|
ups.delay.shutdown
|
|
ups.firmware
|
|
ups.firmware.aux
|
|
ups.id
|
|
ups.mfr
|
|
ups.model
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.status
|
|
ups.vendorid
|
|
Report #5
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.
Known supported variables
This device is known to support the following variables (values are just examples):
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.maximum
|
Wrong value; it should be fixed in newer versions of NUT. |
input.voltage.minimum
|
|
input.voltage.nominal
|
|
outlet.1.desc
|
|
outlet.1.id
|
|
outlet.1.switch
|
|
outlet.1.switchable
|
|
outlet.2.desc
|
|
outlet.2.id
|
|
outlet.2.switchable
|
|
ups.debug.D
|
|
ups.debug.L
|
|
ups.debug.M
|
|
ups.debug.P
|
|
ups.debug.S
|
|
ups.debug.T
|
|
ups.debug.V
|
|
ups.debug.load_banks
|
|
ups.delay.shutdown
|
|
ups.firmware
|
|
ups.firmware.aux
|
|
ups.id
|
|
ups.mfr
|
|
ups.model
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.status
|
|
ups.temperature
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
load.off
Not working.
-
load.on
Not working.
-
reset.input.minmax
-
shutdown.return
Not working.
-
test.battery.start