I tested second cerbo. Same result.
I don’t have GX touch available. I guess I’ll have to buy it. I’ll try to borrow it somewhere.
Anyway, thank you very much for your help. I’ll let you know when I have something new.
2 Likes
HI. After some time, I managed to arrange and borrow a new GX touch 7. Original victron. And I’m glad I only borrowed it. Communication also fails. So there is no problem with the display.
@KRUP85
Ultimately then this is an RMA case.
No, I try 2 cerbos. It is not HW problém.
You are saying the cerbo can fails with your hdmi set up.
And now you say the can fails with an original screen.
The conclusion is both the cerbos have a problem with can 2 useage in your set up. Maybe bothe have a problem? Return for the rma.
The only other way forward is to use a ve direct cable for the MPPT and use the can 1 for the jkbms. Which is isolated.
after everything I tested I’m sure it’s a problem in venus os. So there are solutions for me.
1 -Don’t use a display directly connected to the cerbo ,
2 - connect MPPTs with ve.direct as you write
3- fix SW problem in venus.os
I don’t want to do option 2, option 3 doesn’t matter to me. So I’m clear about it. I’m glad I was able to test it and maybe someone else will have the same problem.
Anyway, thanks for the help.
Easily a solution with WiFi and lan connection.
Only other thing is possibly you have not used the ve can terminators? These add stability to the can network.
already done 
RPI4 + lcd touch
terminators used, with or without same problem
Hi @KRUP85,
There are more reports of VE.Can port 2 not working correctly on the Cerbo GX Mk2. We are working on a solution for that. However, we have not seen any systems with a failing CAN port only when the HDMI port is connected.
If I understand this correctly, CAN communication on VE.Can port 2 fails as soon as the HDMI cable of the GX touch is connected, correct? Is this also the case when the GX touch is connected before booting? The display is not meant to be hot-pluggable.
And the behavior is the same on two different Cerbo GX Mk2 units?
Would you be able to update your device to the latest Venus OS beta version (see here)? We’ve modified the CAN driver to give us more insights in its performance.
Thanks,
Rein
1 Like
I’ve also had a few times after a cerbo update that the communication with the BMS didn’t work. But all I had to do was turn off CAN2 in services and turn it back on. Thanks to that, I believe there’s a problem in the SW. Yes, on two diferent units.
What’s even more strange is that the computer has to be disconnected from the power supply, restarting it alone won’t help.
I’m returning the display tomorrow, but I’ll try connecting it to a powered-off cerbo today. That’s probably the only thing I haven’t tried.
Otherwise, I can say that the communication works without problems for several weeks if I don’t connect anything to HDMI.
I had a problem with the autostart generator with the last BETA. But I can test it for a short time on the last BETA version v3,60 7.
I’ll let you know what I find out.
There is indeed an issue with generator start/stop in the latest beta. Will be fixed in the next release.
And what GUI version are you running? Is the issue only occurring when running V1 or V2?
Let me know what you find with a Cerbo with the GX touch connected before powerup.
So what did I manage to test yesterday and today:
Update to 3.60 - 7, shut down cerbo, conect GX touch, power up (GUI v2), comunication down,In the statistics only the first few bits and then it freezes, no movement, nothing
reboot from GUI, nothing,
switch to GUI v1, nothing
power down cerbo, power up, RUNING
wait 3 hours, still OK
switch to stable 3.52 (i need generator autostart), GUI v1 RUNING
whole night OK, RUNING,
morning, reboot from GUI (just for test), comunication DOWN
disable and enable it back, RUNING
Then I had to disconnect the GX touch because I’m returning it today, Christmas time doesn’t allow me to buy it now. Today I’ll try to reconnect my 7-inch LCD to confirm that it behaves the same.
Any ideas what else I can try? Or we can arrange a remote SSH connection if you want to take a look at something. I’d be happy to help solve this problem.
Hi @KRUP85
Thanks for testing. The issue you experience is a known issue with the Cerbo GX mk2. VE.Can port 2 communication goes down and fails to recover. Running GUI-v2 locally seems to make the issue worse, and in some cases (like yours), the communication only fails when a display is connected and GUI-v2 is running.
For now, please use no display or GUI-v1 locally. You can still use GUI-v2 on your browser or in the remote console of VRM.
We are working on a solution.
1 Like
OK. That’s all clear and thanks for the confirmation. If you need to test something, get in touch. For now, I’ll solve the display using RPI + LCD. I have that tested and working without any problems, regardless of GUI v1 or v2.
Thanks for help.
Thank you. Yes, I can confirm that port 1 with BMS is working without problem. Problem is, I have 4 MPPTs with CAN and I loose conection with those. I basically swap CAN1 and CAN2, including the settings. However, then the communication with the MPPT drops out. I tried this at the beginning when looking for problems. 
Yes, I could connect them via VE.direct, but that seems kind of stupid to me.
Anyway, thanks for the link.
Venus OS 3.60~8 has been released, which fixes the generator autostart issue.
1 Like
As soon as I saw your post, I read the change log and updated my cerbo.
restarted, connected display and … wait for it… both CAN communication is running!!!
I left it alone for about two hours just to see and then just to test it I did a SW restart. After the restarted up, communication still works. GOOD JOB!
And of cource, generator autostart works to.
Big thumbs up from me! 
2 Likes
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.