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
This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
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
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
The data from the Fronius sometimes contains strange readings that confuses the VRM system, we're working on a way to handle this in a way it does not produce the strange numbers.
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.
Happend again about an hour ago. No issues with connectivity.
The Fronius:
0.135kWh today is fairly accurate.
What can I do to troubleshoot this?
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.
Fronius:
GX:
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.
Additional resources still need to be added for this topic
17 People are following this question.