X-Virus-Scanned: clean according to Sophos on Logan.com Return-Path: Sender: To: lml@lancaironline.net Date: Thu, 14 Jun 2007 18:47:03 -0400 Message-ID: X-Original-Return-Path: Received: from wx-out-0506.google.com ([66.249.82.229] verified) by logan.com (CommuniGate Pro SMTP 5.1.9) with ESMTP id 2103045 for lml@lancaironline.net; Thu, 14 Jun 2007 17:34:52 -0400 Received-SPF: pass receiver=logan.com; client-ip=66.249.82.229; envelope-from=akadamson@gmail.com Received: by wx-out-0506.google.com with SMTP id t11so854132wxc for ; Thu, 14 Jun 2007 14:34:15 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:references:subject:date:message-id:mime-version:content-type:x-mailer:x-mimeole:thread-index:in-reply-to:sender; b=GHizUB5JzYpyzx3wSE9PAIE1eKj2ax3Hw0lFi0GMdc1sksomRpDSHzn+NvHhYfewNzP0KSRWB85k15bGZb7H7z9AH45MXEmKHLTFE+MkaAH9wbqnYLYeyXZcfgF4MDHDAccqec7kaiwC0i/D1vw4G0PUvIEGQ4L5bYXOOA5HH/w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:references:subject:date:message-id:mime-version:content-type:x-mailer:x-mimeole:thread-index:in-reply-to:sender; b=fceThLpo1EU+/aNRQBtajvH9W5L3Z4mCpinwv8Y/RybeZ/lK0BO4YnjTrWjGMxMj0kOcgE8W2oKZaPCgrfRsnsHDWF76HMiKQQZ1rA5NemYlSyfRVOxu37L2CBveAJGDBvsZgg4E8qW4gWX9zalZHwTs2mZxtnlj0eChQmMJgWE= Received: by 10.90.102.20 with SMTP id z20mr2228632agb.1181856855070; Thu, 14 Jun 2007 14:34:15 -0700 (PDT) X-Original-Return-Path: Received: from Typhoon ( [76.97.47.101]) by mx.google.com with ESMTP id 3sm3403465wrs.2007.06.14.14.34.14 (version=SSLv3 cipher=RC4-MD5); Thu, 14 Jun 2007 14:34:14 -0700 (PDT) From: "Alan Adamson" X-Original-To: "'Lancair Mailing List'" References: Subject: RE: [LML] Re: FreeFlight 1101/ Trutrak interface/ Flight test X-Original-Date: Thu, 14 Jun 2007 17:34:14 -0400 X-Original-Message-ID: <003a01c7aecb$c1d20870$2201a8c0@highrf.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01C7AEAA.3AC06870" X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: Aceuxgjvww/Qz19uRGK3/kzILjwdpAABYq8Q In-Reply-To: X-Original-Sender: Alan Adamson This is a multi-part message in MIME format. ------=_NextPart_000_003B_01C7AEAA.3AC06870 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Ah, *if* you didn't have the pinpoint or the 425 out there, then there was *no* GPS (nmea) data going to the TT on pin 1. Pin 51 should do the trick, but make sure that the feature that Robert mentioned is turned on if you have 6.0A13 Let us know, glad it worked. Alan _____ From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of Micah Froese Sent: Thursday, June 14, 2007 4:53 PM To: lml@lancaironline.net Subject: [LML] Re: FreeFlight 1101/ Trutrak interface/ Flight test 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 ----------------------- -- For archives and unsub http://mail.lancaironline.net:81/lists/lml/List.html ------=_NextPart_000_003B_01C7AEAA.3AC06870 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
Ah, *if* you didn't have the pinpoint or the = 425 out there,=20 then there was *no* GPS (nmea) data going to the TT on pin 1.  Pin = 51=20 should do the trick, but make sure that the feature that Robert = mentioned is=20 turned on if you have 6.0A13
 
Let us know, glad it = worked.
 
Alan

From: Lancair Mailing List=20 [mailto:lml@lancaironline.net] On Behalf Of Micah = Froese
Sent:=20 Thursday, June 14, 2007 4:53 PM
To:=20 lml@lancaironline.net
Subject: [LML] Re: FreeFlight 1101/ = Trutrak=20 interface/ Flight test

Gentlemen,

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

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

Micah Froese
Lancair Legacy
155 = hours


Alan=20 Adamson wrote:=20 
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,
=20
Robert DuRall

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

--

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