Return-Path: Received: from relay03.roc.ny.frontiernet.net ([66.133.131.36] verified) by logan.com (CommuniGate Pro SMTP 4.1.6) with ESMTP id 2712403 for flyrotary@lancaironline.net; Thu, 06 Nov 2003 10:19:23 -0500 Received: (qmail 27274 invoked from network); 6 Nov 2003 15:19:21 -0000 Received: from unknown (HELO frontiernet.net) ([170.215.97.8]) (envelope-sender ) by relay03.roc.ny.frontiernet.net (FrontierMTA 2.3.6) with SMTP for ; 6 Nov 2003 15:19:21 -0000 Message-ID: <3FAA66BC.160E28B6@frontiernet.net> Date: Thu, 06 Nov 2003 09:20:29 -0600 From: Jim Sower X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rotary motors in aircraft Subject: Re: [FlyRotary] Re: DIE Summary References: Content-Type: multipart/alternative; boundary="------------99E8CCBA79D6DFA42FC654BD" --------------99E8CCBA79D6DFA42FC654BD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit <... a temp sensor in the intake could provide input to the controller which could use a lookup table to determine how to bias the injectors ...> I wasn't willing to automate things that much right out the gate, but down the road it might be feasible. <... The biggest problem would be in selecting injectors ...> What's wrong with using the injectors we have right now? They currently provide all of the fuel for a given runner quite comfortably. I wouldn't guess there would be a problem with them delivering little enough fuel. There might be a problem with non linearity of pulse width - like the pulse width to deliver X amount of fuel through a given injector is 57 "ticks", but due to open/close times, the A and B times might be 12 and 49 for one condition and 31 and 29 for another. But that could be worked out with the internal maps I suppose. In any event, the system should fail over to one injector or the other. Sounds more doable every day ... Jim S. echristley@nc.rr.com wrote: > > This shouldn't be extremely difficult to incorporate into a injector contoller, assuming the processor has enough bandwidth. .... The biggest problem would be in selecting injectors. On a very hot day, the computer might determine that all the fuel needed to come from the throttle body injectors. ....Either way, it may mean a sluggish plane when you're not expecting it. --------------99E8CCBA79D6DFA42FC654BD Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <... a temp sensor in the intake could provide input to the controller which could use a lookup table to determine how to bias the injectors ...>
I wasn't willing to automate things that much right out the gate, but down the road it might be feasible.

<... The biggest problem would be in selecting injectors ...>
What's wrong with using the injectors we have right now?  They currently provide all of the fuel for a given runner quite comfortably.  I wouldn't guess there would be a problem with them delivering little enough fuel.  There might be a problem with non linearity of pulse width - like the pulse width to deliver X amount of fuel through a given injector is 57 "ticks", but due to open/close times, the A and B times might be 12 and 49 for one condition and 31 and 29 for another.  But that could be worked out with the internal maps I suppose.  In any event, the system should fail over to one injector or the other.

Sounds more doable every day ... Jim S.

echristley@nc.rr.com wrote:

 
This shouldn't be extremely difficult to incorporate into a injector contoller, assuming the processor has enough bandwidth.  .... The biggest problem would be in selecting injectors.  On a very hot day, the computer might determine that all the fuel needed to come from the throttle body injectors. ....Either way, it may mean a sluggish plane when you're not expecting it.
--------------99E8CCBA79D6DFA42FC654BD--