X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from [24.25.9.103] (HELO ms-smtp-04-eri0.southeast.rr.com) by logan.com (CommuniGate Pro SMTP 4.3c5) with ESMTP id 945637 for flyrotary@lancaironline.net; Mon, 16 May 2005 09:22:22 -0400 Received-SPF: pass receiver=logan.com; client-ip=24.25.9.103; envelope-from=eanderson@carolina.rr.com Received: from edward2 (cpe-024-074-189-178.carolina.res.rr.com [24.74.189.178]) by ms-smtp-04-eri0.southeast.rr.com (8.12.10/8.12.7) with SMTP id j4GDLYL5008654 for ; Mon, 16 May 2005 09:21:35 -0400 (EDT) Message-ID: <020b01c55a1a$2f470440$2402a8c0@edward2> From: "Ed Anderson" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: TB was Re: EC2 Problem suggestion Date: Mon, 16 May 2005 09:21:35 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0208_01C559F8.A7FE9CD0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine This is a multi-part message in MIME format. ------=_NextPart_000_0208_01C559F8.A7FE9CD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MessageAs I recall there was a port on the left hand side (looking at = the front) of the TB, about on line with the shaft pointed downward. I = think it was just a hole in an aluminum boss.It opens to the manifold = right in back of the butterfly plate. I JB welded a tube in there for a = while, but it worked loose, so I removed the tube and plugged it up = since I have three other manifold pressure sensing ports in my manifold = and did not need it. Ed ----- Original Message -----=20 From: Russell Duffy=20 To: Rotary motors in aircraft=20 Sent: Monday, May 16, 2005 9:07 AM Subject: [FlyRotary] Re: TB was Re: EC2 Problem suggestion Ok, thanks,Rusty, Can't keep all the configurations everyone has in = my tired old brain {:>). By the way the TB in question I mentioned was = 75mm. Thanks Ed. I'm still trying to decide which way to go, but I have to = pick a size either way. Plenty of options, but the two leading choices = at the moment are to duplicate what I already have, using larger tubes = and either a 48 or 50 dual TB from TWM. I could also do the shoebox = intake trick, and use a single 65-70 TB. Decisions, decisions. =20 Do you know if the mustang TB has a MAP port? I know it has an air = motor attachment that has to be dealt with, but can that be used for = MAP? =20 Thanks, Rusty (pager, paging) ------=_NextPart_000_0208_01C559F8.A7FE9CD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
As I recall there was a port on the left hand = side=20 (looking at the front) of the TB, about on line with the shaft pointed=20 downward.  I think it was just a hole in an aluminum boss.It opens = to the=20 manifold right in back of the butterfly plate.  I JB welded a tube = in there=20 for a while, but it worked loose, so  I removed the tube and = plugged it up=20 since I have three other manifold pressure sensing ports in my manifold = and did=20 not need it.
 
Ed
----- Original Message -----
From:=20 Russell=20 Duffy
Sent: Monday, May 16, 2005 9:07 = AM
Subject: [FlyRotary] Re: TB was = Re: EC2=20 Problem suggestion

Ok, = thanks,Rusty,  Can't=20 keep all the configurations everyone has in my tired old brain = {:>). =20 By the way the TB in question I mentioned was 75mm.
 
 
Thanks=20 Ed.  I'm still trying to decide which way to go, but I = have to=20 pick a size either way.  Plenty of options, but the two = leading=20 choices at the moment are to duplicate what I already have, using = larger=20 tubes and either a 48 or 50 dual TB from TWM.  I could also = do the=20 shoebox intake trick, and use a single 65-70 TB.  Decisions, = decisions. 
 
Do you know=20 if the mustang TB has a MAP port?  I know it has an air = motor=20 attachment that has to be dealt with, but can that be used for=20 MAP?  
 
Thanks,
Rusty=20 (pager, paging) 
------=_NextPart_000_0208_01C559F8.A7FE9CD0--