X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 08 Aug 2013 12:31:12 -0400 Message-ID: X-Original-Return-Path: Received: from slow1-d.mail.gandi.net ([217.70.178.86] verified) by logan.com (CommuniGate Pro SMTP 6.0.5) with ESMTP id 6409097 for lml@lancaironline.net; Thu, 08 Aug 2013 12:18:58 -0400 Received-SPF: none receiver=logan.com; client-ip=217.70.178.86; envelope-from=Tim@MyRV10.com Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by slow1-d.mail.gandi.net (Postfix) with ESMTP id CF48347A980 for ; Thu, 8 Aug 2013 18:18:23 +0200 (CEST) Received: from mfilter3-d.gandi.net (mfilter3-d.gandi.net [217.70.178.133]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id 0B61BA80C4 for ; Thu, 8 Aug 2013 18:18:08 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter3-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter3-d.gandi.net (mfilter3-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id yhABBExzDAUe for ; Thu, 8 Aug 2013 18:18:06 +0200 (CEST) X-Originating-IP: 74.115.8.177 Received: from [10.100.125.110] (unknown [74.115.8.177]) (Authenticated sender: send10@myrv10.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 12CFFA80EB for ; Thu, 8 Aug 2013 18:18:05 +0200 (CEST) X-Original-Message-ID: <5203C4BC.30108@MyRV10.com> X-Original-Date: Thu, 08 Aug 2013 11:18:04 -0500 From: Tim Olson User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 X-Original-To: Lancair Mailing List Subject: Re: [LML] Re: Chelton and TAWS Failure (with Pinpoint system) References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------050305040100030805010708" This is a multi-part message in MIME format. --------------050305040100030805010708 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit One possibility I have for you. I didn't think of this before. I know that some menus just aren't there on the PFD that are on the MFD, and some that are on the PFD aren't on the MFD. It doesn't matter if you are on the PFD screen on the MFD, it still doesn't show up. For instance.... if you go into heading mode, the LNAV key will come up on screen 1 (the screen coded as the PFD). That key is not there on the screens 2 and 3 in my plane.....even if I'm on the PFD page. So, it could be a screen numbering issue. Mine are numbered 1, 2 ,3 I know some people have done 0,1 or others. I would say make sure you start at #1. The menu-faults is on the MFD, so use screen 2 to check that.....it just may not be that screen 1 does it. (it may, but I just have never tried that so I can't verify...but I know the MFD does it) Tim On 8/8/2013 9:10 AM, John Barrett wrote: > Agreed about Robert DuRall. He is very helpful and knowledgable. > However, he did not have the answer to lack of TAWS. Also he could > not give me a clue how to correct the persistent lack of "Faults" > submenu that is supposed to be useful in researching fault warnings as > they occur. > > If anyone has a clue why that submenu would not be accessible, I'd > love to hear it. Basically, that slot on the left side of the screen > is simply blank. It's like the strike finder submenu that just > doesn't show up unless you have the Strikefinder installed. > > Best, > John Barrett --------------050305040100030805010708 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
One possibility I have for you.=C2=A0 = I didn't think of this before.
I know that some menus just aren't there on the PFD that are on the MFD,
and some that are on the PFD aren't on the MFD.=C2=A0 It doesn't ma= tter if you
are on the PFD screen on the MFD, it still doesn't show up.

For instance.... if you go into heading mode, the LNAV key will come up
on screen 1 (the screen coded as the PFD).=C2=A0 That key is not th= ere
on the screens 2 and 3 in my plane.....even if I'm on the PFD page.

So, it could be a screen numbering issue.

Mine are numbered 1, 2 ,3

I know some people have done 0,1 or others.

I would say make sure you start at #1.

The menu-faults is on the MFD, so use screen 2 to check that.....it just may not be that screen 1 does it.
(it may, but I just have never tried that so I can't verify...but I know the MFD does it)

Tim

On 8/8/2013 9:10 AM, John Barrett wrote:
Agreed about Robert DuRall. =C2=A0He is very helpful and knowledgable. However, he did not have the answer to lack of TAWS. =C2=A0Also he could not give me a clue how to correct the persistent lack of "Faults" submenu that is supposed to be useful in researching fault warnings as they occur.

If anyone has a clue why that submenu would not be accessible, I'd love to hear it. =C2=A0Basically, that slot on th= e left side of the screen is simply blank. =C2=A0It's like the stri= ke finder submenu that just doesn't show up unless you have the Strikefinder installed.

Best,
John Barrett

--------------050305040100030805010708--