Return-Path: <marv@lancaironline.net>
Received: from [65.33.163.242] (account marv@lancaironline.net)
  by logan.com (CommuniGate Pro WebUser 4.3c2)
  with HTTP id 758380 for lml@lancaironline.net; Thu, 24 Feb 2005 21:10:44 -0500
From: "Marvin Kaye" <marv@lancaironline.net>
Subject: Re: [LML] Re: FADEC Rough idle explanation
To: lml
X-Mailer: CommuniGate Pro WebUser Interface v.4.3c2
Date: Thu, 24 Feb 2005 21:10:44 -0500
Message-ID: <web-758380@logan.com>
In-Reply-To: <718b5514f0538146ff69a98422e115f7@advancedpilot.com>
References: <list-757983@logan.com>
 <718b5514f0538146ff69a98422e115f7@advancedpilot.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit

Posted for Walter Atkinson <walter@advancedpilot.com>:

Finding peak is the same.  The slope of the curve on the lean side is changed
slightly but that's not an operational issue.  The pilot would not notice
anything different.
  
  Walter
  

"""
  so speaking of PRISM, Walter can you say what happens to egt/tit on a PRISM
system when you try to find peak?  I assume it's a little different at least
in magnitude, than with a fixed timing system.
"""