Upgrade to 3.66 lost BMS on RV-C connected Renogy batteries

DIY
, , , ,
1

I’ve been working fine on v3.32. Plugged an RV-C bus into the VE.CAN port and configured it to run RV-C and it merged the three batteries and reported everything well. Been working for over a year now.

Upon upgrading to 3.66 (nice interface upgrade!), the two MPPT units immediately complained of error #67 NoBMS. I rebooted a couple of times and re-configured the RV-C and it still didn’t recognize it as a BMS the way it used to. the CERBO seemed to erroneously report a fully charged battery and seemed to be tracking it using the shunt alone against some assumed capacity…? NOTE: The RC-V did seem to see the three batteries - but just didn’t present them to the system as a unified “BMS” for MPPT and for reporting… (Forgive me if I’ve misused some vocab here)

Downgrading to 3.32 fixed the problem and I’m up and running again. But I am thirsty for the new interface and possible other improvements.

Has anyone seen this and have a fix/workaround?

1 Like
2

I’m experiencing the same issue. Everything was working fine on firmware 3.63.
After updating to current 3.67 (and also testing 3.70~61 Beta), my Renogy battery is still detected as an RV‑C device, but it no longer shows up as an available battery in the system.

So the device is recognized on the RV‑C bus, but it’s not presented to the system as a BMS/battery anymore.

renogy2
renogy21638×725 79.8 KB

3

Hi Peter, Did you ever figure out a fix for this? I am new to this forum and I have 2 400ah Renogy Rego batteries(RBT12400LFPL-SHBT) and the rest of my system is full Victron with a Cerbo GX. I really want to hook this up and create a “closed loop” charging system but I have no experience with this stuff. Is it best to try your way going direct with RV-C connection or try using the dbus-serialbattery method. I appreciate any advice in this matter. Thanks