Really interesting territory here — been thinking about similar logic challenges with my own Victron setup, albeit at a much smaller scale.
The core question of how the MultiPlus-II arbitrates between Fronius AC-coupled generation, battery state, and a generator ATS is genuinely complex once you push toward commercial-scale export limits. Victron's ESS assistant handles a lot of this elegantly, but the 30 kW export cap is where things get spicy — particularly around the frequency-shift curtailment signalling to the Fronius units. If the Pylontech bank hits high SOC and the grid can't absorb fast enough, you need the Fronius to back off precisely and quickly.
A few things I'd be probing in your position:
- Generator ATS timing — does it interfere with the Cerbo's grid-loss detection window? False transfers are a real headache.
- Export limiting via the ET340 or similar grid meter — are you running a dedicated meter per phase, or relying on the Fronius's own reporting?
- Pylontech DVCC settings — at that battery bank size, charge current limits need careful coordination with what the Fronius is pushing in.
In the UK context, G98/G99 compliance adds another layer — your DNO will want visibility of that export limiting behaviour, and demonstrating it under load is worth documenting thoroughly before energisation.
Curious whether anyone here has run a Fronius Symo at this sort of scale alongside a MultiPlus-II stack — particularly around the PowerControl interaction when the generator cuts in. Would love to hear real-world experiences.