X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 2 [X] Return-Path: Received: from ms-smtp-03.southeast.rr.com ([24.25.9.102] verified) by logan.com (CommuniGate Pro SMTP 5.1.8) with ESMTP id 2043313 for flyrotary@lancaironline.net; Mon, 14 May 2007 08:38:11 -0400 Received-SPF: pass receiver=logan.com; client-ip=24.25.9.102; envelope-from=eanderson@carolina.rr.com Received: from edward2 (cpe-024-074-103-061.carolina.res.rr.com [24.74.103.61]) by ms-smtp-03.southeast.rr.com (8.13.6/8.13.6) with SMTP id l4ECbIur001049 for ; Mon, 14 May 2007 08:37:18 -0400 (EDT) Message-ID: <000801c79624$d4d6bb60$2402a8c0@edward2> From: "Ed Anderson" To: "Rotary motors in aircraft" References: Subject: Re: [FlyRotary] Re: Frustrating Sunday Date: Mon, 14 May 2007 08:38:53 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Virus-Scanned: Symantec AntiVirus Scan Engine >> Ed > > I did ground each pin at the EC plug with the injector switches on. I > heard a click from each injector corresponding to the pin. > Another clue is the NOP flashing? > Ed, Do you think it may have something to do with the new wiring that > eliminates the powering the EC thru the injector switches? > You mentioned something about it? > Buly The snubber modification does involve the injector circuit, but after Tracy modified mine, it fired right up and really idled nicely with a "crisp" sound and the mixture control effect was also more "crisp", so I don't think there is a correlation there. However, I went out Saturday to start my engine and it would not start, I did not have time to do any "digging" into it but in my case it appears to be the ignition and I don't think its EC2 related.. I flew 1700 miles after the snubbers were installed and I was down in rotary-no-man-land - Southwestern Louisiana were surely (with my luck) if anything regarding the EC2 were going to happen, it would have. But, it would appear in your case, that either the EC2 is not grounding your injectors OR there is a connection problem between your EC2 and injectors. Since you can't dig into the EC2, I would make certain there is a connection between the EC2 and injectors. You said you grounded the injectors and they clicked, did you ground them at the EC2 terminal - if you did then that would indicate the wiring connection is OK. But, if you just grounded them close to the injectors, then that does not prove anything about your connectivity to the EC2 - only that you have power to the injectors. I will be going out tomorrow to dig into my problem and will let you know what I find. Ed