search for: battery_numb

...with 2.7.4 the 2kv battery.charge is reporting 100. but the new code is reporting 67. details below: 10KV: ./nutdrv_qx -a ftups -d1 Network UPS Tools - Generic Q* USB/Serial driver 0.33 (Windows-v2.8.0-alpha3-1252-g757813e) USB communication driver (libusb 0.1) 0.44 Using protocol: Voltronic 0.07 battery_number: 20 battery_number, settable range: 1..9 bypass_alarm: enabled battery_alarm: enabled bypass_when_off: disabled alarm_control: enabled converter_mode: disabled eco_mode: disabled battery_open_status_check: enabled bypass_forbidding: disabled setvar(bypass_when_off, disabled) bypass_when_off is al...

...with 2.7.4 the 2kv battery.charge is reporting 100. but the new code is reporting 67. details below: 10KV: ./nutdrv_qx -a ftups -d1 Network UPS Tools - Generic Q* USB/Serial driver 0.33 (Windows-v2.8.0-alpha3-1252-g757813e) USB communication driver (libusb 0.1) 0.44 Using protocol: Voltronic 0.07 battery_number: 20 battery_number, settable range: 1..9 bypass_alarm: enabled battery_alarm: enabled bypass_when_off: disabled alarm_control: enabled converter_mode: disabled eco_mode: disabled battery_open_status_check: enabled bypass_forbidding: disabled setvar(bypass_when_off, disabled) bypass_when_off is al...

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

Daniele, Thanks again for your work on both the voltronic and blzr drivers. To get the most exposure to new drivers, what we have typically done in the past is to rename the existing driver as *-old, so that users get the new driver by default when they upgrade (but the old driver is still available if there are regressions). This is how we are incorporating Michal's apcsmart updates. On