Hello, I have just started setting up my Cerbo MK2 with a 3-phase Multiplus 48/5000/70 and two batteries using the JK BMS. Once I configured and connected the BMS-CAN, it showed the JK BMS and several parameters. My VRM console still shows the device as “Generic Can-bus BMS battery” V15.37 but it is no longer reporting.
Then I updated the Cerbo firmware from 3.31 to the latest 3.54, the BMS-Can bus no longer shows up. Not just the JK BMS, but the entire bus is no longer present in the settings panel. Only Ve.CAN 1 still shows.
I tried rolling back to 3.31 firmware, cycled the power, no change. No BMS bus anymore. On Ve.CAN-1, I have a connection to the 3P75CT power meter and it shows up just fine.
Any idea what might be the issue? How do I go about diagnosing this? I read a couple of reports elsewhere that this is happening to others too?
Check the BMS protocol Bus is correct to talk to the battery either 250 or 500
From what I found online:
Here is the CAN protocol for the JK BMS. It should send the CAN messages after power-up according to the protocol, but you will need to make sure you have your CAN receiver set to 250 kbps and have the 120 ohm termination resistor on, otherwise it may stop sending messages. Serial should work fine as well.
Thanks Daza.
The terminator is present, and the BMS to Cerbo cable is from Victron. This worked for a short while, so the hardware configuration appears to be OK. I have also checked the BMS and selected CAN protocol 4 once again.
I could try serial but it doesn’t explain why the Cerbo seems to no longer see its own CAN interface. I cannot set it for 250 or 500kb as the interface itself no longer shows up in the settings page. Could this be a hardware malfunction?
Could be but in the past I’ve heard issues with made up Ethernet cables, but in any instant check the cable is not faulty and maybe check the contacts of the GX ports making sure the connections are free of debris
It really appears to be on the Cerbo side itself. I got ssh access to the cerbo and found this in the logs:
4000000067b208030bdca8c4 INF.task: done in 000.001
4000000067b208040cd32e24 *** starting can-bus-bms ***
4000000067b208040d451a34 can-bus-bms v0.43
4000000067b208040d5615dc
4000000067b208040d562964 -------- dumping backlog -------
4000000067b208040d56351c INF.canhw_drv: adding driver socketcan
4000000067b208040d563cec INF.skcan: ignoring vecan1, interface is not up
4000000067b208040d5644bc ERR.canhw_drv: Could not find gateway ‘socketcan:vecan1’
4000000067b208040d58197c Specified CAN-bus gateway ‘socketcan:vecan1’ not found!
4000000067b208040d5830ec The following gateways were found:
4000000067b208040d5838bc --------------------------------------------------------------
4000000067b208040d584474 socketcan:vecan0 vecan0
4000000067b208040d584c44 --------------------------------------------------------------
So vecan1 (the CAN connection to the BMS) is no longer there.
I will contact my Victron dealer, see if I can get a replacement