New DAH Solar 48V 5kWh LFP battery with Pace BMS shows up on MP2 as "LG resu battery on CAN-bus"

Interesting one this — picked up a DAH Solar 48V 5kWh pack with the Pace BMS a few months back for the garden office setup, and mine does exactly the same thing on my Multiplus-II. Shows up as "LG Resu battery on CAN-bus" which I thought was a misconfig on my end at first.

Spent a good while going through VEConfigure and checking the DVCC settings thinking I'd cocked something up, but honestly? Everything just... works. SOC reads accurately, charge/discharge rates are being respected, and the Victron portal data looks clean. No alarms, no funny behaviour overnight.

My theory is the Pace BMS is mimicking an LG Resu profile over CAN because it's one of the pre-baked protocols they've loaded in — probably the closest match to how they've configured the comms. A bit cheeky but pragmatic if it works.

That said, I'm slightly uneasy about it long-term. Has anyone done a proper teardown or comms log on the Pace BMS to confirm what it's actually broadcasting? I'd love to know if all the protection parameters (high temp cutoff, cell-level balancing comms etc.) are genuinely passing through or if the Victron is just seeing a partial dataset and filling in the blanks.

Also curious — is anyone running this combo with a Cerbo GX rather than just direct VE.Can to the MP2? Does it show the same misidentified battery label in the device list?

Not knocking the battery for the price point — Fogstar and the like are still pricier per kWh — but proper documentation would go a long way with these imported units.

Interesting — does the DVCC still behave properly even with the misidentification? On my shepherd's hut setup I've been wary of anything that doesn't handshake cleanly with the MP2, especially around charge voltage limits being respected.

Wondering if the Pace BMS is just broadcasting on a CAN profile that Victron maps to the LG RESU entry in its lookup table — a known brand ID mismatch rather than anything functionally wrong?

@LisaHunt88 are your charge/discharge parameters actually correct in VRM, or is it pulling LG RESU defaults? That'd be the real tell. If the BMS is sending the right CVL and CCL values regardless of how it identifies itself, it might be a cosmetic issue only — but I'd want confirmation before trusting it long-term on a critical setup.

@SolarDoug — yes, DVCC behaves absolutely fine in my experience. The "LG RESU" label is purely cosmetic; what matters is whether the Pace BMS is correctly negotiating charge parameters over CAN-bus, and it does. You can verify this in the VRM portal or via dbus-spy on the Venus device — check that MaxChargeCurrent, MaxDischargeCurrent, and MaxChargeVoltage are being populated correctly from the BMS rather than falling back to your DVCC fixed values.

On my narrowboat setup with a similar Pace-based pack, I confirmed the BMS was pushing ~52.4V charge voltage and sensible current limits — exactly what I'd configured on the battery side. The Multiplus-II was honouring those figures perfectly despite the peculiar label.

The misidentification seems to stem from Pace reusing an LG RESU CAN profile. Functionally harmless, but worth documenting for anyone else who stumbles across it.

@DevonDweller good to know it's just a label mixup — my Fogstar lithium once convinced my Victron it was having an existential crisis too, so cosmetic misidentification is practically a rite of passage with CAN-bus kit.

@Smithy that existential crisis comment made me spit my tea out 😄

Had almost the same panic moment with my cabin setup when I first saw it. Spent a good hour convinced something was fundamentally broken before I started digging into why it was happening. Turns out Pace BMS uses a CAN protocol that closely mirrors what LG RESU units broadcast — so the MP2 just pattern-matches it and slaps that label on. It's essentially the Victron firmware making its best guess.

Worth checking your actual charge/discharge limits are being respected though — pull up the VRM portal and cross-reference what the BMS is actually reporting versus what the Multiplus thinks it's working with. Mine matched up perfectly, but it's a five-minute sanity check that's well worth doing when you're first commissioning.

@OffGridJess glad it's not just me who had that "wait, what's happening" moment staring at the screen!

Quick question for the thread — when yours shows up as "LG RESU" does it still correctly report the actual capacity figures? Mine is showing the right SOC percentages and charge/discharge limits seem sensible, but I'm slightly uneasy not knowing whether Victron is applying LG-specific charge curves under the hood rather than treating it as a generic LFP.

Running this on a boat as emergency backup so I'd rather not discover the BMS is being sent daft charge parameters after the fact. Has anyone actually logged the CVL and CCL values coming through on the CAN-bus to verify they match what the Pace BMS should be sending? Wondering if VictronConnect or Venus OS shows enough detail to confirm.