X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.120] verified) by logan.com (CommuniGate Pro SMTP 6.0c1) with ESMTP id 5719853 for flyrotary@lancaironline.net; Mon, 20 Aug 2012 11:30:28 -0400 Received-SPF: pass receiver=logan.com; client-ip=75.180.132.120; envelope-from=eanderson@carolina.rr.com Return-Path: X-Authority-Analysis: v=2.0 cv=OtDNOlDt c=1 sm=0 a=g3L/TDsr+eNLfIieSKfGkw==:17 a=AHkS0RJitIMA:10 a=JMGDamdCVwsA:10 a=05ChyHeVI94A:10 a=8nJEP1OIZ-IA:10 a=56S0c1_jCvUA:10 a=ayC55rCoAAAA:8 a=pGLkceISAAAA:8 a=Ia-xEzejAAAA:8 a=C_IRinGWAAAA:8 a=oCcaPWc0AAAA:8 a=7g1VtSJxAAAA:8 a=OkItfNGlXrw-4x6ATbAA:9 a=wPNLvfGTeEIA:10 a=Qa1je4BO31QA:10 a=E6k37eg1NvgA:10 a=MSl-tDqOz04A:10 a=EzXvWhQp4_cA:10 a=si9q_4b84H0A:10 a=g3L/TDsr+eNLfIieSKfGkw==:117 X-Cloudmark-Score: 0 X-Originating-IP: 174.110.170.10 Received: from [174.110.170.10] ([174.110.170.10:51274] helo=EdPC) by cdptpa-oedge01.mail.rr.com (envelope-from ) (ecelerity 2.2.3.46 r()) with ESMTP id CF/6E-29356-0F752305; Mon, 20 Aug 2012 15:29:52 +0000 Message-ID: <2A8D60EE9C1247968CECAD976EEC8EF1@EdPC> From: "Ed Anderson" To: "Rotary motors in aircraft" References: In-Reply-To: Subject: Re: [FlyRotary] Re: EM2 CHT ? Date: Mon, 20 Aug 2012 11:29:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 Ok, Mark, I get your viewpoint. I can see where temp rise would be detected earliest that way and perhaps permit you to throttle back and reduce power before perhaps damage occurs. Be interesting to see what David ends up with. Ed -------------------------------------------------- From: "Mark Steitle" Sent: Monday, August 20, 2012 10:15 AM To: "Rotary motors in aircraft" Subject: [FlyRotary] Re: EM2 CHT ? > Ed, > > I think the idea is you'll get a more accurate measurement at the > combustion surface of each rotor rather than measuring the temp of the > coolant that has already blended with other coolant in the system. > Its my understanding that the coolant temp will be higher around the > plug area than elsewhere, so if you operate near the boiling point of > your coolant, you would be able to tell it sooner rather than later. > Still, if you know the safe high-temp limit, it seems you would get a > better reading off the rotor housing liner than from the coolant. > > If you drill/tap each rotor housing you can see how hard each rotor is > working, similar to EGT's. CHT can serve as a cross-check to EGT. > > Also, monitoring cooling system pressure should alert you to an > imminent boilover event. But you already knew that. ;-) > > > My 2 cents, > Mark > > On 8/20/12, Ed Anderson wrote: >> I agree, Mark, that your suggestion would probably get you as close to an >> equivalent CHT as we can get. >> >> But, I'm still not understanding what that would usefully provide that is >> worth more than your coolant temps. >> >> I presume that if for some reason the engine temperature were to rapidly >> increase (perhaps due to detonation or other combustion events) that the >> CHT >> reading would provide quicker information on the condition than would the >> coolant temp so perhaps you could take corrective action before damage. >> Might be a comfort factor knowing "CHT" if using forced induction on a >> rotary as things can happen pretty fast when at high boost levels. >> >> Ed >> >> >> >> >> From: Mark Steitle >> Sent: Sunday, August 19, 2012 8:48 PM >> To: Rotary motors in aircraft >> Subject: [FlyRotary] Re: EM2 CHT ? >> >> >> Seems that this will tell you the coolant temp near the plugs, but not >> the >> CHT. If you want to measure the CHT, you'll need to locate a >> thermo-couple >> down near the steel liner. You can do this by drilling a small hole down >> into the web adjacent to the leading plug, stopping at the steel liner. >> Then insert a thermo-couple down into the hole so that it is touching the >> steel liner. Now you're reading the temps nearest the combustion >> chamber, >> closest thing we have to CHT. >> >> >> Mark >> >> >> On Sun, Aug 19, 2012 at 10:02 AM, wrote: >> >> Sounds like a plan to me Ed, should have time Sun. to do. David >> >> >> ------------------------------------------------------------------------------ >> From: "Ed Anderson" >> To: "Rotary motors in aircraft" >> Sent: Saturday, August 18, 2012 6:54:35 AM >> Subject: [FlyRotary] Re: EM2 CHT ? >> >> >> I think I would run the engine at operational rpms (>5000) and watch >> the >> coolant/oil temperatures - when they got to my maximum limit, I would >> check >> the CHT reading and perhaps add 50 degrees for the limit (to start with). >> If I got a lot of false alarms at that margin I would try another 50 deg. >> Just a WAG. >> >> Ed >> >> >> From: hoursaway1@comcast.net >> Sent: Friday, August 17, 2012 10:20 PM >> To: Rotary motors in aircraft >> Subject: [FlyRotary] EM2 CHT ? >> >> >> What are we using for high temp numbers from the CHT sensors on the 13B >> rotary, I have the under the spark plug style sensors bolted to each >> rotor >> housing in some factory threaded holes just above the spark plugs, not >> really the hottest spot but the holes were already in place so I KISSed >> it & >> moved on, now I need to set my high temp warning limit & do not know what >> to >> use. Possibly do an eng. run with upper cowl off & check bolt/sensor >> temp >> with a lazer temp gun at about 4000 RPM & go another 50 deg. higher? >> Ideas? David R. Cook RV6A Rotary >> >> >> >> >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.2197 / Virus Database: 2437/5206 - Release Date: >> 08/17/12 >> >> >> >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2012.0.2197 / Virus Database: 2437/5211 - Release Date: 08/20/12 >> > > -- > Homepage: http://www.flyrotary.com/ > Archive and UnSub: > http://mail.lancaironline.net:81/lists/flyrotary/List.html > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2197 / Virus Database: 2437/5211 - Release Date: 08/20/12 >