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.8.0
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.charge.warning
|
|
battery.type
|
|
battery.voltage
|
Not zero with NUT v2.7.4 on same HW |
battery.voltage.nominal
|
Not zero with NUT v2.7.4 on same HW |
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.bus
|
|
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
|
|
driver.version.usb
|
|
input.frequency
|
|
input.voltage
|
Not zero with NUT v2.7.4 on same HW |
output.voltage
|
Not zero with NUT v2.7.4 on same HW |
ups.load
|
|
ups.mfr
|
|
ups.model
|
|
ups.productid
|
|
ups.serial
|
|
ups.status
|
|
ups.vendorid
|
|
About this device
As discussed in the mailing list thread, this device showed zeroed readings for battery, input and output voltages with NUT v2.8.0/libusb-1.0/aarch64 posted here, while it shows correct information with NUT v2.7.4/libusb-0.1/armv7l. It is anticipated that NUT v2.8.2 or later would include a fix.
Except for those marked, all values in 2.8.0 are correct. |
Reported at:
Further system data or configuration example:
Network UPS Tools - UPS driver controller 2.8.0
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
USB communication driver (libusb 1.0) 0.43
Using subdriver: Belkin/Liebert HID 0.18
LineVoltage exponent looks wrong, but not correcting.
LineVoltage exponent looks wrong, but not correcting.
LineVoltage exponent looks wrong, but not correcting.
ConfigVoltage exponent looks wrong, but not correcting.
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.charge.warning
|
|
battery.type
|
|
battery.voltage
|
|
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.bus
|
|
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
As discussed in the mailing list thread, this device showed zeroed readings for battery, input and output voltages with NUT v2.8.0/libusb-1.0/aarch64 (packaged), while it shows correct information with NUT v2.7.4/libusb-0.1/armv7l posted here. It is anticipated that NUT v2.8.2 or later would include a fix.
Reported at:
Further system data or configuration example:
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Using subdriver: Belkin/Liebert HID 0.17