Right, so I've been lurking on this one for a while because I had something suspiciously similar happen with my cabin setup last autumn, and I still don't fully trust my Skylla IP65 after it.
Mine wasn't a VE.Can to N2K adapter specifically — I was fiddling about with a Cerbo GX and briefly had the VE.Bus configured incorrectly — but the end result looked identical: charger sat there completely inert, no error code, no charging, just... nothing. Like it had decided it was someone else's problem.
What I eventually found (after far too many hours with the Victron manuals) was that the unit had latched into what's effectively an external control state. The register value you've mentioned (0x0200 = 0x04) is exactly the kind of thing that doesn't reset itself just because you've unplugged whatever caused it. The Skylla doesn't know the adapter's gone — it's just waiting for instructions that are never coming.
A few things worth trying if anyone else lands here:
- Full power cycle — not just the AC input, but isolate the DC side too if you can. Belt and braces.
- VictronConnect via Bluetooth — check whether the charge mode shows as "External Control" explicitly
- MK3-USB interface to force a configuration write, which can sometimes jolt it back to normal operation
I had to reflash mine via MK3 to get it behaving again, which felt rather excessive for unplugging a cable.
Has anyone managed to reset this purely through VictronConnect without the MK3 interface? Genuinely curious whether that's even possible on the IP65 variant.
