Fronius Hybrid with Modbus TCP

[Tico]

LoxMunich - You're welcome.

1. Ignore the missing numbers. You haven't missed anything. When creating the wiki, I excluded some of my own data fields that filled 07 to 10 that were not relevent for the .loxone file.

2. Look at the Fronius Smart Meter sensor 'W' = Flow to/from grid - kW (Positive=Import, Negative=Export). Run this sensor into a State Block value AI1. Run the Battery State of Charge 'ChaState' into the same State Block AI2.

Set up the argument when AI1 ≤ (minimum charging value) and AI2 ≥ 98, then output value 1. Use the value 1 for whatever switching mechanism you need. The battery varies between 98-100% in the fully charged state. You could make AI2 = 100, but car charging would then stop unnecessarily.

3. Same logic for the Ohmpilot. You need to decide which device has the 1st priority - car charging or Ohmpilot. Then if one device is charging/heating and there's still grid outflow, start the other.

[LoxMunich]

Thanks, I will try this the next days.

One other question: the sensor values in the .Loxone file seem to be different to the sensor values in the .XML files.
E.G.

left the imported .xml / right the .Loxone sample file


What is the latest version / which should I use?

[Tico]

Thanks for pointing that out. The .Loxone file is the most recently updated - use it.

I think I'll delete the .xml files in the wiki. I seem to remember that they were required in previous Config versions when loading up the .Loxone file. Perhaps someone can confirm whether the .Loxone file brings all sensors/actuators across without the underlying xml data? I can't test that on my existing installation.

https://www.loxwiki.eu/display/LOXEN...ith+Modbus+TCP

[LoxMunich]

You have to import the .xml files

Only the memory flag / Merker are added automatically if you just "select all" elements from the .Loxone page and copy & paste it into a new project page.
Neither the sensors nor the actors within the Modbusserver and even not the virtual inputs / outputs are there

[Tico]

That's jogged my memory now when copying into a new project page. I'll get around to updating the xml files in due course.

[renezs]

Hello,

does anyone have the modbus register data for the new smart meter TS65a-3. It seems to bee different with the template from here. The communication works but there are or not the right value.

[Tico]

What type of inverter do you have and what is the firmware version? Have you checked that your inverter is updated to the latest firmware?

[renezs]

I have the Symo Gen24 Plus 8.0 and the firmware 1.9.7-0. This should be the actual

[Tico]

Ok, you might need to contact Fronius direct. As the first user here of the Gen24, congrats! It will be interesting to find out how much more responsive it is than the Hybrid.

I found the following details in the TS 65A-3 instruction manual regarding firmware. Not much help unfortunately.

[renezs]

Thanks,

this is what i have find too :-).
I have sent the questions to fronius. Let's see what's the answer.

[Tico]

One difference I did read with the new smart meter is the Modbus device address -

Fronius Smart Meter 63A-3 has factory value 240.
Fronius Smart Meter TS 65A-3 has factory value 1.

[renezs]

at time i have some values from the inverter. But maybe not the right.
The modbus device adress for the smart meter youn can choose over the webpage of the inverter. The preset her was 200.

[renezs]

i have one other problem
on Pp i have connected my actual production (AC_Power) but on AQp is notting shown, also not on the visualisation.

Hi there

I have a system with 2 pcs. Sym Gen24, each with its own Byd battery pack, and 1 pc. Symo 20. We have just started the system and are going to connect it to Loxone. We have some challenges with getting the right data from both inverter and Smartmeter, I have been on fronius website to find the modbus tables but without success. Have you had any challenges with your connection to Gen24 and the batteries.

[Tico]

For info, the Vendor Operating Codes are as follows (from a question raised earlier in the thread) -



The State Value is set to 0 for regularly occuring (normal operating) status. The Filtered Error codes are passed onto the AIe input of the Loxone Energy Monitor.

[Gast]

Wie kann ich über Modbus auf die Zielgröße am Zählpunkt zugreifen?
Dazu finde ich keinen Register.

_____________________________

[Tico]

Google Translate says -

Gast - How can I access the target size at the metering point via Modbus?

I can't find a register for that.

I assume you mean the minimum battery reserve (paragraph 3 in the index)?

https://www.loxwiki.eu/display/LOXEN...batteryreserve.

[Gast]

No, I mean the target value at the metering point.
Thanks