search for: adelsystem_cbi

...for rules processing part. Driver reads GPIO line statuses and transforms them to NUT statuses using short rules description parameter in the form of status strings and logical operations on line values. Modris -------------- next part -------------- A non-text attachment was scrubbed... Name: adelsystem_cbi.c Type: text/x-csrc Size: 39959 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20230221/f6170038/attachment-0002.c> -------------- next part -------------- A non-text attachment was scrubbed... Name: gpio.c Type: text/x-csrc Size: 18929 bytes D...

...eems that we still do not 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)&q...

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`.