X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from rtp-iport-1.cisco.com ([64.102.122.148] verified) by logan.com (CommuniGate Pro SMTP 5.2.0) with ESMTP id 2719380 for flyrotary@lancaironline.net; Thu, 07 Feb 2008 09:43:46 -0500 Received-SPF: softfail receiver=logan.com; client-ip=64.102.122.148; envelope-from=echristley@nc.rr.com Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 07 Feb 2008 09:43:08 -0500 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m17Eh7X9001608 for ; Thu, 7 Feb 2008 09:43:07 -0500 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m17EgjrU016438 for ; Thu, 7 Feb 2008 14:43:07 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Feb 2008 09:40:01 -0500 Received: from [10.82.209.119] ([10.82.209.119]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 7 Feb 2008 09:40:01 -0500 Message-ID: <47AB1841.8010204@nc.rr.com> Date: Thu, 07 Feb 2008 09:40:01 -0500 From: Ernest Christley Reply-To: echristley@nc.rr.com User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Rotary motors in aircraft Subject: Re: [FlyRotary] Hardwire? [FlyRotary] Re: Ignition advance References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Feb 2008 14:40:01.0528 (UTC) FILETIME=[51E94780:01C86997] Authentication-Results: rtp-dkim-1; header.From=echristley@nc.rr.com; dkim=neutral Ed Anderson wrote: > Ernest, not familiar with your EFI system. However, your statement > about hardwiring it for 20 deg and then using the computer to add > advance caught my attention - normally that is not how it is done. > It is difficult for a CPU design to "ADD" or advance ignition timing > from a static timing point as that implies it has to know in advance > (precognition but not pre-ignition - sorry, couldn't help it) when > the next firing event is coming. All of the EFI units that I am > familiar will set or "Hardwire" the static timing to the maximum > amount of ignition timing advance they will ever want. Then the > computer is used to retard the timing from that point which is much > easier to do. Tracy's EC2 uses this method and that is why his > instruction have you set the static ignition timing to 31-35 Deg BTDC > and then the CPU simply backs off to there to the "Advance" you want. > > FWIW > > Ed http://www.megamanual.com/ms2/EDIS.htm There is no way I can explain it any better than this. My understanding is that for the EDIS system there is a basic advance set by the physical alignment of the parts. That advance is then increased by a controlling computer with the SAW signal. There is precognition of sorts. Because of the missing tooth, the controller knows when the cylinder is coming up to TDC.