Click here to see reports of other supported models from Online.
|
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.5
Report #1
This device is known to work with driver megatec, now replaced by the blazer_ser one. It may also work with driver nutdrv_qx.
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.voltage
|
|
|
driver.name
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
input.voltage.maximum
|
|
|
input.voltage.minimum
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.temperature
|
|
Report #2
This device is known to work with driver megatec, now replaced by the blazer_ser one. It may also work with driver nutdrv_qx.
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.voltage
|
|
|
driver.name
|
|
|
driver.parameter.mfr
|
|
|
driver.parameter.model
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
input.voltage.maximum
|
|
|
input.voltage.minimum
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.temperature
|
|
2.0.0
Report #1
This device is known to work with driver fentonups, now replaced by the blazer_ser one. It may also work with driver nutdrv_qx.
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.voltage
|
|
|
driver.name
|
|
|
driver.parameter.model
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.transfer.high
|
|
|
input.transfer.low
|
|
|
input.voltage
|
|
|
output.voltage
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.status
|
|
|
ups.temperature
|
|
Report #2
This device is known to work with driver fentonups, now replaced by the blazer_ser one. It may also work with driver nutdrv_qx.
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.voltage
|
|
|
driver.name
|
|
|
driver.parameter.model
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.transfer.high
|
|
|
input.transfer.low
|
|
|
input.voltage
|
|
|
output.voltage
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.status
|
|
|
ups.temperature
|
|
