Short answer: every Pylontech alarm falls into one of seven families: over-voltage, under-voltage, over-current, short circuit, temperature, cell imbalance and communication fault. Each exists at two levels, a warning (the battery keeps running) and a protection (the BMS cuts or limits current). Your inverter usually shows only its own generic "battery fault"; the real alarm name and the module that raised it are only visible on the Console port. A single alarm that clears by itself is usually nothing. The same alarm coming back is what you should act on.
Where a Pylontech "error code" comes from
The BMS inside each Pylontech module constantly compares a set of values (voltage, current, temperature, cell balance) with limits stored inside it. When one is crossed, it raises a flag. What you see next depends on where you are looking, and that is where most of the confusion comes from: the same event looks completely different on the front LEDs, in Pylontech's Console software and on your inverter's screen.
The alarm families every Pylontech has
| Family | What it means |
|---|---|
| Cell / pack over-voltage | A cell or the whole pack has charged above its safe upper limit. Usually the end of a charge pushed too far. |
| Cell / pack under-voltage | A cell or the whole pack has discharged below its safe lower limit. Typically a battery left almost empty for too long. |
| Charge / discharge over-current | More current was asked of the battery, in or out, than it is rated for. An inverter or a load pulling harder than the pack can supply. |
| Short circuit | A huge, almost instant current spike. The BMS disconnects immediately. You will not miss this one. |
| Over / under temperature | Cell temperature outside the safe window for charging or discharging. Charge and discharge each have their own limits, and they differ. |
| Cell voltage imbalance | One or more cells moving away from the rest of the pack. A slow signal, almost never a sudden one. Explained in detail in our diagnostics guide. |
| Communication fault | The BMS has lost contact with a neighbouring module or the master. Rare with a single battery; in a stack, very often a cable problem. |
The exact thresholds are set by Pylontech for each model and firmware version. Your module's manual is the reference, not a figure found on a forum.
Warning or protection: two levels of severity
Most of these families exist at two levels. A warning means a value has crossed a cautionary threshold but the battery keeps working: the BMS is telling you something, not stopping you. A protection means a harder limit was crossed and the BMS has disconnected or limited charging or discharging to protect the cells. The difference matters. A warning is worth watching over the next few cycles. After a protection, find out why before you simply reset it and move on.
Reading the front LEDs
As described in our check guide, each low-voltage module has a run light, an alarm light and a row of SOC lights. A steady alarm light usually means something different from a blinking one (often warning versus protection), but the exact pattern depends on the model and firmware, and Pylontech has changed it between generations. This is one case where your module's own manual beats any generic table, this one included.
What your inverter's screen shows
This is what confuses people most: your inverter almost never shows Pylontech's alarm name. It reads the CAN/RS485 link, sees a fault bit, and displays its own generic message, something like "Battery Fault" or a number from the inverter maker's table, not from Pylontech's. Our inverter guide goes through this brand by brand. In short, the CAN/RS485 link was never meant to carry Pylontech's detailed alarm text, only a few coarse status bits for the whole stack.
PYLON Console / BatteryView, reading the Console port directly, is the one place where the alarm appears under its real name with the module that raised it. A permanent monitor on the Console port, such as Pylon-Monitor, shows the same thing all the time, with a timestamp, instead of only during a laptop session.
When the "error" is actually a cable
Communication faults deserve a section of their own, because they are the alarm most often mistaken for a battery failure. In a stack of several batteries, a communication fault is more often a Console/Link cable that is too long for its gauge, pinched inside a closed cabinet, or simply the wrong cable taken from a drawer, than a failed BMS. Before booking an inspection for a recurring communication fault, check the cable run. A correctly rated replacement cable fixes more of these than you would think.
What to do when an alarm goes off
- Note when it happened, not just that it happened. One timestamped event is a data point. A monitor that logs it is worth far more than remembering "sometime this week".
- See whether it clears on its own. Many warnings disappear once the cause has passed: a hot afternoon, a big load spike. That is normal BMS behaviour, not a fault to chase.
- Look for a pattern, not a one-off. The same alarm coming back on the same module, at the same time of day or under the same load, is what you should act on.
- Rule out the cables before the cells. Especially for communication faults in a stack. See our wiring guide.
- Do not just keep clearing it. Restarting a battery again and again to silence a recurring protection hides a trend that is getting worse, not better.
Frequently asked questions
- What does the red LED mean on a Pylontech battery?
- Generally that an alarm condition is active, but whether it's a warning or a protection event — and the exact pattern — depends on the model and firmware. Check your specific module's manual rather than a generic online table; Pylontech has changed LED behaviour between generations.
- Where can I find the actual Pylontech error code, not just a generic inverter fault?
- In Pylontech's own PYLON Console (also shipped as BatteryView) software, reading the battery's Console port directly, or on a permanent Console-port monitor. The inverter's screen reads the CAN/RS485 link and shows its own generic fault message, not Pylontech's specific alarm name.
- What is a "communication fault" on a Pylontech battery bank?
- The BMS losing contact with a neighbouring module or the master over the Console/Link chain. In multi-battery setups it's very often a cabling issue — too long, physically stressed, or wrongly specified — rather than a failed battery.
- Does a Pylontech alarm always mean the battery is faulty?
- No. Most alarms are the BMS reacting normally to a real but often transient condition — a hot afternoon, a heavy load spike, a battery left low too long. What warrants attention is a recurring pattern, not a single event.
- Can I see Pylontech alarms remotely instead of checking the battery in person?
- Yes, with something reading the Console port continuously rather than on a schedule — a permanent monitor logs the alarm, which module raised it, and when, so a transient event that self-clears before you next check doesn't go unnoticed.
Pylon-Monitor shows every alarm all the time, with the time it happened and the battery that raised it, instead of only during a laptop session or once the inverter has turned it into a generic fault.
Order now — €59 One-time purchase, €59 total — no VAT, no subscription.