DHW Setpoint not updated in PS=1 String

This Forum is about the Opentherm gateway (OTG) from Schelte

Moderator: hvxl

DHW Setpoint not updated in PS=1 String

Postby jake3317 » Mon Jan 02, 2017 2:20 pm

Boiler: Remeha Quinta 28C
Thermostat: iSense (v19. external input allowed)

With a manual of Domoticz command SW=62, I am able to change the Domestic Hot Water Setpoint to 62 degrees. This is in OTMonitor visible in both the 'Summary' and 'Status page'. However, in the PS=1 string, and therefore also in Domoticz, I still see the old setpoint, as set by the iSense: 59'C. The iSense itself is also still at 59. Please see the piece of the OT messages at the point where I did the manual / Domoticz override:
Code: Select all
[b]13:14:05.441816  Command (via relay server, from 127.0.0.1:48214): SW=62.0
13:14:05.473613  SW: 62.00[/b]
13:14:05.503507  Command (via relay server, from 127.0.0.1:48214): PR=G
13:14:05.506578  Command (via relay server, from 127.0.0.1:48214): PR=I
13:14:05.510997  Command (via relay server, from 127.0.0.1:48214): PR=O
13:14:05.519177  Command (via relay server, from 127.0.0.1:48214): PS=1
13:14:05.545469  PR: G=00
13:14:05.572440  PR: I=11
13:14:05.595323  PR: O=N
13:14:05.621135  PS: 1
13:14:05.723893  00000000/00000000,6.90,00000001/00000001,100.00,0/0,17.50,0.00,0.00,18.33,22.00,0.00,3.80,21.00,75/20,45/0,[b]59.00[/b],0.00,23970,0,0,12150,30230,4482,1057,4629
13:14:05.734354  Command (via relay server, from 127.0.0.1:48214): PS=0
13:14:05.758500  PS: 0
13:14:05.834997  BC0000000  Read-Ack    Status: 00000000 00000000
13:14:06.662679  T90010700  Write-Data  Control setpoint: 7.00
13:14:06.841803  B50010700  Write-Ack   Control setpoint: 7.00
13:14:07.664694  T00110000  Read-Data   Relative modulation level: 0.00
13:14:07.844461  BC0110000  Read-Ack    Relative modulation level: 0.00
13:14:08.669331  T80190000  Read-Data   Boiler water temperature: 0.00
13:14:08.850636  BC0191600  Read-Ack    Boiler water temperature: 22.00
13:14:09.675638  T90101180  Write-Data  Room setpoint: 17.50
13:14:09.856790  B50101180  Write-Ack   Room setpoint: 17.50
13:14:10.680807  T00000000  Read-Data   Status: 00000000 00000000
13:14:10.863018  BC0000000  Read-Ack    Status: 00000000 00000000
13:14:11.690923  T90010700  Write-Data  Control setpoint: 7.00
13:14:11.867882  B50010700  Write-Ack   Control setpoint: 7.00
13:14:12.785370  T00110000  Read-Data   Relative modulation level: 0.00
13:14:12.877853  BC0110000  Read-Ack    Relative modulation level: 0.00
13:14:13.857413  T80190000  Read-Data   Boiler water temperature: 0.00
13:14:14.046559  BC0191600  Read-Ack    Boiler water temperature: 22.00
13:14:14.705819  T1018124F  Write-Data  Room temperature: 18.31
13:14:14.886787  BD018124F  Write-Ack   Room temperature: 18.31
13:14:15.709942  T00000000  Read-Data   Status: 00000000 00000000
13:14:15.890537  BC0000000  Read-Ack    Status: 00000000 00000000
13:14:16.729307  T90010700  Write-Data  Control setpoint: 7.00
13:14:16.896298  B50010700  Write-Ack   Control setpoint: 7.00
13:14:17.721603  T00110000  Read-Data   Relative modulation level: 0.00
13:14:17.902582  BC0110000  Read-Ack    Relative modulation level: 0.00
13:14:18.727586  T80190000  Read-Data   Boiler water temperature: 0.00
13:14:18.907351  BC0191600  Read-Ack    Boiler water temperature: 22.00
13:14:19.732587  T00090000  Read-Data   Remote override room setpoint: 0.00
13:14:19.744745  R90383E00  Write-Data  DHW setpoint: 62.00
13:14:19.942502  B50383E00  Write-Ack   DHW setpoint: 62.00
13:14:19.953080  AC0090000  Read-Ack    Remote override room setpoint: 0.00
13:14:19.981372  Command (via relay server, from 127.0.0.1:48214): OT=3.8
13:14:20.009733  OT: 3.80
13:14:20.019365  Command (via relay server, from 127.0.0.1:48214): SC=13:14/1
13:14:20.022057  Command (via relay server, from 127.0.0.1:48214): PR=G
13:14:20.024761  Command (via relay server, from 127.0.0.1:48214): PR=I
13:14:20.027159  Command (via relay server, from 127.0.0.1:48214): PR=O
13:14:20.029996  Command (via relay server, from 127.0.0.1:48214): PS=1
13:14:20.053257  SC: 13:14/1
13:14:20.058061  PR: G=00
13:14:20.067003  PR: I=11
13:14:20.076638  PR: O=N
13:14:20.093104  PS: 1
13:14:20.252394  00000000/00000000,7.00,00000001/00000001,100.00,0/0,17.50,0.00,0.00,18.31,22.00,0.00,3.80,21.00,75/20,45/0,[b]59.00[/b],0.00,23970,0,0,12150,30230,4482,1057,4629

