Autor Thema: THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.  (Gelesen 39753 mal)

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #15 am: 06 Februar 2015, 21:03:52 »
I installed a internal temp sensor last week-end;  The NXP KTY81 component has a terrible off-set of -5k
I do not yet understand completely. Did you connect the sensor to X5 panel, pin 5 and 6, labeled as "Raumfühler" ?
If yes: the temperature of this sensor is shown as sGlobal.insideTemp in the data log.

The value sHC1.insideTempRC has nothing to do with this sensor. sHC1.insideTempRC is the value which is read from an external display. If you read out sHC1.insideTempRC values while not having an external display installed I don't believe that you get valid values.

edit:
I added a plot showing both values. The vertical difference is the offset of the sensor; it can be corrected using a userReading. The delay of the red curve is due to the fact that the external sensor ( sGlobal.insideTemp) is mounted inside a wall which causes delayed and equalized values.
« Letzte Änderung: 06 Februar 2015, 21:24:06 von willybauss »
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline immi

  • Developer
  • Sr. Member
  • ****
  • Beiträge: 792
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #16 am: 06 Februar 2015, 21:21:04 »
I do not yet understand completely. Did you connect the sensor to X5 panel, pin 5 and 6, labeled as "Raumfühler" ?
If yes: the temperature of this sensor is shown as sGlobal.insideTemp in the data log.
correct
Zitat
The value sHC1.insideTempRC has nothing to do with this sensor. sHC1.insideTempRC is the value which is read from an external display. If you read out sHC1.insideTempRC values while not having an external display installed I don't believe that you get valid values.
not true in my system
sHC1.insideTempRC = sGlobal.insideTemp  + p99RoomThermCorrection

This is not my problem. My problem why sGlobal.insideTemp (or its offset sHC1.insideTempRC) goes down each time the compressor goes on

immi
« Letzte Änderung: 06 Februar 2015, 21:23:22 von immi »

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #17 am: 06 Februar 2015, 21:34:59 »
ok, now I understand. Where is the sensor located? Close to a hose having flow temperature? You should retest while having both sensors ( brown and red curve) VERY close together.

Is the cable a twisted pair type, not routed in parallel to the compressor's power cable?
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #18 am: 06 Februar 2015, 21:43:06 »
Another topic:
Can anyone imagine the meaning of the x08 value (sHC1.x08) ? There is a FW bug inside the THZ which is obviously related to this value. The bug is, that sometimes the HC1 pump stays on, even after heating cycle has ended, see screen shot.

The endlessly working pump causes a very fast increase of integral value, causing the compressor to start up again very soon.
« Letzte Änderung: 06 Februar 2015, 21:45:07 von willybauss »
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline immi

  • Developer
  • Sr. Member
  • ****
  • Beiträge: 792
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #19 am: 06 Februar 2015, 21:53:51 »
>>You should retest while having both sensors ( brown and red curve) VERY close together.
not possible; the KTY81 is in the wall and the good one is outside..... no pipes near both.

Is the cable a twisted pair type, not routed in parallel to the compressor's power cable?
willy
I hope you are right with crosstalk, which could  cause sGlobal.insideTemp to go down each time the compressor runs.
I try to move the cable now. It is in the same hole as the power supply of the heatpump.

>>You should retest while having both sensors ( brown and red curve) VERY close together.
not possible; the KTY81 is in the wall and the good one is outside..... no pipes near both.
Without the compressor running, they show very similar values.

p.s. I will have a look to x08 as soon as I understand my issue.
you know only woman can multitask :)
immi

Offline houseowner123

  • Full Member
  • ***
  • Beiträge: 157
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #20 am: 07 Februar 2015, 00:28:15 »
Zitat
I try to move the cable now. It is in the same hole as the power supply of the heatpump.

I would think this could be the issue, the induction of the power cable could cause this. Try to move the sensor cable away from there. Just let it hang outside for test purposes.

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #21 am: 07 Februar 2015, 08:56:53 »
I would think this could be the issue, the induction of the power cable could cause this. Try to move the sensor cable away from there. Just let it hang outside for test purposes.
That's the reason why I asked for twisted pair cable. Mine lays in parallel to all the other THZ cables in a cable duct for >4 meters, but without any trouble.
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #22 am: 07 Februar 2015, 11:35:54 »
Hi,


here is the link to the new thread  THZ Tecalor (LWZ Stiebel Eltron) Wärmepumpe -Optimierung und Erfahrungsaustausch.

immi:
Please add the link to the initial contribution of this thread as well as to the last contribution in the initial thread.
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline houseowner123

  • Full Member
  • ***
  • Beiträge: 157
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #23 am: 07 Februar 2015, 11:38:15 »
attr Mythz event-min-interval s.*:4800
attr Mythz event-on-change-reading .*

