X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 14 Jun 2007 16:53:13 -0400 Message-ID: X-Original-Return-Path: Received: from [64.97.157.172] (HELO n034.sc1.he.tucows.com) by logan.com (CommuniGate Pro SMTP 5.1.9) with ESMTP id 2102782 for lml@lancaironline.net; Thu, 14 Jun 2007 14:36:40 -0400 Received-SPF: none receiver=logan.com; client-ip=64.97.157.172; envelope-from=micah@froese.com Received: from [192.168.1.102] (71.31.89.245) by n034.sc1.he.tucows.com (7.2.069.1) (authenticated as micah@froese.com) id 466E7EF50008E7D4 for lml@lancaironline.net; Thu, 14 Jun 2007 18:36:03 +0000 X-Original-Message-ID: <46718A92.9080609@froese.com> X-Original-Date: Thu, 14 Jun 2007 14:36:02 -0400 From: Micah Froese User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 X-Original-To: Lancair Mailing List Subject: Re: [LML] Re: FreeFlight 1101/ Trutrak interface/ Flight test References: In-Reply-To: Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Gentlemen,

First thanks for all the replies. My TT was wired to pin 1, J1 PFD. This did not work. After talking to Mike Huft at Chelton, he suggested wiring to pin 51 on J1 PFD. I just came back from a trip down to Florida and this setup works. The TT followed my flight plan the whole way down.

I am only getting a "hdg" mode and a "GPSS" mode right now though. I will check to see if the COM09 is on.

Micah Froese
Lancair Legacy
155 hours

Alan Adamson wrote:

Ok, I'm going to post this even tho I haven't heard back from Robert as to
"permission".  Robert, I hope you're ok with it.

*NOTE*, based upon this, the original drawings for the FF interface were
indeed correct and I've attached them for reference. (sheesh, who'd have
known).  ALSO if you are upgraded to 6.0A13, then it appears you need to
turn on a feature so that COM9 will spit out what the TT needs.

So, *if* you have a FF, it appears that wiring it to the TT will not work
unless you do what Robert suggest below.

------------Roberts email back to me---------------
I hate to say this, but the drawings are still wrong.  The problem is that
the FreeFlight Model 1201 (1101 for some of the experimental guys) outputs
an RS-232 string that does not meet NMEA-0183 (which is what the TruTrak
autopilot is expecting).  In addition, the baud rate for the FreeFlight is
around 19200.  There are two ways the user can get GPS data to the TruTrak
autopilot with the EFIS:

(1)  Wire the GPS output of the GADAHRS to the autopilot.  The GPS receiver
in the GADAHRS is an NMEA-0183 compatible unit.  This also means that the
operator must install a second GPS antenna for the GADAHRS GPS receiver.

(2)  Wire the COM09 Transmit (J1 Pin 51) to the autopilot computer.  To use
this function with EFIS software 6.0A13 or later, the "COM09 Flight Plan"
option must be selected in the limits.  COM09 will output GPS data, flight
plan data, and radio tuning data at the same time if configured in the
limits properly.  This way, the same wire out of the EFIS can be wired in
parallel to the radio and to the autopilot computer, but provide different
data.

I hope this helps.

Regards,
 
Robert DuRall

-----------------------