Click here to see reports of other supported models from Digitus.
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 nutdrv_qx (detailed comments available)
This device is known to 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.flag.novendor
|
|
driver.name
|
|
driver.parameter.chargetime
|
|
driver.parameter.idleload
|
|
driver.parameter.pollfreq
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.product
|
|
driver.parameter.productid
|
|
driver.parameter.protocol
|
|
driver.parameter.runtimecal
|
|
driver.parameter.synchronous
|
|
driver.parameter.vendor
|
|
driver.parameter.vendorid
|
|
driver.version
|
|
driver.version.data
|
|
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.type
|
|
ups.vendorid
|
|
About this device
I’ve successfully tested the nutdrv_qx driver with the Digitus DN-170076 UPS, connected via USB (it has a DB-9 serial interface as well).
Device manufacturer: Digitus (by ASSMANN Electronic GmbH, www.assmann.com)
Name: DN-170076 Line-Interactive UPS-System, capacity 2000VA/1200W
EAN 4016032441380
With this configuration:
[digitus]
driver = "nutdrv_qx"
port = "auto"
desc = "Digitus UPS 2000VA/1200W (via USB)"
vendorid = "0001"
productid = "0000"
product = "MEC0003"
vendor = "MEC"
default.battery.voltage.low = 20.81
default.battery.voltage.high = 27.40
…it is detected with Q1 protocol and basically works (except the
button.toggle
command did not work with neither blazer_usb
nor
nutdrv_qx
drivers with Q1 protocol).
After adding:
protocol = "megatec"
novendor
…the button.toggle
works and is displayed properly by upsc
.
I did a shutdown test with modified settings, to shorten the shutdown time:
override.battery.charge.low = 30
default.battery.voltage.low = 25.20
runtimecal=60,100,80,50
As UPS does not report battery.charge
, battery.runtime
on its own,
have to provide the default.battery.voltage.{low,high}
values as
mentioned in the man page (otherwise the driver issues "No values
provided for battery high/low voltages in ups.conf"), and added
runtimecal
setting too.
upsc reports the values below when running on main power.
See also DigitusDN-170076nutdrv_qx2.7.402.dev
Reported at:
Vendor/Manufacturer information:
Further system data or configuration example:
upscmd -l digitus@localhost
listing# TODO: Convert to CMD:... markup
:; upscmd -l digitus@localhost
Instant commands supported on UPS [digitus]:
beeper.toggle - Toggle the UPS beeper # works (with megatec protocol)
load.off - Turn off the load immediately # did not work, syslog tells 'instcmd: command [load.off] handled' but nothing happens
load.on - Turn on the load immediately
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 - Start a battery test
test.battery.start.deep - Start a deep battery test
test.battery.start.quick - Start a quick battery test # works
test.battery.stop - Stop the battery test
Report #2 with driver nutdrv_qx (detailed comments available)
This device is known to 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.runtime
|
|
battery.voltage
|
|
battery.voltage.high
|
|
battery.voltage.low
|
|
battery.voltage.nominal
|
|
device.type
|
|
driver.flag.novendor
|
|
driver.name
|
|
driver.parameter.chargetime
|
|
driver.parameter.idleload
|
|
driver.parameter.pollfreq
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.product
|
|
driver.parameter.productid
|
|
driver.parameter.protocol
|
|
driver.parameter.runtimecal
|
|
driver.parameter.synchronous
|
|
driver.parameter.vendor
|
|
driver.parameter.vendorid
|
|
driver.version
|
|
driver.version.data
|
|
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.type
|
|
ups.vendorid
|
|
About this device
See also DigitusDN-170076nutdrv_qx2.7.401.dev for majority of info from this report
Here upsc
reports values when running on battery,
after toggling beeper.status
to disabled
.
Reported at: