I just updated the firmware on a Cerbo GX to version v3.42 and the fronius GEN24 is now not showing on the Dashboard. The inverter is shown in the device list and in the VRM devices. However, since it is not displayed on the dashboard, the inverter PV generation is no accounted for which results in incorrect data showing on the load and grid side.
This has happened before and it was only able to be corrected by upgrading the system from an older CCGX to the Cerbo GX. Extremely frustrating! Does Victron not Beta test using AC-coupled configurations?
I’ve tried rebooting the Cerbo several times, tried to show and hide the PV inverter. Redetect it (even thought it is detected). It’s a common issue and there seems to be no valid explanation or solution.
The system just had an battery overvoltage alarm! This is the first time this has happened on any system and it’s extremely concerning and dangerous. The Absorption voltage set in the Multiplus is 56.8V, yet the DC voltage reached 58.4V.
Is your fronius up to date as well?
Are all components up to date?
The firmware is all designed to work together.
And yes my fronius is fine on v3.42. was tested in beta first.
The usual advice is if it is working don’t update.
Good to hear you have updated and it’s working correctly. I recall updating the Fronius firmware a few months ago but I will check again. Unless there has been another update since then, I was assuming it is up to date.
I was updating the firmware on Cerbo and other connected equipment to enable more features such as the Dynamic ESS. I understand firmware updates can be problematic but they shouldn’t be detrimental to the safety of the system.
guystewart
(Guy Stewart (Victron Community Manager))
5
Most of the time issues with Fronius is because they have not been reconfigured correctly after a firmware change on the Fronius end.
Check to make sure you’re running the latest firmware on the Fronius;
Please confirm the SunSpec support is correctly configured on the PV-inverter.
Log into the Fronius web interface.
Go to the Modbus tab
Set Data export via Modbus to tcp.
set Sunspec Model Type to int + SF
Please take some screenshots and report back. If you’re still having issues with it, please post the VRM URL and I’ll have a look.
Stolen reply
Usually if the comms aren’t working correctly, then then system safety is an issue.
So yes, the first check is of course is -why aren’t the communications working.
Is it networking or protocol related?
Great news. The firmware wasn’t updated on the Fronius GEN24. It took ages to download the latest firmware and after many attempts it finally downloaded to my phone and updated no problem. Then I set the Modbus Data Export to TCP it’s all back to normal.
I faintly recall having the firmware download issue a few months ago and must have never actually updated the firmware on the GEN24. It wasn’t as issue at the time as everything was working normally.
Thanks for your help. I might be good idea to add a notification when updating the Cerbo GX to ensure you have updated all firmware on all related AC-coupled Fronius inverters.
guystewart
(Guy Stewart (Victron Community Manager))
8
Out of interest, do you know the working firmware version you now have for the GEN24?
Yes, it is now updated to version ROW 1.33.8-1 (Release October 7, 2024).
However, I just noticed something very strange. The system is single-phase but the critical load data is now showing L1 and L2. L2 has zero loads but it appears the system thinks there is second phase. Digging into the PV inverter data on the Cerbo also shows a second phase so I suspect the issue has originated from the Fronius firmware update.
Just did a cerbo reboot but it’s still there. I’ll try a few more things and see what happens.
guystewart
(Guy Stewart (Victron Community Manager))
10
Make sure all the sunspec settings are correct as above and post some screenshots of the Fronius settings.
I haven’t had the high-votlage alarm since I updated the firmware to 1.33.8-1. Although, the strange issue with the load and PV generation data showing L1 and L2 (2 phases) is still occuring. I will update to the new firmware now available (1.34.2-1) see if the issue goes away.
