I found some errors in the protocol Modbus TCP, they appeared after changing from a Cerbo GX to an Ekrano. The IP addresses come from my EVCS (I have 2). It’s as if the EVCS were trying to communicate with the old instances (the instance numbers have changed following numerous hardware modifications on my installation). So my question is, how can I prevent EVCS from looking for the old instances? The easiest way would be to flash the EVCS with a firmware containing no parameters ? I have tried an update but the parameters remain.
Hi, I had the same problem when I switched from a Color Control GX to an Ekrano, and everything works now, but there are these codes.
I did a reset and installed a clean firmware, but it didn’t help. I have two terminals, and both report the same errors. For me, it doesn’t affect the operation of the two EVCS terminals.
Hello @MED. That may be related to searching for the correct instance number. EVCS scans some range to find it. Once it finds, the scan is stopped.
Is the error time constant or changing all the time?
Hello, I think the error time is constant but never stops. Attached is a video. The two IP addresses correspond to the two EVCS addresses.
Thank you.
It seems like EVCS is continuing to scan. It leads to the display of errors. Could you please describe which inverter is used in your system(like MultiPlus, RS, etc) and how it is connected to GX?
Hello, I have two single-phase MultiPlus IIs connected in parallel to an Ekrano via Ve.Bus. The Ekrano is wired to a Netgear mesh Wi-Fi hotspot.
Both EVCSs are Wi-Fi enabled but can switch from one Wi-Fi hotspot to the other from time to time. The EVCSs operate normally despite this. I had to enable the Period Scna feature on the EVCSs to prevent them from randomly losing the GX connection to the Ekrano, but the errors were already present before activation.
Ok. Can you please also provide a VRM instance number for both inverters? It should be in the device menu.