It looks like the PS=1 string of data is not updated with the new setpoint.
Is it normal that the iSense is not updated with the new DHW Setpoint? It does react well on changing the Thermostat Setpoint.
jake3317
Starting Member
Starting Member
 
Posts: 16
Joined: April 2016

Re: DHW Setpoint not updated in PS=1 String

Postby hvxl » Sat Jan 07, 2017 10:55 am

Correct. The PS=1 report contains the values from the Write-Data messages received from the thermostat or Read-Ack messages received from the boiler. If your iSense would ever issue a Read-Data for MsgID 56, you would get the new setpoint as returned by the boiler. But if the thermostat only ever sends Write-Data messages, then that's the value you will see in the PS=1 report and the iSense will not learn about the new DHW setpoint.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1035
Joined: June 2010

Re: DHW Setpoint not updated in PS=1 String

Postby jake3317 » Thu Jan 12, 2017 10:30 pm

hvxl wrote:Correct. The PS=1 report contains the values from the Write-Data messages received from the thermostat or Read-Ack messages received from the boiler. If your iSense would ever issue a Read-Data for MsgID 56, you would get the new setpoint as returned by the boiler. But if the thermostat only ever sends Write-Data messages, then that's the value you will see in the PS=1 report and the iSense will not learn about the new DHW setpoint.

Is it possible to manually force a Read-Data for MsgID 56? The iSense might not request it, but in PS=0 mode the summary page shows now for days already the 62'C with 274 updates, so no other temperature (59'C) has been reported back. I wonder what can be done to trigger a change in the PS=1 report. The PS=1 report now still reports a value of 59'C for MsgID=56.
As shown in the log, both a Write Data and a Write Acknowledge are there for the 62'C. Is it correct, that if the thermostat would send a Write Data of 59'C, it would override the 62'C and would show it in the summary page as well? That last part doesn't happen, so I am lost... is the actual setpoint now 59 or 62'C?

For me it is OK if the iSense is not displaying the correct setpoint because of the suggested 'not reading', because it isn't a parameter that I would check out on the thermostat anyway. As long as the correct setpoint value is in the PS=1 report, I can control MsgID 56 with Domoticz.
jake3317
Starting Member
Starting Member
 
Posts: 16
Joined: April 2016

Re: DHW Setpoint not updated in PS=1 String

Postby hvxl » Fri Jan 13, 2017 10:33 pm

You have told the gateway to set the DHW temperature to 62. It will remember that until you tell it otherwise. So every time the thermostat sends a Write Data for 59, the gateway changes it to 62 before sending it to the boiler. This means the actual setpoint is 62 degrees.

If you issue an AA=56 command, the gateway will substitute a command from the thermostat that it knows the boiler doesn't support with a request for MsgID 56. You only have to do the AA command once for the gateway to request the information on a regular basis.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1035
Joined: June 2010

Re: DHW Setpoint not updated in PS=1 String

Postby jake3317 » Sat Jan 14, 2017 1:48 am

hvxl wrote:You have told the gateway to set the DHW temperature to 62. It will remember that until you tell it otherwise. So every time the thermostat sends a Write Data for 59, the gateway changes it to 62 before sending it to the boiler. This means the actual setpoint is 62 degrees.

If you issue an AA=56 command, the gateway will substitute a command from the thermostat that it knows the boiler doesn't support with a request for MsgID 56. You only have to do the AA command once for the gateway to request the information on a regular basis.


Thanks for the clarification. Everything seems to go fine and is as expected. I hardly dare to ask again (I might seem to want something that is impossible, but it is not understandable for me at the moment) , but if the gateway does such a good job of blocking the 59'C and forwarding it as 62'C, why is that not sufficient enough to update the PS=1 value to 62 as well? That would save my day :)
jake3317
Starting Member
Starting Member
 
Posts: 16
Joined: April 2016

Re: DHW Setpoint not updated in PS=1 String

Postby hvxl » Sat Jan 14, 2017 12:00 pm

As I explained before, the gateway stores the values from Write-Data messages received from the thermostat and Read-Ack messages received from the boiler. As a general rule that provides the best results. Normally people want to know the values the attached equipment produce, not the values that the gateway was instructed to send. Those are already known. I can't cater for one user who wants something different for one specific message. The gateway doesn't have RMMADWIM functionality. If you need customized firmware, the sources are available for you to modify to your taste.
Schelte
hvxl
Senior Member
Senior Member
 
Posts: 1035
Joined: June 2010


Return to Opentherm Gateway Forum

Who is online

Users browsing this forum: No registered users and 1 guest