I have recently installed a system which consists of:
Victron Multiplus II 48/5000
Victron Smartshunt
Victron vm-3p75ct energy meter
Victron Cerbo GX
Fronius Primo 8kw solar (existing)
The system is setup as grid tied, so everything on AC input only.
For some reason, ESS operates well for about half a day, the just refuses to charge or discharge the batteries. Even though it still has all the info it needs from the grid meter, from the battery (Smartshunt), and there are no alarms or indications shown as to why it would refuse to do its job.
A simple reboot of the Cerbo GX, and it instantly starts working again.
Here is a video of me walking through the settings showing everything should be happy, and then rebooting the GX and discharge/charge starts happening.
Could a guru from Victron please help? I’m assuming a bug since rebooting fixes it.
If the error occurs, check your battery information to see whether your charge and discharge values are set to 0.
You once had a JKBms integrated … where does your GX get the values for charging / discharging currents from?
Only a SOC from the shunt … nothing more.
Where can I find charge/discharge setpoints when using Smartshunt? I know when I had JK BMS integrated this was something that JK BMS would communicate, but where with Smartshunt?
I gave up with JK BMS for now, since CAN communication would be lost each couple of days, again, resolved after Cerbo GX is rebooted. That’s a battle for another day. For now, I just want the Smartshunt being used for battery monitor, and charge/discharge always 70 amp as configured using Veconfigure.
Ultimately I’m trying to run this as simple as possible for now, to iron out this bug with Cerbo GX ESS.
We have released Venus OS v3.53 that fixes the Cerbo MK2 VE.Can port 2 issue for (almost) all systems that we analysed via VRM.
The complete troubleshooting processs for this is:
Check if VE.Can Port 1 is in use as well. Our VRM stats show that often its not. In case not, replug and reconfigure the GX to work on VE.Can 1 port instead.
If both ports are needed, update to Venus OS v3.53 or later, which will in most cases fix the issue.
I am not certain if that is the issue that you’re experiencing, but it shares enough similar symptoms that it is the first thing that I would try.
Only if that doesn’t fix the issue, contact your dealer for further troubleshooting and if necessary replace that Cerbo MK2 (under warranty).
The change included in Venus OS v3.53 fixes the VE.Can port 2 issue for most Cerbo MK2s, but we’ve seen some of them where there really is a hardware issue and RMA is the only solution.
