Click here to see reports of other supported models from Santak.
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 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.voltage
|
|
battery.voltage.high
|
|
battery.voltage.low
|
|
device.type
|
|
driver.name
|
|
driver.parameter.pollinterval
|
|
driver.parameter.port
|
|
driver.parameter.synchronous
|
|
driver.version
|
|
driver.version.internal
|
|
input.frequency
|
|
input.voltage
|
|
input.voltage.fault
|
|
output.voltage
|
|
ups.beeper.status
|
|
ups.delay.shutdown
|
|
ups.delay.start
|
|
ups.load
|
|
ups.status
|
|
ups.temperature
|
|
ups.type
|
|
About this device
the initial report https://github.com/networkupstools/nut/issues/1039 is also a trove on information on Q6 protocol research to add better support. |
I have a Castle C1K on hand, which is an online ("double conversion")
UPS with two built-in 12V batteries and 1kVA output capacity.
I can make it work by using blazer_ser
driver.
Most things work. The battery voltage reports 2.28 because the
Castle C*K series it reports the battery voltage as the multiplier
of voltage of single piece of battery (2.28 * 12V = 27.36V)
,
unlike the MT*-PRO series that reports the voltage directly.
This can be solved by setting flags in ups.conf:
override.battery.voltage.nominal = 24
override.battery.packs = 12
…in theory, but seems like it does not work.
Reported at: