Click here to see reports of other supported models from Cyber Power Systems.
|
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 usbhid-ups.
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.charge
|
|
|
battery.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.mfr.date
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.type
|
|
|
battery.voltage
|
To the value is applied a 0.667 scale that’s not needed; fixed in newer versions of NUT. |
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.offdelay
|
|
|
driver.parameter.ondelay
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.transfer.high
|
|
|
input.transfer.low
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.realpower.nominal
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.timer.shutdown
|
|
|
ups.timer.start
|
|
|
ups.vendorid
|
|
