Received-SPF: none
 receiver=logan.com; client-ip=68.230.241.38; envelope-from=dale.r@cox.net
From: Dale Rogers <dale.r@cox.net>
To: "Rotary motors in aircraft" <flyrotary@lancaironline.net>
Subject: [FlyRotary] Re: Microtech EFI and Tuning
Date: Wed, 9 Feb 2005 22:46:54 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20050210034654.JHC13222.fed1rmmtao01.cox.net@smtp.west.cox.net>

Ed,

   Dunno if you saw the full text from which Finn quoted 
an excerpt.  Here's "the rest of the story":

> The MicroTech controller may be a great unit, but - as you 
> are beginning to see - you are breaking new ground with 
> your specific application.  If you don't want to be a 
> trailblazer on that many levels (experimental, rotary 
> engine, prop, & 3rd party ECU) then the smple solution is 
> to use the Mazda EC - at least until you get all the other 
> systems stable.

Ed Anderson <eanderson@carolina.rr.com> wrote:

> ... If you are a whiz at deciperhing the code of the typical Auto ECM and really understanding what it does - then go for it.  But, for the vast majority of us  - we'll keep flying with Tracy's EC2.  Nothing hidden and besides the ECM on autos are generally not redundant.  I first flew with an after market HALTECH EFI - a good system, but it did fail completely (fortunately I was on the ground when it did).  I was glad to be able to get an EC2 from Tracy with redundancy.
> 
> But, then this is experimenting and if your risk aversion profile says to go for it,  then the best of luck.  Not that it can't work, but the work and risk regarding the payoff is on the minus side of my personal equation.
>