Click here to see reports of other supported models from Ippon.
|
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
Report #1 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.charge
|
|
|
battery.voltage
|
|
|
battery.voltage.high
|
|
|
battery.voltage.low
|
|
|
battery.voltage.nominal
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.current.nominal
|
|
|
input.frequency
|
|
|
input.frequency.nominal
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
input.voltage.nominal
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.temperature
|
|
|
ups.type
|
|
|
ups.vendorid
|
|
About this device
Tested on FreeBSD 11 with nut 2.7.4_8 from port collections.
Communication is regularly reported lost and data stale, then recovers. Ultimately this was chalked to a dying interface chip on the UPS.
Many of the data point readings fail due to "short reply" and/or timeouts.
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.high
|
|
|
battery.voltage.low
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.temperature
|
|
|
ups.type
|
|
|
ups.vendorid
|
|
About this device
Tested on FreeBSD 11 with nut 2.7.4_8 from port collections.
Communication is regularly reported lost and data stale, then recovers. Ultimately this was chalked to a dying interface chip on the UPS.
Many of the data point readings fail due to "short reply" and/or timeouts.
Sometimes the output is shorter than in the first data dump for this device, as seen here..
Reported at:
