Upgrade procedure itself was without problems, but when the Cerbo is running with 3.52 the Web VRM never goes to realtime status, seems there is a screen update only after every few minutes. Furthermore , when going to device list, the menu Remote VEConfigure or Firmware update cannot be used, instead after a minute or 2 there is a red error message displayed that Twoway communication in Cerbo is not working. However, there is no more such parameter in new version 3.52, VRM status can only be set to full and it is set to full. I tried to switch Cerbo versions a few times back and forth , but it did not help. It works with 3.12, but shows the issue with 3.52. What else I can do for troubleshooting and collect some logs ?
Hi. This sounds a lot like the weirdness one might see with a cpu overload on the Cerbo. You don’t say what kit you have hanging off it, or whether you may be doing something unusual to have a high load.
It may have always been there, but the NewUI bloat in 3.52 may have tipped it over the edge.
You could try reducing anything you think might help lower load. Maybe test lowering reporting frequency, disable ModbusTCP, etc.
Even check the power cable.
Its a pretty big jump from v3.12 to 3.52.
I would flash it from a usb or micro and use the classic UI to make sure the settings are correct (or as you want them)
All the previous options are there just navigation is very different. Under display you can switch beyween the two UIs untill you are comfortable with the new one.
Hi. I tried now 3.12 → 3.42 from USB stick. But the VRM is almost behaving the same as with 3.52 , awful slow updates every few minutes, never realtime. In Cerbo VRM online portal setting I see “connection error=no error” and last contact between 1sec and 1min, as I have set the log interval to 1min. two-way communication=on.
With 3.42 there is one difference to 3.52 though. In device list “remote VE configure” and “firmware update” are responsive and not stuck with this two-way communication error like in 3.52.
The load on Cerbo is quite low, I have only a few external Modbus queries running + the queries from EM540.
I did the upgrade 3.12 → 3.42 via USB to get around potential new gui problems in 3.5x at all but I see almost same behaviour in VRM.
Sounds lile a CPU overload or heat issue.
Try loading the d bus round trip widget and checking the load.
I obviously don’t know where the cerbo is operating i am sure you can evaluate that.
d -bus load is mostly shown below 5ms , with sometimes a peak to 35ms. Environment temp is app. 13 Celsius.
Maybe another useful information: When I open the Remote-console in VRM Web page, it works normally, with same responsivness as from local network. The issue in VRM is with KPI indication only.
So something out of our control…
Nothing blocking the traffic on your network maybe?
Are you getting any log offsets?
If old Cerbo version works and new version has issues, its hardly a networking issue. What du you mean by log offsets?
If you download csv data does it show log offsets
Sorry I dont unterstand what this could tell us. If the cerbo has communication Errors with VRM the the log is probably wrong , incomplete or missing. I think I will wait for next Version and try then again.
After I did a factory reset of CerboGX and installed 3.53 from scratch all works now as expected. My conclusion is, there happend a data corruption during upgrade.