- Joined
- Jul 16, 2009
- Messages
- 5,071
- Reaction score
- 8,108
@Gaël
My ticket regarding my cooling difference questions
Ticket #8494
Was closed without an answer or confirmation. Am I to assume my understanding of cooling difference was correct?
Code:The user manual for Profilux appears ambiguous as to the actual function of cooling difference. It defines where cooling starts, but does not clearly indicate where cooling STOPS or what hysteresis is applied to cooling. My trial and error indicates that all "cooling difference" does is move the operating band (STOP:START) of cooling forward by a fixed ratio but leaves the hysteresis between START:STOP unchanged. Can you confirm? Two examples: Nominal: 25 Hysteresis: 2 Cooling Difference: 0 Heat Start = 24 Heat Stop = 26 Cooling Start = 27.83 Cooling Stop = 26.83 Nominal: 25 Hysteresis: 2 Cooling Difference: 2 Heat Start: 24 Heat Stop: 26 Cooling Start: 29.83 Cooling Stop: 28.83
My ticket also posed a few questions and thoughts that were unanswered
Code:In both examples "hysteresis" is set to 2 degrees. Am I understanding this correctly? In the first example you only get within 1.83 degrees of NOMINAL from cooling, whereas heat gets you within 1 degree of nominal. In the second example you only get within 3.83 degrees of NOMINAL from cooling, whereas heat gets you within 1 degree of nominal. One would think that if "heating" stops at 26 degress, then the logical and proper implementation of the hysteresis band and control points would be Heat Start: nominal - (0.5 * hysteresis) Heat Stop: nominal + (0.5 * hysteresis) Cooling Start: nominal + (hysteresis * 0.83) + cooling difference Cooling Stop: nominal + (0.5 * hysteresis) Cooling would still guaranteed NOT overlap heating, and heating + cooling will still give you a TRUE nominal of 25 +/- 1 I can get somewhat the behavior that I want by setting up a virtual temperature sensor and using it for "cooling" and tweak settings as needed, but am still curious as to why this was not implemented in a single "heat + cool" logic. Thanks, -Bill
Again - not trying to rock the boat here for any other reason than helping myself and others understand, as well has offer input that (in my opinion) would improve the overall user experience and product operation.
Replying to myself - My ticket was closed without an answer and it would appear that GHL has opted to not respond (being active daily in other threads).
GHL (all of you) as much as I love the product and appreciate the help and support when it comes, situations like this are extremely frustrating to those of us who do follow this forum. In this case there are numerous threads here, at the OLD RC and GHL forums with the very same questions and also somewhat ambiguous answers. The same for some of the other topics that I mentioned. To me that illustrates that a more thorough explanation and examples are warranted in the documentation.
In this case, Matthias indicated that he didn't understand the confusion with something so "simple" and several of us have indicated WHY we are confused and what other information we are looking for. Yes there is some noise in this thread, but there are also some very valid points and unanswered questions.