Hi,
My VRM data displays 20kWh in the middle of the night 00:00, this mess upp the data over time.
Is it possible to edit the data on VRM? This must be wrong, there is nothing displayed in System - PV yield.
Kind Regards
asked
20kWh solar in the middle of the night?
Hi @ehsab,
Can you give some more background, what equipment is involved, did it work before etc?
Best Regards
Hi @ehsab
We've looked at your VRM data, and found the cause: the amount from the 3 phases somehow gets 'hussled', causing the strange data numbers in VRM.
We're looking at how we can address this.
@Daniël Boekel (Victron Energy Staff)
I had another false reading (60kWh solar) at 11:00 today.
Whats special about my setup, it's really frustrating that the VRM data gets screwed up.
Hi @ehsab
First check the connection with your Fronius, and make sure all components including Fronius are on latest firmware.
Hi, they are. Connected by cable and no dropped packets on the switchport.
Hi @ehsab
your Fronius is (as far as I can see) -not- on the latest firmware, as is your GX device. Please update firmware first in case of problems, as asked before.
Thank you for updating the GX,
your Fronius is at:
| Firmware version | 3.14.1-10 |
latest according to firmware changelog document:
Fronius Symo 10.0-3 - 20.0-3
Software version: fro30380.upd fro30381.upd
Control unit RECERBO V0.3.23.0
Power stage set SYMO _PS V1.2.11.1
Filter PC board SYMO _FIL V0.9.24.1
Country setups V0.0.93.10
Please contact your Fronius dealer if you have trouble updating.
3.14.1-10 is the software Version of the Datamanger -> and this is the latest released version from fronius. Just checked in my fronius portal a few seconds ago.
Jens
PS: fro30381.upd is the latest version for the inverter and updates the RECERBO to 0.3.23.0 .... thats an other thing ;)
No ..... the version of the Datamanager is relevant for you.
The update from fro30380 to fro30381 is only a minor update regarding dynamic power reduction being ignored.
So if you have no problem on that side: never touch a running system :)
Jens
The underlying cause for this is an issue in the Fronius firmware.
In PV-inverters with an integrated data-manager, you can solve this by upgrading the firmware. It was fixed in an early fro30xxx.upd version.
Where you have an external data manager, this can be caused by a SolarNet timeout between the datamanager and the PV-inverters. New firmware improves the situation but cannot completely rule it out.
To deal with this issue, we modified our Fronius driver to ignore these incorrect zero frames. This will be in a future candidate release.
See here for more information.
