Garmin 796 connections

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Does anyone know if it’s possible to download flight plans from a IFD to a handheld 796 via Bluetooth or WiFi?  I have it hardwired now and it communicates fine if the protocol “Aviation Out” is used. 

Problem is that my MLB100 wants protocol “ADSB+”. This results in my IFD ADS-B traffic always reporting: “ADSB degraded”. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ronl Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 Apr 2015 Status: Offline Points: 88	Post Options Post Reply Quote ronl Report Post Thanks(0) Quote Reply Topic: Garmin 796 connections Posted: 15 Nov 2017 at 3:34pm
	Does anyone know if it’s possible to download flight plans from a IFD to a handheld 796 via Bluetooth or WiFi? I have it hardwired now and it communicates fine if the protocol “Aviation Out” is used. Problem is that my MLB100 wants protocol “ADSB+”. This results in my IFD ADS-B traffic always reporting: “ADSB degraded”.
	Ron L

dmtidler Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 12 Feb 2016 Location: USA Status: Offline Points: 617	Post Options Post Reply Quote dmtidler Report Post Thanks(0) Quote Reply Posted: 15 Nov 2017 at 4:44pm
	I don't know about the Bluetooth or WiFi connection between an IFD and Garmin 796; however, prior to the 10.2.0 software, the IFD could only output "Aviation Out" on one RS232 channel. Since both your 796 and MLB100 appear to be sharing the same RS232 output channel, it may be fairly simple for your avionics shop to separate those devices and put the MLB100 on another unused RS232 output channel. I had a similar situation where prior to the 10.2.0 software upgrade, my MLB100 GPS input, ELT GPS input, and engine monitor GPS input all shared the same IFD RS232 output channel with "Aviation Out". This was the way it had to be wired because of the IFD's single "Aviation Out" channel limitation before 10.2.0. It was fairly simple for my avionics shop to move the MLB100 RS232 GPS input from where the three devices were junctioned and put it in an unused IFD RS232 output channel with ADSB+ data. This change (as well as reconfiguring the MLB100 to receive ADSB+) corrected the "ADSB degraded" message I had prior to the wiring change.

ronl Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 08 Apr 2015 Status: Offline Points: 88	Post Options Post Reply Quote ronl Report Post Thanks(0) Quote Reply Posted: 15 Nov 2017 at 7:02pm
	Thanks, We may have to add additional 232 wiring to get it all working. I was trying to find a way to avoid that because it requires removal of the entire radio stack in my Cirrus. Very invasive.
	Ron L