Click here to see reports of other supported models from Dell.
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.energysave
|
|
battery.runtime
|
|
battery.runtime.low
|
|
battery.type
|
|
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.bus
|
|
driver.parameter.pollfreq
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.product
|
|
driver.parameter.productid
|
|
driver.parameter.serial
|
|
driver.parameter.synchronous
|
|
driver.parameter.vendor
|
|
driver.parameter.vendorid
|
|
driver.version
|
|
driver.version.data
|
|
driver.version.internal
|
|
input.frequency
|
|
input.frequency.nominal
|
|
input.transfer.boost.low
|
|
input.transfer.high
|
|
input.transfer.low
|
|
input.transfer.trim.high
|
|
input.voltage
|
|
input.voltage.nominal
|
|
outlet.1.autoswitch.charge.low
|
|
outlet.1.delay.shutdown
|
|
outlet.1.delay.start
|
|
outlet.1.desc
|
|
outlet.1.id
|
|
outlet.1.status
|
|
outlet.1.switchable
|
|
outlet.2.autoswitch.charge.low
|
|
outlet.2.delay.shutdown
|
|
outlet.2.delay.start
|
|
outlet.2.desc
|
|
outlet.2.id
|
|
outlet.2.status
|
|
outlet.2.switchable
|
|
outlet.desc
|
|
outlet.id
|
|
outlet.switchable
|
|
output.current
|
|
output.frequency
|
|
output.frequency.nominal
|
|
output.voltage
|
|
output.voltage.nominal
|
|
ups.beeper.status
|
|
ups.date
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.firmware
|
|
ups.load
|
|
ups.load.high
|
|
ups.mfr
|
|
ups.model
|
|
ups.power
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.realpower
|
|
ups.realpower.nominal
|
|
ups.serial
|
|
ups.shutdown
|
|
ups.start.battery
|
|
ups.start.reboot
|
|
ups.status
|
|
ups.test.interval
|
|
ups.test.result
|
|
ups.time
|
|
ups.timer.shutdown
|
|
ups.timer.start
|
|
ups.type
|
|
ups.vendorid
|
|
About this device
I’m using a Dell UPS 2700W with an extended Battery Module (EBM). As I have a quite low load on the UPS (about 5%), it is easy to reach a very high runtime (counted in seconds) - so for now it seems like I reached the max of a 16Bit variable.
Per ticket discussion, a calibration run seems to have changed it (shown in second report).
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.capacity
|
|
battery.charge
|
|
battery.charge.low
|
|
battery.charge.restart
|
|
battery.charger.status
|
|
battery.energysave
|
|
battery.runtime
|
|
battery.runtime.low
|
|
battery.type
|
|
device.mfr
|
|
device.model
|
|
device.serial
|
|
device.type
|
|
driver.name
|
|
driver.parameter.bus
|
|
driver.parameter.pollfreq
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.product
|
|
driver.parameter.productid
|
|
driver.parameter.serial
|
|
driver.parameter.synchronous
|
|
driver.parameter.vendor
|
|
driver.parameter.vendorid
|
|
driver.version
|
|
driver.version.data
|
|
driver.version.internal
|
|
input.frequency
|
|
input.frequency.nominal
|
|
input.transfer.boost.low
|
|
input.transfer.high
|
|
input.transfer.low
|
|
input.transfer.trim.high
|
|
input.voltage
|
|
input.voltage.nominal
|
|
outlet.1.autoswitch.charge.low
|
|
outlet.1.delay.shutdown
|
|
outlet.1.delay.start
|
|
outlet.1.desc
|
|
outlet.1.id
|
|
outlet.1.status
|
|
outlet.1.switchable
|
|
outlet.2.autoswitch.charge.low
|
|
outlet.2.delay.shutdown
|
|
outlet.2.delay.start
|
|
outlet.2.desc
|
|
outlet.2.id
|
|
outlet.2.status
|
|
outlet.2.switchable
|
|
outlet.desc
|
|
outlet.id
|
|
outlet.switchable
|
|
output.current
|
|
output.frequency
|
|
output.frequency.nominal
|
|
output.voltage
|
|
output.voltage.nominal
|
|
ups.beeper.status
|
|
ups.date
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.firmware
|
|
ups.load
|
|
ups.load.high
|
|
ups.mfr
|
|
ups.model
|
|
ups.power
|
|
ups.power.nominal
|
|
ups.productid
|
|
ups.realpower
|
|
ups.realpower.nominal
|
|
ups.serial
|
|
ups.shutdown
|
|
ups.start.battery
|
|
ups.start.reboot
|
|
ups.status
|
|
ups.test.interval
|
|
ups.test.result
|
|
ups.time
|
|
ups.timer.shutdown
|
|
ups.timer.start
|
|
ups.type
|
|
ups.vendorid
|
|
About this device
I’m using a Dell UPS 2700W with an extended Battery Module (EBM). As I have a quite low load on the UPS (about 5%), it is easy to reach a very high runtime (counted in seconds) - so for now it seems like I reached the max of a 16Bit variable, as seen in the first report.
Per ticket discussion, a calibration run seems to have changed it (shown in this report).
Reported at: