Pylontech & Victron Multiplus manuals contradict? Confused old guy

Funny timing on this thread — I've been pulling my hair out over exactly the same thing this week.

Setting up a Victron Multiplus-II paired with a Pylontech US3000C bank for my garden office build. The Pylontech documentation says to charge at no more than 0.5C, which for three units in parallel works out at around 74A. Fine. But then the Multiplus settings via VEConfigure seem to suggest different charge current limits, and various Victron DVCC guides online contradict the actual ESS Assistant settings I'm seeing.

Specifically:

• Does DVCC override whatever I set manually in VEConfigure, or do both limits apply?
• If Pylontech's BMS is communicating via CAN bus to the Cerbo GX, does the BMS effectively take the wheel and ignore my manual settings anyway?
• Which document actually takes precedence when they conflict?

I think the answer is that with a proper CAN bus connection the BMS tells the Multiplus exactly what it wants and everything else becomes secondary — but I've read enough forum posts now that I've confused myself completely.

Anyone running a similar Pylontech/Victron setup in the UK who can give me a plain-English explanation? Particularly interested whether anyone's had issues with the Pylontech warranty being affected by charge settings that drift outside their stated limits.

Would really help to hear from people who've actually got this running reliably rather than just theoretical answers from the manuals that seem to disagree with each other.

@DaiLewis69 classic case of two manuals written by people who've never met — Victron says one thing, Pylontech says another, and you're the one left holding the multimeter at midnight 🔧

@DaiLewis69 which specific values are conflicting? That would help narrow it down.

The usual culprit is charge voltage — Pylontech's own documentation for the US3000C specifies 51.8V upper limit, but Victron's Pylontech compatibility guide sometimes suggests slightly different figures depending on firmware revision.

If you're running the DVCC/CAN-bus integration (which you really should be with that pairing), the Pylontech BMS actually takes control and overrides manual settings anyway — so the manual conflict becomes largely academic.

Key questions:

• Are you connecting via CAN-bus or VE.Bus?
• What firmware is on the Multiplus-II?
• How many US3000C units in the bank?

Worth downloading Victron's dedicated Pylontech compatibility sheet separately from the main Multiplus manual — it's more current than what ships in the box.

@BlownFuse is right, we need specifics — but I'd bet it's the charge voltage upper limit causing grief.

In my shepherd's hut setup with a Victron/Pylontech stack, the answer that actually resolved it for me was: trust the Pylontech HVIL and let the BMS have final say, then set Victron conservatively below whatever the manual argument is about.

Also worth noting — if you're using DVCC in VenusOS, the Pylontech communicates directly via CAN bus and effectively tells the Multiplus-II what it wants anyway. Manual charge settings become largely irrelevant once that's working properly.

Download the Victron "Pylontech, BYD, Freedomwon" PDF from their website — it's the document that actually reconciles the two. Should've been in the box, frankly.

@DaiLewis69 worth noting that when Pylontech are paired with Victron via CAN-bus (using the correct cable and DVCC enabled in Venus OS), the battery essentially takes control of charge parameters automatically — the BMS broadcasts its own limits directly to the Multiplus-II. At that point, the manual conflicts become largely irrelevant because you're no longer setting voltages manually.

Check your VE.Configure settings: if you've got DVCC disabled and are trying to manually enter charge voltages, that's where the contradictions bite you.

The Victron-Pylontech integration guide covers the exact cable pinout needed. US3000C is well-supported.

Tiny house build here running the same pairing — once CAN-bus was properly configured, Venus OS just sorted itself out and the manual discrepancies stopped mattering entirely.