The configured loads are working OK up to hour 13.36, when are switched OFF.
Feed-In is active and exporting a lot of energy, SOC 100%, Opportunity Load is configured for 1000W.
Is there a way to monitor or log the conditions for ON or OFF ? Something like a text box saying “ON for Feedin excess”, Fronius is having this small feature for load management status.
Hi,
Please ad a bit of information about your system (inverter, acpv, dcpv, …)
Is it three phased, single phased, saldating or phase individual Multiphase Mode?
It is a Multiplus II GX with 3.80-33 beta, installed on phase 1 from a 3 phase system.
There is only AC PV on AC In, Fronius ECO 27 with ~32KWp.
Measurement is done by EM24 ethernet, set as grid.
All Opportunity Loads are set on phase 1.
Fiddling around, did set “Allow additional loads starting at a battery SOC of” to 80%, actual SOC being 83%, and relays started clicking.
There is something fishy when that parameter is set to 100% SOC.
A single NODE-Red rule implemented, to limit charging current at 20A from hour 8.00 - 14.00.
Any advice is greatly appreciated.
Hi,
send you a PN, if you can give me your system ID, I could review some things eventually.
Chance you had this load turned on manually and switched it to “Auto” at a later point?
OL is going into “sleep mode” when it detects no usable solar overhead. If you just flip a running consumer to “Auto” during that time - OL will not take control until it wakes up the next morning.
That is on our todo to be improved as this is not transparently visible.
Started to test a Pro 2PM on another system and noticed similar behavior.
Both systems have Pro 2 PM installed but no actual loads on relay and just realised that might be a problem for Opportunity loads.
Turning on the relay, system “expect” to see a load increase equivalent to declared number.
No loads connected means that energy keep feed-in and Opportunity loads keep the relay ON, this should go on as long as feed-in is happening.
But sometimes relay has been stuck overnight and this might be a completely different bug, not related to no-load test situation.
