In attempt to fix Ve.Can2 port issues, as per the recommendation of other threads, I decided to switch the unit back to Classic UI.
Now the Unit seems to have lost VE.Can2???
When I go to the Services, only VE.Can port 1 exist:
Or at least view remotely through the VRM console, VE.Can port 2 has disappeared… Multiple reboot did not fix the issue.
I will have to check on the boat tomorrow if this is also true direct from the console…
@Ludo, yes there are many posts about issues with VE.Can2 on the new CerboGX MK2. This case however is a bit different in its’s behavior. It might be the case of a bad hardware.
Today I was able to go to the boat and confirmed the issue is with the VE.can2. and I am looking for a solution.
I confirmed that when I arrived on the boat, VE.can2 port was no longer being displayed as observed through VRM console. After a series of test I can confirm that:
The port reappears if we cycle power. No matter what we do the port status is always “Stopped”.
We tried multiple version: 3.52 the most current, 3.53-2 the current beta version on download site, 3.42, the last known version before introduction of the new UI. In all cases port #2 disappear after a soft reboot. Only a power cycle makes it reappear.
For all 3 version listed above the port is always in “Stopped” State and data sent to the port are not displayed. We tried
a GX reset per website instructions> Same result.
GX Firmware reload using a Einstein 3.42 Image loaded onto a USB Stick per web instructions > Same result.
The issue with the port is not function of the protocol used. We swapped port configuration
made Ve.can2 the NMEA/VE.Lynx at 250 Kbs and the data from the BMS on that port was not displayed. Ve.Can2 Status was still stopped even after reboot.
Plugged 500kBds Network to Ve.can1 set as BMS LV protocol and the data we wanted to see did appear as expected.
Bottom line Ve.Can2 port does not work… What’s next? Local Victron dealer ready to help but he is not sure what the next step should be.
The issue is not the RMA process, He does not feel confident another unit will work any better than the one we just received.
On other posts, they are mentions of newer Beta versions helping with issues related to Ve.Can2 port . But they are not accessible by me at this time. Only version I can access is 3.53-2.
If anyone can confirm the issue is hardware specific to this unit, he will replace it. I have no doubt.
Did you read the answer by mpvader? Some units were affected by hardware. The only way to have a definitive answer is to use the official channel.
The issue is actually signal degredatton.
Other items to look at also mentioned in the thread are interferance and limiting that, opeating temperatures, CPU load etc.
I did read the thread. My dealer (if this is what you refer to as Official channel), “Never heard of any issues. All the units he sold are working fine”. So he is investigating now. MPVader post does acknowledge hardware issue but offered a software solution. No guidance on hardware replacement.
In my previous post, I did ask if changing hardware was advisable and got no response.
Many post refer to released version V3.60-8 as having the solution. But the unit only find 3.53-3 in the beta version folder. Where and how do I get 3.60-8 if this is the answer?
From what i can see is alot can happen in the install to aggravate the issue. It only happens on the non isolated port.
Such as running comms cables near ac and dc wiring.
Or cpu load, so also depends on of there are extras running such as node red or it is a lerger install with plenty of devices.
HI
a bit of update on this issue… It has not gotten away nor been resolved.
All testing confirm that once port 2 is in stopped state, the following reboot will cause the Ve.can Port 2 to disappear from the list of available ports. Only a power cycle will cause the port to reappear.
the issue seems related to the temperature of the unit. If we let it cool down for 10 to 15 minutes, the communication appear normal. all the expected data is displayed. after 5 to 10 minutes, communication stops. No data refresh, no messages counted. no error shown on the network status page. On cycle power, with no cool down time, the port shows as stopped.
It is not caused by external traffic. on the bus. We tested with limited message profile were only 9 of the BMS messages with relevant data are being sent. The unit does not start and port stays in Stop mode.
It is not the Protocol choice. We swapped both Ve.can1 and Ve.can2 and swapped the protocol accordingly, data on port 2 now set as Ve.Can Lynx remains stopped while data on port 1 running Ve.can BMS is displayed.
Just to close this thread.
Tested MK2 with newer firmware 3.53. Still did not work. Port VE2 still not showing up after reboot.
We replaced the unit with a new original cerbo running v3.63 and it all work.
We probably got a faulty Cerbo MK2.
I am still not sure why the system is loosing a canbus port and is not reporting a hardware fault.
