VE.can - NMEA 2000 interfacing and instancing

DIY
, ,
1

I have a fairly large NMEA 2000 network–mostly with Maretron components, including an N2KView system.

I recently connected my new Victron VE.can system (Two Quatros, Two BMS-NG, six 300AH NG Batteries, MPPT controller, Ektrano) to my NMEA 2000 network. It basically works, but I’m seeing a number of strange/intermittent behaviors. The Ekrano seems to occasionally report that it has lost communication with the BMSs. I also see on the Maretron system that the DC monitor is recognizing one of the two BMSs, not the virtual BMS.

I ran Maretron N2K Analyzer and found a lot of instancing conflicts, but I’m concerned about changing instance numbers because I’ve remember seeing that some of the instance numbers can’t be changed for the Victron system to work correctlly.

Finally, I’m also seeing the Ekrano periodically reboot.

None of this happened before I connected the Ekrano to NMEA 2000 (using the Victron cable with the fuse removed, since I have a 24V system).

Where can I find more information about instancing and what I can (or cannot) change.

2

For what it’s worth my Cerbo was crashing my navigational n2k network due to the volume of PGN updates. When this occurred my MP2 would lose connection and go haywire. I’m in the process of creating a separate Victron n2k network and will use a n2k bridge to only send certain PGN’s to my main n2k network so it doesn’t overload it. It’d be nice if they could program the cerbo so I can select which PGN’s to output and the frequency. I don’t need to have temperatures reported every 100ms.