Hi Guys, anyone had this problem. System works fine until 80 US5000B batteries get to 100% and within 5 minutes I receive a error 67 lost BMS. I am presuming it is a problem with the LV Hub not sending any signals to MPPT RS 450/200 X4. My next task is to check the firmware on the LV Hub and upgrade to see if that makes a difference. Is there a setting on the MPPT’s or Cerbo to keep the connection alive? Note, everything works perfectly when charging the batteries.
System is 80 X US5000B Pylontech batteries, 144 475 watt PV panels, 4 X MPPT 450/200, 3 X Multiplus 2 15000/200 inverters for 3 phase, colour GX and cerbo.
1 Like
comms for the Pylontechs go the the LV-Hub, LV-Hub to your GX device and then to the RS450/200.
So, when you have that error #67, something has broken along that chain.
If you are getting the error #67 on the Cerbo, it’s not comms with the RS450/200 units.
If you can see the Pylontechs on the Cerbo, it’s not the LV-Hub.
So, for example, if the Cerbo crashes or the BMS comms fail (ie: recent issues with Venus 3.5x on Mk2 Cerbos) then the RS450 units will report error #67 even if the LV-Hub and US5000s are doing the right thing.
What’s the vintage of the Cerbo, what firmware?
Can you seen in the VRM history any gaps for the the Pylontech logs?
Gaps in the RS450 logs?
Figuring out if the Cerbo is crashing is a bit harder but the VRM reporting (Custom Widget, Gateway, VRM Log Time Offset) or dbus timing (Custom Widget, Gateway, D-Bus Round trip) can give you a clue.
First step, determine which part in that chain is going away.
LV-Hub firmware 1.8 seems pretty good and allows the “modern” cell-level diagnostics to work (stack/battery/cell location) correctly with recent Venus versions.
Thanks Dean, tough one to diagnose, I spoke to a Victron dealer in Oz this morning and he has suggested dropping the battery voltage to float at 50v and Absorption to 51 volts so the Cerbo does not see 100%. Just making up RS232 to RJ45 to update the LV Hub firmware. I was running 3.60 version on the Cerbo but there was some issues from Victron saying it was not stable and a lot of installs were getting error 67, I have downgraded to 3.55.
The 3.60 issues related to CCGX only, not Cerbo, and in rare instances on busy devices, an error could be experienced on the initial upgrade, but once it completed, there were no further occurrences..
1 Like
That suggestion is not great - running Pylontechs unmanaged (which is, as I understand it, the only way you can force the RS450s to obey those abs and float settings) is not ideal and against their warranty terms.
You can force the charge voltage limit in DVCC which would be better but you are just hiding from the original problem.
Hi Guys, problem sorted, incorrect info given for pinout LV Hub to Cerbo. All working as it should, thanks.