PylonCheckPylonCheck
CZEN
Back to blog
Diagnostics and Faults· Ľubomír Sokolík

Why Different Firmware Versions in a Stack Damage Pylontech Batteries

I found four different firmware versions in a single stack. How a FW mismatch between master and slave batteries causes alarms, module disconnections, and gradual cell degradation.

This article was machine-translated from the Czech original.

This is something that isn't talked about much, but I've already seen it in several installations: a customer has a stack of 8–10 US3000C batteries and each one has a different firmware version. In one case, I found V1.2, V1.3, V1.4, and V1.8 — four different versions in a single stack.

How it Happens

Simple. The customer buys batteries gradually — say two in 2022, another three in 2023, and the rest in 2024. Each manufacturing batch has a different FW version. Pylontech continuously updates the firmware, but doesn't tell customers to "update your old units".

The problem is that the master battery (the first one in the stack, address 1) controls communication with the inverter via CAN bus. And if the master has an older FW than the slave batteries, it can lead to:

  • Different interpretation of protection thresholds
  • Inconsistent behavior during balancing
  • Different reactions to temperature limits
  • Communication errors between modules

How to Detect It Remotely

In PylonCheck, we read the FW version of each battery in the stack using the info command on addresses 1 to N. The output looks like this:

Device name       : US3000C
Main Soft version : V1.3
Barcode           : PPTCR03101B16466

If the versions differ, the system automatically generates an alert: "FW mismatch detected". Both the customer and the technician see it in the dashboard immediately.

Real-World Case

An installation with 10× US3000C. The customer reported recurring alarms and occasional disconnections of two batteries from the stack. The inverter reported a communication error.

After remote diagnostics:

  • Battery 1–3: FW V1.2
  • Battery 4–6: FW V1.3
  • Battery 7–8: FW V1.4
  • Battery 9–10: FW V1.8

The two newest batteries (V1.8) had different protection limit behavior. When the master (V1.2) sent a balancing command, the V1.8 batteries interpreted it differently.

Solution

Unfortunately, a remote FW update is not possible. Pylontech requires a physical connection via the EPON port and the BatteryView software on Windows. This means an on-site visit by a technician with a laptop and a special cable.

What we CAN do remotely, however:

  • Detect the problem — automatic alert on version mismatch
  • Set a conservative BOV — reduce the upper charge limit to minimize stress on cells with different behavior
  • Monitor imbalance — check whether the FW mismatch is causing gradual degradation
  • Recommend firmware unification to the customer — with concrete proof of why it's necessary

What This Means in Practice

If you are installing new batteries into an existing stack, always check the FW versions. Ideally, they should all be identical. If that's not possible, set the newest battery as the master (address 1) — newer FW is usually backward compatible with older slave batteries.

And most importantly — monitor. The problem won't show up right away. It can take weeks or months before behavioral differences manifest as actual cell degradation.

More articles