The tech already got back to me on my questions. He did not say that the fw specifically fixes MPPT issues, he just said "it fixes some program bugs, maybe the update can solve the problem".
What I found interesting is that I sent a screenshot of the PC software tool showing my settings and he said I need to do the lithium programming settings from the lithium parameter screen. Here is a screenshot from a video I was sent. I don't know what would be different from this screen than using the user choice.
For now I am going to leave it set up from the user parameter screen.
View attachment 176514
Hi. I have used the slightly 'smaller' BN3215 for several years (older firmware), and it runs MPPT in "Boost Mode" whenever the batteries are less than 99% full (withouth stopping).
One value which I set a lot higher than they showed in this image (for "12v" batteries) is the "Boost Recon. Charge Volt": they have only 13.20 volts, while I am using 13.50 volts. Their value, if I understand correctly, wil prevent "Boost/Absorb" charging when the battery pack has fallen below float (13.6, or 13.8?? -it's fuzzy and my eye's aren't good), but still remains above 13.2 during its intermitten test cycles.
13.2V total (3.300 per cell, in a "12v" 4S configuration) is only around 70% SOC. My value promotes "Boost Charging" whenever the pack is less than 99% full. (That wouldn't be great in long term storage, but works extremely well during my RV trip. My RV is stored in the garage between trips, with no sunlight hitting the panels).
I don't know if "Float Charging" firmware logic might also impose or prefer a low current limit, maybe related to the stated battery capacity, during "float charging". Within a set of squirrely microcod decisions, EpEver might decice that PWM mode is adequate for "mere float charging", even when the battery string is still willing to accept high current at the lower voltage.
My scheme promotes Boost Charging, and EPEVER runs in MPPT mode and high current until my batteries are stuffed to the gills (99%+), and reverts back into 'Boost Mode' on the next test cycle if they've fallen below that value.
- - -
Looking forward to your folow-up report of results with new firmware in both your SCCs, but I'm getting by with a very old version (with this parameter change in place.)