Click here to see reports of other supported models from Legrand.
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.8.0.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.voltage
|
|
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollfreq
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.productid
|
|
driver.parameter.synchronous
|
|
driver.parameter.vendorid
|
|
driver.state
|
|
driver.version
|
|
driver.version.data
|
|
driver.version.internal
|
|
driver.version.usb
|
|
input.transfer.high
|
|
input.transfer.low
|
|
input.voltage
|
|
input.voltage.nominal
|
|
output.frequency
|
|
output.voltage
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.load
|
|
ups.mfr
|
|
ups.model
|
|
ups.productid
|
|
ups.realpower.nominal
|
|
ups.serial
|
|
ups.status
|
|
ups.vendorid
|
|
About this device
Reported at:
Further system data or configuration example:
Voltages seemed to be off by a factor of 10. So the report author
experimented with neutering of `divide_by_10_conversion()` and
`legrand_times10M_info()` in the mapping tables.
NOTE: The report below is not from a stock NUT release (nor snapshot),
but from that experiment. Voltages are bumped (or rather not-nerfed
by default driver logic), `1.2` => `12` etc.
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.voltage
|
|
battery.voltage.nominal
|
|
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollfreq
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.productid
|
|
driver.parameter.synchronous
|
|
driver.parameter.vendorid
|
|
driver.version
|
|
driver.version.data
|
|
driver.version.internal
|
|
driver.version.usb
|
|
input.transfer.high
|
|
input.transfer.low
|
|
input.voltage
|
|
input.voltage.nominal
|
|
output.frequency
|
|
output.voltage
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.load
|
|
ups.mfr
|
|
ups.model
|
|
ups.productid
|
|
ups.realpower.nominal
|
|
ups.serial
|
|
ups.status
|
|
ups.vendorid
|
|
About this device
Reported at:
Further system data or configuration example:
Device support relies on code that went into NUT v2.8.0 release;
the report was done on a development snapshot so dubbed "2.7.4.1".
It outputs the current of all devices, the PDU800 doesn't support
metrics per output plug.