i have done every conceivable update that is released, even tried rolling OS back and still get the error. Have also installed the OS Large. The new update appears to clear the error alarm but still logs a fault. Have changed battery and also changed BMS cable. Am using genuine Victron BMS to CAN cable. Will also be trying this with PYTES batteries to see if fault continues.
Hi All,
Apologies for the long delay in responding to this.
Anyone who is experiencing this issue with the VE.Can 2 port on the Cerbo GX MK2 should get in touch with their dealer for an RMA warranty.
One other thing, if you are not using the other port, VE.Can 1, then moving to that one will also resolve it.
If both are required then the issue is a hardware defect and solution is an RMA.
1 Like
Hi @guystewart
So it’s a defect caused by the update?
Or what is the reason for it?
I’m a bit unsure whether I should do the update…
Thanks for clarification
Hi @ChristianL, here is the current status:
But what we do know is that some Cerbo GX MK2 units have a a hardware issue with their VE.Can port 2. It looks to be a signal quality issue, which by definition can be worsened by a variety of things. Ie. other signals, temperature, cpu load etc etc and varies from unit to unit.
What is important is:
- The majority of Cerbo GX MK2s does not have this issue, exact percentage is unclear.
- Using the New UI aka gui-v2 aggrevates the issue.
- The port with the issue is VE.Can Port 2, on the Cerbo GX MK2, not VE.Can Port 1.
- It looks to be a signal quality issue, which by definition can be worsened by a variety of things. Ie. other signals, temperature, cpu load etc etc and varies from unit to unit.
Lastly, we’ll soon, ie. mid December, deploy a software fix, first only as a beta, that fixes it for most cases. Therefore, on a systems having this issue:
- Check if VE.Can Port 1 is in use as well. Our VRM stats show that often its not. In case not, replug and reconfigure the GX to work on VE.Can 1 port instead.
- If both ports are needed, use the Classic UI aka gui-v1, await the new beta version that is expected soon and which will solve it for most systems, also when using the New UI again.
- If above doesn’t sort it, replace/RMA that Cerbo GX MK2.
2 Likes
I have found using Cerbo MK2 straight out of the box and not updating to have resolved mine and my customers issue.
Thank you Guy!
Hi Matthijs.
Thank you for the detailed explanation.
If only the MK2 is affected, it should not affect my Cerbo’s. Then I’ll give the update a chance 
However, the “old” version has also been mentioned here with problems.
Many thanks, Christian
I have updated my above reply with the last findings:
- we’ve made very promising fix in software; which is expected to fix the issue for most systems.
- running gui-v2 aggrevates the issue a lot. Hence, as a quick work around we advice to switch back to gui-v1 for now in case this happens in a system.
Meanwhile we’re working very hard to get this fixed asap.
@mpvader so far, the working solution to the problem is to switch communication from BMS (Pylontech) to the VE.Can 1 port, on firmware 3.52. The temporary solution works for all 6 customers who experienced the new problem on the new UI. Just to confirm Your previous suggestions in this topic.
Regards
ENERP TEAM
[image]
1 Like
For our client situation it’s not working using old UI workaround.
The Cerbo is not using a Touch so we can access it via VRM by new or old UI.
Please explain if that “also” impacts or if its only the UI setting selected in the Cerbo itself for the purpose of the Touch50/70.
After a reboot the Can.bus LV BMS 500kb/s is reporting STOPPED.
A reboot does not automatically start the Can.bus connecting the BMS.
I need to select disabled and then the Can.bus profile but it shoots in to ERROR immediately.
Sometimes sending 3 sometimes a bit more packets.
When we installed this Cerbo a new it did 9000 RX packets before going into STOPPED state.
@mpvader : We are using the Victron Energy meters on Can.bus 1. Would it be an option to switch them around as that is running on 250kb/s ? So put the Pylontech BMS on Can 1 and the Victron metering on Can 2. ( with their respective correct CAN profiles off course ).