I have a MultiPlus 2x120, a Cerbo, and a Smart Shunt.
I noticed that the MultiPlus never reports the SOC - it always reports it as - -% My guess is that something needs to tell it the SOC…
I have a SmartShunt that does know the SOC and reports it. I implemented DVCC so that the shunt can share the battery temp on the VE Bus and noticed that it also then shares current, which seems smart to me. My understanding of DVCC is that when those variables are shared on the bus other Victron items can make use of them.
This leads me to a probably dumb question, but if DVCC exposes those variables on the bus, why doesn’t it also share the SOC variable on the bus so that the Multiplus can make use of it?
Is the inverter battery monitor enabled and set up? If it isn’t that thats why it doesn’t have an SOC to report.
Usually they ve bus soc synchronises to the monitor set in system set up.
Yes, that is the only way to have the inverter report SOC. Which brings me back to my original question, if the smart shunt is the most accurate (read preferred) way to determine SOC, then why is it not broadcast on the bus when DVCC is enabled? That way the inverter could read that variable and make use of it.
I suspect this is more of a ‘feature request’ just as being able to set the absorption voltage on the inverter is…
Internal logic is too simple. And it does no real processing. It doesn’t care what the soc is for lack of a better way of putting it.
The GX is the one with the brains. And is the system co ordinator
If you don’t enable the ve bus monitor is does not synchronise as the feature on the inverter is not enabled.
The ve bus uses voltage anyway not so much soc for things. And the system will use the battery monitor set on the GX
Bulk and absorption are the same target voltage so two different voltage are not needed for those two stages.
The difference between bulk and absorption is one is constant current (CC- where a hopefully constant current is applied to reach the target voltage) one is constant voltage (CV - not much or no current but he battery is now held at the target voltage).
I do not understand your explanation on the SOC. To me, it’s this simple, apparently the smart shunt is the best source for state of charge, and so, if DVCC is enabled then why not expose that variable on the bus and then the inverter should use it.
With respect to absorption, I made a serious error there, I meant to say equalization voltage. There appears to be no way to get my batteries to equalize at the 16.2 factory spec. I even tried turning up the absorption voltage, to no effect.
DVCC is mainly for charge control → voltage and current not SOC.
DVCC = Distributed Voltage and Current Control
The MultiPlus doesn’t need to know the SOC.
If you want to use the SOC in the configuration of the MultiPlus (controlling an assistant) than you just have to enable the internal battery monitor in the settings of the MultiPlus.
Do you know if DVCC shares battery voltage? Apparently the Multiplus has the ability (optional) to have a battery voltage sensor attached so that it can take into account cabling losses when charging.
Update: I found a good article on this here;
Now if only there was a way to set the equalization voltage…
