Skip to main content
Your goal is to confirm the battery is receiving charge current from the correct source and that the BMS is communicating. Start with the three checks below before opening the causes table. Symptom: sun is available or grid-charge is enabled, yet the battery sits at the same SOC — or charge current is far below expectation.

Check first

  1. Is SOC live and updating on the display? A missing, stuck, or 0% SOC reading means a BMS comm problem. The crossover cable check comes before any settings work — this is the leading cause.
  2. Is charging actually scheduled right now? Check the mode and the TOU window on the platform’s settings page. A battery told to idle until a future window opens is obeying, not failing.
  3. What does the display flag? Note the exact alarm message and the SOC/voltage pair together — both matter for the triage below.

Causes

CauseHow to confirmFix
BMS comms downSOC missing, stuck, or 0%; Kent G3: CAN Fail · Kent M1: E400–E402Follow the Comm Fault flow — cable and connector checks first
Wrong battery selectionKent G3: BatName-FAIL · model shown on display ≠ Pylon-family entryCorrect the battery selection per the platform commissioning page; cable must be proven first
Grid-charge not enabledKent M1: grid-charge is OFF by default · Kent G3: Allow grid charging OFF or grid-charge current set to 0 AEnable grid-charge deliberately per the platform settings page and set the charge current
Battery already at target SOCSOC at 100% or at the mode’s charge target; Kent M1: E406 / OV-Vbatt classNothing to fix — verify the figure against the mode’s configured target
Charge current capped by the battery bankCharge holds steady at (pack count × per-pack limit) with no faultDesign behaviour — see Not Charging / Not Discharging; add packs or match the inverter charge current to the bank limit
Pack in temperature protectionKent M1: E409 / E410; measured ambient extremeWait for temperature to normalise; review the siting if heat is the driver
Pack dormant after deep dischargePack voltage very low; pack unresponsive to normal chargeWake using the platform’s official function: Kent G3 Battery Wakeup switch (use the switch only, never key in voltages manually) · Kent M1 Activate Bat; pack still silent → battery-service case
After any comm repair in this flow, complete the full-charge SOC verification from SOC Mismatch. Drift accumulated while the BMS link was down does not clear itself.

Escalate when

  • The BMS stays silent after the cable is verified against the pin card and the battery selection is confirmed correct — this is a battery-level case for Kent service.
  • E400/E403-class faults survive the one-restart rule.
  • A pack refuses the official wake procedure.
Escalate to Kent New Energy service only — through your registered Kent partner channel or the Kent service desk details on your work order. Do not contact any third-party or component-manufacturer support line for a Kent-branded system: tickets outside the Kent channel are not tracked, not covered, and can void warranty handling.