Click here to see reports of other supported models from Eaton.
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.3
Report #1 with driver bcmxcp_usb (detailed comments available)
This device is known to work with driver bcmxcp_usb.
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):
ambient.temperature.high
|
|
ambient.temperature.low
|
|
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.shutdown_delay
|
|
driver.version
|
|
driver.version.internal
|
|
input.frequency.high
|
|
input.frequency.low
|
|
input.frequency.nominal
|
|
input.transfer.high
|
|
input.voltage.nominal
|
|
output.phases
|
|
output.voltage.nominal
|
|
ups.beeper.status
|
ups.beeper.status appears to not work: the beeper still goes on even though it displays as disabled. |
ups.firmware
|
|
ups.mfr
|
|
ups.model
|
|
ups.power.nominal
|
|
ups.serial
|
|
ups.status
|
|
Known supported commands
This device is known to support the following NUT’s instant commands:
-
shutdown.return
-
shutdown.stayoff
shutdown.stayoff powers off immediately (no shutdown delay), and then powers on again when line power is available.
-
test.battery.start
test.battery.start does not have any noticeable effect: the device does not report any battery information so it’s impossible to know if it actually does a test and what the results are (but most likely it just does nothing).