Software problem at MTN6212-0319 fw

[Raul_Vasvari]

In the attached picture, they are of interest to the problem telegrams highlighted in blue. Initially, the thermostat is in heating mode and can be seen from telegram 1499 that we set the setpoint to 24.5°C, and the thermostat responds correctly (1501 - returning  24.5°).

When set the setpoint to 23.5°C (telegram 1548), it responds with the value 25.5°C (Telegram 1550), and is normal, as the thermostat passed in to the cooling mode (telegram 1551). Once the RTC is in cooling mode, its operation should be normal, with no temperature difference between the send value of the setpoint and the returned one, as long as the mode is not change. So, if it takes a certain temperature "T" by the thermostat, it should respond with the same temperature "T" in the above conditions.

In telegrams 1607-1624, 1659-1661, 1743-1744 can be seen when the controller is in cooling mode, if set temperature sends a "T" to the RTC, it responds with a set temperature "T + 2".

This represents a major problem for centralized control of temperature. For for example, if you send to all the RTC's a value for the setpoint (to be 24.0°C), those that are in heating mode will record a setpoint of 24.0°C, and those that are in the cooling mode a setpoint of 26.0°C (T + 2).

There is anyone who has encountered this problem? And how can we solve it?

[Thomas_Rohde]

Hello Raul, it would be helpful to get your ETS-Project in order to get a better understanding.

Can you please post or sent it to me?

[Cristiano_Carli_Ballola]

@Raul Vasvari,

please check the parameters of your thermostate.
Focus your attention to "On what the setpointadjustment has an effec" within the menu Control General

if the option selected is "All operation mode", any setpoint you will send to the thermostate, will be comparated to a "reference setpoint" and the result of this comparisation will be applied to all the setpoints.

New Setpoint - Reference Setpoint = Result

Base Setpoint +/- Result = New Setpoint

using the image as example:

when the thermostate is in Heating Mode / Comfort and receives 22°C (absolute value) as new setpoint:

22°C compare to 21°C is +1°C
21°C + 1°C = 22°C

when the thermostate is in Cooling Mode / Comfort and receives 22°C (absolute value) as new setpoint:

22°C compare to 21°C is +1°C

24°C + 1°C = 25°C

[Raul_Vasvari]

Thank you Cristiano.

However, since sending an absolute value, it would be logical that the thermostate to set that value in the current mode of operation, regardless of controller status Heating / Cooling.

The customer says that only some thermostats have this problem, the latest. Until now used the same settings with no problem.

[Raul_Vasvari]

Hello Thomas,

I have attached the file received from the customer.

Best regards,

Raul

[Cristiano_Carli_Ballola]

You are right, Raul.

This is the behaviour when You have selected "All operation mode"
If You have selected "Current operation mode", the thermostate should send back a feedback in which the value is equal to the value received.

[Thomas_Rohde]

Hi Raul,

please let me know in case that the valueable answer from Cristiano doesnt bring the expected behaviour.

So that we need to investigate even more deeper.

kind regards

Thomas

[Raul_Vasvari]

Hello

below is the customer comment:

"Indeed, selecting "Current operation mode" for Setting "On what the setpoint adjustment has an effect" solve the problem notified by us, but in this case, the "setpoint adjustment" value is no longer kept when changing the current operation mode of thermostat to another mode, and this is a very important function, as shown below:

Example:

· Comfort heating setpoint: 23 ° C

· Comfort cooling setpoint: 25 ° C

· Standby heating setpoint: 21 ° C

· Standby cooling setpoint: 27 ° C

· Limits of setpoint adjustment: + 5K / -5K

In this case, if the system works in Cooling - Comfort mode and the user change the temperature to 20°C, the temperature measured in the room will reach 20°C, and when the thermostat goes into "Standby" the setpoint temperature will become  27°C, because the value of "setpoint adjustment" no longer maintained at the transition from one mode to another.

So we will have the setpoint of 27°C and measured temperature 20°C, and because the difference between the setpoint and the measured temperature is higher than the dead-zone in the current mode, the system will switch to "Heating", the setpoint automatically changes to 21°C, and the system will start to heat the room, which leads to the "oscillation" of the system.

However, we understand that this is how the thermostat works, but do not understand the utility of the object "Current setpoint temperature input" when for the setting "On what the setpoint adjustment has year effect" option is selected "All operation modes". If setpoint change is based on the difference between the value entered by the user and an internal reference value of the thermostat, which can not be modified or accessed differently than the thermostat parameters, than which is the relevance value written in object "Current setpoint temperature input"?

Why not this object disappears in described situation, as happens with many other objects that are available or not depending on the device parameterization?

If it wants to maintain the value of "setpoint adjustment" in all the modes (this is not a extravagant  requirement, but rather usual), the object "Current setpoint temperature input" not only is not useful but also makes it hard both understanding the operating mode and commissioning of the thermostat."

[Thomas_Rohde]

Hi Raul,

to "However, we understand that this is how the thermostat works, ..."

Yes, you are right with that. This is how the SW currently works and this we cant change that quickly because it would be an operation on the "open heart". So we have only this both options yet. If your client is with the current setting not happy as well than we need to go back to the other setting and configure the deadzone as small as possible.

I understood your comments more in the direction to improve the SW in future and I will forward this to the dedicated Offer-Manager to respect it by future SW-Updates. Is my understanding correct or do you have still a problem with your client?

Kind regards

Thomas

[Cristiano_Carli_Ballola]

Hello Raul,

perhaps, a good compromise would be to use the object "setpoint adjustment input" instead of "current setpoint input"

In this case your customer can choose the "All operation mode" parameter and receive a clearer feedback from the thermostat.
Regards

Cristiano

[Raul_Vasvari]

Hello Thomas,

indeed, my comment is in the direction of improving the SW in the future.

The customer is still dissatisfied with how the thermostat works, but I think we have no choice given that this is how the SW works.

BR,

Raul

[Thomas_Rohde]

Hi Raul, about how many Push-Buton do we talk here?

[Raul_Vasvari]

Hi Thomas,

134 pcs sold to this customer