X-Virus-Scanned: clean according to Sophos on Logan.com X-SpamCatcher-Score: 1 [X] Return-Path: Sender: To: lml Date: Sat, 23 Dec 2006 22:56:02 -0500 Message-ID: X-Original-Return-Path: Received: from mx1.pshift.com ([216.57.116.6] verified) by logan.com (CommuniGate Pro SMTP 5.1.4) with ESMTP id 1710005 for lml@lancaironline.net; Sat, 23 Dec 2006 22:52:13 -0500 Received-SPF: none receiver=logan.com; client-ip=216.57.116.6; envelope-from=colyncase@earthlink.net Received: from ccaselt (unverified [216.57.118.129]) by mx1.pshift.com (Vircom SMTPRS 4.35.480.0) with SMTP id for ; Sat, 23 Dec 2006 22:51:26 -0500 Received-SPF: none (mx1.pshift.com: domain of colyncase@earthlink.net does not designate any permitted senders) X-Modus-BlackList: 216.57.118.129=OK;colyncase@earthlink.net=OK X-Modus-RBL: 216.57.118.129=Excluded X-Modus-Trusted: 216.57.118.129=NO X-Original-Message-ID: <016201c7270e$c3d155d0$7410020a@nvidia.com> From: "colyncase on earthlink" X-Original-To: "Lancair Mailing List" References: Subject: Re: [LML] Re: D2 Update X-Original-Date: Sat, 23 Dec 2006 19:51:16 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_015F_01C726CB.B55E9640" 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_015F_01C726CB.B55E9640 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mike, I think you meant crossbow not pinpoint. ----- Original Message -----=20 From: MikeEasley@aol.com=20 To: lml=20 Sent: Saturday, December 23, 2006 7:39 PM Subject: [LML] Re: D2 Update I spoke to the Pinpoint guy at Oshkosh. He was very careful selecting = his words when I asked about the Chelton/D2AV situation. He basically = told me that the problem was isolated and corrected, but their product = got dropped from the experimental side of Chelton anyway. He described = the problem as a slow booting circuit in the AHRS, in other words, = systems were booting in the wrong order. Once they found of what was = happening (difficult since it didn't happen very often) it was fairly = simple to correct. I'm not sure about the timing of the fix with the decision to drop = Pinpoint, but what I've described above may play into this whole thing. Mike Easley Colorado Springs Super ES ------=_NextPart_000_015F_01C726CB.B55E9640 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Mike,
    I think you meant crossbow not pinpoint.
----- Original Message -----
From:=20 MikeEasley@aol.com
To: lml
Sent: Saturday, December 23, = 2006 7:39=20 PM
Subject: [LML] Re: D2 = Update

I spoke to the Pinpoint guy at Oshkosh.  He was very careful = selecting his words when I asked about the Chelton/D2AV = situation.  He=20 basically told me that the problem was isolated and corrected, but = their=20 product got dropped from the experimental side of Chelton = anyway.  He=20 described the problem as a slow booting circuit in the AHRS, in = other=20 words, systems were booting in the wrong order.  Once they found = of what=20 was happening (difficult since it didn't happen very often) it was = fairly=20 simple to correct.
 
I'm not sure about the timing of the fix with the decision to = drop=20 Pinpoint, but what I've described above may play into this whole = thing.
 
Mike Easley
Colorado Springs
Super ES
------=_NextPart_000_015F_01C726CB.B55E9640--