Hi there,
I’ve just installed the 22kw EVCS and for the life of me can’t get full communication happening between the EVCS and the Cerbo GX. I have the EVCS coming up on the VRM Portal, I can see the EVCS on the remote console, I can log into the EVCS console via both local IP and via VRM, I can see the EVCS on VictronConnect, HOWEVER no network data comes up on the EVCS, and when I run a check on the GX devise page of the EVCS, I get “Can’t connect to the GX device (192.168.0.71)!” I’ve double and triple checked the IP address and VRM Portal ID entries in the EVCS “GX Devise” page, they are correct, it even finds the Cerbo via the discover button, and Modbus is activated.
I’ve done all the basic stuff - firmware is the latest on all components, definitely all on the same network, rebooted everything in every different order I can imagine…but I am stuck with W-104 GX communication warning, and no network data on the EVCS. What have I missed?
Le Cerbo et l’evcs doivent être sur le même réseau.
vérifiez que le modbus tcp est activé sur le Cerbo gx
Vous pouvez entrer l’adresse ip du Cerbo gx dans EVCS ainsi que le VRM Portal ID et faire un check de connexion.
au pire faire un reset de l’evcs et injecter manuellement le dernier firmware dans EVCS.
Thankyou Axelfolly. I have done all that, confirmed the correct IP and Portal ID are both entered in the EVCS, and the EVCS has the latest firmware. When I check the connection to the Cerbo, I still get “Can’t connect to the GX device (192.168.0.71)!” even though the EVCS is visible and accessible on VRM. I have also confirmed that Modbus is activated on the EVCS. I still have the issue that the EVCS has a W-104 warning, and will not display network data from the GX.
What I find puzzling is that when you view the EVCS via VRM portal on the devise list on the GX, it says connected (see screenshot). The problem seems to be a one way issue…the GX can read the EVCS data, but the EVCS cannot read the GX data…???
Screenshot from the GX:
Screenshot from the EVCS:
Stupid question. Is the EVCS in “station” mode for the network and is it connected to the same Wi-Fi SSID as the Cerbo?
Also look at the three attached screenshots. Try entering the Cerbo GX’s IP address in the whitelist on the station (see screenshot).
Yes, EVCS is in “Station” mode, and is connected to the same LAN network, although the Cerbo GX is connected to the network via LAN, not Wifi. Wifi is disabled on the Cerbo GX. It is definitely the same DHCP network though, and the EVCS finds the Cerbo successfully using the GX Device “discover” button. Also have added the GX IP address to the whitelist in the EVCS, but I still get the same “Can’t connect to the GX device (192.168.0.71)!” message when using the “Check” button on the EVCS.
I have also tried having the Cerbo GX connected via WiFi rather than wired LAN, and entered the new IP address in the EVCS…no difference, still “Can’t connect…”
Right then! I’ll give it a few more days to see if any solutions are presented on this forum, if no, I’ll try get some direct support from Victron. I’ll let you know when I get some results ronvantw!
The fact that the Cerbo is wired and the EVCS is wifi is not a problem, it is the case for me. Does the station receive wifi well? Have you entered the VRM identifier in EVCS? Do you have a wifi system with several terminals like Orbi wifi mesh or other repeater? Have you tried a reset and putting the latest firmware on the EVCS station? There should not be something that did not work. during installation. Sometimes they are capricious
reset EVCS
- Open the unit by removing the backing plate. Be careful not to touch the high-power parts inside the unit. Only the area around the DEF button is safe.
- For a full reset, press the DEF button (see the image in EV Charging Station setup web interface for its location) for more than 15 seconds until the RGB light ring starts blinking blue rapidly to indicate that the full reset is in progress, then release the button.
- Mount the backing plate onto the device and tighten the screws.
- Run the First setup again.
Wifi signal is excellent on all components. My Wifi is a TP-Link Omada Mesh network which connects dozens of various wifi and LAN systems on the property, and has always been 100% stable for all other connected clients. I have done a soft factory reset on the EVCS, as well as a firmware update to the latest version being V2.03.
I will try a full hard reset now.
Full hard reset via 15+ second DEF button press (confirmed with 3x blue flashes of the LED ring) complete, first setup run again. No change. Cerbo GX shows the EVCS is connected via Modbus, but the EVCS says W-104 GX Communication warning, and does not display any network data.
Ok…I’ve made some progress. I stumbled across the services page in the Cerbo GX, and there is a “Enable/Disable Modbus TCP” button. It was Disabled by default. I enabled it, and WALLAH! the W-104 error has gone away on the EVCS and it is now displaying data .
There is now however, a continuous error in the Modbus TCP area of the Cerbo GX (see screenshot below) but I have not found anything affected by it on the network.
The only problem left now is that the EVCS does not come up on the VictronConnect App. It is not on the VRM Portal dashboard, but it is live on the VRM Portal devise list, and it can be accessed from there.
Any ideas on how to get the EVCS to appear on the VictronConnect App?
Not sure whether you’re still following this thread @ronvantw - check whether Modbus TCP is enabled in the “Services” page of your GX.
This is a totally separate section to enabling Modbus TCP in the EVCS, I only found it by chance.
This created another error which has not presented any issues so far, but fixed the EVCS > GX W-104 comms error, and my EVCS is now displaying data.
Yes it is working now thanks
Hello, yes, you need to enable Modbus on both devices. I think I noted it above. The main thing is that it is resolved. For errors in the Modbus, don’t pay attention to them for the moment. Many of us have them without it affecting operation. However, for a mesh network, it is essential to enable periodic scanning to avoid dropping the WiFi. In Victron Connect and network settings. Another thing in Victron Connect, the EVCS only appear locally. You can have some commands in the remote console on VRM in the device list section. Here you go