does not work for me at all. I have zero recordings from the night! :(

Offline houseowner123

  • Full Member
  • ***
  • Beiträge: 157
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #24 am: 07 Februar 2015, 18:12:43 »
immi: regarding the heating curve I noted that the ordinate scale is quite large ranging from 10...50°C for HC temp. It is the mixture of flow and return and I think that max. should be 35°C, so that the curve is more noticeable. Do you think that is possible? I cannot change the settings myself for it.
Heating point is off the curve because the oven is on.

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #25 am: 07 Februar 2015, 22:00:10 »
@immi
regarding to your sHC1.insideTempRC topic: today I unplugged the external display for a few hours to watch how the values behave in this case. Unplugging (approx. 9:00 am) doesn't matter at all. But reconnect at 8:25pm shows a surprising behavior. The value dropped by 1.8K, which is almost exactly the same as the offest correction value of the external display (1.7k). Hopefully this can help you in any way to solve your issue.
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline peter456

  • Jr. Member
  • **
  • Beiträge: 96
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #26 am: 08 Februar 2015, 12:09:58 »
Hallo alle zusammen,

vielen Dank nochmals an alle Experten hier. Mein FHEM-Monitoring läuft mittlerweile super stabil und ich bekomme auf einer Seite den Überblick über alle wichtigen Werte (siehe Anhang).
Was mir noch fehlt ist die Änderung der Parameter meiner LWZ303i (Firmware 2.06) über FHEM. Wir waren z.B. Anfang des Jahres für eine Woche im Urlaub. Mein Ziel in so einem Zeitraum wäre z.B., dass ich den Sollwert der WW-Bereitung herunterstelle und am letzten Urlaubstag per Internet diesen Sollwert wieder zurückstelle. Meine Frage an Immi wäre, ob es möglich ist für die Firmware 2.06 wenigstens die Parameter "p01-p12" änderbar zu machen?

freundliche Grüße
Peter

Offline willybauss

  • Hero Member
  • *****
  • Beiträge: 1017
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #27 am: 08 Februar 2015, 12:18:55 »
today I came across an old posting of last year
Zitat
OpMode implemented readonly ("1" =>"Standby", "11" => "Automatic", "3" =>"DAYmode", "4" =>"SetBack", "5" =>"DHWmode", "14" =>"Manual", "0" =>"Emergency")
It looks like there's a bug in the implementation: FHEM always reports "setback" while in fact the THZ works in automatic mode.

@immi
Could you please have a look into the code?

Thanks
Willy
FHEM auf Raspberry Pi B und 2B; THZ (THZ-303SOL), CUL_HM, TCM-EnOcean, SamsungTV, JSONMETER, SYSMON, OBIS, STATISTICS, CO20, FHEM2FHEM

Offline andre.k

  • New Member
  • *
  • Beiträge: 39
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #28 am: 08 Februar 2015, 12:51:55 »
Hallo alle zusammen,

vielen Dank nochmals an alle Experten hier. Mein FHEM-Monitoring läuft mittlerweile super stabil und ich bekomme auf einer Seite den Überblick über alle wichtigen Werte (siehe Anhang).
Was mir noch fehlt ist die Änderung der Parameter meiner LWZ303i (Firmware 2.06) über FHEM. Wir waren z.B. Anfang des Jahres für eine Woche im Urlaub. Mein Ziel in so einem Zeitraum wäre z.B., dass ich den Sollwert der WW-Bereitung herunterstelle und am letzten Urlaubstag per Internet diesen Sollwert wieder zurückstelle. Meine Frage an Immi wäre, ob es möglich ist für die Firmware 2.06 wenigstens die Parameter "p01-p12" änderbar zu machen?

freundliche Grüße
Peter

Hi Peter,

I'm about to implement an update for the subroutine THZ_Set. There is a significant difference between the 2.x Firmware and the later versions. In version 2.x a single  parameter value has to be written in groups of parameters. For example if you want to change P01 you have to write all parameter from P01 to P12 to the THZ. All parameters from 01 to 12 will be written with the same command 0x17.
So I'm on the way.

@Immi: What do you think about using sliders and list boxes for validation of set values:
"p01RoomTempDay:slider,10,0.1,30,1"
or
"p07FanStageDay:0,1,2,3"

This could increase the usability for gui users a little bit.
Andre

Offline houseowner123

  • Full Member
  • ***
  • Beiträge: 157
Antw:THZ Tecalor (LWZ Stiebel Eltron) module support and code improvement.
« Antwort #29 am: 08 Februar 2015, 14:10:56 »
today I came across an old posting of last yearIt looks like there's a bug in the implementation: FHEM always reports "setback" while in fact the THZ works in automatic mode.

@immi
Could you please have a look into the code?

Thanks
Willy

I can confirm this! Seems like a bug.