Hi all.
Could you please help me with a question why the sistem continues to feed to grid even through it is being told to not:
Cerbo, MultiPlus II are all latest firmware as of today 27 September.
Hi all.
Could you please help me with a question why the sistem continues to feed to grid even through it is being told to not:
Cerbo, MultiPlus II are all latest firmware as of today 27 September.
Even if I try set a limit it still has no effect:
You need to set up a Modbus TCP connection between the GX Device and the Fronius inverter to allow the GX Device to control the output power of the Fronius inverter.
https://www.victronenergy.com/live/ac_coupling:fronius
The Modbus protocol is used when the grid is present and the AC frequency is constant (imposed by the grid).
When the grid is disconnected, the Fronius inverter must be controlled by frequency shifting. This means you need to set up the “MG50” country code in the Fronius inverter and the PV Inverter Assistant (or a properly configured ESS Assistant for PV inverters on AC Output) in the Multiplus.
This is all done. ESS with PV Inverter setting configured and Fronius is in MG50 country code.
Fronius is seen as shown in images by Cerbo and communicating well.
I suspect that you don’t have the Modbus TCP connection set up correctly between the GX Device and the Fronius Inverter.
That would explain why on your GX Console it says “Feed-in limiting active: No”
The GX Device can detect and display Fronius inverters via Solar Api (HTTP), but can’t control their output power, just display it.
Good point. How can we check this?
Please see the links I provided above and try to follow the steps there.
The ESS Assistant with PV Inverter support and the MG50 grid code are needed for the system to function without a grid connection (permanent or temporary off-grid).
The Modbus TCP network connection is required for remote control of the Fronius inverter power when on-grid (including feed-in limiting).
By default, the GX Device detects and connects to Fronius inverters using another protocol (Solar API), but this only allows reading data from the Fronius, it does not allow remote control of the output power.
It is a lack of control from the system as it has no way to do so.
Your feed in limit is not active (bottom item in the menu) so there is no system control
From the manual linked
Check your [DNO editor settings] on the fronius (4. Configuration) as suggested by @MondeoMan
Make sure the fronius firmware is up to date. Sometimes it needs a look on their website and a usb update
@lxonline @MondeoMan @Ton_Gans You guys are rockstarts! Thank you! Have a great weekend!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.