Skip to content
07944 877 329 hello@solar-tech-support.co.uk
Get a quote
Fault code index · Pylontech US-series & Force-series batteries

Pylontech Fault Code Index

Every Pylontech battery alarm, BMS protection event, and LED indicator state — what each fault means, the most likely cause, and what to do next. Pylontech batteries are battery-only — faults also surface through your paired inverter's monitoring platform. Covers US2000C, US3000C, US5000, and the Force-L2 and Force-H2 ranges.
Free remote diagnostic · pay only if we fix it — from £75 if remediable remotely
Book Pylontech diagnosisAll fault codes
  • Battery-only — faults surface through your inverter
  • LED indicators and BMS protection events
  • US2000C · US3000C · US5000 · Force-L2 · Force-H2
Pylontech battery fault you can't resolve?

If your Pylontech battery is in protection mode or showing alarms through your inverter, a remote diagnostic identifies the cause and recommends the fix — usually within 30 minutes.

Book free Pylontech diagnosisHow diagnostics work
5.0
Rated 5.0 on Google Read all 48 reviews

What a fantastic service. Had my fault diagnosed within minutes and actually managed to resolve the issue remotely within a few minutes more. This guy is like a “Solar Batman” helping consumers fix their problems using his extensive industry knowledge and expertise. Outstanding service. Thank you so much.

Andrew Palmer · May 2026

