I have a new quattro 48V/10000 with an AC inverter on AC out 1. The AC surplus charges 3 Pylontech US5000 1C batteries. When the batteries reach 100%, the DC current shown by the quattro (via the Cerbo GX) drops to zero, but the actual current going into the batteries (as reported by the Pylontech BMS) causes them to charge slowly (about 2A), and the voltage gradually rises until it eventually exceeds 53V. At that point, the battery sends an “internal failure” alert and briefly cuts out, triggering a “low battery voltage” alert. The battery then restarts in idle mode (on the Cerbo) with an actual current of 0A. It then slowly discharges until it reaches around 52.2V. If there is still AC surplus, this cycle starts all over again indefinitely: slow charging, alerts, idle, slow discharging, etc.
I’ve tried lowering the maximum charging voltage to well below 52V in DVCC, and also in the quattro configuration via VEConfigure, but it makes no difference.
It looks as though the current measurement on the quattro is off by about 2A. The voltage reading is also inaccurate by -0.25V, but that isn’t a problem since the limit set (in DVCC and VEConfigure) is well below 52.8V (the limit specified by the BMS). Perhaps the quattro genuinely thinks the DC current is zero, but that isn’t the case. And the BMS can’t stop the current being fed by the quattro (except by briefly disconnecting the battery).
The batteries are new and there is no cell imbalance (maximum 10 mV).
Single-phase installation, Quattro 48V/10000 (v508) + Cerbo GX (v 3.81) + 3 pylontech US5000 1C batteries on the VE.CAN bus + 3P75CT meter + solaredge SE6000. Unrestricted export for the SE6000.
The voltage difference between the quattro and the BMS remains the same whether charging current is flowing or not. So this really is a measurement error on the quattro’s part (it underestimates the voltage by 0.3 V). When you’re close to 52.8 V, that matters! So 52 V via VEconfigure actually corresponds to 52.3 V. But it’s easy to correct: just set 51.7 V (max) and 50.7 V (float) to get the correct actual values. Well, I think so!
However, what seems to be causing the problem is an error in the quattro’s DC current measurement, as explained above. And that’s more complicated. As long as the quattro doesn’t take the BMS reading into account, charging won’t stop until the BMS reaches its 52.8 V limit and cuts off abruptly.
So the quattro absolutely needs to take the voltage and current readings from the BMS into account!!! That would solve everything.
In the meantime, I’ve entered the values 51.7V and 50.7V, as well as 43.7 and 47.7V, via VEconfigure. This should correct the calibration of the quattro’s voltage measurement. Useful only in an emergency, if I understand correctly. But shouldn’t the value in DVCC, which is compared with the BMS, be changed? 52 V?
I’ve never had an overvoltage alarm or BMS shutdown with Pylotech batteries
I’ve always followed the instructions and, when using the batteries for the first time, let them balance themselves for a long time with “keep batteries charged”.
At the end of the document, there are some troubleshooting tips.