Received-SPF: pass
 receiver=logan.com; client-ip=206.46.173.7; envelope-from=N4ZQ@VERIZON.NET
Content-type: text/plain; charset=iso-8859-1
MIME-version: 1.0 (Apple Message framework v1085)
Subject: Re: Re: Apollo/Garmin SL30 & MX20
From: "Greenbacks, UnLtd." <N4ZQ@VERIZON.NET>
In-reply-to: <9824BEEA-4C1C-4C89-B74A-B9691A70F7EA@VERIZON.NET>
Date: Mon, 02 Sep 2013 22:31:50 -0400
Content-transfer-encoding: quoted-printable
Message-id: <47D6BE8B-4CED-4507-81AA-9CF69F8F54FF@VERIZON.NET>
References: <listdigest-6450790@logan.com>
 <9824BEEA-4C1C-4C89-B74A-B9691A70F7EA@VERIZON.NET>
To: List Lancair Mailing <lml@lancaironline.net>

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.=20

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=BA 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