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:39:25 -0500 Message-ID: X-Original-Return-Path: Received: from imo-m14.mx.aol.com ([64.12.138.204] verified) by logan.com (CommuniGate Pro SMTP 5.1.3) with ESMTP id 1705313 for lml@lancaironline.net; Sat, 23 Dec 2006 20:47:12 -0500 Received-SPF: pass receiver=logan.com; client-ip=64.12.138.204; envelope-from=MikeEasley@aol.com Received: from MikeEasley@aol.com by imo-m14.mx.aol.com (mail_out_v38_r7.6.) id q.c64.8a82e3f (29672) for ; Sat, 23 Dec 2006 20:46:22 -0500 (EST) From: MikeEasley@aol.com X-Original-Message-ID: X-Original-Date: Sat, 23 Dec 2006 20:46:20 EST Subject: Re: [LML] D2 Update X-Original-To: lml@lancaironline.net MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-----------------------------1166924780" X-Mailer: 9.0 Security Edition for Windows sub 5354 X-Spam-Flag: NO -------------------------------1166924780 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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 -------------------------------1166924780 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

I spoke to the Pinpoint guy at Oshkosh. He was very careful selec= ting=20 his words when I asked about the Chelton/D2AV situation. He basically=20= told=20 me that the problem was isolated and corrected, but their product got droppe= d=20 from the experimental side of Chelton anyway. He described the=20 problem as a slow booting circuit in the AHRS, in other words, systems=20= were=20 booting in the wrong order. Once they found of what was happening=20 (difficult since it didn't happen very often) it was fairly simple to=20 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

-------------------------------1166924780--