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.7.4
Report #1 with driver usbhid-ups (detailed comments available)
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.
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.charge.low
|
|
|
battery.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.productid
|
|
|
driver.parameter.synchronous
|
|
|
driver.parameter.vendorid
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
output.voltage
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
About this device
The previously reported issue with the driver crashing is still present.
You can be forgiven for believing that it might be working because upsc
is able to return some information for a while until the driver crashes.
After that, only restarting the driver will fix it…
Reported at:
2.0.2
Report #1 with driver liebert (detailed comments available)
This device is known to work with driver liebert.
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):
|
driver.name
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.status
|
|
About this device
Starts OK, but fails to detect any events I tried (pulling mains, and pulling the serial cable).
Connection: Original RS232 cable
Reported at:
Report #2 with driver hidups (detailed comments available)
This device is known to work with driver hidups, now replaced by the usbhid-ups one.
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.chemistry
|
|
|
battery.runtime
|
|
|
driver.name
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.serial
|
|
|
ups.status
|
|
About this device
Driver recognizes UPS and its state, but crashes and has to be restarted after every (so far) event.
Connection: Original USB cable
Reported at:
