question

thefu avatar image
thefu asked

Cerbo GX Mk2, issues connecting to RV-C on Newmar New Aire

I am at my wits end. That is why I am now here. Let me explain my set up and then where I have come to an impasse. I hope someone out there can help.

I have recently embarked on swapping out my 8 AGM on my 2021 Newmar New Aire for three 460ah LiPo4 batteries from Epoch. These batteries have a Victron-compatible Can-BMS port. The Newmar uses Silverleaf and a RV-C (via Xanbus) connected Xantrex 3012 Inverter.

The changeover went well and all the base systems are working fine.

First let me be clear - because this may or may not make a difference in your answers - I have the newest model of the Cerbo, the Mk2. I have updated the firmware to the latest (March 2024) version.

I installed the Cerbo and connected the batteries to it in the leftmost connector in the leftmost set of ports (VE.Can 2) and have installed the Victron terminator in the other connector. I configured what is labelled in the menus as "BMS Port" in the software menus to be BMS. The information is coming across to the Cerbo as one would want. Packets are moving.

Then, I wanted to connect the Cerbo to the coaches RV-C network. I found out that my coach, and Xanbus implementation, of RV-C over RJ45 connections happens on different pins (4/5) than Victron (7/8). So I made a patch cable, tested it for continuity (even made two), and connected 4->7 and 5->8 as described in various Victron info pages. I removed the terminator on the Xantrek, connected the cable, and connected it into the left connector of the middle set of ports labelled Ve.Can 1. I then went to the software and for the selection labelled Ve.Can I changed the setting to RV-C. No data comes across, only a handful of packets come up on the Rx side and none on the Tx side.

I have swapped around the cables between Ve.Can 1 and Ve.Can 2 and as well the software configuration and in the middel Can ports, VE.Can 1, the BMS does not work at all, and on VE.Can 2 with the RV-C connection and software selection it does not run either.

What gives? I know this configuration should work. What am I doing wrong!?


cerbo gxBMSVE.Can
16 comments
2 |3000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

phil-garver avatar image phil-garver commented ·
I am actually having the same issue, with same battery setup and MK2, but on a different system, a Tiffin Spyder RV-C. However, what you described is exactly the same issue I have. Following / will update if I find anything.

Question, you are able to see the Batteries ok, correct (I am, want to confirm you are).

0 Likes 0 ·
thefu avatar image thefu phil-garver commented ·
Yes, the batteries communicate fine with the Cerbo - you can see the packet traffic and the data comes over. It's the RV-C side that does not. I am fairly certain I have the wiring correct with the 4->7 5->8 patch cable. Wondering if there might be some other firmware issue related to this in the Mk2.
0 Likes 0 ·
Justin Cook avatar image Justin Cook ♦♦ commented ·

Are you sure your coach is actually running RV-C and not Xanbus? They're not the same, and I wouldn't expect a Cerbo to be able to communicate with Xanbus.

Xantrex does make particular inverter/chargers for RV-C rather than Xanbus, like the Freedom SW-RVC series, but if the system in the coach is Xanbus instead of RV-C then that'll be the issue.

0 Likes 0 ·
phil-garver avatar image phil-garver Justin Cook ♦♦ commented ·
For my setup, yes, it is RV-C.
0 Likes 0 ·
Justin Cook avatar image Justin Cook ♦♦ phil-garver commented ·

And you've followed the manual in re to setting it up? Bearing in mind that the MK2 of course negates the "only 1 VE.Can port" admonishment in the manual, but the other steps and limitations would still need to be adhered to.
https://www.victronenergy.com/media/pg/Cerbo_GX/en/rv-c-support.html

If so, would be worth having a chat with your distributor and/or an experienced installer in your area have a look to ensure proper connection and setup, and possibly replace or correct anything necessary.

0 Likes 0 ·
thefu avatar image thefu Justin Cook ♦♦ commented ·

Yes, it is RV-C, I only stated Xanbus because that is how it is labelled on the side still. RV-C is what the coach uses as this is a silverleaf managed coach based on RV-C.

0 Likes 0 ·
thefu avatar image thefu Justin Cook ♦♦ commented ·

Yes it is RV-C. Since you are responding here, and an expert, I can only assume you have not done an install on the Newmar before so that is why you might be unfamiliar. Sorry for any confusion on my part.

Also, the menus in the firmware (3.3) still reference a "BMS" port but one does not exist any longer. It is incredibly confusing and dealers are not up to date on this new model - some did not even know it existed or thought there was no material difference with the Mk2.

