Where a Pylontech "error code" actually comes from
The BMS inside every Pylontech module continuously checks a fixed set of conditions — voltage, current, temperature, cell balance — against limits it holds internally. When one is crossed, the BMS raises a flag. What happens next depends entirely on where you're looking from, and that's the part that causes most of the confusion: the same underlying event shows up completely differently on the front-panel LEDs, in Pylontech's own Console software, and on your inverter's screen.
The alarm categories every Pylontech battery has
| Category | What it flags |
|---|---|
| Cell / pack over-voltage | A cell or the whole pack has charged above its safe upper limit — most often the tail end of a charge cycle pushed too far. |
| Cell / pack under-voltage | A cell or the whole pack has discharged below its safe lower limit — typically a battery left to sit near empty for too long. |
| Charge / discharge over-current | More current was asked of the battery, in or out, than it's rated to handle — an inverter or load drawing harder than the pack can supply. |
| Short circuit | A near-instant, very large current spike. The BMS reacts by disconnecting immediately; this one is never subtle. |
| Over / under temperature | Cell temperature outside the safe charge or discharge window — charge and discharge each have their own limits, and they're not the same. |
| Cell voltage imbalance | One or more cells drifting away from the rest of the pack — a gradual signal, almost never a sudden one. Covered in depth in the diagnostics guide. |
| Communication fault | The BMS lost contact with a neighbouring module or the master. In a single-battery setup this is rare; in a bank, it's very often a cabling issue. |
Exact trigger thresholds are set per model and firmware version by the manufacturer — treat the figures in your own module's manual as the authority, not a number found on a forum.
Warning vs. protection: two different severities
Most of these categories exist at two levels. A warning means a value has crossed a cautionary threshold but the battery keeps operating — this is the BMS telling you something, not stopping you. Protection means a harder limit was crossed and the BMS has actively disconnected or limited charge/discharge to protect the cells. The distinction matters: a warning is worth watching over the next few cycles; a protection event is worth understanding why before you simply reset it and move on.
Reading the front-panel LEDs
As covered in the check guide, every low-voltage module carries a run indicator, an alarm indicator and a row of SOC lights. A steady alarm LED generally reads differently from a blinking one — often warning versus protection — but the exact pattern is model- and firmware-specific, and Pylontech has changed it between generations. This is genuinely one case where the manufacturer's own manual for your specific module beats any generic table, including this one.
What your inverter's screen actually shows
Here's the part that trips people up most: your inverter almost never displays Pylontech's own alarm name. It reads the CAN/RS485 link, sees a fault bit, and displays its own generic message — something like "Battery Fault" or a numeric code from the inverter manufacturer's own table, not Pylontech's. The inverter guide covers this gap by brand; the short version is that the CAN/RS485 link was never designed to carry Pylontech's detailed alarm text, only a handful of coarse status bits for the whole stack.
Pylontech's own PYLON Console / BatteryView software, reading the Console port directly, is the one place that shows the alarm by its actual name and which module raised it — which is also exactly what a permanent Console-port monitor like Pylon-Monitor exposes continuously, with a timestamp, instead of only during a laptop session.
When the "error" is really a cabling problem
Communication faults deserve their own mention because they're the alarm category most often misdiagnosed as a battery failure when it isn't one. In a multi-battery bank, a comms fault is more often a Console/Link cable that's too long for its gauge, physically pinched inside a closed enclosure, or simply the wrong replacement cable grabbed from a drawer — not a failed BMS. Before scheduling a battery inspection over a recurring comms fault, check the physical cable run first; a correctly-rated replacement cable resolves more of these than people expect.
What to actually do when an alarm fires
- Note when it happened, not just that it happened. A single timestamped event is a data point; a monitor that logs it is worth far more than a memory of "sometime this week."
- Check if it clears on its own. Many warnings self-clear once the triggering condition passes — a hot afternoon, a heavy load spike. That's normal BMS behaviour, not a fault to chase.
- Look for a pattern, not an instance. The same alarm returning on the same module, at the same time of day or under the same load, is the signal worth acting on.
- Rule out cabling before the cell. Especially for communication faults in a bank — see the wiring guide.
- Don't just keep clearing it. Repeatedly power-cycling a battery to silence a recurring protection event hides a trend that's actually 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 surfaces every alarm flag continuously, with a timestamp and which battery raised it — instead of only during a laptop session or after the inverter has already reduced it to a generic fault.
Order now — €59 One-time purchase, €59 total — no VAT, no subscription.