X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Tue, 12 Jun 2007 22:47:39 -0400 Message-ID: X-Original-Return-Path: Received: from mx3.pshift.com ([216.57.116.8] verified) by logan.com (CommuniGate Pro SMTP 5.1.9) with ESMTP id 2099246 for lml@lancaironline.net; Tue, 12 Jun 2007 22:05:58 -0400 Received-SPF: none receiver=logan.com; client-ip=216.57.116.8; envelope-from=colyncase@earthlink.net Received: from ccaselt2 (unverified [216.57.118.64]) by mx3.pshift.com (Vircom SMTPRS 4.4.568.30) with SMTP id for ; Tue, 12 Jun 2007 22:05:09 -0400 Received-SPF: none (mx3.pshift.com: domain of colyncase@earthlink.net does not designate any permitted senders) X-Modus-BlackList: 216.57.118.64=OK;colyncase@earthlink.net=OK X-Modus-RBL: 216.57.118.64=Excluded X-Modus-Trusted: 216.57.118.64=NO X-Modus-Audit: FALSE;0;0;0 X-Original-Message-ID: <0a8e01c7ad5f$4885dfe0$0202a8c0@nvidia.com> From: "Colyn Case on earthlink" X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] Re: Boost switch X-Original-Date: Tue, 12 Jun 2007 19:05:14 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0A8B_01C7AD24.9BC538D0" 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 This is a multi-part message in MIME format. ------=_NextPart_000_0A8B_01C7AD24.9BC538D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable whoops. forgot a NOT below ----- Original Message -----=20 From: Colyn Case on earthlink=20 To: lml@lancaironline.net=20 Sent: Tuesday, June 12, 2007 6:52 PM Subject: [LML] Re: Boost switch Alan said, That is why it would need to be tested which should be = pretty simple in run-up, etc.=20 Alan, I agree with your LOGIC concerning how the system SHOULD work. However, I totally disagree with what you propose here for testing the = high boost on TO option. You would want to know that your idea works = through the range of fuel temp, rpm, deck angle, outside air pressure, = outside air temp, engine temp, variations in engine fuel pump mfg = tolerances, wear etc. That's a sizable testing proposition. Meanwhile, the few data points I have say that the system is sensitive = to input pressure. e.g. there have been conditions where my engine was = fine without boost but very unhappy with it. In this case the idle = mixture was out of adjustment but it still proves that the fuel is NOT = correctly metered no matter what the input pressure. Also, coupling even a tested policy to a computer would then require = extensive software testing also. ...at least if I were going to bet my = life on it. (I've spent too many late nights wondering why my program = "DID THAT" to take software testing lightly)=20 My solution is going to be to learn where the high boost button is and = be cocked to hit it if necessary. Colyn ------=_NextPart_000_0A8B_01C7AD24.9BC538D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
whoops.  forgot a NOT below
----- Original Message -----
From:=20 Colyn=20 Case on earthlink
Sent: Tuesday, June 12, 2007 = 6:52=20 PM
Subject: [LML] Re: Boost = switch

Alan said, That=20 is why it would need to be tested which should be pretty simple in = run-up,=20 etc. 
 
Alan, I agree with your LOGIC = concerning how the=20 system SHOULD work.
 
However, I totally disagree with what = you propose=20 here for testing the high boost on TO option.  You would want to know that your idea works through the range = of fuel=20 temp, rpm, deck angle, outside air pressure, outside air temp, engine = temp,=20 variations in engine fuel pump mfg tolerances, wear=20 etc.     That's a sizable testing=20 proposition.
 
Meanwhile, the few data points I have = say that=20 the system is sensitive to input pressure.  e.g. there have = been=20 conditions where my engine was fine without boost but very unhappy = with=20 it.  In this case the idle mixture was out of adjustment but = it=20 still proves that the fuel is NOT=20 correctly metered no matter what the input pressure.
 
Also, coupling even a tested policy = to a computer=20 would then require extensive software testing = also.  =20 ...at least if I were going to bet my life on it.   (I've = spent too=20 many late nights wondering why my program "DID THAT" to take software = testing=20 lightly) 
 
My solution is going to be to learn = where the=20 high boost button is and be cocked to hit it if = necessary.
 
Colyn
 
------=_NextPart_000_0A8B_01C7AD24.9BC538D0--