Return-Path: Received: from imf23aec.mail.bellsouth.net ([205.152.59.71] verified) by logan.com (CommuniGate Pro SMTP 4.2b4) with ESMTP id 121141 for flyrotary@lancaironline.net; Wed, 02 Jun 2004 15:36:47 -0400 Received: from TOSHIBAjhr ([209.214.14.161]) by imf23aec.mail.bellsouth.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with SMTP id <20040602193616.ZUSL24541.imf23aec.mail.bellsouth.net@TOSHIBAjhr> for ; Wed, 2 Jun 2004 15:36:16 -0400 From: "John Slade" To: "Rotary motors in aircraft" Subject: Turbo boost limits in the EC2 Date: Wed, 2 Jun 2004 15:36:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01C448B7.5594B2C0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal This is a multi-part message in MIME format. ------=_NextPart_000_0002_01C448B7.5594B2C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit MessageFellow turbo people, I just had a conversation with Tracy while ordering my EM2. We discussed ways to detect and limit overboost. I suggested that the EC2 is watching MAP anyway, so it could spot a user programmable boost limit - e.g. 50 MAP being exceeded, and cut the training coils until the MAP drops below it. At first glance Tracy felt this was fairly easy to do. He has the MAP data and control of the coils there anyway, so it would just be a few lines of code [my words, not Tracy's] to implement. I agreed with Tracy to run it by the other blow hards to see if there was a consensus on whether this would be worth the effort on his end. Opinions? John Slade (for once, the term blowhards doesn't include Rusty) ------=_NextPart_000_0002_01C448B7.5594B2C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Fellow turbo = people,
I just had a conversation with Tracy while = ordering my=20 EM2.
 
We = discussed ways=20 to detect and limit overboost. I = suggested that=20 the EC2 is watching MAP anyway, so it could spot a user = programmable=20 boost limit - e.g. 50 MAP being exceeded, and cut the training coils = until the=20 MAP drops below it. At first glance Tracy felt this was fairly easy to = do. He=20 has the MAP data and control of the coils there anyway, so it would = just be=20 a few lines of code [my words, not Tracy's] to implement.  =
&nbs= p;
I = agreed with=20 Tracy to run it by the other blow hards to see if there was a consensus = on=20 whether this would be worth the effort on his=20 end.
&nbs= p;
Opinions?=20
&nbs= p;
John = Slade (for=20 once, the term blowhards doesn't include=20 Rusty)
------=_NextPart_000_0002_01C448B7.5594B2C0--