BatteryLife not activating Load Output. Float is running for hours now. What could’t be the cause?
This is from AI: is it right?
The Core Reason: The “Locked” Logic Loop
The reason the load output has not turned on even for a split second is that the BatteryLife algorithm has entered a defensive “lockout” state.
If the battery fails to reach a true, sustained 100% saturation charge for several consecutive days (which matches the dominant purple “Bulk” sections in your 7-day chart), BatteryLife automatically increases the reconnect voltage threshold every single day.
By day 7, this software threshold has likely been pushed so high (e.g., up to 14.2V or more on a 12V system) that it now sits above your current Float voltage (which usually drops down to around 13.5V – 13.8V). Because the actual battery voltage in the Float phase never hits that heavily inflated reconnect target, the controller’s software never triggers the “ON” switch at all.
Why “Float” Can Be Deceptive
Your controller switches to Float because it registers that the battery has touched the target absorption voltage. However, the BatteryLife algorithm requires a time-and-capacity-based confirmation over 24-hour cycles.
If you have a constant background load pulling current directly from the battery terminals, or if the battery is older and suffers from sulfation, its voltage will spike quickly (tricking the charger into entering Float early) while the actual chemical state of charge remains low. BatteryLife detects this discrepancy and keeps the load output firmly shut.