search for: bval_hialrm_i

...t fully know what a "HB High Battery" NUT flag can mean physically, and if the few existing drivers that use it do so consistently with *some* single definition; I looked at precedents of `git grep -w HB` in the codebase, there are a few `setval()` hits, namely: * adelsystem_cbi.c: "BVAL_HIALRM_I", * al175.c: "BATTERY VOLTAGE STATUS", * asem.c: "charge_percentage >= hb_threshold (default 75)", * generic_modbus.c: "usually ... charging state > 85%", * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRESHOLD (macro 75)" * similarly in hwm...

...t;HB High Battery" NUT flag > can mean physically, and if the few existing drivers that use it do so > consistently with *some* single definition; I looked at precedents of `git > grep -w HB` in the codebase, there are a few `setval()` hits, namely: > > * adelsystem_cbi.c: "BVAL_HIALRM_I", > * al175.c: "BATTERY VOLTAGE STATUS", > * asem.c: "charge_percentage >= hb_threshold (default 75)", > * generic_modbus.c: "usually ... charging state > 85%", > * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRESHOLD (macro 75)&quot...

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes: > During discussion at > https://github.com/networkupstools/nut/pull/2430#discussion_r1592317940 I > found that while `nut-names.txt` documents the `battery.charge.low` as the > "Remaining battery level when UPS switches to LB (percent)", there is no > counterpart as `battery.charge.high`.

...ag > > can mean physically, and if the few existing drivers that use it do so > > consistently with *some* single definition; I looked at precedents of > `git > > grep -w HB` in the codebase, there are a few `setval()` hits, namely: > > > > * adelsystem_cbi.c: "BVAL_HIALRM_I", > > * al175.c: "BATTERY VOLTAGE STATUS", > > * asem.c: "charge_percentage >= hb_threshold (default 75)", > > * generic_modbus.c: "usually ... charging state > 85%", > > * pijuice.c: "battery_charge_level > HIGH_BATTERY_THRES...