Click here to see reports of other supported models from Salicru.
|
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 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.capacity
|
|
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charge.restart
|
|
|
battery.charger.status
|
|
|
battery.protection
|
|
|
battery.runtime
|
|
|
battery.runtime.low
|
|
|
battery.type
|
|
|
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
|
|
|
input.frequency.nominal
|
|
|
input.voltage.nominal
|
|
|
outlet.1.status
|
|
|
output.current
|
|
|
output.frequency
|
|
|
output.frequency.nominal
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.date
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.firmware
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.model
|
|
|
ups.power
|
|
|
ups.power.nominal
|
|
|
ups.productid
|
|
|
ups.realpower
|
|
|
ups.realpower.nominal
|
|
|
ups.serial
|
|
|
ups.shutdown
|
|
|
ups.status
|
|
|
ups.temperature
|
|
|
ups.test.interval
|
|
|
ups.test.result
|
|
|
ups.time
|
|
|
ups.timer.shutdown
|
|
|
ups.timer.start
|
|
|
ups.type
|
|
|
ups.vendorid
|
|
About this device
As initially reported in https://github.com/networkupstools/nut/issues/1142 modified back to "native" VID/PID (that report was done with UPS apparently modified to reply to IDs supported by existing drivers to check its work "out of the box").
Reported at:
Further system data or configuration examples:
:; upsrw -s battery.runtime.low Unity
Enter new value for battery.runtime.low: 240
OK
:; upsc Unity battery.runtime.low
240
### I successfully set the `ups.delay.shutdown` from 20 to 120
### via `upsrw -s ups.delay.shutdown Unity` command:; upscmd -l Unity
Instant commands supported on UPS [Unity]:
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 test
### * Send command `upscmd Unity load.off`, the output
### voltage has changed from 230.2 to 0 after loading off.
### * Send command `upscmd Unity load.on`, the output
### voltage has changed from 0 to 230.2 after loading on.
