Click here to see reports of other supported models from PowerWalker.
|
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.7.4.1
Report #1 with driver usbhid-ups (detailed comments available)
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.
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.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.type
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.flag.ignorelb
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.voltage
|
|
|
outlet.1.status
|
|
|
output.frequency
|
|
|
output.frequency.nominal
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.power.nominal
|
|
|
ups.productid
|
|
|
ups.realpower
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.test.result
|
|
|
ups.timer.shutdown
|
|
|
ups.timer.start
|
|
|
ups.type
|
|
|
ups.vendorid
|
|
About this device
Without the overrides and ignorelb posted in the ups.conf snippet,
the UPS not reporting Low Battery for some reason (tried running on battery
till the 1% battery.charge).
Charging status and battery.voltage is missing too (but they are present
with Phoenixtec/Liebert HID 0.3), as you can see. The ups.power.nominal and
ups.realpower values also looks strange.
Reported at:
Further system data or configuration examples:
[pw]
driver = usbhid-ups
desc = "PowerWalker VI 650 SH"
port = auto
ignorelb
override.battery.charge.warning = 30
override.battery.charge.low = 15
override.battery.runtime.low = 180
override.ups.model = "PowerWalker VI 650 SH"upscmd -l pw@localhost listing# TODO: Convert to CMD:... markup
:; upscmd -l pw@localhost
Instant commands supported on UPS [pw]:
beeper.disable - Disable the UPS beeper
beeper.enable - Enable the UPS beeper
beeper.mute - Temporarily mute the UPS beeper
beeper.off - Obsolete (use beeper.disable or beeper.mute)
beeper.on - Obsolete (use beeper.enable)
load.off - Turn off the load immediately
load.off.delay - Turn off the load with a delay (seconds)
load.on - Turn on the load immediately
load.on.delay - Turn on the load with a delay (seconds)
shutdown.return - Turn off the load and return when power is back
shutdown.stayoff - Turn off the load and remain off
shutdown.stop - Stop a shutdown in progress
test.battery.start.deep - Start a deep battery test
test.battery.start.quick - Start a quick battery test
test.battery.stop - Stop the battery testupsrw pw@localhost listing# TODO: Convert to RW:... and RO:... markup
:; upsrw pw@localhost
[output.voltage.nominal]
Nominal output voltage (V)
Type: ENUM
Option: "200"
Option: "208"
Option: "220"
Option: "230" SELECTED
Option: "240"
[ups.delay.shutdown]
Interval to wait after shutdown with delay command (seconds)
Type: STRING
Maximum length: 10
Value: 20
[ups.delay.start]
Interval to wait before (re)starting the load (seconds)
Type: STRING
Maximum length: 10
Value: 302.7.4
Report #1 with driver usbhid-ups (detailed comments available)
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.
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.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
About this device
Here is the output from FreeNas 11.0-U3
Reported at:
Report #2 with driver usbhid-ups (detailed comments available)
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.
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.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
About this device
Here is the output from FreeNas 11.0-U4.
UPS Notification works on FreeNas 11.0-U4 so I assume that the shutdown sequence should also work. If the service can detect a change, the service will probably shut down the machine also.
Reported at:
Report #3 with driver usbhid-ups (detailed comments available)
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.
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.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
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
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
About this device
And here for completeness the output from the PI running Armbian
Reported at:
2.7.3
Report #1 with driver usbhid-ups (detailed comments available)
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.
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.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.serial
|
literally all "0" |
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
still some COMMBAD dropouts with pollfreq=40/pollinterval=20 |
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
About this device
Shutdown sequence tested on FreeNAS-9.10.2-U1 (86c7ef5) successfully. Emails from FreeNAS received notifying of On Batt and Shutdown.
Reported at:
Vendor/Manufacturer information:
2.7.2
Report #1 with driver usbhid-ups (detailed comments available)
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.
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.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
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
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.productid
|
|
|
ups.serial
|
|
|
ups.status
|
|
|
ups.vendorid
|
|
About this device
Output from the PI running Armbian
Reported at:
