Hi all, an update on this. The cause is indeed that a small percentage of CCGX-es is just at its limits, and updating it to v3.60 pushes it over.
Rather unfortunate that we - I - have not recognised that during the development.
Also, while today most GX-es being installed have automatic updates disabled by default, most CCGX-es where manufactured when we had that the default to be enabled. And - apparently - left that way, as the vast majority of CCGX-es that report to VRM were updated overnight. Note that we recommend to keep the auto updates setting to Check only. Don’t let a GX update itself automatically.
Anyway, we’re now sending below email out to all (admin) users of the concerning installations on VRM. Which means CCGX-es with a concerning high CPU usage, measured by looking at D-Bus round trip time (see custom widgets on VRM advanced page). And recommend to roll back to v3.55.
On a similar note, there have been three or four reports of similar issues but then on an Ekrano GX, MultiPlus-II GX, EasySolar-II GX, or Cerbo GX. And they were either modded systems where some installed mod was constantly crashing, restarting, and causing a lot of extra CPU load, or very nice systems but also ones with lots and lots of devices connected, which apparently were on the edge and then tipped over after updating to v3.60.
It looks like we’ll decide that v3.55, and if needed due to bug fixes perhaps a v3.56 or v3.57, will be the last CCGX firmware version available for online updates. And then anyone that does want to go to a newer firmware version can still do that manually.
All the best, Matthijs
Hi,
Your Victron Energy system recently updated the firmware on your Color Control GX (CCGX) to a new version, v3.60.
This release includes some changes which have increased the CPU load on the CCGX leading to some issues (specifically Error 67 - BMS not found, VRM realtime being disabled, GX rebooting, and others).
Our statistics show that approximately 3% of all the CCGX-es that were updated, and unfortunately this includes one or more of your systems.
When investigating the cause, we identified those who are most affected have three or more solar charge sources (either Victron MPPT or AC PV) connected.
If you are managing a large fleet of systems using the CCGX as their GX device, there is no need to immediately worry about all of them. Our VRM stats show that 97% of updated CCGX are still working well and as expected.
To solve the issue, we recommend to manually revert to the previous version. This is a simple procedure, documented below, accessible via the CCGX screen, or via the VRM remote console.
If you are not experiencing any issues, it is fine to do nothing right now. This situation is not urgent unless you are having problems. We are treating it as a priority to assist in resolving any issues as soon as possible.
A few notes on future updates: The CCGX is quite an outdated design and the majority of units was sold a long long time ago, having shifted to the Cerbo GX and Ekrano GX. We’re currently analysing this deeper and might very well decide that there will be no further (automatic) updates for the CCGX - except for serious bug fixes. To remain up to date on how we’ll proceed with the CCGX & Venus OS updates, subscribe to the news section on Victron Professional and or below linked Community thread.
We’re sorry for any trouble this has caused!
Yours sincerely,
Victron Energy BV
How to downgrade the CCGX to v3.55
The CCGX keeps a copy of the previous firmware version to make it fast and easy to revert to it.
The step by step instructions for how to “Revert to a previous firmware version” are here.
If you are a fleet operator and not sure which site this is referring to, please reply to this email and we will be able to help more directly.
Further information on CCGX and Venus OS on Community
More details on the CCGX and Venus OS will be shared on this community thread.