Garmin GTN 6XX/7XX Descent Vertical Navigation, July 18, 2018

[g3xpert]

Originally Posted by Mark Dickens

I posted this earlier, but I think it got lost in the Labor Day postings. I'd like to get an answer please:

"I went out this morning and set up a short cross country, using a "along track offset" waypoint to see if my Dynon autopilot would couple to the VNAV signal from the 650. Nope. In fact, other than telling me when to descend, that feature was almost useless. No glidepath indication, nothing. Is the 650 not putting out the glidepath info through the A429 stream? It works for LPV approaches, why not enroute VNAV? Am I missing something?"

Hello Mark,

VNAV (VPATH) guidance is different from glidepath/glideslope approach guidance, and thus anyone providing support for VNAV A429 data would need to add this support separately.

Garmin has already added this support and released new V5.50 software for G5 systems (with/without autopilot), and is currently testing the new V6.20 software with this capability for G3X Touch systems.

Thanks,
Steve

[Mark Dickens]

Originally Posted by g3xpert

Hello Mark,

VNAV (VPATH) guidance is different from glidepath/glideslope approach guidance, and thus anyone providing support for VNAV A429 data would need to add this support separately.

Garmin has already added this support and released new V5.50 software for G5 systems (with/without autopilot), and is currently testing the new V6.20 software with this capability for G3X Touch systems.

Thanks,
Steve

Thank you! I'll go hammer Dynon now

[N49ex]

Hi Steve,

Just installed the GTN750 6.50 SW, and love the keyboard update! AND!!! The DISTd export error on active approaches is fixed!!!! Thanks!!!

So now, can we in experimental world also get the GDL-88 SW updates free please? I get the periodic loss of ADS-B IN data that is referred to in the GDL service bulletin, and the GDL SW can be updated from the GTN...But the local shop wants a bunch of $$.

Thanks!
Reinhard Metz

[RONSIM]

"Barometric altitude lost" ------is the message I am getting on my 650 --- popped up after installing 6.5 --


FAA ADS-B Report says everything is working (transponder, encoder, ads-b_


Suggestions?


Ron

[g3xpert]

Originally Posted by RONSIM

"Barometric altitude lost" ------is the message I am getting on my 650 --- popped up after installing 6.5 --


FAA ADS-B Report says everything is working (transponder, encoder, ads-b_


Suggestions?


Ron

Hello Ron,

Have you checked to see if the input on your GTN which is supposed to receive this data from some other device in your aircraft is still properly configured?

Feel free to contact us directly by email if you would like.

Thanks,
Steve

[RONSIM]

Steve, as always, appreciate your attention ----- before doing the 6.5 update, I took pictures of each of my configuration screens. I have gone back over those and did not detect any changes. I also checked my G327 TXP for any changes --- none detected.

I did notice, on one of the main screens (forget which one -- setup, utilities, etc??? ) there was a window I had not noticed before, something like "VNAV enable" ---- I have that enabled.

Anyway, apparently no one else has experienced this, so I will contact you by email ---- by the way --- Love the keyboard!!

Ron

[jthocker]

Check your ARINC settings on the 650. 650 to G3X touch is EFIS format 2
and GAMA format 1.

When I upgraded a couple of 650/ G3X touches I got that same Baro message.
I had inadvertently set the arinc to EFIS format 1. They had worked flawlessly with that setting until the 650 upgrade.

[g3xpert]

Originally Posted by jthocker

Check your ARINC settings on the 650. 650 to G3X touch is EFIS format 2
and GAMA format 1.

When I upgraded a couple of 650/ G3X touches I got that same Baro message.
I had inadvertently set the arinc to EFIS format 1. They had worked flawlessly with that setting until the 650 upgrade.

Hello Jon,

Needing to configure the GTN EFIS/Airdata input to EFIS Format 2 is nothing new (see page 27-29 of Rev. AF G3X Installation manual), but as you say, perhaps you were getting away with using the other format until this GTN version.

Thanks for sharing this tip.

While we are on the subject of GTN A429 settings, the GTN GPS A429 output will need to be changed from "GAMA FORMAT 1" to "GARMIN 429" when GTN V6.50 is used with G3X Touch V6.20 to allow the new VNAV capability to work.

Thanks,
Steve

[RONSIM]

I changed my ARINC setting from EFIS Format 3 to EFIS Format 2 ----- the Baro message went away!

As always --- I appreciate the forum and the help it provides!

Have a great day and pray for the folks in the Southeast!

Ron

[Spirko]

Looks like G3X GDU 46x v6.20 is out,

At the top of the list of Changes made from version 6.10 to 6.20 is:
"Add support for GTN vertical navigation guidance"

Thank you Steve and G3X team.

Has anyone loaded it yet? I'm excited to use the new GTN s/w, I'll probably update my GTN and G3X today.

-Craig