Victron Multiplus 2 will run into charge / discharge loop

[christian1980nrw]

I tested your driver but unfortunately my charger is running into a charge & discharge loop with this. Perhaps the amount of data is too large and cannot be processed in time.

[Langer75]

Hi, first of all thanks for your work. Unfortunately I have the same issue. The values seems to be delayed more and more in venusOS after 8hours I have 12 seconds delay. With this behaviour one can not regulate the venus in correct way. I can support the investigation of this issue. I can provide time series how it looks on venusOS side and how it should look. Does anybody has not this issue? My setup is VenusOS on a Raspi 4 2GB. Beside the script for JKBMS data is running. Further on I have a 3-phase system with another three MPPT. May be it is a performance issue. But with a Raspi4 and 2GB it should not.

[hengst12]

Same problem as Langer75. After only a few minutes, the values are delayed by several seconds. This makes a proper regulation impossible.

[Langer75]

https://github.com/Knedox/venusos_sma_energy_meter The timing is fine with this script, but the decoding works only for over all power and energy. L1, L2 and L3 are not decoded correct with Homemanager2.0 protocol. Thats why the values are not used as gridmeter in the graphic. My python knowledge is not good enough to find the problem. Also the comparison of both does not help.

[Langer75]

It looks like the decoding of all the values needs to long. I have used https://github.com/Knedox/venusos_sma_energy_meter with adapted offsets (see issue #1). This script only decodes the necessary values.

Can be closed

[c0deliner]

Adjusted the receive buffer size to match the real packet size. Also set receive timeout to 1s. Unfortunately I don't have any ESS setup available for testing. But hopefully those changes will fix this issue. Created a new branch /fix/charge_discharge_loop