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.
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.
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
Seriously? I just pulled out the RV and was going to finally connect my Rego via RV-C to my Cerbo but if the system is broken that is a huge disappointment.
Just confirming - This is still a problem in v3.75. Upon upgrading, I lost the battery level stats and received alerts for ‘BMS Lost’, ‘#67 - No BMS’, and ‘Low battery’. After booting back to v3.54, all three alerts cleared and the battery level stats are reporting again.
I haven’t upgraded my cerbo in over 2 years because of this issue. Would love it if someone could give us a steer for how we can get this working again…
I haven’t found any way to update the firmware on the battery. As far as I can tell, Renogy does not provide firmware updates for the REGO 400 Ah battery.
Buy a supported battery or log a case with the manufacturer.
Nothing has changed in Venus that would break a specific battery using a standardised form of communication.
Unfortunately, Nick, that’s not true. This DID work and DOES work under v3.32 - so something changed on the victron side that made this battery that works on older versions of the OS with little-to-no specific configuration stop working in later versions of the OS. I’m not necessarily looking for victron to make a patch for us - but it would be great if someone had some suggestion for what could be going wrong - other than buy a different battery… The REGOs are talking RC-V - must not be uncommon - and in the old version, the CERBO sees my 3x400ah batteries as one big bank - and I didn’t do much fiddling to get that to happen - it “just worked”.
None of Victron’s supported batteries are over anything except BMS.CAN. RV-C is not listed as a supported form of battery comms for managed batteries.
I suggest it is very uncommon to try do this.
RV-C replaces VE.CAN. You then can’t use VE.CAN devices - something which is only for victron devices.
BMS CAN is a separate BUS/profile and is the only one to support a managed battery.
There is nothing that says you can use RV-C for battery management, I can see zero support statements for this. As is true for most unsupported configs, because something works, doesn’t mean it will keep working.
Put the battery onto a BMS.CAN profile/port and it should work.
The only reference to managed batteries over RV-C IN are in 3.50 and 3.65 which adds support for Battleborn and Lithionics, None of this is documented in the battery compatibility matrix, so likely still very niche and implementations may vary.
I connect to the battery with the Renogy DC Home app, which lets me see information about the battery. It doesn’t have an option to update anything, though.
In my case, this complete installation was done by the RV manufacturer as part of their solar feature package. I don’t know that I’ll ever need to update the Cerbo GX firmware beyond 3.54, but I was just sharing my experience when I tried to do so. The BMS communication works fine with the REGO at v3.54, so I’m just going to leave it alone.
Fantastic how long you stuck with it and that you finally managed to solve it. I was actually the second person in your thread who confirmed the issue for 2025.
I didn’t have that kind of perseverance and installed a shunt — which of course never worked properly, because the Renogy, with its active balancers and internal heater, has consumers that an external shunt can never detect.
OK, technical problems happen, that’s normal. But the fact that Victron hasn’t responded for such a long time, while fanboys showed up acting all arrogant — that really shouldn’t happen here.
