|
|
I was really getting confused...one of the attachments is my exact
setup...Chelton IUD1, Pinpoint ADAHRS, FreeFlight 1101, Garmin SL30, and
Garmin 430 and TT Sorcerer. I wired the Pinpoint and the Freeflight
using J1, pin 51 as advised by D2A and everything works. I recently
upgraded to 6.0A13 and everything continued to work. I guess my COM09
Flight Plan option is selected, but I don't think I did it. I'll check
tonight.
Chat Daniel
Super ES
-----Original Message-----
From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of
Alan Adamson
Sent: Thursday, June 14, 2007 10:50 AM
To: lml@lancaironline.net
Subject: [LML] Re: FreeFlight 1101/ Trutrak interface
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
-----------------------
Hopefully this will clear up the point.
Alan
-----Original Message-----
From: Lancair Mailing List [mailto:lml@lancaironline.net] On Behalf Of
Tim
Olson
Sent: Thursday, June 14, 2007 2:22 AM
To: lml@lancaironline.net
Subject: [LML] Re: FreeFlight 1101/ Trutrak interface
That was one of my thoughts as I was writing my last reply.....the old
"IF
the Freeflight speaks in NMEA".
I figured someone else must know more (Alan ;)) because I don't have a
Freeflight so I haven't gone down that road yet.
Great point though Rob...you probably can't just wire a FF like a PP and
have it work.
Tim
Rob Logan wrote:
> > here are the updated drawings for the FF, last I checked the FF
> doesn't do nema (why its not -2 chelton code) and the TT wants nema.
> (only for heading not for flight path) if thats still the case, this
> print will not work.. (the PP does nema and would work fine into the
> TT leaving the FF to chelton)
>
> but what do I know, perhaps a call to the mfg is in order...
> http://cheltonflightsystems.com/contact.html
>
> Rob
>
> --
> For archives and unsub
> http://mail.lancaironline.net:81/lists/lml/List.html
>
--
For archives and unsub
http://mail.lancaironline.net:81/lists/lml/List.html
|
|