Ron is a super star. Two months ago my GivEnergy battery failed a firmware upgrade leaving it a brick. My installer couldn't/wouldn't fix it. GivEnergy couldn't/wouldn't fix it. Then they went into administration and all hope was lost. A flurry of emails later and Ron had diagnosed the fault (failed USB flash drive, something I'd suspected) and talked me through resolving it. Two months of nothing resolved in about 3 hours. It's great to work with someone who pays attention to the details, knows that they're doing (not just following a script) and gets stuff sorted without a fuss or up-charging.

Christopher · Apr 2026

My 90-year-old father-in-law had a solar system installed nearly three years ago that never worked properly and kept tripping out. Neither the original installer nor GivEnergy could resolve the issues, and we were even pushed towards replacing the system entirely when GivEnergy went bust. I contacted Ron at Solar Tech Support via WhatsApp, and within a few hours he had diagnosed multiple faults — including incorrect wiring that posed a potential fire risk. He carried out a home visit in Nottingham for £295 (including parts), fixed everything, completed firmware updates, and ensured the system was fully operational. Since then, it has worked perfectly. Ron was knowledgeable, responsive, and took the time to explain everything clearly. Highly recommended — excellent value and complete peace of mind.

Julian F · Jun 2026 Google

My GivEnergy hybrid inverter + battery system had worked faultlessly for 3 years when it suddenly stopped charging and discharging the battery. On contacting my supplier, who had used a sub-contractor for the installation work, I was provided with an email address at GivEnergy but, as it turned out, this is only for GivEnergy Software who are not able to assist. A Google search led to the Solar Tech Support web site, which contains a wealth of helpful information. I requested a remote solar diagnostic, and after providing Ron access to my inverter, he was able to identify and fix the problem within minutes. I am very impressed by Ron’s expertise and knowledge, which included useful information on the current state of GivEnergy Ltd. I would thoroughly recommend Solar Tech Support.

Simon Riddle · Jun 2026 Google

Contacted Solar Tech Support in desperation. After explaining the issues I had with my system a diagnosis was made and a solution proposed. Fantastic service, even contacted a manufacturer to arrange replacement parts for me. Great communications, explained all they were doing and what I had to do, clearly and precisly. Followed up to confirm all was ok. Excellent service.

Mr Machin · May 2026

After GivEnergy went into liquidation, just my luck, my battery started playing up (internal board crashed). Contacted my installer - not interested! Found Solar tech support on a Google search. Sooo glad I found this company! Ron is extremely helpful and has plenty of experience. He soon confirmed what the fault was, and helped me to get my system up and running again. Now moved my GivEnergy account to Solar tech support, and will definitely use again if I have more issues. Unusual to find such a helpful company in these times, no morons reading scripts, just direct contact with the engineer.

Keith Ballard · Apr 2026
How to read Pylontech faults. Pylontech batteries do not display numbered fault codes on a screen. Instead, the ALM LED on the front panel indicates alarm or protection mode. The specific fault type is identified through your paired inverter's monitoring platform (GivEnergy portal, Victron VRM, Solis Cloud, Fox Cloud, etc.) or by connecting to the battery via Pylontech BatteryView software over the console port using a USB cable.
LED indicator states

The front panel LEDs are the primary way to identify Pylontech battery status. The RUN LED shows operating state, the ALM LED shows fault conditions, and the SOC LEDs show charge level. These states apply to all US-series models.

RUN LED — solid greenNormal · charging active
The battery is operating normally and is actively charging. One of the SOC LEDs will flash to indicate the current charge level. This is the expected state when the inverter is sending charge current to the battery.
RUN LED — slow flash (~3.5s)Normal · idle / standby
The battery is powered on and communicating with the inverter but not actively charging or discharging. This is normal during periods of low demand when the inverter does not need battery power.
RUN LED — fast flash (~1.5s)Normal · discharging active
The battery is actively discharging — providing power to the home or backing up loads. The SOC LEDs show the current charge level. This is normal during evening self-consumption or during a power cut if EPS is enabled.
ALM LED — flashing red (~1.5s)Warning · approaching limit
The battery BMS has detected a parameter approaching its operational limit — this could be temperature, voltage, or current. The battery continues to operate normally under this state. Check your inverter's alarm log for the specific parameter triggering the warning. Common triggers include high ambient temperature in summer or a cell voltage nearing the upper limit during charge.
ALM LED — solid red, all others off Protection mode — battery shut down
The BMS has shut down charge and discharge to protect the battery cells. The battery will not accept or deliver power in this state. Common triggers include cell overvoltage, cell undervoltage, overcurrent, overtemperature, or a short circuit. Check the inverter alarm log for the specific protection type, then power cycle the battery — switch off, wait 60 seconds, switch back on. If protection mode returns immediately, the underlying cause needs diagnosis.
All LEDs off — battery appears dead Deep sleep or hardware fault
No LEDs lit means the battery has no power or has entered deep sleep protection after being fully discharged. Check the breaker or power button is on. If the battery was deeply discharged (left at 0% for an extended period), it may need a controlled bench recharge to recover. Do not attempt to force-charge a battery showing 0V without professional guidance — this can be dangerous if cells have degraded.
Force-series LED states (Force-L2 & Force-H2)

Force-series batteries use a different LED scheme from the US-series — a STATUS LED on the controller plus blue and orange module LEDs, with no ALM LED. The Force-H2 is a high-voltage DC system: Pylontech's manual restricts anything beyond reading the LEDs and using the normal switches to qualified persons.

STATUS LED — solid orange (Force-L2)Power relay open · will not self-recover
The Force-L2 controller has opened the power relay — the manual describes this state as an important protection, a failure, or a failed address assignment, and it does not recover on its own. By contrast, a flashing orange STATUS LED is a normal protection that self-recovers once the trigger clears, and flashing blue is an alarm with the relay still closed. Restart the system once and note whether any individual battery module also shows orange — a single orange module means that module is in protection or has failed, and the manual's recovery for a module in low-voltage protection is a controlled recharge, which is an engineer's job rather than a homeowner one. If the STATUS LED stays solid orange after a restart, the controller itself needs professional diagnosis and possibly replacement.
All 7 module LEDs flashing orange (Force-L2)Address distribution failure · stack will not run
Every battery module LED in the tower flashing orange together means the controller has failed to assign addresses to the modules — the BMS cannot enumerate the stack, so the system will not run. The manual's remedies are to replace the controller, or to identify a failed module by removing modules one at a time and restarting until the stack enumerates. That elimination procedure involves working on live DC connections and is strictly an installer or engineer job. Power the system off and back on once using the documented sequence (power switch, then BMS switch, then start button) — if the pattern returns, book a diagnosis rather than dismantling the stack. A single module flashing orange on its own means that module is offline, which is a different fault.
STATUS LED — slow flashing orange at power-on (Force-H2)Self-check failure · system will not connect
If the STATUS LED slow-flashes orange immediately after turn-on with the module LEDs off, the Force-H2 BMS has failed its startup self-check and the system will not connect. The manual gives two causes: the DC side already has voltage that differs from the battery string voltage by more than 20V (a commissioning or turn-on sequence issue with the hybrid inverter), or an internal BMS failure in the controller. Do not keep retrying the start button. The Force-H2 is a high-voltage DC system — correcting the inverter-side DC voltage before the turn-on sequence, or analysing and replacing the controller, are both strictly installer jobs.
STATUS LED — solid orange, module LEDs blue (Force-H2)Communication lost or BMS error
A solid orange STATUS LED on the Force-H2 means communication lost or a BMS error — the module LEDs tell you which. Module LEDs solid blue points to lost communication with the inverter (the communication cable and its pinout need checking), an overcurrent protection that releases once DC conditions normalise, or a controller failure. One or more module LEDs solid orange instead points to a module in temperature or voltage protection, or a module BMS failure — under-voltage recovery uses the black-start function followed by charging, which on this high-voltage system is strictly an installer procedure. If every LED is blue but there is no output, the manual points to a blown fuse inside the controller, which means a controller-module replacement rather than a user-serviceable fuse.
Voltage protection alarms

Voltage alarms trigger when individual cell voltages or the total module voltage exceeds safe limits. These are the most common Pylontech protection events, often caused by incorrect charge settings or cell imbalance.

Cell overvoltage protection Protection mode — charge stopped
One or more cells have exceeded the safe voltage limit (typically above 3.65V per cell or 54V module voltage). The BMS cuts off charging. Usually caused by the inverter's charge voltage being set too high — check the battery charge voltage setting in your inverter matches Pylontech's recommended parameters (typically 52.0–53.5V for a 48V stack). Cell imbalance can also cause one cell to overshoot while others are normal — this requires balancing.
Cell overvoltage warningALM flashing · charge continuing
A cell is approaching the overvoltage threshold but has not yet triggered protection. The battery continues charging but the BMS is signalling that it is close to its limit. If your inverter supports it, enable the "limit managed battery charge voltage" feature and reduce the charge voltage slightly. This gives cells time to balance before hitting the hard limit.
Cell undervoltage protection Protection mode — discharge stopped
One or more cells have dropped below the safe minimum voltage (typically below 2.5V per cell or 44V module voltage). The BMS cuts off discharge to prevent permanent cell damage. This happens when the battery is discharged too deeply — often because the inverter's low-voltage cutoff is set incorrectly or the battery was left in a discharged state for an extended period. Charge the battery from AC to recover.
Cell undervoltage warningALM flashing · discharge continuing
A cell is approaching the undervoltage threshold. The battery continues discharging but the BMS is signalling that charge is critically low. The inverter should stop drawing power before the hard cutoff triggers. If you see this warning regularly, your inverter's minimum SOC or discharge cutoff voltage may be set too low.
Module voltage imbalanceMulti-unit stack · SOC mismatch
In a multi-battery stack, the voltage or SOC of individual modules has diverged significantly. One module reaches full or empty before the others. Usually caused by mixing batteries of different ages or capacities, or by a faulty cell in one module dragging its voltage down. Check individual module voltages through BatteryView or your inverter's per-battery monitoring. Persistent imbalance may require isolating the affected module.
Current protection alarms

Current alarms trigger when charge or discharge current exceeds the battery's rated limits. The US5000 supports up to 100A continuous — exceeding this causes the BMS to shut down the affected direction.

Charge overcurrent protection Protection mode — charge stopped
Charge current has exceeded the battery's maximum charge rate. Each US5000 module supports 25A charge (100A for a 4-unit stack at recommended max). This can occur if the inverter's charge current limit is set higher than the battery can accept, or if solar generation spikes and the inverter sends all available power to the battery. Reduce the charge current limit in your inverter settings.
Discharge overcurrent protection Protection mode — discharge stopped
Discharge current has exceeded the battery's maximum discharge rate. Each US5000 module supports 25A continuous discharge. A sudden high-power load — such as a kettle, immersion heater, or oven — on the backed-up circuit can exceed the battery's discharge capability, especially with a single module. Add more modules to increase discharge capacity, or remove high-power loads from the backed-up circuit.
Short circuit protection Immediate shutdown — do not restart
The BMS has detected a short circuit on the battery output and shut down immediately. Do not attempt to restart the battery without first identifying the cause. Check the DC cables between battery and inverter for damage, exposed conductors, or loose connections. If cables are intact, the short may be internal to the inverter's battery input circuit. Requires professional inspection before reconnecting.
Temperature alarms

Temperature alarms protect the lithium cells from operating outside their safe range. Pylontech US-series batteries operate between 0°C and 50°C for discharge and 0°C to 45°C for charge — exceeding these limits triggers protection.

Charge overtemperature protectionCharge stopped · discharge may continue
Internal cell temperature has exceeded the safe limit for charging (typically above 45°C). The BMS stops charge but may allow discharge to continue. Common in summer when batteries are installed in enclosed garages, lofts, or utility cupboards without ventilation. Improve airflow around the battery stack — leave at least 100mm clearance on all sides and consider adding a small extraction fan in enclosed spaces.
Discharge overtemperature protectionFull shutdown · above 50°C
Cell temperature has exceeded the safe limit for discharge (typically above 50°C). Both charge and discharge are stopped. The battery must cool before it will resume operation. If this happens repeatedly, the installation location is unsuitable — batteries should not be in direct sunlight, next to heat sources (boilers, hot water cylinders), or in unventilated roof spaces.
Low temperature charging protectionCharge stopped · below 0°C
Cell temperature is below 0°C and the BMS has stopped charging to prevent lithium plating — a permanent and dangerous form of cell degradation. Common in unheated garages and outbuildings during winter. The battery will resume charging once temperature rises above 0°C. Do not attempt to bypass this protection. If the battery is in a location that regularly falls below freezing, consider relocating it to a warmer space.
Temperature sensor faultBMS internal · sensor disconnected
The BMS cannot read one or more internal temperature sensors. This may cause the battery to enter protection mode as a precaution since it cannot verify the cells are within a safe temperature range. This is a hardware fault inside the battery and requires professional inspection or warranty replacement.
Communication faults

Communication faults are the most common Pylontech issue in UK installations. These appear when the inverter cannot talk to the battery BMS over CAN or RS485 — and are often caused by incorrect cabling rather than a fault with the battery itself.

Battery communication fault (CAN)Inverter shows: BMS Lost / Batt Comm Fail
The inverter cannot communicate with the Pylontech battery over the CAN bus. Check: the communication cable is plugged into the CAN port on the master battery (not RS485), the correct battery type/protocol is selected in the inverter settings, the cable pinout matches your inverter brand (many supplied cables are wired for one inverter only), and the DIP switches on the battery are set for CAN mode. Inverter pairing guide →
Battery communication fault (RS485)Inverter shows: No Battery / BMS Error
Some inverters communicate with Pylontech over RS485 instead of CAN. Check the cable is in the RS485 port (not CAN), the DIP switches are set for RS485 mode, and the baud rate matches. RS485 wiring is polarity-sensitive — if the A and B pins are swapped, communication fails silently. Try swapping the A/B wires at one end if the connection was working previously.
Master battery not setMulti-unit stack · no CAN output
In a multi-battery stack, only the master battery communicates with the inverter. If no battery is set as master, the inverter receives no data. On US-series batteries, the master unit is the one with the CAN/RS485 communication cable connected to the inverter. On newer units, the DIP switch or link cable configuration determines the master. Check that the top or designated master unit has the communication cable fitted.
Inter-module link cable faultStack comm · link cables between units
In a stacked configuration, the short link cables between battery modules allow the master to communicate with each slave. A loose or faulty link cable causes the master to lose sight of one or more modules. The inverter may show reduced capacity or intermittent communication drops. Check each link cable is firmly seated in the correct port on each module. Replace any visibly damaged cables.
Module & stack faults

Faults specific to multi-module stacks and individual module hardware — internal BMS failures, firmware issues, and charge profile problems that affect the battery independently of the inverter.

BMS internal failure Internal error — firmware or hardware
The battery's BMS has reported an internal fault. This is a known issue on early firmware versions of the US3000C and US5000. Check your firmware version through BatteryView or your inverter's battery info page. If the firmware is outdated, a Pylontech-authorised installer can update it. If the firmware is current and the fault persists, the BMS board may need replacement under warranty. US-series faults guide →
Early charge cutoff (80–85%)Not reaching 100% · BMS limiting
The battery consistently stops charging at 80–85% instead of reaching 100%. This is typically caused by cell imbalance — one cell reaches the overvoltage threshold while others still have capacity. The BMS caps charge to protect the highest cell. Enable the battery's internal cell balancing by keeping it at a high SOC overnight periodically. Also check the inverter's charge voltage is set to Pylontech's recommended value and is not set for lead-acid profiles.
SOC stuck or inaccurateDisplay shows wrong % · SOC drift
The reported SOC does not match the battery's actual charge level — it may jump between values, stay stuck at one number, or show 100% when the battery is clearly not full. SOC drift occurs over time when the battery has not completed a full charge cycle. Perform a full charge to 100% and leave it at 100% for 2–3 hours to allow the BMS to recalibrate its SOC counter. If SOC remains inaccurate after calibration, a firmware update may resolve the issue.
Mixed stack capacity mismatchDifferent models in one stack
Stacking different Pylontech models (e.g. US3000C with US5000) is not officially supported and causes capacity and voltage mismatches. The smaller module reaches its limits before the larger one, triggering protection events and reducing usable capacity. If you have mixed models, separate them into independent stacks each connected to the inverter individually, or replace the mismatched unit.
Codes shown on the inverter & GX — Pylontech side

Pylontech batteries are battery-only, so many faults first appear as a code on the paired inverter or GX device rather than on the battery itself. The exact wording depends on the inverter brand — these are the strings UK owners most often see on Solis hybrids and Victron systems. Sofar, LuxPower, and Growatt inverters show their own battery codes, covered on those brands' fault-code pages.

Batt_Comm_FAILSolis hybrid · battery CAN data lost
The Solis inverter can see battery voltage on its DC terminals but is not receiving valid CAN data from the Pylontech BMS — on older Solis firmware the same condition was displayed as CAN_Comm_FAIL. The inverter will typically refuse to charge or discharge until communication is restored. In SolisCloud, compare the BMS voltage and battery voltage readings — if BMS voltage reads zero while battery voltage is normal, it is a communication problem, not a flat battery. Reseat the communication lead at both ends (battery CAN port to inverter CAN/BMS port) and power cycle the battery, then the inverter. If the fault persists, the communication cable is the usual cause — Solis's guidance is to replace early cables with the updated version or re-pin to their published diagram, something an engineer can confirm remotely rather than re-wiring plugs yourself. Inverter pairing guide →
BatName-FAILSolis hybrid · wrong battery profile
The Solis inverter has no battery model selected, or the wrong battery profile for what is connected. Check the battery selected in the Solis battery settings menu exactly matches the installed model (the Pylon option for US-series), and that the battery DIP switches are set for the Solis protocol, then power cycle the inverter and battery. Some third-party batteries that use the Pylontech protocol can also trigger this alarm because they do not identify themselves the way the inverter expects. If the profile and DIP switches are correct and the alarm persists, Solis's guidance is to work through the Batt_Comm_FAIL checks above.
NO-BatterySolis hybrid · 0V on battery terminals
The Solis inverter is sensing 0V on its battery DC terminals — as far as the inverter is concerned, nothing is connected. A healthy Pylontech 48V stack presents roughly 42–58V, so 0V points to the power path: the battery breaker or power switch off, an open fuse or isolator in the DC run, or the battery in deep sleep after a full discharge. Solis documentation spells this code both ways — NO-Battery and No Battery. Check the battery's own breaker or switch first and note whether any LEDs are lit. The documented Solis wake procedure is to power down the inverter, switch every battery rocker switch off, wait 10–20 seconds, switch back on, then press the red SW button on the master battery for about one second until the LEDs light. Do not probe the DC terminals or open covers — if the battery will not wake it may need a controlled bench recharge, and Solis's EU guidance also lists communication-cable causes worth checking once the battery is clearly awake.
Alarm-BMSSolis hybrid · battery reporting an alarm
Communication between the Solis inverter and the Pylontech BMS is healthy, but the battery itself is reporting an internal hardware or environmental problem — the inverter is relaying the battery's own alarm, so the fix lives on the battery side. Solis cites roughly 10–40°C as the comfortable ambient range, and unventilated cupboards, lofts, and freezing garages are the usual environmental triggers in UK homes. Note the battery's LED state (ALM flashing or solid), then power cycle the battery once — off, wait 60 seconds, back on. If Alarm-BMS returns, the battery's alarm history needs reading through your inverter's monitoring platform or Pylontech BatteryView to pinpoint which protection fired before any hardware work is recommended.
Internal errorVictron GX · slave modules offline
On Victron systems paired with Pylontech, the battery status on the GX device or VRM can show Internal error. Victron's compatibility guidance is clear that this is not a critical error — it appears when one or more slave batteries in the stack have dropped offline, either because they were discharged to a very low state of charge or because the stack has sat idle for more than 72 hours. The documented fix is simply to get charge into the stack — use grid charge if solar is poor — and the error clears automatically once charging begins. If it persists after a proper charge, individual module voltages need checking through the GX device or BatteryView to find the module that is not rejoining. This is a different fault from the US3000C/US5000 BMS internal failure covered above.
Fault not listed here?

Pylontech faults often appear differently depending on which inverter brand is paired with the battery. If you're seeing an alarm in your inverter's monitoring that you can't match to this list, share the exact alarm text and your inverter brand and we'll identify it. Retrieving the Pylontech log files via BatteryView is the fastest route to a definitive diagnosis.

Book diagnostic
Full diagnostic guides by fault type
Internal failure · BMS fault · firmware
US2000C / US3000C / US5000 faults

Full diagnostic — BMS internal failure, firmware versions, cell balancing, and warranty process.

CAN · RS485 · protocol · DIP switch
Inverter compatibility & pairing

Cable pinout, protocol settings, DIP switches, and brand-specific wiring for GivEnergy, Victron, Solis, and more.

Manuals · datasheets · wiring
Pylontech documents

Official US-series and Force H2 user manuals, datasheets, and installation guides.

FAQ

Pylontech battery fault questions

Pylontech batteries do not display numbered fault codes on a screen. Instead, they use LED indicators on the front panel. The ALM LED flashing red means a warning condition — the battery is approaching an operational limit but still working. The ALM LED solid red with all other LEDs off means protection mode — the battery has shut down. The specific fault type is identified through your paired inverter's monitoring platform or by connecting via Pylontech BatteryView software over the console port.
A flashing red ALM light means the battery is in an alarm state — a parameter like temperature, voltage, or current is approaching its limit but the battery continues operating. A solid red ALM light with all other LEDs off means protection mode — the BMS has shut down charge and discharge. Common triggers include cell overvoltage from overcharging, cell undervoltage from deep discharge, high temperature in an enclosed space, or a communication fault. Check your inverter's alarm log for the specific type.
Switch off the battery using the breaker or power button, wait at least 60 seconds, then switch it back on. If the battery entered protection due to low voltage, you may need to charge it from the inverter's AC supply before it will resume. If the battery shows 0V or will not power on, it may be in deep sleep protection and require a controlled bench recharge. If the same protection event triggers repeatedly after reset, the underlying cause needs professional diagnosis — do not keep resetting without investigating.
STS offers remote diagnostic assessments from free. Pylontech batteries log detailed operating data including cell voltages, temperatures, and alarm history. Our engineers can analyse this data remotely through your inverter's monitoring platform to identify the root cause and recommend the fix — whether that is a settings change, a firmware update, or a physical inspection.
Battery communication faults are the most common Pylontech issue. The inverter cannot talk to the battery BMS over CAN or RS485. Common causes include the cable plugged into the wrong port on the inverter, incorrect cable wiring (many supplied cables have the wrong pinout for your inverter brand), the battery not set as master in a multi-unit stack, or the wrong battery protocol selected in the inverter settings. Check the cable, port, and inverter battery type setting first. See our inverter pairing guide for brand-specific wiring.
Book

Battery alarm you can't clear?

Describe the LED state on the battery, what your inverter's monitoring is showing, and when the fault first appeared. We'll analyse the data remotely and tell you whether it needs a settings change, firmware update, or site visit.

  • Not affiliated with Pylontech
  • No fix, no fee
  • Written report with cause and recommended action

By submitting you agree to be contacted about your diagnostic request. We don't share your data with 3rd parties.

Call 07944 877 329 Book free diagnostic