Fronius Flickering on AC out - reactive power settings?

Hi Dan

Apologies, i have no experience controlling Fronius via node red or any other device, I only use the Cerbo inbuilt control and it can control the feedout and charging. My only aim with this firmware was to end the irritating flicker, and it did (I assume you are using Victron?)

You can search the forums, I have seen a number of posts where people discuss controlling the export (watts) with the Cerbo. (Grid setpoint: the value can be -ve (export) or +ve (import)) This might be a better approach, otherwise you just land up fighting the cerbo that is also giving Fronius control parameters and clashing with what you are asking it to do. Search the forums for “controlling grid setpoint”. Key is you will put the cerbo Mode into “external control”, and do everything yourself in Node Red. You can run Node Red on the cerbo

Hope that helps

Appreciate the help.
The only reason I’m trying to limit output with HA is the Primo keeps throwing a 435 error when it starts to produce more power than I’m using. Could be a fault with the Primo.. I also run VenusOS on a Rpi4.
I need to try and find the register list for the Primo, as I think I’ve accidently made a change I now can’t find. Primo only outputing ~ 50%, ramps up on a reset, then throttles back within a couple of seconds..

Noticed my AC voltage swings from 210-250 (probably wider, but too brief for me to see). Is this normal when coupling a grid tie inverter over a victron?

Possibly if it is intermittent then it is LOM related.

It shows either a weak grid or high resistance connection.

1 Like

There is roughly a 25m run of 2.5mm back to the Victron.. with breakers and a earth leakage in the run… I could run a straighter 2.5mm run direct from Primo to Victron I guess.. just as a test?

It is an offgrid system with ~15kWatt of Lifepo4’s on the Multi

Off grid. Ok. So this is on the output?

The inverter should be outputting 230v. Unless you programmed it otherwise.

This storage amount means not much what is athe DCL and CCL of the battery bank as a whole.

1 Like

What is the primo (size) you are using. 2.5mm2 cable would be good for maybe 2kw.

Another thing- when you see the voltage swing: is that at victron or fronius side? If at victron, you might have full battery and victron has no where to ‘put’ the energy. If you don’t have network connection between Fronius and cerbo, victron only has frequency shift available to throttle the fronius, this takes time

Also like LX said, say what is the vitron you are using (eg 5000/70, etc), battery AH and voltage nominal. Do you have a cerbo (or GX)

On the output, yup.

Stable 230v output, until Primo output exceeds system load. Then the V starts to swing. Victron is set to pump up to 1500Watts in Battery bank. But with only ~100watts or so above load, voltage swings build up. bulk light comes on, but typically doesn’t stay on long.
DCL CCL , Battery bank can delivery and absorb well over what is causing dramas :frowning:

Ok:

  • size of mp—2?
  • Size of fronius?
  • Wp of solar panels?
  • Do you have cerbo ( or GX)?
1 Like

The frequency should shift. Is it doing that?

1 Like

3000mp (EasySolar)
Primo 3kw
~1000watts of panels
GX s VenusOS on rPi

frequency shifting only flickers from 49.9-50.1. Although bulk light comes on, and batteries can take a lot more power than what it takes to start going wonky..

Ok. Your 2.5mm2 is too small for 3kw, but if you only have 1kw panels it will technically work.

Have you enabled ESS on the MP2? This is essential if you have any ac solar connected, even if you are not connected to grid

Yes, ESS - PV inverter support. Setting are all correct y default, but I checked them, several times.

Found this

Scroll down to error 435

Doesn’t sound good….

Was hoping error was being caused by the voltage swings I notice, and not the other way around …

HUH. This morning, the mischievous gremlin left the system.. Its just working!!
Unsure what remedied the situation though :P. Thanks for the support guys :slight_smile:

So I found something interesting! If I set the soft limit say 50 watts above the power being created by the primo. Both the flicker dissappears and so does the 435 error! Now I’ll just need to work out an automation to do this and, problem solved!