Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
CHV-TSTAT force "extended" run times?
|
So my house has started running "cool" cycles for the year and I'm noticing that the cycle times seem much shorter and more frequently than prior years and actually if I look at the temps the temp is 1-2 degrees above the setpoint within a few seconds of the cool cycle ending. (I can't say I've ever noticed that before - but cycle times haven't bothered me before either)
The TSTAT is admittedly not in a great place -- it's where the HVAC contractor/prior owner put the old school Honeywell stat - but since all of the other walls on this floor are either exterior, a common wall with my next door neighbor, or have a fireplace/plasma on them I can't really do much better. (Also: Whomever designed the HVAC system was, IMO, smoking crack - there's only one return in the house and it's on the first floor of a 3-story townhome) Is there any way to force the TSTAT to make the cool call longer / reduce the number of cycles? I'd much rather a longer cool cycle and have it overshoot the setpoint by a degree or five than have it firing every 10 minutes or so. Or am I barking up the wrong tree in the first place? -- Lincoln King-Cliby, CTS Sr. Systems Architect | Crestron Certified Master Programmer (Silver) ControlWorks Consulting, LLC Crestron Services Provider |
|
If I recall correctly, there are heating and cooling 'anticipators' in the setup screen on the tstat. Sounds like the cooling one may be set a bit too aggressively.
toggle quoted message
Show quoted text
--- In Crestron@..., Lincoln King-Cliby <lincoln@...> wrote:
|
|
Thanks -- apparently I need to refresh my memory of the "Anticipator"'s function -- Cool was at 6 [though I swear, other than FW updates I haven't touched the state since it was installed.
toggle quoted message
Show quoted text
I knocked it down a bit and the frequency of cool calls has dropped -- but of course, today everything is overcast and relatively cool anyway so it's hard to be positive... Lincoln -- Lincoln King-Cliby, CTS Sr. Systems Architect | Crestron Certified Master Programmer (Silver) ControlWorks Consulting, LLC Crestron Services Provider -----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of Brian Gross Sent: Friday, May 10, 2013 6:15 PM To: Crestron@... Subject: [Crestron] Re: CHV-TSTAT force "extended" run times? If I recall correctly, there are heating and cooling 'anticipators' in the setup screen on the tstat. Sounds like the cooling one may be set a bit too aggressively. --- In Crestron@..., Lincoln King-Cliby <lincoln@...> wrote:
------------------------------------ Check out the Files area for useful modules, documents, and drivers. A contact list of Crestron dealers and programmers can be found in the Database area. Yahoo! Groups Links |
|
I found the heat and cool anticipators did not work on the older firmware levels. But when I switched to v2.061, they started working. I seem to recall however that they worked in reverse of what the manual said. But I have a dual fuel system so that issue may only be unique to that mode.
toggle quoted message
Show quoted text
If the thermostat is in a bad location, you could use a remote temperature sensor. Even if you mount the sensor real close to the thermostat, you will probably observe an improvement. The big problem with the internal sensor is the inside of the TSTAT runs so hot that it messes up the internal temperature sensor. Depending on how the air current changes when the blower turns on, it can cause the thermostat to either short cycle or run too long. The internal sensor is mounted near the bottom of the thermostat. A downward draft will cause the internal sensor to heat up while an upward draft will cause the internal sensor to cool down. The big issue I have with v2.061 is occasionally the outdoor temperature sensor intermittently jumps up about 50 degrees and stays there until you reboot the thermostat or run the internal sensor calibration test. A different sensor behaves the same way and the problem started when I updated the firmware. Just downgrade firmware and waiting to see if the problem recurs. Steve --- In Crestron@..., Lincoln King-Cliby <lincoln@...> wrote:
|
|
You may be on to something there...
toggle quoted message
Show quoted text
I know I haven't changed the TStat setup since before I last updated the firmware, and I remember at the time thinking that the anticipators weren't having any/much affect. And the anticipators were set for what I "thought" would do what I wanted based on the manual (e.g. backwards from what reality appears to be) -- I'm using a "normal" single stage system (burner/forced air heat and ac). On the 2nd floor (Kitchen/Living) where the TStat is, there really isn't a "less bad" location for either the stat or an RTS, but I would like to get an RTS on the 3rd floor (Master Bed) anyway so I might force myself to do that while I'm doing some other work over the summer -- if any of this "free time" I hear speak of surfaces. I haven't seen the OD temp behave as you describe using an RSS for OD... Before that, I originally had a RTS that did all sorts of weird things toward the end of its life including at one point reporting the OD temp oscillating between something like +126F and -200F until you entered and exited setup, but that clearly wasn't a firmware issue. Lincoln -- Lincoln King-Cliby, CTS Sr. Systems Architect | Crestron Certified Master Programmer (Silver) ControlWorks Consulting, LLC Crestron Services Provider -----Original Message-----
From: Crestron@... [mailto:Crestron@...] On Behalf Of highfidelityinc Sent: Sunday, May 12, 2013 5:33 PM To: Crestron@... Subject: [Crestron] Re: CHV-TSTAT force "extended" run times? I found the heat and cool anticipators did not work on the older firmware levels. But when I switched to v2.061, they started working. I seem to recall however that they worked in reverse of what the manual said. But I have a dual fuel system so that issue may only be unique to that mode. If the thermostat is in a bad location, you could use a remote temperature sensor. Even if you mount the sensor real close to the thermostat, you will probably observe an improvement. The big problem with the internal sensor is the inside of the TSTAT runs so hot that it messes up the internal temperature sensor. Depending on how the air current changes when the blower turns on, it can cause the thermostat to either short cycle or run too long. The internal sensor is mounted near the bottom of the thermostat. A downward draft will cause the internal sensor to heat up while an upward draft will cause the internal sensor to cool down. The big issue I have with v2.061 is occasionally the outdoor temperature sensor intermittently jumps up about 50 degrees and stays there until you reboot the thermostat or run the internal sensor calibration test. A different sensor behaves the same way and the problem started when I updated the firmware. Just downgrade firmware and waiting to see if the problem recurs. Steve --- In Crestron@..., Lincoln King-Cliby <lincoln@...> wrote:
------------------------------------ Check out the Files area for useful modules, documents, and drivers. A contact list of Crestron dealers and programmers can be found in the Database area. Yahoo! Groups Links |
to navigate to use esc to dismiss