Comfort Automation/ Security System Forums > Software Applications > Comfigurator > Comfort's Built-in Thermostat Function for Heating and Cooling |
Moderated by: admin |
Author | Post | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
ident Administrator
|
Comfigurator 3.7.6 see http://www.comfortforums.com/forum20/3543.html has a new Functions Category. The Functions are a new concept in Comfort where previously, what required complex programming using Responses can be replaced by the built-in Functions which require the entry of parameters Functions are implemented in Comfort Firmware 7.039 (yet to be released) Only Comfort Ultra and Logic Engine shall support Functions The first functions available are Thermostats and Blinds The Thermostat function allows Comfort to control the Heating and Cooling valves of a heating system or cooling system or a combined system using Comforts Outputs Comfort starts with 8 outputs and can be expanded to 96 outputs with Slaves and LEMs and a further 120 outputs using RIOs In the Thermostat function, Temperatures are kept in Comfort Sensors (1 to 32) The sensors can be loaded from temperature sensors in SCS, TCS or other systems like KNX or Heatmiser, Zwave which is able to map to Sensors. The Heating and Cooling Setpoints are kept in Counters. Changing the value in Heating Counter changes the heating setpoint and changing the value of the Cooling Counter changes the cooling setpoint A Comfort Flag is assigned to a thermostat. The Thermostat can be turned on or off by setting and clearing the associated Flag Using Comfort Counters, Sensors and Flags allows the thermostat to be controlled easily by manipulating these in Comfort The next part will show how to configure the Thermostats Function Last edited on Monday Oct 7th, 2013 01:41 pm by ident |
|||||||||
ident Administrator
|
The Thermostat function screen is shown below 8 Thermostats are available Common Thermostat properties The common properties for all thermostats are Maximum Heating Temperature This is the maximum heating setpoint temperature. If a higher value is put into the Heating Setpoint counter, the setpoint will be limited to this maximum value Minimum Heating Temperature This is the minimum heating setpoint temperature. If a lower value is put into the Heating Setpoint counter, the setpoint will be limited to this minimum value Maximum Cooling Temperature This is the maximum cooling setpoint temperature. If a higher value is put into the Cooling Setpoint counter, the setpoint will be limited to this maximum value Minimum Cooling Temperature This is the minimum cooling setpoint temperature. If a lower value is put into the Cooling Setpoint counter, the setpoint will be limited to this minimum value Hysteresis This is the Hysteresis temperature value used in the comparison between actual temperature and setpoint. Each of the 8 Thermostat has the following settings Sensor Number This is the Comfort sensor assigned to the Temperature of the Thermostat. Sensors assigned to Thermostats must be unique, i.e. they can be assigned to only 1 Thermostat The temperature reading can be from TCS01 or external temperature sensor like Heatmiser, Zwave or Velbus Flag Number This is the Comfort Flag assigned to the Thermostat. Assign a flag to a thermostat to enable and disable the thermostat. When the flag is off, the heating and cooling outputs will turn off. When the flag is on, the heating and cooling setpoints will operate the outputs based on comparison between the temperature and the heating/cooling setpoints. Flags assigned to thermostats must be unique, i.e. they can be assigned to only 1 Thermostat. Note that Flags are not reset by Comfort Reset in firmware 7.039 and above but cold Reset (power off without battery) will reset the Flags to 0 Heating Output Number This is the Comfort Output number for Heating control. If the Heating Output is Unassigned then the heating function will not work. Heating and Cooling cannot be on at the same time but they can both be off. Outputs must be uniquely assigned to one heating or cooling only and cannot be also assigned to security outputs, blinds function, Responses or other purposes Heating Setpoint Counter Number This is the Comfort Counter number which holds the Heating Setpoint. The counter value is limited by the Minimum Heating Setpoint and Maximum heating Setpoint and cannot be set to any values outside this range. Setting the heating counter value= 0 will disable the heating function and turn off the heating output The same counter number can be used in more than 1 thermostat so the same setpoints can be used Note that Counters are not reset by Comfort Reset in firmware 7.039 and above but cold Reset (power off without battery) will reset the counters to 0 Cooling Output Number This is the Comfort Output number for Cooling control. If the Cooling Output is Unassigned then the cooling function will not work. Heating and Cooling cannot be on at the same time but they can both be off. Outputs must be uniquely assigned to one heating or cooling only and cannot be also assigned to security outputs, blinds function, responses or other purposes Cooling Setpoint Counter Number This is the Comfort Counter number which holds the Cooling Setpoint. The counter value is limted by the Minimum Heating Setpoint and Maximum heating Setpoint and cannot be set to any values outside this range. Setting the cooling counter value= 0 will disable the Cooling function and turn off the cooling output. The same counter number can be used in more than 1 thermostat so the same setpoints can be used Note that Counters are not reset by Comfort Reset in firmware 7.039 and above but cold Reset (power off without battery) will reset the counters to 0 |
|||||||||
ident Administrator
|
Principle of Operation If the Flag assigned to the thermostat is ON, then the thermostat is enabled. If it is off, then Heating and Cooling outputs will be off and the thermostat is disabled. This works by comparing the setpoint with the actual temperature for each Thermostat. In cooling mode, if the actual temperature is higher than the setpoint + hystereris, the cooling is turned on (and heating off) using an output. If the temperature is lower than setpoint - hysteresis, the cooling is turned off. The hysteresis prevents constant switching between on and off. In heating mode, the opposite applies. If the temperature is lower than the setpoint, the heating is turned on (and cooling off) until the temp rises to the setpoint. When the temp falls below the setpoint - hysteresis, the heating is turned on again Heating and cooling cannot be switched on at the same time (interlocking) The flowchart is shown below. The sequence is triggred by a change in Sensor value (Temperature), a change in the setpoint (counter) value or a change in state of the Flag (on.off). |
|||||||||
ident Administrator
|
Sample Configuration The cclx file blindshvactest.cclx attached has the configuration descrbed here. Thermostats 1 and 8 are programmed for this example The common parameters by default are; Max Heating Temp = 30 Min Heating Temp = 16 Max Cooling Temp = 26 Min Cooling Temp = 16 Hysteresis = 1 These can be changed as required Thermostats 1 and 8 are programmed in the example Thermostat 1 Sensor = 1 Flag = 1 Heating Output 8 Heating Setpoint Counter 2 Cooling Output 9 Cooling Setpoint Counter 3 Thermostat 8 Sensor = 8 Flag = 8 Heating Output 10 Heating Setpoint Counter 2 Cooling Output 11 Cooling Setpoint Counter 3 Note that you are not allowed to select any Outputs that are used for other purposes like Security Status Outputs, Blinds, and Responses The Home Control Menu shows how it can be used to set temperature setpoints turn the thermostats on and off and read the temperature of the Thermostats 1 and 8 The "Execute Response" link on each control menu action key allows the programmed response to be activated for testing. Execute Responses is also available in the Responses page. The Feedback is programmed as Sensor 1 so that the temperature can be heard or seen Next we will show how KT03 can be used to control the thermostats Attachment: blindshvactest.zip (Downloaded 13 times) Last edited on Monday Oct 7th, 2013 02:07 pm by ident |
|||||||||
ident Administrator
|
This shows how KT03 can be programmed to change setpoints and show temperature The KT03 Thermostat 1 page is seen below(in KT03 simulation Mode) Touching the On/Off button will toggle the On/Off state by toggling the assigned flag The temperature box shows the value of Sensor 1 The Cooling and Heating Setpoints (counter values) are shown. The + and - buttons below the heating and cooling setpoints increment and decrement the heating and cooling setpoint counters. The Heating and Cooling Boxes show the state of the respective Outputs. The + and - buttons next to the temperature display is to simulate the temperature to see the effect on the heating and cooling. Use this to increment and decrement the sensor holding the temperature and see the heating and cooling outputs turn on and off accordingly. These boxes can be deleted in the final configuration. The KT03 can fully simulate the action of the thermostat without connecting any hardware If only heating is required set the cooling setpoint counter value to 0. If only cooling is required, set the heating setpoint counter value to 0. |
|||||||||
juwi_uk Member
|
Can I ask why for the thermostats are you referencing counter, flags etc by a number dropdown list instead of the names dropdowns you use just about everywhere else in Comfigurator? I'm sure there must be a reason but I'd suggest maybe now it is going to be more prone to making mistakes? Julian |
|||||||||
juwi_uk Member
|
Any why every time I submit a reply does it do it twice! Julian Last edited on Monday Oct 7th, 2013 03:51 pm by juwi_uk |
|||||||||
ident Administrator
|
You are right, the counters sensors and flags shoould be selected by name in future We wanted to get this version out first |
|||||||||
wexfordman UCM Pi Users
|
Looking forward to playing about with this. Just a query though, my heating is controlled by velbus relays, so how do I asking this as a heating output? Do I just have it assigned to any output and associate a velbus response to the output also? Also, just a point regarding the name rather than counter number, if you are fixing this issue in the next release of configurator could you also apply the same logic to velbus device names? The same issue applies where when holiday responses for velbus modules you reference the module and channel number rather than a device name and it's very confusing |
|||||||||
ident Administrator
|
The function is meant to control heating and cooling is currently by Comfort outputs, not by 3rd party This would be the simplest and most reliable way to do it instead of having another communication device There are no responses triggered by Outputs. Perhaps you could connect outputs to velbus using their input module? Your point has been noted about velbus names |
|||||||||
wexfordman UCM Pi Users
|
Thanks ident. Would there be any plans in the future to map to external devices rather than comfort outputs? |
|||||||||
ident Administrator
|
If there is a lot of demand it may be done, but we are concerned about having less complications for the heating appplication |
|||||||||
ndh Comfort Installers
|
You can run a looping response(s) that does a list like: If Output Output001 = 0 Then ! Velbus command Off etc. Else ! Velbus command On etc. End If ! If Output Output002 = 0 Then ! Velbus command Off etc. Else ! Velbus command On etc. End If ! etc. Do ThisResponse After 2 Seconds Using Timer01 Not pretty but works. |
|||||||||
wexfordman UCM Pi Users
|
ident wrote:If there is a lot of demand it may be done, but we are concerned about having less complications for the heating appplication I understand what you mean, but from the perspective of existing users, or even users who plan to deploy comfort, most will use some level of protocol be it velbus crus zwave etc, so it's perhaps a bit of a departure to have a feature like heat control to only work with comfort relays. If as part of the heating control setup you first identified and named your heating channels (be it a comfort output, or other trchonigy)? Anyway, sorry to go on about it, was really excited when I heard this feature was comming, bit gutted I can't use it with my setup. |
|||||||||
ident Administrator
|
let us look at it again and see what can be done |
|||||||||
wexfordman UCM Pi Users
|
ident wrote:let us look at it again and see what can be done Thanks ident :-) |
|||||||||
agenor Comfort Installers
|
Hi! I'd like to try and implement this feature in one of our potential projects. The thing not entirely clear to me is: how is the room temperature measured? Is it by TCS01? If so, I can't find any documentation about it. Where do I connect it? How does it look? Where do I mount it? What mounting accessories do I need? Does it need to be powered? etc... I understand that any SCS also has built-in temperature measurement and this is a good solution if the client is aesthetically satisfied with it. But I wish to explore the alternative. |
|||||||||
ident Administrator
|
Temperature can be measured by TCS. TCS is a PCB only without any housing so you will have to use your own housing. The TCS is the SCS PCB without any of the buttons etc. We are developing a more complete temperature sensing module You can also use any external device with temperature measurement with an interface to Comfort eg Heatmiser,C-Bus, KNX, Velbus, Zwave. These external devices send temperature to a Comfort Sensor The Comfort Thermostat function takes its temperature from one of the sensors, so any of the above devices can be used |
|||||||||
agenor Comfort Installers
|
Yes, that's the way we already did it (using KNX temperature stations). However, this pushes the whole system into the next price grade. |
|||||||||
wexfordman UCM Pi Users
|
ident wrote: let us look at it again and see what can be doneHi Ident/slychui Is there any chance of an update on this issue? Regards Eamon |
|||||||||
slychiu Administrator
|
Its piossible to do it but it is not imminent as there are other addtions waiting in line How many people would like to use this feature? |
|||||||||
wexfordman UCM Pi Users
|
slychiu wrote: Its piossible to do it but it is not imminent as there are other addtions waiting in line Me :-) |
|||||||||
wexfordman UCM Pi Users
|
I sill cannot get this working, even using the basic therm function. I have a response which is converting the scs value from de f to deg c and then load it back in to the sensor regiser, is it possible that this is causing problems with the therm function ? |
|||||||||
wexfordman UCM Pi Users
|
I sill cannot get this working, even using the basic therm function. I have a response which is converting the scs value from de f to deg c and then load it back in to the sensor regiser, is it possible that this is causing problems with the therm function ? |
|||||||||
slychiu Administrator
|
It may be the conversion in the same sensor. Try using a diferent sensor for the conversion also what scs firmware do you have 2.04 is able to send temperature in degrees C or F and Comfigurator 3.11.9 has fixed the bug on sensor temperature units see http://www.comfortforums.com/forum20/4558.html |
|||||||||
wexfordman UCM Pi Users
|
slychiu wrote: It may be the conversion in the same sensor. Try using a diferent sensor for the conversion Hi Slychui, Where can I download the latest scs firmware ? My scs says version unknown ? I have looked in the scs support pages and cant see any link to download the firmware, and it also does not workk via comfigurator ? |
|||||||||
slychiu Administrator
|
SCS uses older technology which does not allow firmware upgrade. You need a physical upgrade of the PCB. Let me know if you are interested in this |
|||||||||
wexfordman UCM Pi Users
|
OK, so I cant upgrade the scs firmware, what impact does this have on my thermostat function, seeing as I am trying to work in deg c. I suspect what is happening is as the scs senses a change in temp, then it triggers the thermostat function response ? If that is the case, I also have a response to convert the sensr register from deg f to deg c, and my setpoint is in deg c. Is the thermostat function herefore reading the scs sensor in deg f, rather then deg c, and therefore turning off my heating ? |
|||||||||
slychiu Administrator
|
I suspect what is happening is as the scs senses a change in temp, then it triggers the thermostat function response ? yes If that is the case, I also have a response to convert the sensr register from deg f to deg c, and my setpoint is in deg c. Is the thermostat function herefore reading the scs sensor in deg f, rather then deg c, and therefore turning off my heating ? In the sensor response, you can do the conversion from F to C and save it in another sensor. Then use the second sensor for your thermostat function |
|||||||||
wexfordman UCM Pi Users
|
Hi Slychiu Getting there now, it seems to be working for me. I have one additional question however. With the therm function, what happens if the setback temp is changed, when will the therm function react to that ? From looking at it, it appears that it will only act when the sensor temp next changes ? So in theory, if the setback temp is 23 deg, an the actual sensor is 22 deg, then if I change he setback temp to 22 deg, comfort will not react until the sensor hits 24 deg ? edit!! Dam it, its still not working, I simply cannot get my heating relay to go on as expected via the thermostat function. Sorry, if its ok, I will send my file to support, I cannot figure out why this is not working! Last edited on Monday Nov 21st, 2016 01:44 am by wexfordman |