Click here to see reports of other supported models from Guardian.
|
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.runtime
|
|
|
battery.voltage
|
|
|
battery.voltage.high
|
|
|
battery.voltage.low
|
|
|
device.type
|
|
|
driver.name
|
|
|
driver.parameter.pollfreq
|
|
|
driver.parameter.pollinterval
|
|
|
driver.parameter.port
|
|
|
driver.parameter.productID
|
|
|
driver.parameter.protocol
|
|
|
driver.parameter.runtimecal
|
|
|
driver.parameter.synchronous
|
|
|
driver.parameter.vendorid
|
|
|
driver.version
|
|
|
driver.version.data
|
|
|
driver.version.internal
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.type
|
|
|
ups.vendorid
|
|
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.voltage
|
|
|
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
|
|
|
input.frequency
|
|
|
input.voltage
|
|
|
input.voltage.fault
|
|
|
output.voltage
|
|
|
ups.beeper.status
|
|
|
ups.delay.shutdown
|
|
|
ups.delay.start
|
|
|
ups.load
|
|
|
ups.productid
|
|
|
ups.status
|
|
|
ups.type
|
|
|
ups.vendorid
|
|
About this device
Reported at:
Further system data or configuration examples:
[guardian]
driver = nutdrv_qx
port = auto
desc = "Guardian LCD 1500 AP by Inform"
#manufacturer = Inform
#modelname = "Guardian LCD 1500 AP"
vendorid = 0001
productID = 0000
protocol = q1/var/log/messagesJan 3 13:50:06 tunis kernel: usb 2-1.2: new low speed USB device number 6 using ehci_hcd
Jan 3 13:50:16 tunis kernel: usb 2-1.2: New USB device found, idVendor=0001, idProduct=0000
Jan 3 13:50:16 tunis kernel: usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 3 13:50:16 tunis kernel: usb 2-1.2: Product: MEC0003
Jan 3 13:50:16 tunis kernel: usb 2-1.2: configuration #1 chosen from 1 choice
Jan 3 13:50:16 tunis kernel: generic-usb 0003:0001:0000.0003: hiddev96,hidraw0: USB HID v1.00 Device [MEC0003] on usb-0000:00:1d.0-1.2/input0
