Anyone else had grief with a Victron MultiPlus 24/2000 dropping to float too early on a bulk charge?

by Simon · 1 week ago 88 views 1 replies
Simon
Simon
Member
8 posts
Joined Jan 2025
1 week ago
#8078

Been scratching my head with this for a couple of weeks now. Running a 24V system with 200Ah of Battle Born LiFePO4s and a MultiPlus 24/2000/50. When charging from shore power the unit seems to be jumping to float after only getting the batteries up to about 80-85% SOC, rather than pushing through to a proper full charge. Bulk absorption is set to 28.4V and float at 27.2V, which should be fine for these cells.

I've had a look through VE.Configure and the absorption time is set to "adaptive" at the moment — wondering if that's the culprit. The voltage seems to be hitting 28.4V fairly quickly under the lower loads I'm drawing during charging, which might be convincing the unit it's done when it really isn't. Battery monitor is a Victron BMV-712 and that's reading a consistent 82-83% when the MultiPlus decides it's happy.

Has anyone gone through this with LiFePO4s specifically? I know the charge profile is quite different to AGM and I'm wondering whether fixed absorption time would be more reliable than adaptive for this chemistry. I've seen a few people mention switching to a custom ESS profile but I'd rather keep it simple if possible.

Dizzy83
Dizzy83
Active Member
13 posts
Joined Aug 2024
6 days ago
#16314

Dizzy83 | 📍 Mid Wales | Posts: 847


@Simon1988 Classic one this! First thing I'd check is your absorption voltage setting in VEConfigure - if it's set too low for LiFePO4 the unit will hit that threshold quickly and bail out to float thinking it's done. Battle Borns want around 29.2V absorption for a 24V bank.

Also worth checking your "repeated absorption time" and "absorption time" settings. The default absorption time can be surprisingly short.

Have you got a BMV battery monitor connected? If the MultiPlus is relying on its own current sensing rather than a proper shunt, it might be deciding the battery's full based on dodgy readings.

What firmware version are you running? There were some quirks in older versions around charge algorithm behaviour with lithium profiles.

Log in to join the discussion.

Log In to Reply