Sender: <marv@lancaironline.net>
To:  lml@lancaironline.net
Date: Tue, 03 Sep 2013 09:38:58 -0400
Message-ID: <redirect-6451964@logan.com>
Received-SPF: pass
 receiver=logan.com; client-ip=206.46.173.17; envelope-from=skipslater@verizon.net
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=original
From: "Skip Slater" <skipslater@verizon.net>
References: <list-6451473@logan.com>
In-reply-to: <list-6451473@logan.com>
Subject: Re: [LML] Re: Apollo/Garmin SL30 & MX20

Hope you find the problem.  These things can be maddening!

----- Original Message ----- 
From: "Greenbacks, UnLtd." <N4ZQ@VERIZON.NET>
To: "List Lancair Mailing" <lml@lancaironline.net>
Sent: Monday, September 02, 2013 7:31 PM
Subject: [LML] Re: Apollo/Garmin SL30 & MX20


Hi Skip,

The issue is simply that the MX20 is unable to see the serial data output 
from the SL30 and so the MX20 displays an amber NAV flag. So in switching 
from GPS to NAV mode, the destination VOR or ILS feathers are not 
highlighted in magenta. I've got the header tank off at the moment so I'll 
be checking for correct wiring in the morning. The MX20 is configured 
correctly with Port 3 for NAV.

Time will tell...

ps. One might ask why the header tank is off.....Both Lightspeed Plasma III 
modules were returned to the manufacturer due to a 10º difference in timing
at idle with vacuum disconnected. One module was operating correctly but the 
other had drifted significantly. Notwithstanding the fact that these 
ignition modules went out of warranty years ago, Klaus confirmed my 
diagnosis, repaired the one unit and calibrated both at no charge. Can't ask 
for more that!

Angier Ames
N4ZQ


--
For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.html