Click here to see reports of other supported models from Greencell.
|
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
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.capacity.nominal
|
|
|
battery.charge
|
|
|
battery.charge.low
|
|
|
battery.charge.warning
|
|
|
battery.packs
|
|
|
battery.runtime
|
|
|
battery.type
|
|
|
battery.voltage
|
|
|
battery.voltage.high
|
|
|
battery.voltage.low
|
|
|
battery.voltage.nominal
|
|
|
device.mfr
|
|
|
device.model
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.chargetime
|
|
|
driver.parameter.idleload
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.protocol
|
|
|
driver.parameter.runtimecal
|
|
|
driver.parameter.synchronous
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
driver.version.usb
|
|
|
input.frequency
|
|
|
input.frequency.nominal
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
input.voltage.nominal
|
|
|
output.current.nominal
|
|
|
output.frequency.nominal
|
|
|
output.voltage
|
|
|
output.voltage.nominal
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.mfr
|
|
|
ups.mfr.date
|
|
|
ups.model
|
|
|
ups.power.nominal
|
|
|
ups.product
|
|
|
ups.productid
|
|
|
ups.realpower.nominal
|
|
|
ups.status
|
|
|
ups.type
|
|
|
ups.vendor
|
|
|
ups.vendorid
|
|
About this device
The UPS looks to be working with the nutdrv_qx driver,
different status events are properly reported.
The (v2.8.0) nut-scanner tool suggested nutdrv_qx driver
according to vendorid/productid which is used in many unrelated
devices, that driver supports the (Qx) protocol here.
Reported at:
Further system data or configuration example:
maxretry = 1
pollinterval = 2
battery_voltage_reports_one_pack
[gc2000va]
driver = nutdrv_qx
protocol = q1
port = auto
desc = "Green Cell PowerProof 2000VA UPS05"
chargetime = 28800
idleload = 4
default.battery.type = PbAcid
default.battery.capacity.nominal = 18.0
default.battery.charge.low = 10
default.battery.charge.warning = 50
default.battery.voltage.nominal = 24
default.battery.voltage.low = 21.00
default.battery.voltage.high = 25.00
default.battery.packs = 2
runtimecal = 2340,8,4740,4
default.input.frequency.nominal= 50.0
default.input.voltage.nominal= 230.0
default.output.current.nominal = 8.0
default.output.frequency.nominal = 50.0
default.output.voltage.nominal = 230.0
default.ups.mfr = "Green Cell"
default.ups.model = "PowerProof 2000VA UPS05"
default.ups.mfr.date = "2024/12/17"
default.ups.vendor = "Fry's Electronics"
default.ups.product = "MEC0003"
default.ups.power.nominal = "2000"
default.ups.realpower.nominal = "1200"
