Only problem I have (rather serious now) is that I keep getting the #67 error (No BMS) more frequently (over 6 times a day now!). I have tried everything, upgrading to latest and downgrading to 3.4x. Nothing seems to improve the situation.
When I change the cabeling from the VE.Can port 1 to 2 and vise versa, the trouble seems to port to the connections on port 2 (ie, BMS works, but all the other devices RS-es, SHUNT, PE-meters fail).
I’m positive now that it is truly hardware related and am in the process of sending the CerboGX MK2 back for RMA.
Here is the catch though, I don’t want to have my system down for weeks waiting for the RMA process to be done. So I’m opting to buy a new one and try to get my money back for the broken item. But… What if the dealer sends me a new one that came out of the same batch? Then I will be getting the same issues right?
Is there any way to identify if I get a proper (newer) version?
This is the interesting part. And part of the reason for not pinning down the problem. It is not the whole batch. I have some in “from that batch” with no issues.
In any case make your request known to the dealer. Most are reasonable.
Or you can totally circumvent the issue and swith to an ekrano. With a tablet for a screen in a different location.
Sorry for this situation. It is not as clear as a bad batch, for sure not all units are affected.
Though once the issue was identified, there were changes made to production processes that means all units produced after the fix do not have the issue.
Given the situation, it should be fine for the dealer to begin the warranty RMA process without you needing to send them the unit.
Proper documentation showing the error, the updates to the firmware versions (3.56) that included fixes for it, and the error persisting should be enough to begin the claim. Then you keep the system as it is for now until a replacement is provided. It’s then important that the unit with issues is returned to them, so there might be some deposit required.
I would think that is easier than buying another brand new unit and then trying some kind of refund when the old one is replaced under warranty.
guystewart
(Guy Stewart (Victron Community Manager))
6
One other thing, I am also normally very reluctant to recommend this, but there are additional fixes specific to this Can port issue currently in testing with Venus 3.60 beta - Venus OS v3.60~66 available for public testing
Have you tried this beta yet?
v3.60~59
Fix Cerbo GX MK2 VE.Can 2 port issues. A while back we’ve already released a an improvement for that issue, but that still left a certain percentage of units failing, with the remedy being to RMA/replace them under warranty. OK - but not good.
Now, we’ve finally been able to, in software, find a fix that promises to be a 100% solution. Also VRM data this morning confirms it: all units that had issues running v3.60~58 yesterday, and now updated to v3.60~59, report a 100% operational VE.Can 2 port. More testing is needed to be 100% sure, but so far all signals and results are promising!
I can now confirm, the update to V3.60-66 did the job! No more alarms for a day now! Looking forward to the official V3.60 release! Tnx again for you help guys!
