On a boat that previously had Cerbo 1 installed, with a HDMI extension cable for the display, everything worked tickety-boo for approx 18months. Now we have upgraded to a Cerbo 2, with same extension cable, same display etc. etc. after ~24hrs or so, the display freezes. The only way to correct it is to depower the Cerbo and reboot.
Anyone else fitted a Cerbo 2 with an extension cable? Any issues?
Any ideas?
Have you tried without the extension? HDMI extensions are not supported and the non-supported use of them has caused issues for years, so I’d try reverting to without the extender first to see if that’s the issue. To be clear, I know loads of people are using them without issue for extended periods of time, but eh… everything works until it doesn’t, so in troubleshooting it’s always best to start from a manufacturer-supported configuration.
I’ve used HDMI extension cables for a long time, on lots of installs with lengths up to 20m and never had an issue, with the Cerbo 1. First time using one with a Cerbo 2, and the only thing that has changed on this install is that we upgraded to a Cerbo 2, primarliy for the second CAN port, for better integration with CZone.
The main issue is that Cerbos are not designed for large boats, with the poxy VE Direct connection/serial protocol. There always has to be a compromise and I have found that an HDMI extension has been the most robust compromise, until now.
It’s working but it’s not officially supported.
Did you try another extension or to connect the display directly to the Cerbo?
Tried a different cable, and issue still exists. Will relocate display and try with display connected directly. Although this is not a solution, as the Cerbo is located midships on a catamaran underneath a hanging locker, and the display is where it should be, at the Nav Station. Cerbo is located where it is such that all VE Direct devices can be connected directly within the 10m limit of the VE Direct cables. Everything on this boat worked perfectly with a Cerbo 1, the installation architecture has not changed, except replacing the Cerbo 1 with a Cerbo 2.
This is a major issue, as I said before, the Cerbo is not designed for larger boats, because the VE Direct connection/protocol is so poxy. A compromise needs to be used, and with a Cerbo 1, a HDMI extension cable is the best compromise. Looks like something has changed with the HDMI interface in the Cerbo 2, that means that extension cables do not work. Unless someone can tell me otherwise.
Hi. Have you looked at Wifi or Ethernet cable? If your Nav Station has a MFD, it may be compatible with the GX. There’s even a Victron MFD app, a different display again, with coool layout and display options for mariners.
Have you used the second CAN interface for anything? Are you absolutely certain the reboot is required because of the HDMI interface or has something else changed on this installation apart from swapping the CerboGX?
Why would we do that??? We have a perfectly good 7" Victron Touchscreen, that was working fine until upgrading to the Cerbo 2. Well aware of the MFD app, but it does not work with the new UI, and who wants to keep their Nav instruments on all the time just to see what should be already on the touchscreen only 200mm away!
No, have not used the second CAN interface for anything yet, I need to write the program for the integration, before doing so. Only change is the change to the Cerbo 2. Nothing else.
There was a small change made to the Touch-specific usb port, which was power supply only, but then changed to both usb and power functions with the later Cerbo. Maybe it’s the power supply that isn’t handling the long distance? Have you a local usb option at the helm you could try?
Why would you not? New UI is now multi-user. I’ve an ancient CCGX that has ClassicUI on it’s own screen, NewUI on a PC, tab or phone. Along with VRM and MFD too. Via Ethernet or Wifi. Frankly, I have no use for the function of a Touch. And for HDMI over distance, why bother?
We all know there was the change to the third USB port, making it the same as the other two - this has been widely communicated. However, we (including you) don’t know whether there has been a HW change to the HDMI port, and they’re unlikely to tell us.
You can’t use Remote Console from the new UI on an MFD. What do I tell the boat owner about the great big hole in his dash, where I have removed the display because it crashes continuously, because we tried to upgrade his kit.
Horses for courses, you personally might not like a screen. But I have done loads of installs and only two without a screen, one then came back and asked for a screen, because he got sick of booting his tablet everytime.
You don’t seem interested in finding a (better) solution. But here’s another alternative for a dedicated NewUI screen… NEW: Use an Android tablet as dedicated GX Wi-Fi Display (beta)
I know all this can be done. And I get that you have an opinion that what you are suggesting is better, but that’s your opinion.
We already have a very elegant install that I designed and had manufactured for the customer. Which worked perfectly with a Cerbo 1 and I am trying to make work with a Cerbo 2!
Why did you even switch from the MK1 to the MK2?
Such that we can have the Victron networks and the CZone networks isolated, and the Victron network will pass battery data to the CZone network via the CAN1/CAN2 bridge in the Cerbo. The previous methodolgy (using a YD bridge) required a script for any data changes.
I am remembering users complaining about HDMI problems together with CAN2 port problems on Cerbo Mk2.
So wait until you’ll use CAN2…
See here: HDMI connection breaks the VE Can 2 port
Maybe this is a consequence of some modification made to the hardware…
Ok, so we changed the Cerbo out, fitted a new Cerbo 2.
Have not updated the FW, so running V3.33, pre the UI update on 3.5.
Working tickety boo for ~90hrs. Now to determine whether it is the Cerbo, the update >3,5 or the new UI. I suspect it is the new UI. Will update FW to 3.54 and leave running classic UI. Will see if it is stable. Then will change to new UI if it remains stable. If it crashes at any point, then we can determine where the issue is. It could even be the Cerbo.
It was the Cerbo itself. Have replaced the Cerbo and everything working a-ok. Running latest FW and new UI.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
