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.0.2
Report #1
This device is known to work with driver liebert.
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):
|
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
Report #2
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.
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
