Hi
Will the VE.Bus BMS NG broadcast battery information (via RJ45) to a cerbo gx without the use of a BMV,
Similar to the information from the Connect app for the VE.bus NG
Thank Grant
Unfortunately it does not (yet).
It only sends ATC and ATD signals to the system.
I guess it should be possible to add that with an update in the future.
While I haven’t used on yet, the Victron webpage for the VE.Bus BMS NG states “It also receives current and state of charge data directly from the batteries, so there’s no need for a separate SmartShunt”.
I can find in the manual where SoC is transmitted to the GX Device, but nothing on current.
Are you saying that the data is available to the VE.Bus BMS NG, but not transmitted to the GX device?
Still trying to get to the bottom of this. Why would the VE.Bus BMS NG be advertised as no smart shut needed if it doesn’t transmit all the battery data to the GX device?
Hi John, did you ever get resolution on this? I just installed a Cerbo in conjunction with a VE BMS NG and I can’t get battery SOC, or any coms, to show up on the Cerbo. I thought it was me…
Did you follow the manual to enable the Battery Monitor function on the MultiPlus or Quattro?
The VE.Bus BMS NG does not natively relay the SOC or current to the GX device; the monitoring available as listed on the product listing is via the bluetooth connection and VictronConnect. To enable SOC (only) being relayed to the Cerbo, it’s necessary to turn on the battery monitor function of the MultiPlus or Quattro that’s connected to the BMS first.
No, I didn’t notice this in the manual as I was performing the install, I’ll try it next time and see how I like it. The amount of data provided by the NG BMS’s is wonderful, too bad that more of the data isn’t passed to the Cerbo. I like to have amperage displayed as one of the key metrics. I ended up installing a SmartShunt to fill the gap. Future functionality planned for this?
I’m almost sure it’s not possible with the VE.Bus BMS to transmit more data from the batteries.
1 Like
I’d doubt it as well, since -as we can see from the procedure outlined in the manual- the BMS isn’t even transmitting SOC to the GX device at all, it’s sending it to the MultiPlus or Quattro which then sends it to the GX device. The functionality between the BMS and the GX device, in the case of the VE.Bus BMS NG, is simply allowing the GX device to act as a remote control for the MultiPlus or Quattro.
For full data comms between the BMS and a GX device, a Lynx Smart BMS NG would be the way to go; that connects the BMS directly to the GX device via VE.Can, with the GX device then relaying the information to the connected VE.Bus devices rather than, with the VE.Bus BMS NG, sending limited data to the connected VE.Bus device which then relays it to the GX device.
To be fair, the Lynx Smart BMS NG is substantially more expensive, but with the cost comes capabilities certainly; comms over VE.Can allow much more data throughput than over VE.Bus as is the case with the much lower-cost VE.Bus BMS NG.
In reality, for what you have existing, adding in a SmartShunt or a BMV-712 (which is shown in the one sample schematic available that covers the VE.Bus BMS NG) would be a much more cost-effective solution to getting all the information you want into the GX device than changing over to a Lynx Smart BMS NG.