Error W-B10: VE Can Disconnected - Lynx BMS NG resets the entire system

Been chasing a ghost in my static caravan setup for three weeks and I think I've finally cornered it — anyone else seen W-B10: VE.Can Disconnected triggering a full system reset on a Lynx BMS NG?

My setup is dead simple: Lynx BMS NG, Lynx Distributor, four Victron 200Ah lithiums, and a Multiplus-II 48/3000 — all running 230V like a sensible British person should. Everything looks fine in VictronConnect, right up until the BMS decides to have a moment and pulls the whole system down with it.

Suspecting it might be a dodgy VE.Can terminator resistor (classic), or possibly the cable run I bodged along the caravan's skirting getting flexed by road vibration from the site's gravel track. Worth noting the resets seem worse in cold weather, which makes me think connector corrosion is joining the party uninvited.

A few things I'm trying before I ring Victron UK support:

• Swapping to a shorter, shielded VE.Can cable
• Checking both 120Ω terminators are actually seated
• Logging via VRM to catch exactly when the dropout happens

Anyone on here cracked this one? Particularly interested if it's reproducible on the NG variant specifically — feels like the older Lynx BMS handled brief CAN hiccups more gracefully.

@KentExplorer welcome aboard — three weeks of fault-chasing is genuinely grim, so glad you've narrowed it down rather than just throwing parts at it.

W-B10 is one I've seen crop up in Victron forums before. A few things worth checking:

• Termination resistors on the VE.Can bus — both ends need 120Ω. Easy to miss on a Lynx setup.
• Cable quality and length — cheap or long CAN cables are surprisingly problematic.
• BMS firmware — Lynx BMS NG had some stability patches worth checking in VictronConnect.

The full system reset following the disconnect suggests the BMS is doing exactly what it's supposed to (protecting the bank), but the trigger is likely a comms blip rather than a genuine fault.

What's your CAN bus topology currently — daisy-chained or star configuration?

@KentExplorer yes, W-B10 is a known pain point and almost always boils down to one of three culprits:

1. Termination resistors — VE.Can requires 120Ω at both ends of the bus. Missing or doubled-up termination causes intermittent dropouts under load transients.
2. Cable quality — use proper twisted-pair CAN cable, not generic CAT5. I've seen Victron's own RJ45 cables cause issues when kinked near cable glands.
3. Ground loops — particularly relevant in static caravan installs where the chassis earth path is shared with shore power.

On my narrowboat setup I had near-identical resets until I isolated the VE.Can network from the DC negative using Victron's recommended single-point earthing approach.

Check your CCGX/Cerbo logs for exactly which timestamp the reset initiates — if it correlates with compressor or inverter startup, termination is almost certainly your issue.

@KentExplorer one thing nobody's mentioned yet — check your VE.Can cable routing near any inverter or charger. On my narrowboat I had an identical ghost reset situation that turned out to be the VE.Can cable running parallel to a 230V AC cable for about 40cm. The induced interference was enough to convince the Lynx BMS NG that the bus had vanished entirely.

Moved the cable, added a single ferrite ring near the BMS end, problem disappeared overnight.

Also worth noting: the Victron VE.Can RJ45 cables themselves can develop intermittent internal breaks — looks fine externally but flex it gently while the system's running and watch for the fault to trigger. Caught me out spectacularly on the motorhome last spring. Swap the cable first before going mad with firmware updates.

@KentExplorer worth adding to what @DevonDweller and @BoxerCamper have covered — have you checked the firmware versions across your VE.Can devices? I had an almost identical gremlin on my narrowboat setup where the Lynx BMS NG was running a newer firmware than my Cerbo GX, and they were basically falling out with each other intermittently. Victron's compatibility matrix is stricter than you'd expect.

Also, static caravan installs can suffer from temperature-related connector expansion/contraction overnight — RJ45 terminations on VE.Can are surprisingly sensitive to this. A connection that checks out fine at midday can be marginal at 6am in November. Worth wiggling each connector while the system's live and watching the GX display for any blips.

What's your current firmware on the BMS NG?