Hello,
For me ESS setup “Individual phase regulation” doesn’t work at all.
All the time ESS count all phases together. It’s BUG, please can you solve ?
Fed-in is disabled, Individual phase regulation, One phase system on the L1.
I have never encountered that. Does not mean it can’t be a bug…but we have systems like this and there is usually a problem with settings or hardware if ESS does not work.
This to me seems like a 1 phase-only system (only one Victron inverter)? Critical loads usually displays all 3 phases unless you have 1 phase system (physically / configuration-wise).
Such a system won’t be able to do what you request even though you would this option in Cerbo GX.
It’s a bug. Local supplier confirmed it. When there isn’t any load on the L2 and L3, ESS works as expected.
It’s one phase system, physical and also configuration. Also checked by local supplier.
Ok, I see.
I suggest you submit this bug in a new thread if you think (or have it confirmed) it is a bug.
I also think it is unrelated to this topic and most likely has nothing to do with ESS phase compensation but metering and data manipulation. Phase compensation between phases can’t happen in 1-phase systems. ESS is very broad term.
I would also check your Carlo Gavazzi meter via RS-485 connection, if type B metering is selected and I would flash its firmware.
I have exactly the same system with 1 phase Fronius with 3.52 Cerbo GX and FW 556 Multiplus 5000 inverter and everything works correctly. The only difference I see is that I am using ET340 to meter only L1 phase (grid and Fronius). So unlike you, I am independent of dbus-fronius implementation and it’s power throttling feature, which of course is neccessary for disabling or limiting grid feed-in.
Anyhow, submit a new thread and Victron staff will investigate it if it is an unknown bug or confirm a known bug (and maybe you will also get some timeline if you are lucky). But you can expect it at the end of the year. This topic is opened since February and I am hoping it will be fixed in 3.60 which should roll out soon, it is release candidate at the moment I think.
Sorry to butt in here, but I see an opportunity to present some additional documentation I have been working on;
While we wait for the original bug to be fixed,
If you could give it a read and provide any feedback I would appreciate it.