This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
I have a fronius primo connected on the AC output. It appears on the PV iNVERTER menu. It is selected in the menu and also declared in the ESS setup of the Multiplus.
Sometimes (like the photo attached) the PV inverter does not appear. I only see the Smart PV charger.
Why is this happening?
Are both the Fronius and the CCGX connected together on the local network with a hardwired, manufactured ethernet cable?
Is the Fronius setup with a fixed IP address?
Those are two common issues, and resolve a lot of problems.
Thank you for the reply.
The Fronius is in the same wifi network (always online) it has a fixed IP that is recognized by the cgx. The problem is not permenant. It sometimes stops showing the Fronius...
Please try using a hardwired ethernet cable, even temporarily, and see if that resolves the issue.
Have you tried to "ping" the fronius if he is not showing up ? I have three fronius inverters connected via Wifi to a Fritzbox 7590. The Fitzbox has some problems with 2.4 Ghz Wifi and Fronius disappears. The Fronius Symo reconnects after some time.
So try: "ping x.x.x.x" while x.x.x.x is the ip address of your inverter if the inverter is not showing up in the panel. If he is answering you have to search further ..... if not you have a wifi problem.
Jens
The Fronius inverter appears online realtime at the Fronius solarweb site at the moment it is not appearing on the cgx. Also I can perform a "scan" for inverters at the minute it not appears. The CGX finds the inverter with its correct IP but still does not show it. Rebooting the cgx makes the inverter reappear but only for a short time after that it disappears again.
@vbelijohn, Have you tried not using the wifi connection, but trying hardwired ethernet cables between the Fronius, the router, and the GX device?
There are other options to try as well (including the beta Venus firmware with more AC PV stability improvements).
But testing a hardwired ethernet connection is the very first thing to do, and often resolves the problem.
