Victron posted the new update to Venus OS to 3.62 reporting lots of bug fixes unfortunately it seems to have introduced a bug
I have a multi 2 set up as ESS with a smart meter for monitoring grid power connected to the usb on the GX Cerbo after installing the system went into pass through mode, check all the setting BMS, Smart meter, PV could all be seen reporting no errors etc
So had to revert back to 3.6 version system now working as before
Is it a Shelley meter? Do you have a Cerbo or a CCGX?
The meter is an ET112 carlo Gavazzi according the Gx firmware 4, but the GX see it fine with no errors it more likely to be the Plylon force L2 battery BMS
As that indicates no charge current allowed or is set at zero
Cerbo GX
How long did you wait before reverting?
The image doesn’t show the state being in passthrough, it is still under external control.
You can see loads being serviced by PV, if it was passthrough, grid usage would be higher.
What CCL was being reported?
It is charging, just very slowly.
About 1/2 hour I will update again to show some screen shots and the CCl levels
Just check that the meter setting doesn’t revert to internal in ESS.
The common causes are:
- When the GX device is no longer receiving data from the grid meter. Note that this is only for systems that are configured to have an external grid meter. See the Settings → ESS → Control without grid-meter setting.
- Systems with a canbus-connected lithium system: when the GX device is no longer receiving information from the battery, via the CAN-bus.
- When charging the battery is not allowed (BMS max charge current = 0A, or max charge power = 0W) and there is excess PV power.
So if you can see the meter and it is reporting, then you want to check points 2 and 3.
Yep checked all the points and all working or communicating with no errors
Will have another look later in more detail
Only obvious observation is the system is modified, which is the #1 cause of 3.6x issues.
As a test you can use the disable all mods option (it will stop everything including nodered etc), click the firmware reinstall option (it leaves settings intact) and reboot. See if that helps.
You can enable the mods again after.
I also see you have dropped the CVL in DVCC, that really shouldn’t be there or be set like that, it is unrelated but worth a mention.
Ok will give that ago
CVL is set to absolutely stop over charge voltage as well as the setting in multi it seems to be ok as the batteries now get 100% SOC with no issues, I see what your saying and probably not required more of a battery balancing set point when batteries where new
Thanks for mod thing
Hi it only works if modification are not on once I re-enabled modifications went back to pass through
Ok, so you have a mod that needs to be updated, which is a common issue.
The mod developers don’t always keep in step with Victron updates.
Best is to check the relevant git page and see if you are current, and update if you aren’t, or log an issue with them if you are.
Not much Victron can do to help as mods are unsupported and untested, and as mentioned, are almost always the underlying cause of issues after updates.
Are you using GUI mods?
There was someone else who had a similar issue. Can’t remember what exactly it was. Maybe serial battery. No idea anymore.
I am using gui mods but to be honest it’s a bit pointless now with the new gui but there was lots of nice functions with it like all the signal or gauges that could be displayed
Any way I thought I would have a look at that and tried 123 smartBMS Venus the only smart thing with that it completely locks the system as it sends a load of dodgy data BMS alarm solar alarms etc only way to recover is disconnect everything from the Cerbo except Ethernet and remove it as the gui screen just locks up and you can’t get to the screen to remove it
After all sorts of different enabling dis-enabling functions 3.6 is still the most stable I stick with that until victron update Venus OS again sometimes best to leave things working if nothing broken
Ok so another GUI mod failure it was. Anyway. Cool that you’ve figured it out.
I usually don’t update firmware. Not without something that I really need. So far I am lucky - knocking on wood. - but you never know until it hits you.
Have a wonderful weekend 