Return-Path: <13brv3@bellsouth.net> Received: from imf22aec.mail.bellsouth.net ([205.152.59.70] verified) by logan.com (CommuniGate Pro SMTP 5.0) with ESMTP id 814530 for flyrotary@lancaironline.net; Fri, 04 Nov 2005 08:33:39 -0500 Received-SPF: pass receiver=logan.com; client-ip=205.152.59.70; envelope-from=13brv3@bellsouth.net Received: from ibm65aec.bellsouth.net ([65.6.194.9]) by imf22aec.mail.bellsouth.net with ESMTP id <20051104133255.BHOR6855.imf22aec.mail.bellsouth.net@ibm65aec.bellsouth.net> for ; Fri, 4 Nov 2005 08:32:55 -0500 Received: from rd ([65.6.194.9]) by ibm65aec.bellsouth.net with ESMTP id <20051104133252.FEIF4534.ibm65aec.bellsouth.net@rd> for ; Fri, 4 Nov 2005 08:32:52 -0500 From: "Russell Duffy" <13brv3@bellsouth.net> To: "'Rotary motors in aircraft'" Subject: RE: [FlyRotary] Re: Another Run - with Questions Date: Fri, 4 Nov 2005 07:32:53 -0600 Message-ID: <000001c5e144$424c4e90$6101a8c0@rd> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C5E111.F7B1DE90" 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.2527 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C5E111.F7B1DE90 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable But I'm in a bit of a quandary. I set TDC on the flywheel as Lynn = described and it looked so perfect. But the timing light is showing it firing at 40+Deg. ATDC and when I turn the Crank Angle sensor as far as it will go trying to advance it I can only get up to about 20Deg ATDC.=20 =20 Hi Joe, =20 Static timing is just that "static". Once you start running, your = ignition controller decides where it wants the timing to be relative to the = static timing, so think of the static timing as nothing more than a reference = for the controller. =20 =20 As you know, the faster the rotor is moving, the less time the spark has = to complete ignition, so you have to advance the timing to start it a bit earlier, so ignition occurs in the correct position of the rotor. Using = the same logic, the timing can be retarded at idle. For a complex = controller like the MicroTech, I would not be surprised to find out that they're = taking advantage of a larger range of timing than aircraft normally use. =20 Now, I am supposed to put the timing light on the #1 Leading plug lead, right? That's what my Mazda manual says.=20 =20 That would be my guess. I'd assume that it's done the normal, Mazda = way, unless MicroTech tells you otherwise. =20 =20 I guess I'll have to see if I can re-position my Crank Angle sensor this weekend and see what happens when I can advance it further.=20 =20 I haven't looked at it closely in a while, but I'm guessing you can pull = the CAS, and rotate the gear a tooth, then reinstall it. By experimenting = with this, I'd bet you can get the desired timing within range of the slot on = the CAS. =20 =20 The MicroTech setup manual says to set the idle timing to 5Deg ATDC - it also says that is the yellow mark on the pulley).=20 =20 They're probably right :-) At some point, you'll want to verify that = the MicroTech is advancing the timing properly at higher rpms, but if the = only timing adjustment they gave was at idle, then I'd bet a few beers it's = going to be right everywhere. =20 =20 Joe Hull (loving the smell of exhaust in the my hair, my clothes, my = skin.) =20 Might cut into your social life though :-) =20 Cheers, Rusty (XL pulling farther into the lead)=20 ------=_NextPart_000_0001_01C5E111.F7B1DE90 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
But I’m = in a bit of a=20 quandary.  I set TDC on = the flywheel=20 as Lynn described and it looked so perfect. But the timing light is = showing it=20 firing at 40+Deg. ATDC and when I turn the Crank Angle sensor as far as = it will=20 go trying to advance it I can only get up to about 20Deg ATDC. 
 
Hi=20 Joe,
 
Static timing = is just that=20 "static".  Once you start running, your ignition controller decides = where=20 it wants the timing to be relative to the static timing, so think of the = static=20 timing as nothing more than a reference for the controller. =20
 
As you know, = the faster the=20 rotor is moving, the less time the spark has to complete ignition, so = you have=20 to advance the timing to start it a bit earlier, so ignition occurs in = the=20 correct position of the rotor.  Using the same logic, the = timing can=20 be retarded at idle.  For a complex controller like the=20 MicroTech, I would not be surprised to find out that they're taking = advantage of a larger range of timing than aircraft normally=20 use.
 
Now, I am = supposed to=20 put the timing light on the #1 Leading plug lead, right? That’s = what my Mazda=20 manual says. 
 
That = would be my=20 guess.  I'd assume that it's done the normal, Mazda way, unless = MicroTech=20 tells you = otherwise.  
 <= /FONT>

I guess = I’ll have to=20 see if I can re-position my Crank Angle sensor this weekend and see what = happens=20 when I can advance it further. 

 

<= FONT=20 color=3Dnavy size=3D2>
I haven't = looked at it=20 closely in a while, but I'm guessing you can pull the CAS, and rotate = the gear a=20 tooth, then reinstall it.  By experimenting with this, I'd bet you = can get=20 the desired timing within range of the slot on the=20 CAS.  

 <= /FONT>

The MicroTech setup manual says to set the idle timing = to 5Deg=20 ATDC – it also says that is the yellow mark on the pulley). 

 

<= FONT=20 color=3Dnavy size=3D2>
They're = probably right=20 :-)  At some point, you'll want to verify that the MicroTech is = advancing=20 the timing properly at higher rpms, but if the=20 only timing adjustment they gave was at idle, then I'd = bet a few=20 beers it's going to be right everywhere.    

 

Joe=20 Hull (loving the smell of exhaust in the my hair, my clothes, my=20 skin…)

 

Might cut into = your social=20 life though :-)

 

Cheers,

Rusty (XL = pulling farther=20 into the = lead) 

------=_NextPart_000_0001_01C5E111.F7B1DE90--