Calcul courant CC incohérent suite erreur sur Phoenix Inverter 12V 500VA 230V

by Boat Gemma · 1 week ago 34 views 4 replies
Boat Gemma
Boat Gemma
Active Member
10 posts
thumb_up 10 likes
Joined Dec 2024
1 week ago
#20019

Has anyone else noticed wonky DC current readings after a fault on a Phoenix Inverter?

Running a Victron Phoenix 12V 375VA on my boat (narrowboat, continuous liveaboard), paired with a Cerbo GX on the latest-ish firmware. After the inverter threw an error last week — think it was a low voltage shutdown — the DC current figures in the VRM portal looked completely off. We're talking readings that made no sense relative to what was actually drawing power at the time.

A few questions I can't quite get my head around:

  • Does the Phoenix reset its internal current calculations properly after recovering from a fault, or does it carry some kind of offset forward?
  • Could this be a firmware mismatch between the Cerbo and the inverter causing the displayed values to go strange?
  • Is there a way to force a proper recalibration short of a full factory reset?

I've checked the cabling and there's no obvious loose connection. The BMV-712 is showing sensible numbers, so it doesn't feel like a shunt issue — more like the Phoenix itself is reporting odd figures upstream to the Cerbo.

Wondering if anyone else has hit this on a boat install specifically, where the 12V system is doing a lot of work and the inverter cycles fairly frequently. Would love to know if there's a known fix or if this is just a case of watching it and seeing if it settles.

Pete
Pete
Member
7 posts
Joined Mar 2025
1 week ago
#20043

@BoatGemma had the exact same gremlin on my shepherd's hut Phoenix 500VA — DC current went completely haywire after a low-voltage cutout, turned out the Cerbo GX needed a full power cycle (not just a soft restart) to resync its shunt readings properly. 🔌

Worth checking in VictronConnect whether the internal shunt calibration has drifted post-fault — there's a hidden reset buried in the settings that most people miss entirely. Also double-check your VE.Direct cable isn't loose; mine was giving phantom readings for weeks before I spotted it had worked itself slightly out of the socket on the Cerbo end.

RetiredChef
RetiredChef
Regular
62 posts
thumb_up 75 likes
Joined Aug 2023
1 week ago
#20072

Classic Victron "phantom amps" syndrome — after a fault event, the Phoenix can lose its internal current calibration reference until you do a full power cycle (disconnect DC completely for 30 seconds, not just standby).

@BoatGemma on a liveaboard narrowboat I'd also check your VE.Direct cable connection to the Cerbo GX — a dodgy connection causes the GX to interpolate nonsense figures rather than throw a clean error, which looks exactly like miscalibration but isn't.

Worth doing in this order:

  1. Full DC disconnect (30s minimum)
  2. Check VE.Direct seating
  3. Update firmware via VictronConnect — there were known current-reporting bugs fixed in recent Phoenix firmware

If readings are still drifting after all that, the internal shunt may have taken a knock during the fault — Victron UK support are actually decent about warranty replacements.

YEL_Marine
YEL_Marine
Active Member
11 posts
Joined Jun 2025
1 week ago
#20110

@BoatGemma worth checking whether your Cerbo GX is still receiving clean VE.Direct comms from the Phoenix after the fault. In my experience, if the VE.Direct connection gets interrupted during a fault event, the Cerbo can start displaying stale or miscalculated current figures that look completely bonkers. Try disconnecting and reconnecting the VE.Direct cable, then do a proper power cycle on both units — isolate the Phoenix fully from the battery for a couple of minutes before restarting. Also worth pulling the device history in VictronConnect to see exactly what fault triggered this, as that'll help narrow down whether it's a comms issue or something deeper in the inverter itself. If the readings are still off after that, a firmware update on the Cerbo sometimes resolves display anomalies following fault events.

Dan Hughes
Dan Hughes
Member
9 posts
Joined Jun 2025
6 days ago
#20317

Good shout from @YEL_Marine on the VE.Direct comms — I'd go a step further and check the VE.Direct cable itself for any corrosion on the connectors. Boat environments are brutal for that, especially on a liveaboard narrowboat where you've got constant condensation cycles.

One thing nobody's mentioned yet: try a full power cycle of the Phoenix (not just standby — properly isolate it from the battery for a couple of minutes). I've seen this reset the internal shunt reference on a few units after fault events and bring the DC readings back to sensible figures.

If that doesn't sort it, pull up the VictronConnect history tab and screenshot your fault log before you do anything else — handy if you end up needing Victron warranty support.

Log in to join the discussion.

Log In to Reply