Im asking this question as a professional Victron installer, I propose to install a EVCS into a clients MP 3 Phase ESS system, they currently have CCGX with LAN connected. My question is will the EVCS connect via wifi to CCGX? and would i require a simple Wifi dongle? Can we have both wifi and LAN operating at the same time?
Can someone give a bit more clarity on how to bring the Multi RS in VRM?
The manual is... limited in this regards.
I have a CCGX (on my existing quattro installation) and just bought a RaspberryPi on which I installed VenusOS and I also purchased a MK3 adapter.
From what I can tell, only VECan is available on the Multi RS, but when I connect to CCGX it won't show anything. Do i need the little RJ45 end plugs (which didn't came with any device...) ?
What would I need to connect it to RPi?
Hi, I have a setup using 4x separate banks and each powered by 24v 100a / 1out.
I'd like to have a screen that showed the status and power output of each plus I/0 control. Is this possible on cerbo or any other type of custom set up.
Je n'arrive pas a accédé au contrôle a distance sur VMR que se soit depuis mon app ou depuis un pc.
J'ai bien suivi les étapes : maj du logiciel 2.9, VMR fonctionne bien le réseaux est câblé sans mot de passe, j ai cocher l option sur le color contrôle de travaillé en bi latéral.
l'erreur fournis par le color control est : impossible de se connecter a distance vérifier la connection réseaux.
Merci de votre aide
Is VRM borked?
The Color Control GX lost power and then the Multplus 3000/24/120 shut down too. We have 50 amp shore power; the 240v works but not the 120v.
Can I connect multiple Tank 140 to a CCGX. How many Tank senders would the CCGX recognise ? The CCGX has two USB inputs, meaning 2 Tank 140 ? or can I connect more via a USB hub ?
The question is answered for the Cerbo GX, but is the CCGX the same ?
I'd like to update the fimware of the CCGX unit in my EasySolar 24/3000/70 to the latest version.
Anything over v2.18 results in the CCGX being stuck in the Victron logo Splash screen on boot.
I tried updating it via Wifi, the SD card via the 3 button boot menu procedure and with and without the CCGX connected to anything as suggested here.
Tried replacing the USB cable aswel to no avail...
The SmartSolar and Multi plus units inside the EasySolar never gave me any issues and I could update them to their latest versions.
(Currently both running on the latest stable release candidates.)
With v2.18 running the CCGX sometimes looses all readings on the SOC and/or spontaneously reboots.
I'd like to update the CCGX to the latest version (v2.98), any idea's what I might have overlooked or can try?
Thanks in advance for your input !
Salesmen have sold a job that I'm a little unsure about on paper. Have a 3kW EasySolar II with Pylontech setup (straightforward as have done many of these), alongside this though is a separate Colour Control GX device which will be situated in the living area of the home to allow for easier monitoring of the system.
Having a read through the manual I noticed it mentions difficulties setting up the CCGX if using VE Bus managed batteries. However with Pylontech being BMS Can, I'm just curious if it will be as simple as running a VE Bus and power cable from the EasySolar II out to the CCGX, standard VE Can to BMS Can on the battery and away we go as per usual? Or if there is anything else that might cause me some hiccups?
Cheers in advance.
the relay in my CCGX stopped working and I have been given a replacement under warranty. I swapped everything across but I get a #67 error, which I looked up but it isnt clear to me which setting I need to modify to get it to work. Any assistance would be helpful.
My system includes:-
Quattro 48/8000/110-2x100 rev2
BYD B-Box Pro
2 x BlueSolar Charger MPPT 150/60
I would like to replace a faulty controller (Blue Hybrid Energy controller) IMG_0550 conv.jpeg in an existing system that has been in operation for 5 years. The system has Victron Quattro inverters IMG_0551 conv.jpeg and LG Chem batteries IMG_0554 conv.jpeg IMG_0545 conv.jpeg.
The idea is to replace the existing controller with Victron Color Control GX. Issue is compatibility with existing system.
I recently installed an EM111 Carlo Gavazzi meter to monitor my grid connection point to limit my grid feed-in.
To make the meter work, I had to change the meter parameter "Measure" to "b", such that reverse power flow would read as -ve and forward as +ve. When set up like this, the Victron system works perfectly.
However, after a couple days, I am finding this "Measure" parameter changes itself back to mode "a". When it does this, all power, even feeding-in to the grid, is labelled as a +ve power flow. The Victron sees energy being consumed, and then raises it's feedback to combat it. The system is actually feeding in this power, so this results in a positive feedback loop until the Victron maxes out.
Would Victron be resetting this parameter via the modbus RTU? I have seen no indication in the EM111's manuals that they would self-reset, so I am at a loss. Any help would be greatly appreciated!
My system is as follows:
EM111 connected to RS485-USB adaptor in CCGX
2x 150/45 BlueSolar MPPTs
400Ah 48v Lithium CANBus Battery Set.
a few days ago, my ColorControl lost the connection to the BlueSolar MPPTs. After reboot, it worked for some seconds an then the values from MPPTs were not longer updated. In ESS-Mode they stop working. I tried to connect one MPPT with USB-VE.Direct cable, but it also just worked for a few seconds.
I then tried to flash the latest firmware. Was 2.18 before and I installed 2.87 from SD-Card. But after the installation-reboot, the ColorControl did not start anymore, just hangs in bootscreen. After more than one hour, I decided to fore a new reboot, but it's not working anymore.
I used the Serial Console to connect to the device, enabled the kernel-boot-messages and this is the last printed output:
starting resolv.conf manager: resolv-watch... [ 13.953216] device eth0 entered promiscuous mode done. Starting crond: OK [ 14.688568] UBIFS error (ubi0:2 pid 445): ubifs_scan: garbage [ 14.694427] UBIFS error (ubi0:2 pid 445): ubifs_scanned_corruption: corruption at LEB 76:73728 [ 14.703216] UBIFS error (ubi0:2 pid 445): ubifs_scanned_corruption: first 8192 bytes from LEB 76:73728 [ 14.719329] UBIFS error (ubi0:2 pid 445): ubifs_scan: LEB 76 scanning failed [ 14.726501] UBIFS warning (ubi0:2 pid 445): ubifs_ro_mode.part.0: switched to read-only mode, error -117 [ 14.736114] CPU: 0 PID: 445 Comm: connmand Not tainted 5.10.42-venus-8 #1 [ 14.742980] Hardware name: Generic AM3517 (Flattened Device Tree) [ 14.749176] [<c010be0c>] (unwind_backtrace) from [<c010a168>] (show_stack+0x10/0x14) [ 14.756988] [<c010a168>] (show_stack) from [<c0355558>] (ubifs_ro_mode.part.0+0x40/0x48) [ 14.765197] [<c0355558>] (ubifs_ro_mode.part.0) from [<c0361288>] (ubifs_garbage_collect+0x214/0x39c) [ 14.774536] [<c0361288>] (ubifs_garbage_collect) from [<c03489cc>] (make_reservation+0x124/0x424) [ 14.783508] [<c03489cc>] (make_reservation) from [<c0349694>] (ubifs_jnl_write_data+0x108/0x2ac) [ 14.792419] [<c0349694>] (ubifs_jnl_write_data) from [<c034c7f8>] (do_writepage+0x98/0x260) [ 14.800872] [<c034c7f8>] (do_writepage) from [<c01f2fb4>] (__writepage+0x14/0x8c) [ 14.808471] [<c01f2fb4>] (__writepage) from [<c01f4180>] (write_cache_pages+0x178/0x3d4) [ 14.816650] [<c01f4180>] (write_cache_pages) from [<c01f57e8>] (do_writepages+0xa8/0xec) [ 14.824890] [<c01f57e8>] (do_writepages) from [<c01eccc0>] (__filemap_fdatawrite_range+0xb0/0xd0) [ 14.833892] [<c01eccc0>] (__filemap_fdatawrite_range) from [<c01ece34>] (file_write_and_wait_range+0x48/0x98) [ 14.843933] [<c01ece34>] (file_write_and_wait_range) from [<c034bcc4>] (ubifs_fsync+0x40/0xb4) [ 14.852630] [<c034bcc4>] (ubifs_fsync) from [<c0278068>] (do_fsync+0x3c/0x70) [ 14.859893] [<c0278068>] (do_fsync) from [<c0100060>] (ret_fast_syscall+0x0/0x54) [ 14.867462] Exception stack(0xc2a9dfa8 to 0xc2a9dff0) [ 14.872619] dfa0: 00000000 b6f476d0 00000008 00000058 24051905 00000000 [ 14.880889] dfc0: 00000000 b6f476d0 0088cc10 00000076 00000008 b6f476e0 0088b000 00000000 [ 14.889160] dfe0: 41e5e03c be989b00 41d868b4 41b20088 [ 14.894317] UBIFS error (ubi0:2 pid 445): make_reservation: cannot reserve 150 bytes in jhead 2, error -117 [ 14.904205] UBIFS error (ubi0:2 pid 445): do_writepage: cannot write page 0 of inode 1398313, error -117 [ 14.915863] UBIFS error (ubi0:2 pid 155): make_reservation: cannot reserve 160 bytes in jhead 1, error -30 [ 14.925720] UBIFS error (ubi0:2 pid 155): ubifs_write_inode: can't write inode 1398311, error -30 [ 14.991394] UBIFS error (ubi0:2 pid 155): make_reservation: cannot reserve 160 bytes in jhead 1, error -30 [ 15.001251] UBIFS error (ubi0:2 pid 155): ubifs_write_inode: can't write inode 1398312, error -30 [ 15.058044] UBIFS error (ubi0:2 pid 155): make_reservation: cannot reserve 160 bytes in jhead 1, error -30 [ 15.067810] UBIFS error (ubi0:2 pid 155): ubifs_write_inode: can't write inode 67, error -30 Checking available software versions... Active rootfs: 2 Active version: 20220531142416 v2.87 [ 16.148559] UBIFS (ubi0:0): Mounting in unauthenticated mode [ 17.467224] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs1", R/O mode [ 17.475799] UBIFS (ubi0:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 17.485900] UBIFS (ubi0:0): FS size: 208373760 bytes (198 MiB, 1615 LEBs), journal size 9033728 bytes (8 MiB, 71 LEBs) [ 17.496704] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB) [ 17.502624] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 921B723C-D0FC-4876-BB2D-0A4AFF5C863F, small LPT model Backup version: 20180916222247 v2.18 [ 18.723663] UBIFS (ubi0:0): un-mount UBI device 0 dbus-daemon: [system] Activating service name='fi.w1.wpa_supplicant1' requested by ':1.2' (uid=0 pid=445 comm="connmand --nodnsproxy --nodaemon ") (using servicehelper) INIT: no more processes left in this runlevel dbus-daemon: [system] Successfully activated service 'fi.w1.wpa_supplicant1' ������������������������������������������������������������������������������������������������������������������
The strange characters at the end appear in two steps. When I then insert the SD-card, some more of this characters appear. It seems, they are simply console output but with wrong baud rate or so.
Have you ever seen this behavior before? Is the ColorControl simply broken or is there a chance to recover from this?
Have a system where we have recently added a second Fronius inverter to Multiplus.
The CCGX itself has been configured accordingly and is able to see values from both Fronius PV inverters. However, through VRM the customer is unable to see productions values from the new Fronius.
It’s as if the information is simply not being forwarded through to the VRM properly.
Has anybody had any experience with a similar issue and have a potential workaround?
Cheers in advance.
Hi, I have a multiplus II (not a quattro) installed on boat with CCGX controller. I would like to be able to identify the incoming source of AC power and report it to VRM. The multiplus has inputs that I could trigger with a contactor when the generator is running. Can these be used to advise the GX that the AC input is coming from the geni rather then shore power?
38 People are following this topic.