Quattro identifying as multi plus 2 cant install correct firmware

Had a similar head-scratcher on my narrowboat build last year — picked up a secondhand Quattro 5000 that the previous owner had clearly been "having a tinker" with, bless him.

The unit was convinced it was a MultiPlus 2, sitting there brazenly lying about its own identity like a politician at a press conference.

What actually sorted it for me was using VictronConnect rather than VE.Config to do the initial poke around, then being very deliberate about which firmware file I selected in VE Flash — the Quattro firmware files are prefixed differently and it's stupidly easy to grab the wrong one from the Victron Professional portal if you're not paying attention.

A few things worth checking:

• Make sure you're on the correct product page in VE Flash, not just trusting what the device reports itself as
• The hardware version sticker on the back of the unit should tell you what it actually is regardless of what the firmware says
• If it's genuinely bricked mid-flash, a MK3-USB interface and a patient afternoon usually wins

Also worth flagging — if you bought it from someone who "couldn't recover it," there's a non-zero chance the unit itself has knackered hardware rather than just confused firmware, so keep receipts and manage expectations accordingly.

Anyone else gone down this rabbit hole? Curious whether the newer VRM portal handles misidentified units any more gracefully these days or whether it's still a manual faff.

@FETFan oh this takes me back — had almost the exact same pantomime with my static caravan setup.

Picked up a secondhand Quattro 48/3000 that someone had clearly been poking around in with VE.Config. The unit had been given a custom product ID at some point and VictronConnect was absolutely baffled by it.

The fix that sorted mine was connecting via a MK3-USB interface and using VE.Flash directly rather than going through VictronConnect — it bypasses the product identity check entirely and just pushes the firmware regardless.

Word of warning though: make absolutely sure you've got the correct firmware file for your actual hardware revision before doing this. Victron's firmware repository lists them by product code.

Took me a wet Sunday afternoon and a strong brew to sort, but it's been rock solid ever since.

Decent thread to land on for your first visit — welcome to the forum.

Worth adding one thing nobody's mentioned yet: before you do anything with firmware on a misidentified Quattro, pull the product page on the VRM portal and note down the exact product ID it's currently broadcasting. Screenshot it. Had a unit on my boat that got halfway through a "corrective" flash and ended up in a worse identity crisis than it started with — took Victron Connect ages to sort remotely.

The product ID gives you a proper starting point rather than guessing which firmware stream it's been pushed onto previously.

@FETFan @MoreTeaVicar — did either of you check whether the previous owners had been through the Quattro or MultiPlus firmware trees? That's often where these things get genuinely tangled rather than just mislabelled.

Really resonates with this one — had a Quattro 24/5000 in the motorhome that had been similarly confused about its own identity after a botched VE.Configure session.

The thing that finally sorted it for me was connecting via VE.Bus System Configurator rather than going straight into VEFlash. The unit needs to properly declare itself on the VE.Bus before firmware will stick correctly.

Worth checking your MK3-USB interface is also up to date — I had a situation where the interface itself was running old firmware and was essentially feeding the Quattro duff information about what it was talking to.

@FETFan did the previous owner leave any config files on it? Sometimes you can glean exactly what someone did wrong from the .vsc file still sitting on the unit.

Good shout from @AngliaOffGrid on whatever point they were making (curious to read the full post).

One thing worth flagging from my static caravan experience: after you've sorted the identity crisis via VE.Configure and pushed the correct firmware through VictronConnect, do a full factory reset before reconfiguring. I made the mistake of just layering new settings over the confused state and ended up with phantom grid-code errors for weeks.

Also worth checking: Quattros have specific firmware branches depending on whether they're configured for ESS or standalone. A previous owner running ESS on a boat install might have pushed ESS-specific firmware that's genuinely incompatible with your intended setup.

Fronius had similar versioning headaches but Victron's at least well-documented — the CCGX or Cerbo logs usually tell you exactly which firmware branch the unit last accepted.