Click here to see reports of other supported models from XPCC.
|
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.4.1
Report #1
This device is known to work with driver powercom.
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
|
|
|
driver.name
|
|
|
driver.parameter.linevoltage
|
|
|
driver.parameter.manufacturer
|
|
|
driver.parameter.modelname
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.type
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.frequency
|
|
|
output.voltage
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.model.type
|
|
|
ups.serial
|
|
|
ups.status
|
|
2.2.2
Report #1
This device is known to work with driver powercom.
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
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.type
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.nominal
|
|
|
output.frequency
|
|
|
output.voltage
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.model.type
|
|
|
ups.serial
|
|
|
ups.status
|
|
