Click here to see reports of other supported models from Liebert.
|
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.3.0
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.runtime
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.vendorid
|
|
|
driver.version
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
2.2.1
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.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
unmapped.ups.powersummary.capacitygranularity1
|
|
|
unmapped.ups.powersummary.capacitymode
|
|
|
unmapped.ups.powersummary.designcapacity
|
|
|
unmapped.ups.powersummary.flowid
|
|
|
unmapped.ups.powersummary.imanufacturer
|
|
|
unmapped.ups.powersummary.iproduct
|
|
|
unmapped.ups.powersummary.powersummaryid
|
|
|
unmapped.ups.powersummary.rechargeable
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
