My system consists of a 5kWh 48V Lithium with CanBus to a CCGX. It has a Multiplus as well as an MPPT150/35 and 1000W of panels. It has been working for more than a year without the MPPT or panels and this week i added the charge controller and connected it up to VRM. I now have an error banner everytime i look at it which says
System overview - GX Error #48 DVCC with incompatible firmware: Warning
It does not show an error on the CCGX. As i understand it is because the Multiplus is older it has V158 installed on a Product ID 2622 and says it cant be updated to V552 (I did updated it a year or so ago but not sure how far it can be updated) The CCGX has V3.53 and i further understand the error arises because DVCC is forced on which i think was done so it can control the charging of the battery via both the inverter and charge controller.
I can see that the system works by ramping charging up and down as required based on load and battery SoC and my question is,
āIs this an alarm to be worried about and what should i do to improve the situation?ā Thanks
There is almost nothing you can do besides buy a new inverter.
What is means is the system canāt control the inverter through DVCC. It usually onky gets forced on by battery comms though, what battery do you have?
But that is not really an issue as the inverter is programmed to know what to do and has been doing it for some time now.
So if you can live with it, your battery will be fine. (Which is really what it is about) I am assuming besides with the addition of solar you are pretty much using it the same way you were before?
Hi Matthias, I have the MK3 but only got it that far. See the attached photo when i look for updates via the VRM.
If there is a way to use the MK3, do you have a copy of the procedure?
The 1342 message is signifying the CCGX is too old to use the VRM update method. Download the VE Configuration Tools package from the Victron website and look for VEFlash. Best done with a Windows machine. There should be instructions there too, and plenty of warnings to follow them.
Matthias and John, Thanks for the extra info. I have all the documentation and software updated via Dropbox and will try back down this path. I already have VE Flash installed so will check if it is up to date. I know i did do this about 18 months ago but only got so far. I will try again.
Cheers
The system is now working exactly as i had expected but i did have problems i hope you can shed some light on.
When using 2622158 I got the above warning so i updated to 2622552 (latest version) however, the inverter then showed low voltage and would not switch on. At first i thought it was the VE Bus cable but soon found it was not though this appeared to indicate that the CCGX and Multiplus were not communicating. Finally, i decided to roll back to an xxxx4xx version of firmware and chose 2622459 and with little more than loading the original configuration it is now working fine. I have of course disabled auto update.
Is there a hardware sunset for firmware upgrades or could something else i did have caused this? I am reluctant to try upgrading again but could do it if there is an explanation that maybe i took too large a leap in firmware versions and needed to settle on an intermediate first?
Edit: After i wrote this a link to another thread popped up
I can confirm that the VRM is still seeing the old 159 version which was the nearest to a total roll back i could get before i then tried the above xxxx4xx intermediate. I would have thought the VRM was more of a reporting and SCADA system than an integral part of local control.
Hi Michael, thanks for reporting back. Iām interested in your progress because I have an old 2624 Multi that came with v158 fw and a similarly ancient CCGX that also throws that 1342 message.
Have been running v552 on the Multi for a while now without issues, but a couple days ago updated the CCGX from 3.53 to 3.54. Since then I noticed that VRM never reaches the āRealtimeā state.
I was previously aware of the possibilities of that āmultiple rebootā thing you quoted. But that prompted me to try another anyway today. And it worked, VRM now reaches Realtime fine. And I havenāt seen anything to suggest our old kit canāt handle it, but there may well come the day when firmware bloat pushes it over the line. And then it should say āToo Busyā or suchlike.
Thatās great news John, I love it when someone asks a dumb question and it prompts someone else to try something that works for them
The Engineer in me wants to rush out and do as you suggest but the pragmatist says let sleeping dogs lie. The van is having some work done all of next week and so i need to be a stable point for that but once we get it back, i will have three weeks before we head out to take that leap of faith and let you know.
BTW, i had already upgraded the CCGX to V3.54 before i did the Multi so it seems likely that there is a gremlin in there that needs two iteration s of chasing its tail around the loop to become stableā¦?
