Click here to see reports of other supported models from Talegent.
![]() |
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.3.64
Report #1 with driver blazer_ser (detailed comments available)
This device is known to work with driver blazer_ser. It may also 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.mfr
|
|
device.model
|
|
device.type
|
|
driver.debug
|
|
driver.flag.allow_killpower
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.synchronous
|
|
driver.state
|
|
driver.version
|
|
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.firmware
|
|
ups.load
|
|
ups.mfr
|
|
ups.model
|
|
ups.status
|
|
ups.temperature
|
|
ups.type
|
|
About this device
I tested both NUT2.7.4 and NUT2.8.3.64, and they can both read the UPS status normally and control the UPS devices properly, such as shutting down.
MAINTAINER NOTE: Initial contribution had broken markup; it is possible that fixing attempts lost some data near output.voltage and/or that some data points were not even posted originally.
Reported at:
Further system data or configuration example:
:; cat /etc/nut/ups.conf
[myups]
driver = blazer_ser
port = /dev/ttyCH341USB0
desc = "My UPS"