Click here to see reports of other supported models from GE Digital Energy.
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.0
Report #1 with driver blazer_ser (detailed comments available)
This device is known to work with driver blazer_ser. 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.voltage
|
|
battery.voltage.nominal
|
|
beeper.status
|
|
device.type
|
|
driver.name
|
|
driver.parameter.cablepower
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.version
|
|
driver.version.internal
|
|
input.current.nominal
|
|
input.frequency
|
|
input.frequency.nominal
|
|
input.voltage
|
|
input.voltage.fault
|
|
input.voltage.nominal
|
|
output.voltage
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.load
|
|
ups.status
|
|
ups.temperature
|
|
ups.type
|
|
About this device
Reported at:
Report #2 with driver blazer_usb (detailed comments available)
This device is known to work with driver blazer_usb. 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.voltage
|
|
battery.voltage.nominal
|
|
beeper.status
|
|
device.type
|
|
driver.name
|
|
driver.parameter.bus
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.version
|
|
driver.version.internal
|
|
input.current.nominal
|
|
input.frequency
|
|
input.frequency.nominal
|
|
input.voltage
|
|
input.voltage.fault
|
|
input.voltage.nominal
|
|
output.voltage
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.load
|
|
ups.productid
|
|
ups.status
|
|
ups.temperature
|
|
ups.type
|
|
ups.vendorid
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
beeper.toggle
Returns
OK
, but seems to have no effect -
load.off
Returns
OK
, but seems to have no effect -
load.on
Returns
OK
, but seems to have no effect -
shutdown.return
Returns
OK
, but seems to have no effect -
shutdown.stayoff
Returns
OK
, but seems to have no effect -
shutdown.stop
Returns
OK
, but seems to have no effect -
test.battery.start
Returns
OK
, starts a test, UPS status changes toOL CAL
(didn’t wait for the test to finish) -
test.battery.start.deep
Returns
OK
, starts a test, UPS status changes toOL CAL
(didn’t wait for the test to finish) -
test.battery.start.quick
Returns
OK
, starts a test, UPS status changes toOL CAL
for a short time -
test.battery.stop
Returns
OK
, stops a test, UPS status changes back toOL
About this device
Issuing several test.battery.start* commands without test.battery.stop kills USB communication. The UPS needs to be disconnected and re-connected to USB before communication can be re-established.
Reported at: