Fronius Batterieladung per Loxone steuern?

[Triple-M]

Meine Batterie-Steuerung funktioniert wohl nicht mehr. Ich habe zwar den Router gewechselt und dann die IP-Adressen neu angepasst aber wenn ich z.B. ein Limit einstelle das die Batterie nicht entladen wird, wird dies ignoriert. Auch der Status verändert sich nicht mehr, woran kann das liegen?

Oder ist dass alles mit dem Routerwechsel nur Zufall und es wurde im letzten Firmware-Update des Wechselrichters was verändert?

[Tico]

Welche Firmware verwenden Sie? Überprüfen Sie die IP-Adresse des Wechselrichters unter 'Systeminformationen'. Ich bin auf v1.12.1-10. Es gibt eine spätere v1.16.6-1, aber ich aktualisiere nicht.

[Triple-M]

Die IP-Adresse passt, Werte werden ja gesendet. Ich habe die v1.16.1.1 drauf. Kann der Routerwechsel damit zutun haben? Die IP-Adressen habe ich aber aktualisiert und es wird auch kein Fehler angezeigt in der Config.

[Tico]

I can only suggest a reboot of the Inverter and double-check that 'Inverter Control via Modbus' is checked. Controlling priorities should display -

1. Controlling via Modbus
2. Dynamic power reduction
3. IO control

[Triple-M]

Alles klar danke, Fehler gefunden. Ich hatte „Steuerung einschränken“ aktiviert und hierbei natürlich die IP-Adresse vergessen zu aktualisieren.

[19domi89]

Today i updated my symo hybrid to 1.20.6-1, now its not possible to set the battery satus with loxone again?
Anyone has a solution?

[Tico]

Try rebooting the inverter and check the IP address assigned. Is it the same as previously set?

[19domi89]

Yes, everything works. A also can see all the data from my fronius. But not to set the min Battery staus

[Tico]

Do you have the ‘Emergency power Operating mode’ set to Automatic?

Paragraph 3 in the link provides further information -

https://loxwiki.atlassian.net/wiki/spaces/LOXEN/pages/1316061809/Fronius+Hybrid+with+Modbus+TCP

Note that the inverter settings webpage will also be considered for Battery Minimum Reserve. Whichever interface (Modbus or Webpage) has the higher setting, that will take priority.

[lox]

Hallo,
ich habe die Steuerung der maximalen Lade/Entladeleistung per Loxone über den Modbus hinbekommen.
Ich würde gerne auch den min SOC des BYD Akkus steuern. Allerdings funktioniert es bei mir nicht so wie hier beschrieben. Wenn ich z.B. 30% einstelle, gibt Loxone den Wert 30000 an die Modbusadresse 40320 aus. Ist das aber die richtige Adresse? Bei mir wird der Akku weiter unter den gesetzten Grenzwert entladen.
Modbus ist für mich komplettes Neuland und leider funktionieren hier die Links zu LoxWiki nicht mehr. Villeicht kann mir jemand helfen?

[Tico]

Here is a link to the updated loxwiki page -

https://loxwiki.atlassian.net/wiki/spaces/LOXEN/pages/1316061809/Fronius+Hybrid+with+Modbus+TCP

