G1000 and Garmin Flightstream in the Mooney

[Farolone]

I have been searching all forums and only read "it's not possible". Now I have it in my Mooney and it is working like a charm. 

 

[LANCECASPER]

4 hours ago, Farolone said:

I have been searching all forums and only read "it's not possible". Now I have it in my Mooney and it is working like a charm. 

 

That's great to hear

What software are you running in the G1000? 401.37?

Can the shop that did yours explain the installation and how they got it to work?

@Pmaxwell was hopeful that this could be done at some point.

@AVDB Michel do you know how to make this work?

[Schllc]

BOOM!!!!

Sign me up!  this is one of the only substantial changes the NXI brought to the g1000.  

IF they can make this work with a legacy g1000 that is huge!!!

Who did this install?

its registered in germany, i didn't think the acclaim was certified in europe, thats why all of them kept the us tails...  this is awesome but not sure if it is legal.  I sure hope it is!

[exM20K]

Want.

[midlifeflyer]

3 hours ago, Schllc said:

Sign me up!  this is one of the only substantial changes the NXI brought to the g1000.  

Believe it or not, even in the NXi, it's an airframe manufacturer choice.  My flying club had a Diamond DA40 NG with the NXi. Turned out Diamond blocked access to regular Connext so we had to have portable ADS-B if we wanted weather and traffic on our iPads. 

[Farolone]

That's great to hear
What software are you running in the G1000? 401.37?
Can the shop that did yours explain the installation and how they got it to work?
[mention=14708]Pmaxwell[/mention] was hopeful that this could be done at some point.
[mention=18998]AVDB[/mention] Michel do you know how to make this work?

Yes, .37 and some compnents of the cirris G1000. 100% legal.


Gesendet von iPhone mit Tapatalk

[dkkim73]

@Farolone This is very cool!!! 

I agree with @Schllc, it is one of the big "missing pieces" in terms of function between the legacy G1000 and NXi. May I ask how you accomplished this? Did you use the Garmin HSDB with another device like a GI-275, or a Flightstream device (210 or 510)? Or some other magic box :)?

Or perhaps even just a SW switch/fix?  I know some folks out there actually offer services hacking G1000's, showing alternate backgrounds, etc, but that sounds a bit like unknown territory? 

Thanks,

David

 

[LANCECASPER]

2 hours ago, dkkim73 said:

@Farolone This is very cool!!! 

I agree with @Schllc, it is one of the big "missing pieces" in terms of function between the legacy G1000 and NXi. May I ask how you accomplished this? Did you use the Garmin HSDB with another device like a GI-275, or a Flightstream device (210 or 510)? Or some other magic box :)?

Or perhaps even just a SW switch/fix?  I know some folks out there actually offer services hacking G1000's, showing alternate backgrounds, etc, but that sounds a bit like unknown territory? 

Thanks,

David

 

@Farolone mentioned in his initial post that it's a Flightstream 210, in fact the title of the post mentions the Flightstream.  The video he provided shows no GI-275. He has since said that he runs 401.37 software.

 

The ability to use the Flightstream 210 was included in the base software that is included in 401.37 since Cirrus uses that. This was mentioned over 4 years ago in the post announcing 401.37

 

[dkkim73]

1 hour ago, LANCECASPER said:

@Farolone mentioned in his initial post that it's a Flightstream 210, in fact the title of the post mentions the Flightstream.  The video he provided shows no GI-275. He has since said that he runs 401.37 software.

...

The ability to use the Flightstream 210 was included in the base software that is included in 401.37 since Cirrus uses that. This was mentioned over 4 years ago in the post announcing 401.37

...

Got it. Was moving too fast. So it feels almost like a feature flag that is turned off. IIRC some Acclaim owners with the 2700 RPM STC would somehow choose an Ovation profile to get the right #s and redlines in the G1000 (apologies if I'm butchering the specifics). Kind of makes me wonder if it has to do with what aircraft the G1000 is thinking it's in. He did mention some Cirrus parts (I do kind of wish I had the keypad, but where would it go? ;))

D

[Schllc]

31 minutes ago, dkkim73 said:

Got it. Was moving too fast. So it feels almost like a feature flag that is turned off. IIRC some Acclaim owners with the 2700 RPM STC would somehow choose an Ovation profile to get the right #s and redlines in the G1000 (apologies if I'm butchering the specifics). Kind of makes me wonder if it has to do with what aircraft the G1000 is thinking it's in. He did mention some Cirrus parts (I do kind of wish I had the keypad, but where would it go? ;))

D

