This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Have a Color Control GX managing my system. I managed to brick it by incorrectly editing the sytem.conf file. Then I managed to install a fresh image to get it running again. Hope to help someone save a few hours of head scratching, caused by my own fault
Just to save someone a headache I want to share my experience.
I edited my system.conf file as per instructions:
https://flows.nodered.org/node/@victronenergy/node-red-contrib-victron
/etc/dbus-1/system.conf and add the following directly above <policy context="default">: <listen>tcp:host=0.0.0.0,port=78</listen>
<auth>ANONYMOUS</auth>
<allow_anonymous/>... but not in the correct place in the system.conf file. This was going to hurt.
Result was the CCGX would not reboot, it got stuck on the blue splash screen for Victron energy.
Looked it up and found the three button method for rebooting from the flash drive.
followed these instructions.
https://solaradvice.co.za/wp-content/uploads/2016/10/Updating-Firmware.pdf
Still the CCGX would not reboot until I changed the swu file within the zip file.
Based on the venus-upgrade-image-ccgx.zip I replaced the upgrade .swu file for the latest new venus image I could find for the CCGX. These were the files I used to reboot my CCGX.
Copied these files to my sd card and finally it rebooted.. Phew almost an expensive mistake.
Then I edited the system.conf file , but correctly this time, and many many hours later it is running well again. This saved my CCGX. Lesson to self slow down and follow instructions meticulously. Thanks
