VE.can - NMEA 2000 interfacing and instancing

Been wrestling with this exact problem in my van setup. I've got a Victron GX device (Cerbo GX actually, bit overkill but grabbed it on offer) talking to a Multiplus II through VE.can, and I'm trying to integrate some navigation kit without everything screaming at each other.

The thing that caught me out was assuming NMEA 2000 would just... work seamlessly. It doesn't. Victron's documentation on instance numbering is decent, but it's easy to configure two devices with clashing instances and end up with the GX dropping the connection mid-journey, which is precisely what you don't want when you're off-grid relying on system data.

What I've found works better than expected is using the Victron's built-in NMEA 2000 gateway functionality rather than trying to bridge everything through a separate multiplexer. Saves a fair bit of headache, though you do need to manually assign instances in the GX settings—it won't auto-detect overlaps.

Curious whether anyone else here is running multiple Victron components on a VE.can backbone and mixing in third-party NMEA 2000 gear? The documentation assumes either pure-Victron or pure-marine setups, but actual off-grid vans often sit awkwardly in between.

Are you seeing drop-outs with your Maretron kit, or is it more of a configuration puzzle? Would be useful to compare notes on what's actually reliable in the field versus what the spec sheets promise.

The Cerbo's definitely capable of handling that architecture, though you might find the VE.can bus gets a bit chatty if you're not careful with instance numbering. Had similar issues in my shepherds_hut setup when I initially tried daisy-chaining multiple devices.

Key thing is ensuring each device on the bus has a unique instance ID — the Multiplus II should auto-assign, but I'd manually verify in the GX device menu rather than assuming. Check Settings > System setup > VE.can on the Cerbo itself.

One gotcha: if you're also trying to pull NMEA 2000 data into the mix (sensors, displays etc), you'll need the VE.can to NMEA 2000 gateway mode properly configured. The Victron documentation on this is oddly sparse, but the forum archives have some useful troubleshooting threads.

What other devices are you planning to network through it? That'll determine whether you're genuinely stretching the bus or just overthinking it.

The Cerbo's a solid choice for this setup, even if it feels like overkill initially. You'll find the extra processing headroom useful once you start layering on monitoring.

One thing worth noting — if you're planning to expand beyond just the Multiplus II (adding a MPPT, BMV, etc.), the VE.can bus scales quite well. I've got a similar architecture on my narrowboat with three devices daisy-chained, and it's rock solid once you sort the termination resistors.

The real trick is making sure your device IDs don't conflict. Victron's documentation is decent for this, but it's easy to miss if you're configuring on the fly. Have you set explicit instance numbers in the GX settings yet, or still working through that part?

Have you looked into whether you need multiple device instances on your VE.can bus? I ran into something similar with my setup — got a Cerbo talking to a Multiplus II plus some battery monitoring, and initially thought I'd need separate instances for different parts of the system.

Turns out the real challenge isn't the bus itself, it's making sure your device IDs aren't conflicting. The Cerbo should handle the addressing fairly well out of the box, but worth checking your device list in the GX interface to see if anything's showing duplicate instance numbers?

Also — what specifically are you trying to interface? If it's just monitoring, the Cerbo's NMEA 2000 side is pretty straightforward. If you're trying to control devices across the bus, that's where it gets more intricate. What's the full picture of what you're connecting?

The Cerbo's definitely the right choice for this — you're not overdoing it. VE.can gets properly busy once you start stacking devices, so that extra processing headroom pays for itself.

Worth checking your device instances in VEConfigure if you haven't already. I had a right mess with mine when I added a second MPPT to my setup — both were trying to report on the same instance and the GX was having a mare sorting it out. Once I manually assigned them it was fine.

Also make sure your VE.can termination is sorted at both ends. Sounds daft but loose terminators cause all sorts of phantom issues that look like instancing problems. Victron's documentation on this is actually decent if you dig into it.

What else you running on the bus? That'll help work out if you've genuinely got a congestion issue or just config gremlins.

The Cerbo's a gateway drug — you'll end up daisy-chaining half the Victron catalogue to it before Christmas, mate. On the NMEA 2000 side, watch your device IDs don't collide; I learned that one the hard way when my BMV-712 decided it was also a battery monitor (spoiler: it wasn't). The instancing gets properly mental once you've got multiple Multiplus units, so maybe sort that before adding more sensors. Honestly though, if you're planning expansion, the Cerbo just shrugs and carries on — beats ripping everything apart in six months.

@GoldenTrekker sounds like you've not finished describing the actual problem — your OP got cut off! What's the specific issue you're seeing, instancing conflicts on the bus, or something else?

That said, worth knowing that on a VE.can/NMEA 2000 mixed network, device instances need to be unique across all devices sharing that backbone, not just within the Victron kit. If you've got a chartplotter or any third-party NMEA 2000 devices on the same bus, they can claim conflicting instance numbers automatically, which causes all sorts of weird behaviour on the Cerbo's device list.

The Victron VictronConnect app lets you manually reassign instances on most devices — handy for sorting clashes. Also double-check your bus termination, a missing 120-ohm terminator at each end causes gremlins that look deceptively like software issues.

@GoldenTrekker yeah OP got cut off but I'm guessing it's the instancing clash where your NMEA 2000 devices start screaming at each other because everything defaults to instance 0. Drove me mental on my motorhome build.

Short version: you need to manually reassign device instances in the Cerbo's VRM portal or directly through the console. VE.can and NMEA 2000 share the same physical bus but Victron handles the translation — just make sure nothing's fighting over the same instance number.

What other devices are on the network?