[FR] P092_DLbus.ino: Support for TA Fristar3WP

[githubuser2050]

I'd like to use Plugin Heating - DL-Bus (Technische Alternative) (P092_DLbus.ino) to read and write values from/to my TA Fristar3WP

I'd like a hardware/device "Fristar3WP" to be added in the plugin, which can read and write values according to the TA Fristar3WP manual:

Read values:
Index: Messwert:
1 Warmwasser-Isttemperatur T ww [°C]
2 Kaltwassertemperatur TKW [°C]
3 Volumenstrom [l/h]
4 Primärtemperatur TPri [°C]
5 Zirkulationstemperatur [°C]
6 Solltemperatur [°C]
7 Pumpenleistung [%]
8 Ventilstellung [%]
9 Momentanleistung [kW]
10 Gesamtenergie [kWh]
11 Gesamtenergie [MWh]
12 Wasserzähler [m3]
13 Status (siehe „Status“ auf Seite 17)

Write values:
Index: Messwert:
1 Solltemperatur [°C]
2 Zwangsb. Zirku. [Ein/Aus]
3 Pausenzeit Zirku. [s]
4 Solltemp. Zirku. [°C]

Ideas for alternative solutions are welcome

[TD-er]

@uwekaditz Maybe something for you, since you wrote the original plugin if I'm not mistaken?

[uwekaditz]

I'll take a look to the manual.
Let's see if it can be integrated to the plug in.

[sharkcow]

I would also be very interested in communication with the Fristar3WP via ESPEasy.
If it helps: I have measurements of the signals on the bus and some crude python code that can talk to the device and read all parameters. I have not worked on writing yet.

[TD-er]

Well some code concepts/snippets are always useful to have, since we don't have the hardware ourselves.

[johnbaersdfsfo]

I would love to see this happen!

[sharkcow]

my findings were posted here:
https://www.mikrocontroller.net/topic/134862#7966452
If anything is unclear, just ask. I can also take measurements or test code on my hardware.

[tonhuisman]

The Fristar3_Kommunikation.pdf file (1 message up from the link in the previous comment) also seems quite helpful in implementing this protocol 💡

[githubuser2050]

The Fristar3 supports both DL bus and CORA-DL bus according to the manual. I guess DL bus is simpler and easier to implement, but I read that CORA-DL has some (performance?) advantages over DL (can request data with higher frequencies or with higher precision?). Anyone has more info?

Anyhow, would be great if Fristar3 is supported by this plugin - no matter which protocol, either CORA DL or DL bus.

[sharkcow]

Yes, but I'm not sure what the advantage of Cora DL exactly is. If you don't have multiple devices on the DL bus I doubt there's a difference in performance. The communication clock is 488Hz, I'm reading all 12 about every 5s since I don't have any other TA devices connected.

[TD-er]

Well the DL-bus is already implemented and known to work. (I don't have those devices, so I can't test myself)
So if there is no extremely clear advantage of another bus, then I suggest to keep it as close as possible to the existing implementation.

[uwekaditz]

I'm not so happy to integrate the Fristar3WP to the plug-in Heating - DL-Bus (Technische Alternative) (P092_DLbus.ino)
The operating principle of the devices programmed in the P092 differs completely from that of the Fristar3WP:

• All devices send data automatically, there is no need to request data as Fristar3WP requires, that means writing on the DL bus was never tested
• Only the first instance of P092 sniffs the real DL bus and after detecting the starting condition all data are read and stored in a device depending structure, all other instances just using the data from this structure

[TD-er]

@uwekaditz Another option can be to move the DL bus specific code to a helper class and then have a separate plugin for it.
If those devices differ more than a few extra registers, then it is a no-brainer to have different plugins for them.
However I really would like to have bus/interface specific code separate so we don't need to duplicate it.

Also after I have finished the network rewrite, one of the planned changes is to add an extra tab in the ESPEasy UI to define shared buses (like Modbus/1wire/SPI/I2C., etc) on that page so tasks using one of those can then select a predefined bus.

[githubuser2050]

It would be great if support for TA Fristar3 could be added to ESPEasy - may it be in the P092 plugin or in a separate one.
@uwekaditz: Would you implement TA Fristar3 support also in a separate plugin? I'm not an experience developer, but I can offer testing the code with a TA Fristar3.