Hello developers,
As per title, is it possible to be restricted to only Cerbo Mk2 or Mk1 is also affected?
.
On the latest firmware (3.51), Cerbo GX loses communication with Pylontech’s BMS - after a few minutes of operation.
After returning to (backup) firmware 3.42, communication with Pylontech’s BMS is stable, but there is no connection via the Remote Console.
The settings related to the remote console (on firmware 3.42) are correct.
I have an issue with a couple of units.
Both are coming up #67 BMS Communication lost.
Am using Pylontech US5000B batteries and Cerbo MK2.
Have used Old cerbo model prior to the MK2 with no issue.
Have tried;
DIP Switch
New Cable
Another MK2 Cerbo.
and calling supplier of batteries, still same issue.
No packets dropped under services
Battery is not in alarm state.
Could anyone shed some light on this?
Much Appreciated.
Error 67, before v3.5x everything was working fine.
A reboot sometimes works.
MPPT stops producing energy.
Not sure if it’s only on MK2, I also have some installations on Cerbo MK1 which don’t have this problem after the update to 3.5x
Cable (own crimped) is measured and tested good.
Also tested with a Victron type A cable.
After updating to 3.50 and also to 3.51 I notice that when selecting the new GUI v2 interface, the Cerbo GX MK2 loses connection to the two Energy Meters (Grid & Enphase AC loads), both connected through VE.Can. It does this intermittently. Switching back to the previous GUI interface, the problem disappears and it is stable again.
1 Like