My system runs with a 2s2p PV configuration (1620 Wp) and a 16s LiFePo battery using an MPPT SmartSolar 150/45. Last summer, this setup worked without noticeable issues. This summer I noticed that the power output stays well below expectations (at about 50%-60%). Initially I suspected an MPPT hardware issue so I replaced the MPPT with a brand-new device. This did not change the situation.
I discovered the following today:
I noticed that the MPPT keeps the string voltage always approx. 5V over the battery voltage. The Vmp of the cells is 31.2V or 62.4V - so this is close to the battery voltage (~54V) but well above what Victron requires for startup.
After noticing this I confirmed by re-wireing my setup to a 3s configuration. This puts the Vmp well above the battery voltage. I found that the output power reached an expected level.
According to Victron a 5V Voltage difference is needed for MPPT startup but I did not expect that the MPPT maintains this constraint after starting up. Instead Victron outlined here around the 6:00 minute mark that 1V is sufficient https://www.youtube.com/watch?v=uTMVmW7GTus
I remember that I updated the firmware in spring so I suspect that firmware changes are the reason why my setup worked last summer but acts up this year. (*)
All tests were done on a perfect day in the middle of a heatwave close to the summer solstice around mid-day.
Is the 5V minimum voltage difference between PV voltage and battery voltage is mandatory for proper MPPT operation on the current firmware? And if so, would this explain the reduced performance I observed with the lower-voltage PV configuration?
(*) I tried to downgrade to an older Firmware version but the MPPT does not properly connect anymore to the VictronConnect app. It is stuck in “Fetching Data”. MPPT reboots did not change this. The used app version is v6.34 on an Android Pixel8a. (I crosschecked on a different Android device as well)
This is the situation running 2s2p. You can see the 5V voltage difference which limits the max power in this case:
This is the situation running in 3s.