30% should output 3000 (ie. two extra zero's). The value -2 should be placed on I2 of the formula block.

I1/10^I2

Address 40320 is correct (at least for the Fronius Solar Battery). I think people with BYD batteries have had success using that address.

[lox]

Hi, Tico I have the Fronius primo gen24 and a 13kwh BYD hvm battery. I will check the outputvalue this evening. Probably i have the right output value, but it takes no effect. I don't have the tecnician password for the fronius. But the modbus acess is activated.
To set the min. Soc i have to turn on the manual mode (storCtl mode 3)? I did activate this manual mode and i can set the max. .charge or discharge value. But the min. Soc value takes no effect.
If i enter in the BYD Be connect plus program the battery is set to off grid mode, but this probably has noneffect!?
The fronius converter has still not activated the emergency power functionallity, because this installation is still not done.
My idea is to set the min Soc to 30% because in my place now for about 1 month there is no sun and the production will be verry low. So i think it is better to have a higher soc.
The load is verry low, between 100 and 700W. So during the day i may reach only 2kwh. The battery is in the celler and at the momend it has 8degrees celsius and will go down to 2degrees. So would it be better to bring the battery to 30%soc and turn it completly off?

[Tico]

In the inverter settings, you will have a choice in SunSpec Model Type between (int + SF) or (Float).

The Gen24 has Modbus registers different to those published for the Symo Hybrid -

MinRsvPct is address 40360 in Lox Config for the 'Float' choice.
MinRsvPct is address 40350 in Lox Config for the 'int + SF' choice.

I use the Float option as preference to avoid the Scale Factor (SF). Notwithstanding, you may still need Scale Factor for some metrics when Float is used.

[lox]

Thank you so much Tico,
the 40350 adress worked fine. Now i can set the SCO of the battery from Loxone and when the soc is reached, the battery also goes in energy save mode.
In future i will try to make an automatic charge management with Loxone.

[Tico]

The recommended long-term storage value for my Fronius Solar Battery battery (LiFePO₄) is 53%. The BYD battery is the same LFP chemistry.

Because the voltage curve of LFP batteries is so flat, they pick the mid-point to avoid either deep discharge or excess voltage. Given your very cold storage temperatures and the fact there is minimal use of the battery, I would be inclined to increase MinRsvPct to 53%. If the battery is turned completely off at those temperatures, it is better protected from deep discharge at 53%.

If the battery is maintained simply in Energy-Saving Mode, there are monitoring protections to avoid deep discharge.

[lox]

Hello Tico,
With your help, BYD Battery has charged the last few days and discharged overnight to the set SOC. But last night I saw that after holding the min SOC of 30% for a while, it then started to discharge further. I then changed the SOC value in Loxone several times and also changed the max. charging power / discharging power, but the inverter no longer reacts to the Loxone inputs. I then also restarted Loxone, switched the inverter and battery off and on again. I can see the data from the PV system in Solarweb and also in Loxone, but there is no reaction to the Mod Bus entries made by Loxone. I have the StorCtl mod displayed in the visualization and it is set to 3, so Modbus inputs should be possible.
Could it be that the Modbus activation on the Fronius inverter was only temporary? Unfortunately, I do not have access to a technician to check the data

[Tico]

Modbus activation is permanent, so I don't think it's possible to revert unless done actively on the inverter web-page. Switch-on order is important so that the inverter is aware of the existence of the battery. I follow this order from a completely 'black' shutdown system -

1. Battery to ON, then wait 60 seconds,
2. Inverter to ON, then wait 2 minutes,
3. Loxone to ON.

How you get to a 'black' shutdown system is not so important, only that you never switch off DC isolators if current is flowing. The rule is to turn off the Inverter AC isolator first (that will de-power any current flow), then DC isolators. I remember it by the neumonic ACϟDC, a famous Australian rock band...

As an aside, StorCtl being set to 3 is only relevant for the battery Charge/Discharge control. It's not specific to Modbus control. Have a re-read of paragraph 2.a. in the link -

https://loxwiki.atlassian.net/wiki/spaces/LOXEN/pages/1316061809/Fronius+Hybrid+with+Modbus+TCP#FroniusHybridwithModbusTCP-2.Controlthebatterychargerateanddischargerate.

With StorCtl set at 0, you're allowing the inverter to make all the logic decisions. With StorCtl set at 1,2 or 3 you take applicable control over Charge, Discharge or both.

The only other aspect that has caused Modbus issues is Loxone upgrades.... I assume you haven't made a change recently?

[lox]

I dit some changes in Loxone config, but nothing about photovoltaik. I also did a shutdown of the inverter and the battery. Reading out the set min soc was about 5%
It did not take the min soc given by loxone.
Now i made a black shutdown as you described, taking down also the grid power and now it works again.
Thank you so much for your help!

[lox]

Hello,
the sun is back on my roof and is producing a lot of electricity. Unfortunately, the power grid in my region is weak and my neighbor runs a large PV system. Therefore, it will soon happen again that the AC grid voltage will rise above the limit of 253V around midday and then the inverter will switch off due to the long-term grid voltage limit.
That's why I want to build a controller with Loxone that I can switch on via the app and that then controls the maximum charging power of my BYD storage so that the maximum mains voltage is not exceeded.
I had imagined it like this:
In the morning i will not charge my battery. At about 10o clock i give a starting value for the maximum charging power of e.g. 3000W
Loxone asks every 10 seconds. the current AC voltage via modbus. If AC >252V, the maximum charging power of the BYD storage should be increased by 200W
If AC < 249V, the maximum charging power should be reduced by 200W.
Is there a similar example I could use?
Unfortunately, I have no experience with Modbus and the status blocks in Loxone.

[Tico]

You should probably be aware that your desired control logic is very complex and can only be designed and tuned by yourself. It will be a bespoke solution unique to your circumstances.
I would recommend that you 'get your hands dirty' by experimenting with Status blocks and Controllers. Also re-read the attached link, paragraph 4. Automating Battery Charge Control.

https://loxwiki.atlassian.net/wiki/spaces/LOXEN/pages/1316061809/Fronius+Hybrid+with+Modbus+TCP#FroniusHybridwithModbusTCP-4.AutomatingBatteryChargeControl

There are differences between the Fronius Hybrid and Primo Gen24 in Modbus addressing -

https://www.loxforum.com/forum/faqs-tutorials-howto-s-aa/132379-fronius-hybrid-with-modbus-tcp/page7#post346804

The attached picture is not intended to provide a complete solution. It provides one way (of many options) to have a stepped output dependent on an input. Another option is to use the PI-Controller or PID-Controller. These could provide proportional increases (or decreases) in output dependent on the degree of voltage deviation.

In the attached picture, the Scaler output will increase in 200W increments if the voltage is >252V. This value is added to the desired starting value.
When the voltage is <249V, the Scaler output will decrease in 200W increments and will go into negative values. This is subtracted from the desired starting value. The steady-state charging output would eventually reduce to 0W if voltage remains <249V. Conversely, the steady-state charging output would eventually increase to 6000W if voltage remains >252V. You should experiment using an artificial voltage input (Virtual Input) until you design and test your logic flow.

Note the use of inverted inputs on some blocks (red text).

[lox]

Hello Tico,
last week i found the time to read through the linked pages and also to understand your example. First I took a quick look at the PID Controller, but your example with the stepper is the easiest way to solve my problem. I only had to adapt your example a little and now i have a good control system to avoid the overvoltage around noon when grid feeding and the associated restarts of the inverter.
There was just a small problem with querying the current voltage via Modbus. When the inverter is in standby, there are no voltage readings. That's why I then queried the voltage on the smart meter. But it was sometimes up to 4V lower than on the inverter. I don't know why. Now I use the voltage at the inverter directly again for the regulation. If the inverter goes into standby during the night and I don't get any voltage values, it doesn't matter either, since the control is then not needed either.
I want to thank you for your example. Without your help I would not have been able to get this control, which is very useful for me.