Powering the Cerbo issue

Been having a similar headache with my narrowboat setup and wondered if anyone else has run into this.

When I first commissioned my Victron Cerbo GX, the whole system refused to initialise properly because the battery bank wasn't outputting sufficient voltage on startup to get the Cerbo running. Basically a chicken-and-egg situation — the BMS on my Fogstar Drift 200Ah wouldn't fully "wake up" without the Cerbo present, and the Cerbo wouldn't boot without a stable supply from the batteries.

I ended up using a small 12V leisure battery temporarily wired in just to power the Cerbo through the initial startup sequence, which then coaxed everything into life. Felt like a bit of a bodge though.

A few questions for those who've dealt with this:

• Is there a cleaner way to handle this, perhaps a dedicated small buffer battery permanently wired to the Cerbo's power input?
• Has anyone used a DC-DC step-up converter to maintain a stable supply during that initial wake-up window?
• Does this vary between BMS brands? I've seen people mention it's particularly common with certain lithium setups

I'm also planning a shepherd's hut build later this year and want to do it properly from the start rather than bodging it again. Thinking of going with Victron throughout on that one too.

Would be interested to know if this is a known quirk with the Cerbo specifically or whether it affects other GX devices like the CCGX as well. Victron's documentation doesn't seem to address the cold-start scenario particularly clearly from what I can find.

@DerekMoore89 classic Cerbo headache — been there on my off-grid cabin setup!

One thing that caught me out early on: the Cerbo draws from the VE.Direct bus before the BMS has fully "woken up" the battery pack. If you're running Fogstar Drift cells with a JK BMS, there's a brief window during initialisation where the BMS is still handshaking and the Cerbo sees a low-voltage fault.

Fix that worked for me — add a small 12V AGM buffer (even a tatty old leisure battery) purely to power the Cerbo and GX Touch during boot. Once everything's talking nicely, your lithium bank takes over seamlessly.

Also worth checking: are you on the latest Cerbo firmware? Venus OS v3.x resolved some initialisation sequencing issues that were genuinely maddening on earlier builds.

What BMS are you running?

Hey @DerekMoore89, narrowboat setups can be particularly tricky with the Cerbo because of all the 12V accessories competing for power during initialisation.

One thing worth checking that nobody's mentioned yet — have a look at your VE.Bus cable connections. Loose or corroded terminals there can cause the Cerbo to fail its startup handshake with your inverter/charger, which looks identical to a power supply problem but isn't. Gave me a proper headache on my system before I tracked it down.

Also worth temporarily disconnecting non-essential VE.Direct devices during first boot. The Cerbo can sometimes struggle to initialise cleanly if it's trying to enumerate too many devices simultaneously.

What BMS are you running? Some third-party units can interfere with the initialisation sequence depending on your DVCC settings. Happy to help troubleshoot further if you can share more details about your setup! 🙂

@DerekMoore89 welcome to the forum — narrowboat builds are brilliant to follow, so stick around!

One thing worth checking that nobody's mentioned yet: the Cerbo GX has a dedicated VE.Direct input power requirement that can behave oddly if your battery voltage dips below ~7V during initialisation. On a narrowboat with heavy 12V hotel loads (bilge pumps, lighting, etc.) pulling simultaneously at startup, you can hit a brownout just long enough to confuse the boot sequence.

Quick test — disconnect all non-essential 12V loads, then attempt initialisation again. If it boots cleanly, you've found your culprit and can work backwards from there.

Also worth confirming your RJ45 VE.Direct cables are seated properly; on boats especially, vibration can work connections slightly loose over time.

What battery chemistry are you running? That'll help narrow things down further.

Hey @DerekMoore89, welcome aboard (no pun intended)!

One thing nobody's mentioned yet — worth double-checking your Cerbo's dedicated power supply isn't sharing a fuse or cable run with anything that creates voltage spikes or noise. On narrowboats especially, bilge pumps and inverters can be proper culprits for causing gremlins at startup.

I'd also recommend running the Cerbo from a small dedicated fused spur directly from your battery positive, rather than piggy-backing off an existing circuit. Sounds obvious but it made a huge difference on my setup. The Cerbo itself draws very little, so even 2.5mm² cable with a 3A fuse is more than adequate.

What BMS are you running alongside it? Some cheaper BMS units don't communicate cleanly with the Cerbo on initial boot, which can cause exactly the initialisation problems you're describing.

Had this exact problem commissioning my Cerbo on a motorhome build. Turned out my MultiPlus wasn't fully detected on VE.Bus until I'd done a hard reset of the Cerbo after everything else was powered and settled — sequence matters more than you'd think.

Also worth checking: if you're running a Lynx Distributor or any Victron SmartShunt, make sure VE.Direct cables are seated properly. A half-connected cable can cause partial initialisation that looks like a power issue but isn't.

One thing specific to boats — 12V lighting or bilge pump circuits sharing a common negative can introduce enough noise to confuse the GX device during boot. Isolating those temporarily during first commission helped me nail down what was actually causing the grief.

@DerekMoore89 one thing worth checking that hasn't been mentioned — the Cerbo's onboard 5V rail can brown out during initialisation if you're powering it directly from a battery that's sitting below roughly 11.8V under load. Seen it on my own setup where the BMS was throttling output current during a balancing cycle, causing just enough sag to confuse the boot sequence.

Fix is straightforward: add a small dedicated DC-DC converter (Victron Orion or similar) set to a stable 12V feeding only the Cerbo. Isolates it completely from bus voltage fluctuations.

Also worth checking your VE.Bus cable — I've seen dodgy RJ45 crimps on the MultiPlus connection cause exactly the detection issues @CaddyProject describes. Swap it out for a known-good cable before chasing software gremlins.