Click here to see reports of other supported models from Inform.
|
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 with driver megatec (detailed comments available)
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.
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.voltage
|
|
|
battery.voltage.nominal
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.frequency.nominal
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
input.voltage.maximum
|
|
|
input.voltage.minimum
|
|
|
input.voltage.nominal
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.temperature
|
Not polled, always @ |
|
ups.type
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
beeper.toggle
Not working
-
load.off
Not tested
-
load.on
Not tested
-
reset.input.minmax
Not working
-
reset.watchdog
Not working
-
shutdown.return
Not tested
-
shutdown.stayoff
Not tested
-
shutdown.stop
Not tested
-
test.battery.start
Not working
-
test.battery.start.deep
Not working
-
test.battery.stop
Not working
About this device
Reported at:
