X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Sun, 10 Feb 2008 22:58:37 -0500 Message-ID: X-Original-Return-Path: Received: from elasmtp-galgo.atl.sa.earthlink.net ([209.86.89.61] verified) by logan.com (CommuniGate Pro SMTP 5.2.0) with ESMTP id 2722913 for lml@lancaironline.net; Sat, 09 Feb 2008 21:35:44 -0500 Received-SPF: none receiver=logan.com; client-ip=209.86.89.61; envelope-from=colyncase@earthlink.net DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=V+TGp85y2ETMC4UysczaEW82Eq9MA3LNA87tCANlVa2bBOumji0vM4UL0rKRRCGn; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [216.57.118.94] (helo=ccaselt2) by elasmtp-galgo.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1JO226-0003gL-VJ for lml@lancaironline.net; Sat, 09 Feb 2008 21:35:07 -0500 X-Original-Message-ID: <062201c86b8d$8c4aeb20$0202a8c0@nvidia.com> From: "Colyn Case on earthlink" X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] VM1000 Failure X-Original-Date: Sat, 9 Feb 2008 21:35:06 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_061F_01C86B63.A2F8FC60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-ELNK-Trace: 63d5d3452847f8b1d6dd28457998182d7e972de0d01da9400f8f895e506b12b9a833418a858b5eb8350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 216.57.118.94 This is a multi-part message in MIME format. ------=_NextPart_000_061F_01C86B63.A2F8FC60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Brent,=20 While we're on that, I had a situation with a grt eis 6000 (similar to = the eau that Chelton sells or used to). One day my MAP started indicating zero concurrently with erratic = indications on several of the egt's. On investigating I found that = squeezing or moving the wire harness from the probes to the eis caused = different erratic indications. Tearing apart the wire harness revealed = several spade connectors that weren't connecting anymore. It's also = possible that some were shorting to ground via the shielding on adjacent = probes. The unexpected (for me) finding was that fixing the egt connections is = what made the MAP work again. I would guess there is a way to build a = more robust interface to the probes such that badness on one input = doesn't cause badness on another. Is there any way I can provide better = isolation outside the box? Colyn ------=_NextPart_000_061F_01C86B63.A2F8FC60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Brent,
 
While we're on that, I had a situation = with a grt=20 eis 6000 (similar to the eau that Chelton sells or used = to).
One day my MAP started indicating zero = concurrently=20 with erratic indications on several of the egt's.   On = investigating I=20 found that squeezing or moving the wire harness from the probes to the = eis=20 caused different erratic indications.  Tearing apart the wire = harness=20 revealed several spade connectors that weren't connecting=20 anymore.    It's also possible that some were shorting to = ground=20 via the shielding on adjacent probes.
 
The unexpected (for me) finding was = that fixing the=20 egt connections is what made the MAP work again.   I would = guess there=20 is a way to build a more robust interface to the probes such that = badness on one=20 input doesn't cause badness on another.  Is there any way I can = provide=20 better isolation outside the box?
 
Colyn
 
------=_NextPart_000_061F_01C86B63.A2F8FC60--