Displaying 3 results from an estimated 3 matches for "min_bypass_freq".
Did you mean:
max_bypass_freq
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
...s_forbidding: disabled
setvar(bypass_when_off, disabled)
bypass_when_off is already disabled
setvar: FAILED
max_bypass_volt: 264
max_bypass_volt, settable range: 231..276
min_bypass_volt: 110
min_bypass_volt, settable range: 110..209
max_bypass_freq: 64.0
max_bypass_freq, settable range: 61.0..64.0
min_bypass_freq: 56.0
min_bypass_freq, settable range: 56.0..59.0
No values for battery high/low voltages
Using 'guesstimation' (low: 208.000000, high: 300.000000)!
setvar(ups.delay.start, 60)
setvar: SUCCEED
setvar(ups.delay.shutdown, 12)
setvar: SUCCEED
battery.charge: 100
battery.packs: 1
battery.protec...
2023 Jan 17
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
...s_forbidding: disabled
setvar(bypass_when_off, disabled)
bypass_when_off is already disabled
setvar: FAILED
max_bypass_volt: 264
max_bypass_volt, settable range: 231..276
min_bypass_volt: 110
min_bypass_volt, settable range: 110..209
max_bypass_freq: 64.0
max_bypass_freq, settable range: 61.0..64.0
min_bypass_freq: 56.0
min_bypass_freq, settable range: 56.0..59.0
No values for battery high/low voltages
Using 'guesstimation' (low: 208.000000, high: 300.000000)!
setvar(ups.delay.start, 60)
setvar: SUCCEED
setvar(ups.delay.shutdown, 12)
setvar: SUCCEED
battery.charge: 100
battery.packs: 1
battery.protec...
2023 Jan 15
1
PR to test for users of Qx devices (blazer and nutdrv_qx)
Cheers,
One PR waiting to get into 2.8.1 release timeframe is
https://github.com/networkupstools/nut/pull/1652 stemming from issue
https://github.com/networkupstools/nut/issues/1279
The gist of it is that "battery.voltage" and "battery.charge" were not
always reported correctly with nutdrv-qx driver (might be handled better by
blazer drivers though), and the overrides