G1000 and Garmin Flightstream in the Mooney

[PaulM]

40 minutes ago, LANCECASPER said:

If I already have the GTX345R will this need to be re-loaded?

I'm pretty sure that if you update to the .37 software.  Each software reload will put in the manifests from that software card.   That will be the GTX33ES firmware version.   Fixing the version is the only item on that  special 3X5R manifest. 

I see that it is page D27 in Rev 9.   I was referencing an older rev. 

[LANCECASPER]

29 minutes ago, PaulM said:

I'm pretty sure that if you update to the .37 software.  Each software reload will put in the manifests from that software card.   That will be the GTX33ES firmware version.   Fixing the version is the only item on that  special 3X5R manifest. 

I see that it is page D27 in Rev 9.   I was referencing an older rev. 

I am already running 401.37 software.

 

Page D27 Rev 9 comes from the link you posted.

[PaulM]

9 minutes ago, LANCECASPER said:

I am already running 401.37 software.

Then it should only be adding the 3 wires between the MFD and FS210 and setting the port to Connext Format 1.   (unless that other Cirrus manifest is required) 

That should be the minimum to enable the flight plan transfer.. The other wires to the GDL69 and 345R are only needed to get the complete FS210 experience.  Transfer, ADSB, + GDL69a control. 

[LANCECASPER]

5 minutes ago, PaulM said:

Then it should only be adding the 3 wires between the MFD and FS210 and setting the port to Connext Format 1.   (unless that other Cirrus manifest is required) 

That should be the minimum to enable the flight plan transfer.. The other wires to the GDL69 and 345R are only needed to get the complete FS210 experience.  Transfer, ADSB, + GDL69a control. 

Thanks, that's very helpful.

[MatthiasArnold]

A big thank you to @LANCECASPER & @PaulM for putting all the pieces together.

Some additional remarks regarding typical G1000 installations found across Europe.

• Since Sirius XM services are unavailable in Europe, the GDL69 is of little to no use. However, it remains installed mainly to avoid confusing/messing up the G1000 system (otherwise we would have to install Charly weights instead ;-)
  • IMHO for the FS210 install, the wiring to GDL69 RS232 #1 and all configuration should be done for the exact same reason: to prevent any confusion within the G1000 system.
• Because we lack ground based ADS-B services that provide traffic or WX information, we can only receive ADS-B position signals from equipped aircraft. As a result the GTX33ES is typically installed in our G1000 Mooneys instead of GTX345R i.
  • For traffic information the GTX33ES is often complemented by an AirAvionics AT-1 or one of its predecessors connected to the G1000 MFD which provides traffic information via Mode-S (proximity & altitude only), ADS-B- in, FLARM in and sends out ownership position via FLARM out.
    The AT-1 configuration of G1000 RS232/AirInc423  is provided manually anyways (no config file available):
    • ADS-B in (traffic only) AT-1
    • ADS-B out: GTX33eS
    • FLARM in: AT-1
    • FLARM out: AT-1 (with antenna diversity)
  • FLARM is particularly useful, as there is a significant amount of glider traffic between March and November—most of which is invisible to radar. (One notable exception was a glider riding a wave at FL270 in the Frankfurt region; he was on radar frequency, but that’s another story!)
  • For satellite based in-flight WX Information we often utilize an Iridium satellite transceiver provided by Golze Engineering (typically no G1000 MFD integration)
  • Long story short: since the GTX33ES SW is provided by 0401.37 we typically don't have to fiddle with GTX345R updates or different gtx.rgn files.
• Of course we have to do the wiring from FS210 to MFD RS232#3 as described above and provide the configuration with CONNEXT Format 1 in/out.
• Last but not least remains the question which exact "magic" Cirrus configuration file is required (if any at all)..

Let's get this integration done!

Best,

Matthias