Short answer: most Pylontech shutdowns are the BMS doing its job: a cell reached its low or high voltage limit, the temperature left the allowed range, the current was too high, or the inverter lost communication. The inverter usually only shows the consequence. The cause is in the BMS, readable through the CONSOLE port: per-battery protection flags, cell voltages and temperatures at the moment it happened.
The seven usual causes
1. One cell hits its low voltage limit
Typical symptom: the battery cuts out at night or early morning, while the inverter still showed 10 or 15 % state of charge. The BMS protects every cell individually. If one cell is lower than the others, it reaches the limit first and the module stops discharging, even though the average says there is energy left. Often linked to cell imbalance (cause 5) or to state-of-charge drift after weeks without a full charge.
2. One cell hits its high voltage limit
Typical symptom: charging stops at 90 to 98 %, or the battery briefly disconnects in the afternoon on sunny days. Same logic at the top: one cell above the others reaches the high limit first and the BMS stops charging. Charge voltage set too high in the inverter makes this worse.
3. Temperature out of range
Typical symptom: no charging on cold mornings in a garage or outbuilding, or cuts on very hot days. The BMS limits or blocks charging near freezing and protects against overheating. The US datasheets give a charge range of roughly 0 to 50 °C and discharge of roughly −10 to 50 °C (check your model).
4. Overcurrent
Typical symptom: a cut when a big load starts (oven, heat pump, car charger) or when the inverter pushes a strong charge. If the current asked of the stack exceeds what its modules accept, the BMS protects itself. Common when a stack was sized with too few modules for the inverter, or when one module of a stack carries more than its share because of unequal wiring.
5. Cell imbalance
Not a protection in itself, but the root of causes 1 and 2 in many cases. When the spread between the highest and lowest cell grows beyond a few tens of millivolts, the usable window shrinks and protections trigger earlier. See our cell imbalance guide.
6. Lost communication with the inverter
Typical symptom: “BMS communication error” or “battery not detected”, sometimes intermittent. The battery itself may be fine; the CAN/RS485 link between the master battery and the inverter dropped. Causes: loose or wrong cable, wrong protocol in the inverter, or a slave battery that dropped out of the LINK chain.
7. A module dropped out of the stack
Typical symptom: the stack suddenly shows less capacity or a lower maximum current. One module went into protection or lost the LINK connection, and the master now reports fewer batteries. The inverter rarely says which one.
Symptom → likely cause
| What you see | Likely cause | What to check in the BMS data |
|---|---|---|
| Cut at night with 10–15 % left | Low cell voltage | Lowest cell at the time of the cut, cell spread |
| Charging stops before 100 % | High cell voltage | Highest cell near the end of charge, inverter charge voltage |
| No charging on cold mornings | Low temperature | Module temperatures |
| Cut when a big load starts | Overcurrent | Current per battery, protection flags |
| “BMS communication error” | Inverter link | Cable on the master’s CAN/RS485 port, protocol setting |
| Capacity suddenly lower | Module dropped out | Number of batteries seen, LINK chain |
How to find the real cause
The difficulty is timing: by the time you look, the battery has often recovered and the inverter just shows a past error. What you need is the BMS data at the moment it happened, battery by battery.
- Note the time and the conditions: night or day, cold or hot, which appliance was running.
- Read the BMS through the CONSOLE port of the master battery: protection and alarm flags per battery, cell voltages, temperatures, current.
- Compare modules: a problem confined to one battery points to that module or its wiring; a problem on all batteries points to settings, temperature or the inverter.
- Look at history: a cell spread growing over weeks, a module always warmer, a state of charge that drifts between full charges.
PylonCheck does exactly this continuously: it reads the BMS of every battery through the CONSOLE port, stores a snapshot every two minutes for days, five-minute averages for 90 days and hourly averages for three years, and shows the protection flags battery by battery. When a cut happens at 4 a.m., you can open the cloud dashboard the next morning and see which cell, which module and which flag caused it. If the box itself goes silent for six hours, it emails you.
The usual fixes
- Cell limits: let the stack reach a full charge regularly so the cells can balance, set a reasonable minimum state of charge in the inverter, and keep the charge voltage within Pylontech’s recommendation.
- Temperature: move the battery to a frost-free, ventilated place, or accept reduced charging in winter.
- Overcurrent: limit the inverter’s battery current to what the stack supports, add a module, or fix unequal wiring between modules.
- Communication: check the cable on the master’s CAN/RS485 port, the battery protocol in the inverter and the LINK chain (LINK PORT 1 → LINK PORT 0).
- Persistent imbalance or a module that keeps dropping out: collect the data and contact your installer; the history makes a warranty discussion much easier.
For a structured health check, follow the 10-point Pylontech battery check.