X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Received: from fed1rmmtao07.cox.net ([68.230.241.32] verified) by logan.com (CommuniGate Pro SMTP 5.1c.4) with ESMTP id 1414370 for flyrotary@lancaironline.net; Thu, 21 Sep 2006 23:41:24 -0400 Received-SPF: none receiver=logan.com; client-ip=68.230.241.32; envelope-from=alventures@cox.net Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao07.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060922034041.TVMV21457.fed1rmmtao07.cox.net@fed1rmimpo02.cox.net> for ; Thu, 21 Sep 2006 23:40:41 -0400 Received: from BigAl ([72.192.132.90]) by fed1rmimpo02.cox.net with bizsmtp id RFgj1V00E1xAn3c0000000 Thu, 21 Sep 2006 23:40:43 -0400 From: "Al Gietzen" To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: It runs! Date: Thu, 21 Sep 2006 20:40:50 -0700 Message-ID: <000001c6ddf8$e5cb9470$6400a8c0@BigAl> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C6DDBE.396CBC70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C6DDBE.396CBC70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable =20 However, I put the timing light on each of the plug leads and was really = confused at what I saw. #1, both lead and trail, 35 degrees before TDC So good so far. =20 Timing marks on the pulley are set for timing on rotor one. Spark on #2 should be 120 degrees later (40 degrees rotation of rotor) and another = 120 degree later on rotor 3. I don't know about 'waste' sparks, but it does seem you should see consistent sparks at the right place for each rotor. =20 I am hopeing that the extra length of my embilical=20 cord from the firewall to engine (Seawind) accounts for all of that, but = I=20 have a hard time convincing myself that is so. =20 What do you mean by 'embilical' cord engine (I think the word is = umbilical) - wires from the box to the engine? Do you have the 'triggering' leads = from box to coils separated from the leads from the CAS to the box? I think inductive coupling there could be a problem, even if the CAS leads are shielded. I'm sure you've double checked all the coil wiring, ground = points, etc. =20 Good luck, =20 Al =20 =20 Any other good ideas????? =20 Bob Darrah Seawind/20B Near Austin, TX =20 (But my spell checker said it was ok)=20 =20 =20 -- Homepage: http://www.flyrotary.com/ Archive and UnSub: http://mail.lancaironline.net/lists/flyrotary/ ------=_NextPart_000_0001_01C6DDBE.396CBC70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

However, I put the timing light on each of the plug leads and was really =

confused at what I saw.

#1, both lead and trail, 35 degrees before TDC So good so = far.

Timing marks = on the pulley are set for timing on rotor one. Spark on #2 should be 120 = degrees later (40 degrees rotation of rotor) and another 120 degree later on = rotor 3. I don’t know about ‘waste’ sparks, but it does seem you = should see consistent sparks at the right place for each = rotor.

I am hopeing that the extra length of my embilical =

cord from the firewall to engine (Seawind) accounts for all of that, but I =

have a hard time convincing myself that is so.

What do you = mean by ‘embilical’ cord engine (I think the word is umbilical) – wires from the box = to the engine? Do you have the ‘triggering’ leads from box to = coils separated from the leads from the CAS to the box? I think = inductive coupling there could be a problem, even if the CAS leads are shielded. = I’m sure you’ve double checked all the coil wiring, ground points, = etc.

Good = luck,

Al

Any other good ideas?????

Bob Darrah

Seawind/20B

Near Austin, TX

(But my spell checker said it was ok)

--

Homepage: http://www.flyrotary.com/

Archive and UnSub: = http://mail.lancaironline.net/lists/flyrotary/

------=_NextPart_000_0001_01C6DDBE.396CBC70--