Sender: <marv@lancaironline.net>
To:  lml@lancaironline.net
Date: Tue, 06 Dec 2011 15:23:46 -0500
Message-ID: <redirect-5294584@logan.com>
Received-SPF: none
 receiver=logan.com; client-ip=216.12.62.56; envelope-from=weinsweigd@tsnci.com
From: "Dr. Weinsweig" <weinsweigd@tsnci.com>
Subject: [LML] Re: cheltons losing gps signal
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

hi all,

i received the following below from cobham(chelton) technical support who =
has been responsive once i got ahold of the proper person.  apparently the =
fellow i dealt with there previously has retired(david black).

interestingly, on my flight to pittsburgh on Sunday to see the steelers =
whoop up on the bengals(GO STEELERS!),  the cheltons did the same thing =
with approximately 20 minutes of no gps signal which then normalized  for =
the end of the flight and landing but on the return flight yesterday for =
the first time since the software and hardware update everything worked =
fine with no chelton gps outages.=20

 to be continued........

david weinsweig
n750dw propjet
weinsweigd@gmail.com=20
304-633-5221

> I suspect you are having a GPS receiver thermal shutdown issue. Since =
the NO GPS flag is consistent at 25 minutes into flight and comes back =
after a cooling down period of approximately another 25 minutes. If =
possible, look at the COM Port Inspector on either the PFD or MFD when you =
get the NO GPS flag. Can you reproduce this on the ground without the =
engine running?
>=20
> The GPS come in on COM1. You should be able to see GPS Lat, Long, and =
Altitude if the GPS is working. COM Port Inspector looks at the incoming =
data without any EFIS processing. This will tell you if the GPS is working =
or not.=20
>=20