The CAN2 port of Cerbo MK2 is having problems.
I have the feeling that it’s a hardware problem exacerbated in some situations by software usage / load…
Probably the developers will try to solve / avoid the hardware problem in software, but from my experience this kind of situations will end in a new hardware revision in most of the cases.
We’ll see…
Hi all,
Apologies for the hassle and the delay in responding.
The good news is we have found the solution; see here;
Hi Guy, does the VE.Can port troubleshooting process also apply for Error #67 at systems with standard CERBO running Firmware e.g. 3.3.
The unit: 1pcs Multi II 10000 + 1pcs. Smart Solar MPPT 450/200 (on VE.Can) with Pylon Communication on CAN Bus communicating with Cerbo.
Every 50 to 70days the VEBus (inverter unit) switches off following a Error#67 followed by VEBus BMS lost / Low Battery Alarm .
So far 5 identical shutdowns in approx 8 months
Try it and please report back, I would expect it will help.
Hi,
Maybe this is related to a different issue but I am having a weird problem with Pytes Battery and new Cerbo MK2
I had the Pytes Battery in use with a Cerbo MK1 without any problems. Then I took the same battery and installed it to a new system which uses a Cerbo MK2. At the beginning it worked but than stopped working and the battery stays in IDLE no charging nor discharging.
I use original Victron A Cable, newest firmware 3.5X.
CAN 500 activated
I checked the battery and even performed a firmware update. The battery seems to be fine.
Is there a chance that an engineer looks into the problem?
Hi Stewart, I did yesterday firmware update and VECan position 1 with Terminal block in VECan2. We did also a better shielded CAT cable. It works well so far. As Error 67 was intermittent (every 80 to 120days) we now will wait. I keep you posted. Thank you
Hi,
I can (sadly) confirm the issue. As in my previous post stated, the Cerbo MK2 has an hardware issue. I tested the same battery with various Cerbo GX and here is the result:
- 1st Cerbo GX MK2 Batteries stay in IDLE
- 2nd Cerbo GX MK2 Batteries stay in IDLE
- Cerbo GX MK1 Batteries working charge and discharge
All 3 devices are running latest 3.54 firmware and same cable / system were used to check.
I would like to have it reported to Victron, so they may improve. And while improving, I would appreciate if you give the hardware a push, Cerbo is a very low power machine 
Hi @FireStorm,
It is unusual to have a Cerbo GX MK2 with this hardware issue that is so severe that the firmware fix doesn’t solve it.
Then to have two of them is very very rare.
The situation now is that the source of the problem is understood, and already fixed in product of new Cerbo GX.
For those still in the field that do not get fixed by running the latest firmware, they can be returned to a service centre for a warranty replacement.
The new Ekrano GX has twice the number of CPU cores as the Cerbo GX MK2 if you need a more powerful GX device.
It would be nice if it was a simple thing to just upgrade the Cerbo GX CPU as well, but nothing to announce on that yet.
Trust me I couldn’t believe it as well and I felt like “no way Victron always works” that’s why I blamed Pytes in first place and flashed bootloader and firmware. Even blamed the cable so I changed cable, Bootloader, Firmware and changed every possible and even unrelated config I could find.
At the end I took one battery out of two and took it to a other customer just to check if the battery was faulty. After the battery proofed to work I came to the idea it could be the Cerbo. As a big Victron Fan it was hard to confess that Cerbo GX MK2 was the reason.
However, another challenge will be to convince my dealer about this case.
Any chance to get your support on that?
Have you already tried and they have denied the RMA?
It should be no problem, it’s a known issue.
Matthijs’ official post was here - Pylontech BMS Connection Lost - firmware OS 3.51 - #26 by mpvader
Victron Sales managers have also been notified, to get them involved if absolutely necessary you can submit a support request here - Need support? - Victron Energy
I am in the process, I attached your message and it seems that worked, so they asked me for the SN of the two devices. So will update you. However, is it possible to get in touch with an engineer, as I am having a weird behaviour for a different installation.
The best path for issues is directly with your dealer, and if they aren’t able to assist then creating a post here with as much details as possible.
We don’t provide direct access to R&D engineers without a specific case that needs to be escalated.
Thank you for the information. I will do that.
Hi,
I did contact dealer and I changed the Cerbo with a new one. However, the issue is the same. So I doubt it is related to the Cerbo itself.
I rather think there might be a other problem and I think it is pretty much possible that the 2 mppt (1x 450/100 & 1x 250/100) might be responsible for that issue.
So is there any chance to receive remote support? I would use my MK3 adapter and provide full access.
I have installed almost 100 setup’s so far but this drives me crazy.
I had a look at your profile and I think I have found the site with the issues, " Ther… Pam…". Is that correct?
The active alarm I see for that site is “Internal Failure”.
This is different to the issues described, and totally unrelated to the MK2 VE.Can port.
This alarm state begins in the battery, so that is where you will need to do your investigation. The Victron system is reporting it, but only passing on the message that is being sent from the battery where the fault is.
The battery is not the problem. I thought at the beginning it’s the battery too but I took the battery for testing to our warehouse and it worked perfectly.
Even had this double checked with Pytes engineer too.
I tested it with 3 different Cerbo (which worked on other systems) used MK1 and 2x MK2 And still same issue.
Therefore, I think it is indeed not an MK2 related issue. However, still an issue. As a result I kindly request an engineer for support. Could it be possibly the MPPT charger?
Hello,
I have a similar problem - the CAN2 port stops sending TX packets after about an hour of operation.
Changing the firmware doesn’t help, changing the GUI doesn’t help, disconnecting the HDMI doesn’t help, soft reset doesn’t help, hard reset doesn’t help, nothing helps.
Turning off the Cerbo for about 1 hour helps and then the Cerbo works without a problem for about an hour.
In my opinion, the problem is with the internal temperature of the unit, where the parameter of one of the components shifts outside the tolerance. The temperature in the room where the PV is located is around 21 degrees Celsius.
This is how the problem manifested itself on four units.
Hopefully the information will be useful, I have PV installations as part of my professional portfolio and this is causing me quite serious problems.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.