8 Commits
Author SHA1 Message Date
Sleeper85 7d347ae626 Examples - Add bms_fake_equalizing_enabled
Every example including a BMS that ships Fake Equalizing (EG4 LL V2,
Seplos V1/V2, Seplos V3, Demo BMS) now declares
bms_fake_equalizing_enabled on each BMS, with a comment explaining what
enabling it does and warning that a BMS without a balancer can stay in
Cut-Off for a long time before reaching EOC.

The EG4 and Seplos examples set it to 'false', the package default. The
DEMO examples set it to 'true'.
2026-11-19 04:18:57 +01:00
Sleeper85 c428e3470f Examples - EG4 LL V2 RP example: BMS 3 used bms_id 2
The third BMS block of RP_BMS_example_EG4_LLV2_RS485_Modbus.yaml declared
bms_id: '2', a duplicate of BMS 2. It now uses bms_id: '3'.
2026-11-19 02:31:42 +01:00
Sleeper85 9dd22fa56b Inferred equalizing for BMS that do not report a balancing flag
Some BMS balance their cells but never expose a balancing flag, so
`bms_equalizing` stays false and the core cannot tell a pack that is still
balancing from one that has finished. This is not cosmetic : while
equalizing is true, yambms_core.yaml stops the Cut-Off timer and lets the
charge run to the EOC timer instead of terminating early.

bms_options_fake_equalizing.yaml infers that flag from the pack itself. No
absolute cell voltage is hardcoded : the anchor is bulk_voltage / cell
count, the same derivation as cell_bulk_v in yambms_core.yaml, so it
follows `yambms_battery_chemistry`, the cell count and the configured bulk
voltage automatically.

  START when BOTH are true
    max cell >= cell_bulk_v                     the pack is at the setpoint
    AND (max - min) >= trigger voltage          its own balancing threshold

  STOP when EITHER is true
    max cell <  cell_bulk_v - hysteresis        the pack dropped off the setpoint
    OR (max - min) <  trigger - delta hyst.     the spread closed back below it

Only two deltas and one offset are configurable, and none of the three
depends on the chemistry - LFP, Li-ion and LTO all want the same few tens
of mV. The absolute anchor they hang off comes from the core, for free.

The delta condition is what keeps this honest : a pack that reaches the
setpoint perfectly balanced has nothing to equalize, so it reports false
and the Cut-Off timer does its job. A plain voltage comparison would report
balancing forever and terminate every charge on the EOC timer.

It extends bms<id>_bms_equalizing, the raw BMS flag, and not the combined
bms<id>_equalizing sensor. bms_base_balancer.yaml is therefore neither
modified nor duplicated, and keeps giving an external balancer priority
whenever one is online : the inference only applies when no balancer
reports for this pack.

This commit only adds the package. Nothing includes it yet, so no existing
configuration changes behaviour. Candidates sharing the same case are
Seplos V3, Seplos V1/V2, EG4 LL V2 and JK RS485 DISPLAY, whose
bms_equalizing is a hardcoded `return false;`.
2026-11-08 23:08:33 +01:00
Sleeper85 d178ffa5c8 YamBMS 1.7.0 examples (2026.02.16) 2026-02-16 15:15:21 +01:00
Sleeper85 e5d903005c Improved LP / RP examples 2026-02-15 22:11:47 +01:00
MrPabloUK 447a18b832 Component Fault Registry & Advanced LED Control (#194) 2026-02-05 09:26:49 +01:00
Sleeper85 6722216f86 Adjust bms_name to something unique #122 2025-12-23 21:15:21 +01:00
Andrew Rankin d01de31f7a Adding EG4 LLV2 BMS (#85) 2025-09-09 16:10:35 +02:00