Click here to see reports of other supported models from Powercom.
|
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.6.5
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.date
|
|
|
battery.runtime
|
|
|
battery.type
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.frequency
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.date
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
beeper.toggle
The beeper is not disabled.
The ability to disable the beeper had been added by Powercom in 2010 only. So UPS devices built after 2010 should support this option.
It turned out that according to the UPS serial number it had been manufactured in 2012. So, the device should support the ability to disable the beeper. But still I can not disable the beeper using the latest version of UPSMON Plus in Windows.
However, beeper can be disabled with the button on the UPS (except when the device starts and the battery capacity is 0 the beeper should/will work); NUT gets the correct value now:
$ upsc powercom ups.beeper.status disabled -
test.battery.start.quick
2.4.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.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.date
|
|
|
battery.runtime
|
|
|
battery.type
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.productid
|
|
|
driver.parameter.vendorid
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.frequency
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.date
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.timer.shutdown
|
|
|
ups.timer.start
|
|
|
ups.vendorid
|
|
