Symptom
Battery charge capped below full
- ID
symptom:battery-charge-capped
- IRI
https://solarlattice.org/kb/symptom/battery-charge-capped
- Status
- active
- Also known as
- Does not charge to 100%, Limited to a maximum charge level of 75% (SOC), Self-consumption range cannot be set above 75%, SOC holds at 99%
The battery stops charging, or reports its state of charge, below full even when a full charge seems to have finished. On SMA Sunny Island systems, look in the event log for the change to full charge. If SOC is still below 100% afterwards, the loads may have drawn too much power before the full charge ended. For that case, set a longer full charge time, also called the absorption period. Check the charge limit settings first. A maximum or cut-off charge SOC, or a time-slot charge SOC, set below 100% makes the battery stop charging at that value. On the Sunny Boy Storage SBS2.5-1VL-10, older firmware does not allow the self-consumption range above 75%. Updating to firmware 3.11.10.R or later sets it to 90%. Seasonal self-consumption ranges also change automatically how much of the battery capacity is used through the year. Incorrect battery parameters can also be the cause, such as the battery type, the nominal capacity or the full and equalization charge settings, so compare them with the battery manufacturer's recommendations. The SOC shown is an estimate from ampere-hour counting plus voltage recalibration. The goal of a full charge is a state of charge of at least 95%, not exactly 100%.
<!-- review notes
- sentence 1: support check: partial - SOC below 100% after full charge is stated, but the passages don't say the battery stops charging below full.
- sentence 2: support check: partial - Event codes and the high-load explanation are in the passages, but not the instruction to check the event log for the change to full charge.
- sentence 4: support check: partial - Max/cut-off and time-slot SOC stopping charging are stated, but not the advice to check them first or that a value below 100% is the cause of a capped SOC.
- sentence 7: support check: partial - u32 lists BatTyp, BatCpyNom, full and equalization charge parameters to check, and other passages say to set them per manufacturer recommendations, but the passages don't link the manufacturer comparison to this symptom.
- sentence 8: support check: partial - The passages state the SOC method (Ah counting plus voltage recalibration) and the 95% minimum goal, but not 'estimate' or 'not exactly 100%'.
- sentence 4: review: partial - The passages state that a max/cut-off charge SOC or a time-slot charge SOC stops charging at that value, but they do not support the instruction to check these settings first.
-->
Claims
observed_as
c1 verified · fact
SOC below 100% after full charge proposed
The displayed battery SOC stays under 100% even though the full-charge phase has finished. The SMA documents say loads drew so much power before the full charge ended that the battery could not reach 100%.
verified by: review-workflowverified on: 2026-10-24
c2 drafted · lead
Full charge status event proposed
SMA event 9321 or E205 marks the change to full charge. Use it to confirm that a full charge was actually started before reading a capped SOC as abnormal.
review note: support check: partial - Events 9321 and E205 mark the change to full charge, but the passages do not say to use them to confirm a full charge before judging a capped SOC.; review: partial - Events 9321 and E205 do mark the change to full charge, but the passages never say to use them to confirm a full charge before treating a capped SOC as abnormal.
c3 verified · fact
Max charge SOC setpoint reached proposed
Charging stops at the configured maximum or cut-off SOC, or at a time-slot charge SOC. Generac's MaxSoCAbs can be set from 10 to 100% and defaults to 100%.
verified by: review-workflowverified on: 2026-10-24
Data