X-Virus-Scanned: clean according to Sophos on Logan.com
Return-Path: <thomasmann51@gmail.com>
Received: from mail-vb0-f53.google.com ([209.85.212.53] verified)
  by logan.com (CommuniGate Pro SMTP 6.0.6)
  with ESMTPS id 6439402 for flyrotary@lancaironline.net; Fri, 23 Aug 2013 15:06:23 -0400
Received-SPF: pass
 receiver=logan.com; client-ip=209.85.212.53; envelope-from=thomasmann51@gmail.com
Received: by mail-vb0-f53.google.com with SMTP id i3so675675vbh.40
        for <flyrotary@lancaironline.net>; Fri, 23 Aug 2013 12:05:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=HJv7Usnl64stQy1l8kv/ajStPLW28u5a3tUaylJbv7U=;
        b=AU+wtaA3Uw5oOzhdd1V1Ts5HnCeIMNb+UEm0Van/aPEuKHJU7PcNF5ZY96h8vug3Ip
         oROuyHctIbBR6T37dZMAiWg6GFW72IccSzjHw2yrmd9ZCFgbSZwonhe12jrK/iQUY9do
         7T9KJmyJnZGkaS/WtNcYcUhcJC1DK25nlmHqgbtNi2NnvIG1MhR+HyvB/cvTzr2k0KP6
         wzj+3OdoU9ukoYT0iUXRwv3Yn6m8xk05zGnUaZMzxAwEQa7/wkEsFuVRUDbL5pOKi4/0
         SSf5PbZWggfOr+If5aF1/dWiVGsvn5xIsNSi9nfjB2p0MlDT+nbsYmjKDGCPZtW+2Xiw
         n0Jw==
MIME-Version: 1.0
X-Received: by 10.58.127.202 with SMTP id ni10mr731321veb.27.1377284747531;
 Fri, 23 Aug 2013 12:05:47 -0700 (PDT)
Received: by 10.58.2.6 with HTTP; Fri, 23 Aug 2013 12:05:47 -0700 (PDT)
In-Reply-To: <CAH_WSmoDBL7_82AzTKQ5k=a79oRr5-6E=y0s4eKYWOTJGYYnbw@mail.gmail.com>
References: <CAH_WSmoDBL7_82AzTKQ5k=a79oRr5-6E=y0s4eKYWOTJGYYnbw@mail.gmail.com>
Date: Fri, 23 Aug 2013 14:05:47 -0500
Message-ID: <CAH_WSmrrNW0Zs1vmqcz5k27Tubo9+KP0XuZSrVGjx-09JtG7NQ@mail.gmail.com>
Subject: Re: Injector Location
From: Thomas Mann <thomasmann51@gmail.com>
To: Fly Rotary <flyrotary@lancaironline.net>
Content-Type: multipart/alternative; boundary=047d7b5d870f219cce04e4a218e7

--047d7b5d870f219cce04e4a218e7
Content-Type: text/plain; charset=ISO-8859-1

.....whoa not everybody at once!

Has anyone used the approach where the injector locations in the block were
bypassed (blocked) and all of the injectors were located in the
intake manifold assembly?


On Fri, Aug 23, 2013 at 7:56 AM, Thomas Mann <thomasmann51@gmail.com> wrote:

> I wonder why nobody sets up the second set of injectors the same way the
> primaries are setup (i.e. shoot through the iron into the intake port. )
> That would sure simplify things and pretty much match up the fuel delivery
> method.
>
> Is there a logical/rational reason this isn't configured in this manner?
> ......or .... has someone already done this?
>
> T Mann
>

--047d7b5d870f219cce04e4a218e7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>.....whoa not everybody at once!</div><div>=A0</div><=
div>Has anyone used the approach where the injector locations in the block =
were bypassed (blocked) and all of the injectors were located in the intake=
=A0manifold assembly?</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
 Aug 23, 2013 at 7:56 AM, Thomas Mann <span dir=3D"ltr">&lt;<a href=3D"mail=
to:thomasmann51@gmail.com" target=3D"_blank">thomasmann51@gmail.com</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I wonder why nobody se=
ts up the second set of injectors the same way the primaries are setup (i.e=
. shoot through the iron into the intake port. )<br>
 That would sure simplify things and pretty much match up the fuel delivery=
 method.</div>
<div>=A0</div><div>Is there a logical/rational reason this isn&#39;t config=
ured in this manner?</div><div>......or .... has someone already done this?=
</div><div>=A0</div><div>T Mann</div></div>
</blockquote></div><br></div>

--047d7b5d870f219cce04e4a218e7--