As an expert, how would you determine how to wire up the Xanbus 3012 clearly connected and communicating with RV-C as it is listed on the Silverleaf device list, but will not comm correctly according to the info I posted above. Suggested troubleshooting steps you would take?

0 Likes 0 ·
Justin Cook avatar image Justin Cook ♦♦ thefu commented ·
Well that's what I mean, as far as I can tell the Xantrex 3012 uses Xanbus, not RV-C, so I'm not sure what's going on there. I would defer to an installer experienced in those systems, and highly encourage you consult one - I'm a Victron expert, but not an RV-C, Silverleaf (no idea what that is, actually), or Xantrex expert at all unfortunately!
0 Likes 0 ·
thefu avatar image thefu Justin Cook ♦♦ commented ·
Well whatever the bus, the Xantrex is connected to the RV-C bus on the coach and responds on that bus being shown in the list of devices on the silverleaf and reports status to the control panel and the control panel turns it off and on. It uses pins 4/5 as does the rest of all the RJ45 CanBus connections on the coach. So, if Xantrex wants to call it XanBus, but it is a subset of RV-C, then that is fine. It is not relevant to the issue since it is communicating on the CanBus of the coach correctly. Now, in case there is some issue with the secondary connector on that xantrex, I will disconnect it upstream and connect the cerbo directly into the coach CanBus.
0 Likes 0 ·
Justin Cook avatar image Justin Cook ♦♦ thefu commented ·
Again, it is relevant to the issue: Xanbus is one thing, RV-C is a different thing. That's why Xantrex sells Xanbus inverter/charger models or RV-C inverter/charger models.

Good luck!

0 Likes 0 ·
thefu avatar image thefu Justin Cook ♦♦ commented ·

I think we both do not know the entire story. My guess is that the Xanbus protocol runs on CanBus (so wiring and data format are the same) and the command set is a subset of RV-C. I have come to that conclusion from this passage in a Lithionics battery BMS manual. So, this is why the Xanbus CAN and IS connected to the RV-C network on the Newmar coaches and how it is monitored and controled by the Silverleaf management devices and control panel. Why they also have an RV-C version of the Xantrex inverters I cannot tell you - but it is not germane to this conversation or issue.


1713462135093.png

0 Likes 0 ·
1713462135093.png (145.9 KiB)
thefu avatar image thefu thefu commented ·

Even more digging turned up we were both kind of right. The TM-102 referenced in this screenshot of the Silverleaf reference manual refers to the main brain of the Silverleaf control system. So, while Xanbus protocol is not RV-C, it still uses a standard CanBus implementation so its connections are in fact Xanbus over CanBus. Connecting the Cerbo to this should not present any issue but I will once again tap the coach CanBus elsewhere for another test just to be certain the Xantrex is not causing any other issues. 1713469946779.png

0 Likes 0 ·
1713469946779.png (117.6 KiB)
thefu avatar image thefu commented ·

Also, from what I can tell, no updated manual has been posted yet for the Mk2 model. And, as I said, the firmware menus do not align up with the labels on the ports any longer as well.

0 Likes 0 ·
phil-garver avatar image phil-garver thefu commented ·
One thing I have noticed is the tap point for my RV-C only has Blue and White wires (CAN Hi and Low). Not sure if this is causing an issue or not. There was an RV-C (Go-Power) solar controller in this tap point that was working, so not sure if the Cerbo needs the ground reference and that is causing the issue. Will look to update the tap and try.
0 Likes 0 ·
thefu avatar image thefu phil-garver commented ·
Ground is really not necessary in this configuration - at least according to the engineer at the Victron dealer I spoke to. Most 2-wire comm systems like CanBus are fine with just the two wires.
1 Like 1 ·
thefu avatar image thefu commented ·

So I just got off the phone with an engineer at Solar Energy Systems to go over all that I have done and see what he thinks. He did not have any experience with the Mk2 and RV-C yet but said that to him it sounded like (given all the work and testing I have done) that it could be something with the firmware in the unit. I also find it strange that in the firmware menu, the settings for the the two ports still have them labelled the old way. He suggested trying an original Cerbo to see. I don't have one handy and really dont want to order one just to test this theory. I am going to go back out and make a new patch cable, test it for continuity, and see what happens. I guess it is also possible that the Ve.Can1 port is bad, but if that were the case, why would it not work on Ve.Can2 when configured as RV-C when the batteries work fine on Ve.Can2 when its configured as BMS.

It would be great if someone from Victron sees this and at least brings it to the engineers and gives it a look - and if alls well, tell me I am crazy. I am fine with that :)

0 Likes 0 ·
0 Answers