I had the keypad. It is grossly overrated and actually an impediment in the cockpit of the Mooney. Furthermore it is rendered almost useless when you have a phone with garmin pilot or ForeFlight. 
the biggest issue I have with the g1000 is airways.
ATC never provides transitions and without that you often don’t have the option for the airway.  On the ground it’s just a minor inconvenience but on reroutes in the air it’s a pia. 
typing the clearance in your phone and sending to the NXI was flawless and the one thing I really miss from the ultra. 

[Farolone]

Very busy right now, will post details on the weekend.

[Farolone]

FS210 and G1000: 
Sorry for the delay: My Mooney was for 2 Month in AVIONIK Straubing (https://www.avionik.de) where the figured it out, the contact Persons are Mr. Schub Software, Mr. Schönsteiner Operations. 
The first thing was the .37 Software update.
The problem when the Flightstream 210 is installed,  Bluetooth is showing up, but you cannot connect to it. This needs some software adaptations. As far as I heard, Cirrus G1000 Software is involved. And there are Emails from Garmin (don't know the contact persons) that confirm the first time that it works, and giving help how it works. (as in the past the GARMIN answer always was: Is neither intended nor possible.) As I am engineer but not an avionics guy, I will send some configuration screenshots and the part number with the hope it will help you. 
All I can say it is absolute game changer for the G1000 in the Mooney!

22082024_AUTHORIZED RELEASE CERTIFICATE.pdf

[Farolone]

Yes, I told them that there would be some demand for that. 

They do not give out there numbers, but here's the central number: ‭+49 9429 94240‬

You can refer to the D-EVIF.

 

[PaulM]

As I theorized in a previous thread, I knew it would work.. If a software rev has the feature, it is there, just that the default config templates (that are airframe specific) won't include it. you just have to configure the interfaces by hand. 

I have all of the Cirrus wiring diagrams related to this and everything is documented in the FS210 Install manual/wiring diagram except for the 2 wires from the MFD.   Those would connect to RS323 #3.   (as shown in the picture) 

I still need to get .37 installed,  and convince the tech to add the extra wires.   Two annuals ago I had a number of extra wires run from the front to the back to be able to connect the FS210 and a ARTEX1000 to include the NEMA datastream from a GIA63W.  (Also in the Cirrus wiring) 

[Schllc]

1 hour ago, PaulM said:

As I theorized in a previous thread, I knew it would work.. If a software rev has the feature, it is there, just that the default config templates (that are airframe specific) won't include it. you just have to configure the interfaces by hand. 

I have all of the Cirrus wiring diagrams related to this and everything is documented in the FS210 Install manual/wiring diagram except for the 2 wires from the MFD.   Those would connect to RS323 #3.   (as shown in the picture) 

I still need to get .37 installed,  and convince the tech to add the extra wires.   Two annuals ago I had a number of extra wires run from the front to the back to be able to connect the FS210 and a ARTEX1000 to include the NEMA datastream from a GIA63W.  (Also in the Cirrus wiring) 

Is that something you could forward so I could help Brian K figure out how do this for everyone?

[PaulM]

55 minutes ago, Schllc said:

Is that something you could forward so I could help Brian K figure out how do this for everyone?

Sure, lets build this.. #1 FS210 install manual

https://www.rvplane.com/pdf/Garmin/FlightStream210IM.pdf

Pages B2 (Power)   B3  GDL69 connection    B5  RS232 to the GTN (G1000 GDU1000 MFD) 

GTX345R install manual:

http://www.aeroelectric.com/Installation_Data/Garmin/Garmin_GTX3X5_InstallationManualRev9-2017-06.pdf

D37  shows a RS232 and RS422 rather than 2 RS422.. 

From the cirrus wiring diagrams:
http://servicecenters.cirrusdesign.com/tech_pubs/SR2X/pdf/wm/SR22/html/wmmain.asp

FS210: diagram  24-50-08 Page 12   Shows GDL69, and wires to UAT and MFD

MFD: diagram 31-60-02 Page 9   Shows Data Link (210) connected to RS232 #3  (Matches picture in previous post) 

Once all wires are configured, you must turn off bluetooth on the GTX345R, configure and update the FS210.  

Update the G1000 to .37.    the GTX345 needs different configurations after GDU software v15.X , you can find them in the GTX3x5 manual above. Page C11 & C12

Manually configure GDU#2 RS232 #3 to protocol Connext Format 1 (in & out) 
There will be some config in the GDL69 page  for RS232 #3 Connect format ?, and the GTX345R needs to be set for Connext format 3  Input and Output. 

There will also be a G1000 manifest to load the  GTX345R which is needed after the .37 update since .37 still expects a GTX33ES. 
Remember your 8GB terrain cards and the 4.9arc terrain database for SynVis.   (it will technically fit on the 4GB cards if you don't have approach plates. )

[LANCECASPER]

On 1/31/2025 at 5:15 PM, PaulM said:

GTX345R install manual:

http://www.aeroelectric.com/Installation_Data/Garmin/Garmin_GTX3X5_InstallationManualRev9-2017-06.pdf

D37  shows a RS232 and RS422 rather than 2 RS422.. 

Thank you for all of the effort you put into this.

There is no page D37 in the GTX345R install manual. Page D27 maybe?

[LANCECASPER]

On 1/31/2025 at 5:15 PM, PaulM said:

From the cirrus wiring diagrams:
http://servicecenters.cirrusdesign.com/tech_pubs/SR2X/pdf/wm/SR22/html/wmmain.asp

FS210: diagram  24-50-08 Page 12   Shows GDL69, and wires to UAT and MFD

On this link the Table of Contents only goes to 24-50-05

Edit: It looks like 34-50-08 applies

[MatthiasArnold]

31-60-02 page 9
To my understanding ANFS2740-22 connects FS210 (not GDL69A) with the MFD GDU?

34-50-08 page 12

[LANCECASPER]

On 1/31/2025 at 5:15 PM, PaulM said:

Sure, lets build this.. #1 FS210 install manual

https://www.rvplane.com/pdf/Garmin/FlightStream210IM.pdf

Pages B2 (Power)   B3  GDL69 connection    B5  RS232 to the GTN (G1000 GDU1000 MFD) 

GTX345R install manual:

http://www.aeroelectric.com/Installation_Data/Garmin/Garmin_GTX3X5_InstallationManualRev9-2017-06.pdf

D37  shows a RS232 and RS422 rather than 2 RS422.. 

From the cirrus wiring diagrams:
http://servicecenters.cirrusdesign.com/tech_pubs/SR2X/pdf/wm/SR22/html/wmmain.asp

FS210: diagram  24-50-08 Page 12   Shows GDL69, and wires to UAT and MFD

MFD: diagram 31-60-02 Page 9   Shows Data Link (210) connected to RS232 #3  (Matches picture in previous post) 

Once all wires are configured, you must turn off bluetooth on the GTX345R, configure and update the FS210.  

Update the G1000 to .37.    the GTX345 needs different configurations after GDU software v15.X , you can find them in the GTX3x5 manual above. Page C11 & C12

Manually configure GDU#2 RS232 #3 to protocol Connext Format 1 (in & out) 
There will be some config in the GDL69 page  for RS232 #3 Connect format ?, and the GTX345R needs to be set for Connext format 3  Input and Output. 

There will also be a G1000 manifest to load the  GTX345R which is needed after the .37 update since .37 still expects a GTX33ES. 
Remember your 8GB terrain cards and the 4.9arc terrain database for SynVis.   (it will technically fit on the 4GB cards if you don't have approach plates. )

Avionik Straubing in Germany is also telling me that there is a Cirrus config file that needs to be downloaded from the Garmin DRC (Dealer Resource Center?). Do you know which file that would be?

[PaulM]

21 hours ago, LANCECASPER said:

Thank you for all of the effort you put into this.

There is no page D37 in the GTX345R install manual. Page D27 maybe?

Hmm.. figure D-18 page D26... (I think I wrote that from another install manual first). 

As for requiring a specific manifest from Cirrus, I can't say.    Many of the configuration expansions for GDL88 and GTX345R were done by manually updating the config on the RS485 and RS232 ports, manifests weren't required.    This might be one of the, you can do it by loading the cirrus manifest.. but you can also do it by setting the Connext format manually.  No matter what you will need a Garmin tech to load the 345R manifest which is an update to the gtx.rgn 

[LANCECASPER]

1 minute ago, PaulM said:

Hmm.. figure D-18 page D26... (I think I wrote that from another install manual first). 

As for requiring a specific manifest from Cirrus, I can't say.    Many of the configuration expansions for GDL88 and GTX345R were done by manually updating the config on the RS485 and RS232 ports, manifests weren't required.    This might be one of the, you can do it by loading the cirrus manifest.. but you can also do it by setting the Connext format manually.  No matter what you will need a Garmin tech to load the 345R manifest which is an update to the gtx.rgn 

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

[LANCECASPER]

3 minutes ago, PaulM said:

Hmm.. figure D-18 page D26... (I think I wrote that from another install manual first). 
 

Figure D-18 is on page D27 and shows the connection between the GTX345/345R and the FS210.

 

[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.