Hello, I have a 48/5000 MultiPlus system with JK BMS 32 KW batteries (LIFE04). Last night I set the system to “keep batteries charged” to let the batteries balance. This morning I saw on the dashboard that the battery level was 90%. The batteries’ display showed 99% (so it may even have reached 100% overnight). I changed the system back to “optimised without BatteryLife”. My question now is: why do the readings differ? The system has been running for a month now, so how can I fix this? Thanks in advance for your replies, and hopefully some answers. P.S. The ESS does seem to be working normally.
How is your system setup? In order for the GX to be able to read the batteries SOC there needs to be communication between the two. Then the battery BMS needs to be set as the controlling BMS in the GX. Under System Setup, Battery, Battery monitor.
If either of the two is not done, then what you see on the GX or in VRM (or whatever you see as “the dashboard”) is the estimate of the Multiplus.
Thanks, Chrigu. I’ve already set up what you suggested. The GX can read the batteries, and on the dashboard I’ve tried setting it to automatic and also to battery, but nothing changes. Is there perhaps another solution?
Under Battery measurment ive also set the Multiplus to invisible. Maybe thats the difference
There is still a 9–10% difference between the value in the VRM portal and the value shown on the batteries’ display. This is additional information.

The cell voltage is then 3.55 volts (that’s 100% for me)
What values have you set in the JKBMS (do you have one or two BMSs?)
Hello Fredd, I have the same issue. The cell voltage is good and the battery is at 100%, but the dashboard shows 90%. DESS is working normally, and you can see that the battery is consistently 8, 9 or 10% higher than the dashboard shows. I have 2 batteries daisy-chained via RS484
I experienced this too with a JK-type BMS.
It would be better to turn off the Multiplus battery monitor and manage the battery through the JK.
The Multiplus can measure the battery differently due to things like self-consumption and voltage drops. I don’t think it’s the right device for measuring this accurately anyway.
Hello Muammer, that sounds like a good tip. Could you tell me where to disable the battery monitoring on the Multiplus and where I can manage battery monitoring via the JK? I’m still learning and don’t know everything. Many thanks in advance.
It is done in th base programming of the inverter, but if you are using ess, then the internal monitor has to be enabled.
The way to have the ‘correct’ percentage shown is to have the battery monitor set as the one you want in the GX under system set up.
You are running with an unsupported battery though. It seems the driver you are using is not updating the system correctly.
I assume the connection runs via VE.Can and is daisy-chained with RS484.
Try using just one battery with VE.CAN and check whether that makes any difference.
I also have 2 batteries and connected them to VE.CAN 1 and 2
Hi Fredd, I’ve connected the battery via BMS.can, and linked the second battery to the first using RS484. I’ll give it a try. Thanks.
I’m cautious with USB RS484 myself and have used galvanic adapters.
Not all connections on the Cerbo are galvanically isolated.
An alternative is a two-wire connection (without GND).
I do this with VE.CAN as well, and it works fine for me.
Sorry folks…I’m finding it almost amusing by now. Do finally learn this…your SOC values from the BMS (regardless of manufacturer) are generally inaccurate. It’s a problem that has been described dozens of times. The BMS don’t detect small charging and discharging currents, or only detect them inadequately. Especially with multiple units, when the currents are split between the units, the SOC values can drift extremely far apart. Posts about this topic have been piling up a lot lately. The problem is usually not incorrect or inadequate communication, but incorrect readings by the BMS units.
yep, that’s how it is — still annoying, and it can even be dangerous for the batteries!
in my case, I have 2 identical Liontron batteries, each 5 kWh, connected to the Multi via Cerbo,
both have the same very good cell voltages, which differ only slightly in the third decimal place. The Cerbo shows an SOC of 15% for the (single battery overall), and you think everything’s fine — not at all.
In reality, with the same capacity, the same total voltage and the same cell voltage,
Battery 1 SOC 22% and Battery 2 SOC 8%, giving an overall SOC of 15%
if you keep using it, Battery 2 risks conking out …
The solution would be: enter the SOC manually in the BSM, …
Regards, stocki
I record my SOC values purely via the shunt; the system doesn’t care at all what the BMSs report. I check it regularly, but that’s all. I have 7 battery blocks, and the BMS SOC values are all over the place, sometimes differing by more than 50%, even though I’m sure they’re all at the same level.
The shunt accurately measures what goes in and out, and runs for months without much calibration. Setting up the shunt is a bit fiddly, but once it’s done, it works.
The SmartShunt does have one weakness, though: it doesn’t measure the standby consumption of the BMS, balancer and other equipment connected directly to the battery block. This leads to regular discrepancies in winter, especially if a full charge and calibration aren’t carried out regularly. In my view, Victron could do something about that on the software side.
But anyway… the BMS SOC values are nothing more than rough estimates, and that’s putting it positively, in my view.



