What's new
Van's Air Force

Don't miss anything! Register now for full access to the definitive RV support community.

Garmin G3X Touch Software V6.20 (September 12, 2018)

g3xpert

Well Known Member
Advertiser
Good Moring! As of just a few minutes ago G3X Touch software version 6.20 has been posted to the Garmin website. You can download the software here: https://www8.garmin.com/support/collection.jsp?product=010-00G3X-00

Version 6.20 contains the following changes with respect to version 6.10:
  1. Added support for GTN vertical navigation guidance
  2. Added display of VNAV target altitude to PFD (GDU 46x only)
  3. Added annunciation of secondary armed vertical flight director mode
  4. Added VFR annunciation to HSI
  5. Added Navigation configuration page
  6. Added configuration for VNAV deviation scale
  7. Added EFIS/Airdata 2 ARINC 429 output format
  8. Added GPS AGL height sentence to Text Out RS-232 format
  9. Added configuration option to invert display of elevator trim gauge when using Vertical Power position data
  10. Changed autopilot airspeed annunciation display
  11. Changed default name for coolant temperature gauge
  12. Improved interface with GNC 300XL and similar navigators
  13. Improved flight director command display across multiple displays that use different attitude sources
  14. Improved display of Mogas availability
  15. Improved airspeed comparison between multiple GSU 25Bs
  16. Improved Rotax FADEC caution/warning annunciation
  17. Improved Connext data interface
  18. General improvements to system operation
  19. Includes update to G5 software version 5.60
  20. Includes update to GDL39 software version 4.81
  21. Includes update to GEA24 software version 3.40
  22. Includes update to GMC507 software version 2.50
  23. Includes update to GTR20/200 software version 3.20
  24. Includes GAD27 software version 2.20
  25. Includes GAD29 software version 3.00
  26. Includes GDL5X software version 2.11
  27. Includes GI260 software version 2.70
  28. Includes GMA245 software version 2.40
  29. Includes GMA245 audio software version 2.20
  30. Includes GMA245 Bluetooth software version 2.00
  31. Includes GMU11 software version 2.00
  32. Includes GPS20A software version 2.20
  33. Includes GSA28 software version 4.10
  34. Includes GSU25 software version 3.70
  35. Includes GSU73 software version 3.70
  36. Includes GSU73 IGRF database version 1.03 (Base Year 2015)

Recently, we announced the release of GTN version 6.50 software. If you missed that announcement, you can read about it here: http://www.vansairforce.com/community/showthread.php?t=162365
NOTE: If you do not have a GTN navigator, the G3X Touch continues to support the same VNAV functionality as was previously available. In addition, the magenta VNAV target altitude will now be displayed above the altitude strip.

a45tAM-wGHWW-AwUwITNBOGicyiVf5uQSxxtSl8WPgO6zxbekYzNgTOCv39lp42N0NSM25Qcp3Jh4WOC8n4miEZXTOBiED4aSk35OYhdSBKxbX5gM2l4lMUx-mcxJsbZxQNwRTWeey6RmnozLUQ0LSTEYLM2KtF5hPyXRGhY7ixSpQHiDHvh-tNUvedvBGqruPSDl_7YsFE902T38lUui-EYqYtIEDBxxu9s2lNlnmjtjy-jyN30t2DLHqZsa5kEFuOj6JWF2ygRiusmWAf399WVzdJPWHX3zBkdYJ3RdIKUBYrh5csTh6nNNW4kOjxgO_Pbo0BmxewRb6o_qOOyzPEgA9T9TKtwN5yzOlVrq9KDS4vdTubUMcQj2WpB0wlvwuiiWuV7yzBmIjd4RuAHtDE4-wQAr19PMrpjnTP06wOUKJXE2XgErCqyIQk9j_gXCrocVdVHMJg8WoWlq1rjiX39is7k-RdyAUUOFlION23XVkjYrGW1X9X9HnCuB8qbq5eT0dMiNr-AUbSgjU7eZkSn9K1XzzBtNbBjqk1BUoyIv_saFZ90owCjlBmfxEeqgGSTxP1tgWlGpIg4PbQijbBuwrv1Lx9GgcB1cbgt99jQqihbRUOS36oIS6S94XpLTDB4_8pjWZj5u8ZhFo9LngHqlls-ybjPI5Pm7jYDurqhE6pS1v5NGlexYw=w135-h122-no


One of the key new features of the GTN is support for VNAV constraints at multiple waypoints in the flight plan. When loading an arrival or an approach, the GTN will auto populate the altitude constraints.

The integration of this feature in the G3X Touch enables the display of VNAV deviation and altitude constraint on the PFD. In addition, the autopilot when engaged in VNAV mode will follow the vertical descent profile. Take a look at the next post for an example approach using this new capability.

Thanks,
Levi
 
Last edited:
Example VNAV Approach

You are flying to Leadville, Colorado at 16,000 feet listening to your favorite tunes as the autopilot guides you toward your destination in NAV and ALT modes. As you approach Leadville, ATC clears you for the GPS RWY 16 approach. Upon loading the approach, each waypoint is auto populated with a vertical constraint on the GTN flight plan page.

jyGsw8kibyG52P7NyPYUOiHqbt-m_4jKgs8iUI5q2nyfX9vS-oPF3teImui9hm2tLs2Fnnn3QIVUZ-0RdOW-LmuAouZSvP0dw6jJZzDpBaDB385IUVZil7V8bNatXSbuqUqaJobVGpSzTj6OZzvdt8lia8BxWDqKWwTtwSjVHjn2ipg7eXiAVrVkXwfJdyHvs7amT3vUPmLPvhQjobZZEQhA0aarjp1UFmNEEJcCVUp-STvCqRtdr-sxNswB0-9oPPmxnOqQCFcYRASbciiQl04Cw4FY_2pG2CxY9iPahrbCjkwvvNnBzhRfVmqHruvb6yDPahsw3tmWjUbyWrRHl90fZcnSRvfceDjoVBPWFPfkytvgnYdEZAAsD8cgNExPNKH3LfpeJwRVINRZTtzBn3fDn2q0QX4UD2vM0XZMCK-dZNlzpxoCitNeBvyysdUDOW6oUEpZbI6tT1Mq533CijHJN58Cd84Kxv1XpxCnHkVTcaRyBAk3aVNs2V6GuLrQi5n7DseUVmzsCCzviZVpIB9aPjMWrC0bR-qQ-xRwj4FcnjmPX2eyZb79IAO85YiuFscHj_mdWfUMyeL1rcuzXRK6HrOJmlE1LWrKRf2vw9ZOB44qzYwL4rKGNtmAZXsK3_jCyI5tESiUbOfA2u4bWjJh8wswzgHsLGCF9KnNh1SprYvNVFeeDjHyPw=w853-h512-no

K9T_86LNTh9s6oa50h55mytk0M5F8hVVuJJH69BfjNSfJNozVjiI1u-BpEDrXFea_OgGtAqLCrhQrRj8mFkoUndIG51-TxCIlXqsciim0ujAJamE6kKiQRSw4Gc5kgp6JP7Y4d_aGf1usjbifXZWCW8e6trFNSWLqACpk2x6yHD72bAocXRzcFbil7wl5eU8ZTGHb-VhDoeL_RmU7OXecpuaMEk5hDIJaviTthPKQAtT1p3wgV_PpXMoeyg8wssnt78AYJZgV95dd6KVx0Cl_ObVOYUPb_0-UTkeXRiuy6NNsat292WSVVM3RkVH13dhg2u2owRaatz0pxj8A4NkP-UJoIhcFzoG4kb7XS5YVqYVmvvvzDasqcrOykGdwWcf3SXHTSzK4ncaOWGKThVjVTqVnLe018zakPKe3EUd2y_liBxlPaf2LZXQyCWubLEEilKhIfnxVre07zuaEsbtwMm5X8w9I7Vz8Kp2Ggyw--CSXuGA0_J2KHdVnmsK-Sy3xPRpkLc6LAolNZKOhHlLEhkSAU1RbNOfnT5P1kRUAN0_5zxPrNTxYb2URpIHVxtH-9E28_mHBuC4J1pMy7hnqQ41cVZrbrQTtZCnO8vyjm0QmGeYSXTkyYKy2pK2cucfGBTi2r-o72V9kOO91x6Mqdk21gyLfPYm1BLVIQUXdGalXwqNlmb0Z5Fbxg=w600-h266-no


Arming the VNAV autopilot mode you cruise along until you can see the top of descent (TOD) indicated on your GTN map display. As you approach the TOD, the VNAV deviation indicator begins to move down the vertical deviation indicator on the PFD. The first VNAV target altitude is shown on the PFD above the altimeter.

Oj_UZlGiorKcWClRASC93s2-7wXEzoUQx4vVW7WNE7tKAVAfs1aGyX3SHodAACaoHvIXxP1-h366JCOeMc2hTZT7sEM1fYATL9g4_WSophbKjsUgKaPqKl8JFRehFUBNM_6Jpikgwuxes0aBMu4HFkC5uIIkL4VPNEAKmWaq7E09AR9kVdQ2mNzVG92Cx_nVlIwegolfnr9iIDD3MKkf3WIlcLUAxAAl7p5Y7D-iwtL5ysWJuexaFccWSWwXoZ6VjeHCO-ApzkEQ_2RRXEEvenjkr2dl5ZjeMuqAZruNevX-6V7LZOnPHY7iAnnoHXJL8ClgS3VHKytzDCJ9GZvhOtku7C3j2V1_Decc2dSRF7z8uwY6TkveItPj4-fu77Bzheb4cOqa4Dj6HncND77Iv8dnu4mwpeZZcFxMEpDznrxJOqDYST037bxRSTY3F-tFxnXyImeBNNy9DjmOohGruFEZ3D-atDjlA2Q1ch6HjoQ0riTKcRV81_tlmfHMOJCbBf-E0ElYsMdbQ6W7j-iR7hWO78fske2TKAPog0TDnrg-YAM6HNb6o6vmq1PfvYOm7L7PM2xhVtInBx-fZGL-iodyybx8qk_HPlNQJpnpLzKxlOF-FO9WSyS3jczC6zpJ2Z5ZYItJcfiNaITzOMC0_pG56yUuLtl5jZaUDs3DZGzlyAY5V9DlpIfCLg=w853-h512-no

OMR_s4GV0tOkXX5gK00zFTXGGUWLE2nUFbo22dHOBzeBeyHkBzd4uF1YHcRKX_AUv1VFqkb7uYHvgkICetvYde4Os1MClKck5REK18dQDwP9nRL6_AKtyLDW9eYo37M0B7oGxF6hJWoqgSAkScCPm6X_Z31WDyzwerV0QLw1gr21CiD0I7hBOff1qcuakf_rTIE389FvqCNXW3PCNDzwJ0OjGEVcOdhDvg8UA9GZfy9UlgcZY0mEecwA02lx6CzjRl6HfOA_PaJPwqN89LGU4ggjottblNqSKpkzRjMHWKh43X-edosvDPW3yOn9C3ibZQPAyzIaEbXBZGbyi-iwO3C1FVp5YU_F6xkqIqqGMjwbG7IzRRmXse-KSPpxI9sZANYJsqdde9lE91EdQPpon5wMybxlJ5xHY-wh3OJKaKgWsm0yLss8Pj8PWOH8UUTxwv3jzSEyzbN-K9Gpjl70P_s60P8fpi1Zch3S5ZgmHri1C4m75yM3fFoj6jw3rphugOltgOuGvDpyihKBTCCAEbF_PJAZESnkjl0KWsxUDSuZY2cOBkpEpjiVXDVG5ewXelXG_bdUr2sobehy50exvf7Ce09VvZqoV4NLNm0IIL8rrollXXQd9hy5hm2ACKjjNgmTkN74EAdhAR6e5I-lRNfVdmzaykKAX40QOqS12SKeiCVCV9w_-L5fng=w600-h266-no


As the VNAV deviation indication centers, the autopilot captures the vertical profile and centers the VNAV deviation through the decent. The ALTV autopilot mode is automatically armed. When the VNAV constraint altitude is reached, the aircraft levels out and maintains altitude until the next VNAV descent leg.

x8CJ4YNleQfXX8yvwoz8PronoZQVr3VZ3xsycgD1_1LP6Ov67kY2-2XzOUqgn8uayBSZRJcYdnRzMR5rCyd_Dzt0JMA9DPBIRkPyQc-IhGUYDqGckb2DZvEEf1itR_WUb3MGAZBgpkJBMF6STFgBXTAnm5s9lnlCetunBrtP16uY1ER58fwmYEPWOaLjnKy3aHjb201Re8Ovj39-QYVghhCI1pcXY8sZ16QzceICQ82B4itUu_iutWQdZr1XtELsxC8L0OCugTM-r2qehKzDXr500IHcIDYJ-29qNrh3xLZBB_sOH_3kZZbEmjhGE9fb_y-BJAyA9VENaba20liEFgLYs1-Xaukj8rXiJBQHMawd3uuv1GI92OnsD6v2HHVeOWk3IhXsM5U8mqVqMvflFLH-EVH8xD6KkAW3unqlqR1dn6cgZFbqXbzFKh24u4hCRopPJYRSsMzGjClaOx_NBWHcdhyBd6ghY1uuO2bDmwMTh_JIbhQQ-iQr9EhWatu1H-wNwSBfrewMd2mh3rRmCH50OZkxKOqe8nauOAT5u-8z_KR0iWT1FF3vLZmqOFzMwKZDot3LFEmW6RsI0JNETc8sKKyi7mdxeXdYxZ_gCogg8pxoZjIDB93RTxKNvaja4oy5yKTDaLYJ0LtsndHoD_UTPJJds-2BKATq8BQKGnuGdUIMltHjqbISLw=w853-h512-no

gBvkrGbUSqUdKqVzVzlXzo9YEF6snHi5xwsESUcR-l0McFsQzDLvg49Q4FRgq9wHdLQ4fucPIaMMKQpfFiKiPert4d2mwnm0OCeCuR7sH1dzotBdPhYqwFd2IRkX92z6wKLscbs628O8VGQS6tyqEgSB9GxYEiAgb5RGpSEaHpOG0key-D5NnTL7wDcorCRXBfrVmVkHms4xsShDnXVB7gp49-J_qn0Q2T2OK3E84cfMoY3G1Jrl7wxFqOK_c954RCc8o8ffq954g1GldaevkmGhcSbYvlJGJNPsx6nSW6TjGXENJ_Beas-ocOGLz_o4p1bn68D-SLTkJd6yapN0QQiGfw5Ef2ph2EUr0vImhfL7rZqP2RQPObP_oZmwuihhHT7rEaWJg4_S2MdMynh7Kh5Wv79cpcLV4uvqYmXh7PAWmoEw7d56KisHP7AKy0863os0XM_gW4PwzpnrQkYGe_Wl_i8NjYNDgkeGqkRma4hOkXE67eIyxkBlVd5dLMF3wtzG8qqFH2vUnmc_07czBqGadvuF4HG6nO_0knFVjTezUZMnKZV48SQk4poLHSOMKNNagYI_J2OShq8wwFmnlzqEZYtzHtDJ-PdhW9YJ9pmX9j92yodS8laLElNOFEZGqujzbDkvbukXkcG0ztfu-DpsRy_MjwyrPVkmcHL7lUv3ekiE5XHtp878Xg=w600-h266-no


At any point on the last VNAV descent segment, the APPR mode can be armed. Nearing the final approach fix, the approach vertical guidance is ghosted on the deviation indicator as a gray diamond showing a preview of glidepath (GP).

4HJUnP78y6KyobNkUuCQUnYerFwsI3hAnFXKDugS04oxaLxOEavXWM0bLygPCCCdKxAfZXYipp4L3rpChAdFykBMXP2PmEKekslqw1mhGlOmMf7g_sRSMaIJEp6oKFc_s4vE1yuxQSse_3K-30sMBQPrN9wE5ky9Sb42KBUlzyBPa_UMX-icIHf8bWSLJg7Ad1ePw0018WY-XPwdH7nvaNBNZCCRsBBJazVnUERnCLQMg0lTx0RN8YN4DW698Zlsm0r7sjL4pDonSTfhzg6M0Jvdx8jrjgPKNqzlmGJ2wJXMMGPovmnUEe-8ry2uobfhAnf2ca7YJ4qw1t7nN3QCBCa-pdMXjCAmn-Tzp51uC77C2izGQ4bXvjpF1jtJ7Rd0fZNjhOrSCZLmU0EZjoTK1BMdLFHxIakI2aUJ4buyt6WU-_6wg0APGzA7HWwaXvGHt2gzdXdYQPLNuKdA-DbWBeQJbY2PULtVSg1BDhtTJ9Z79iyCAu6OEGJdgq7t0FT_9L5yhLtWPXuTpUUTMLul65qVmZ4TNSH7xmckMZgv4Rd7l1lXQlA5aVjm0fGZBvw27YlO_rxFppQuGZdHkRbITL-bmcVkJsRyhFJKYuo2IHhaoXZN4N_2-DDamUKeIy5It867hI4w5Sv_F8Cg1WzBN1hIYBwJ2XCHyQt77jcV4v3-6IfRR6UMzEnvLQ=w853-h512-no

R3_IEcAbR7c4fbUbVL3FxgLILYDDRqj5pVCZTaNnFJWe-I8wvxB0_Cg17GDP1BqdVetCzvMPApKCKN0Q7Hm6og9re6dTuXybPX-xAS4K_9khk-DrSxZ_7DkEnsvWC-7GYyqRgJK6qyEC416BLAEYcBhQgzUDfI5vdgDEQoDHEbPNoaAqTK6OIKZUIWCWnVr7-4EDAIMssLbCnrmBlJHne3v51Iqd3QVo0PMPnDGkIRQcIyCmmM9DKyXg1kQcG_YRgQRXVNy0oeONKXvdfGS-fW2fN8b6NRdpAbbxrfQIEvWzbFkVQUcneJZx387VIzY4kTPUp8QQjkurUbCaOg01dlf45i2CP0dMQk6QYmzniKzAAAIaCsoNYRZe5dvvwwWr1AvBHIU0b61pQIRk6tSBZRdDqeDCAnB2TOtnsUOdYo-I3GL0NTUizpGjR8W2Q4w5bwAmi2c1v09gdEOKGBL1miTcOK_DzjAIm28AossPyMNwN2abBh5d3Q36XO_VhydrZKtfqHDenxCuqepxlPgFzV8B64YCDIPL40GLNuJRBQdS_SjHh3JkBYaUPYLXCHh21TZCh7V1cZSfZ46BnEQBQVn2Ga2N5C2ZlU01ty1GEisbatFEQJA0c9T8KxQK5bgmCa855I6Z1J8ZQX_7YpgsGiAh6iYDbhOIRC7NpwC1bO2UI6TiHffxa0CcnA=w600-h266-no


NOTE: If APPR mode is armed prior to capturing the final VNAV descent leg, the autopilot will not capture the final VNAV descent leg.

As you cross the FAF, the autopilot captures the glidepath (GP) and flies the final approach segment.

YGPotg4Z662z0ptRK8SyJezeaMdj8Jl3MFRHRcFIqy0U889HrR6mnyxVXcOHidCviMXrXc2wSHGhThtkew_chIaFLogdS5q0GCOfKaN0oN_4I603mEaACN3DZz13z_5JdBdgrxg9Q0-okc0ZUzvBAS0Nl_aL8bOB2vJ5Qu-zPJu-7ukX3J99GVnkr1X9xLg9DzDAEuy9iwEyWqOFHWIHQ3NqRBfYbCYEpIOEmDn31DoaTE0FgUo0deffNSf2r3RjHFcNWZsCB88MFRg3NJ9-cesS8ydYZYxj0rakGydP5VOOlZmhT04EBnV1PfMAdrIK-d5k4Q9o2OcS0Ju2krT86cacjMUu0-W7Zbe2HwzMS46TL9-PkJ8KBjxvVjQxe_oNFg_G7PesX0AD61_eGVoBinfVIMzzQ-9ildCG7Dw7AIINX-6IrT5Mb_nMEpZdOThcwGdzAKr0wbl4ODcW6vFQfpvQA3W5wc7C7hahCCh-VnsdwOl5YmMSszBhw2RdsqYXYdilnNH4Vz8ZXUxcPNOQmCG5mMB8gI7l5QOdqdb9J4ndNHyANMNQdr_ZpxIFFUjv1vrvip7GWN1IFgv71_R0B9HUeDjWdTDvJztUbo15Pj6gueFIhk5Bdczmh6NpmfZLXA538fStXaAudZmvEWzMWYHrlaBwllWe8jAPnbGDI0Jm-_amaqKJT1mKKw=w853-h512-no

SpTElQlIauWi8aoaAM0Hyb8EGa8cTBCaP4QIK6uGr0H2rxYl-K68iTd0wAkedHmUT6LhS2ou1Z-U2nJ9hW3cA3_X-IrKbi0rixXSSbndRmozpWXtQfyQocQiPIFhXRWZ-Z4-f5XdaatlIgSW7DL9yiOr-o_aGhjqINQClrKb3RjATpWM2s1l6irAFR3j335V4F8mYoYseMefqcDHC9wtlI8AT5-9IIuuUxwDeAuzuHcpOTguC49KQkLoH1Mk8aqnWoufWSfcQ5UGXf3qMvJ9Q_Qwbc5_WQA0ZukhBIcE1TNu6pQnECZlWLkTvRkjTt3rPx5a_Vcg_x3mNvQ-npw51iuXCb5pmqVmWbwb1-lTbMquA0bBthDcz-8MXBxMmfmLgnLrRJkHzFx4yhpKIndPRDxxwJaY5nHZG5ew6f0NvRo3RpBv77RmW_JHU_C03fQYeEysY0Leh2ebVCTaOzFBdfq-wjPEUwcgrNK-HCMaLuvL6rHeIt25dD4ofSK5ssjQ3ZZ5CveQZM3XBoSnec8Z5NBqOCZDUlchqviCmKjXmBOOR3IQII6NyWFH2M7UeeNgMDvhef-zHM2AXeXobc0IoJk7bs8wwfeSKMDLHn525QnlMxyWOWMrktPmRaaD3o6EtOHbWKEpZjkBzE9DzEp_cAruVyfimYQj7MHej1sTF7w2afdU__xW7U6Kig=w600-h266-no


The new VNAV capabilities introduce a new level of automation to the G3X Touch allowing the autopilot to fly both the lateral and vertical profiles from cruise to your missed approach point with just two button presses. After the approach is loaded, arm the VNAV autopilot mode. Once you are on your final VNAV descent leg, arm APPR mode and the autopilot will capture your glide path for the final segment of the approach. It really is that simple!
There are new configuration settings to allow you to enable and customize this new feature.

To get the additional VNAV information out of the GTN, the GTN GPS A429 output will need to be changed from "GAMA FORMAT 1" to "GARMIN 429". Also, verify that the GTN A429 input is set to EFIS Format 2, but this didn't change.

Thanks,
Levi
 
Last edited:
I don't see a G3x 429 input option for EFIS Format 2. Might you mean the 429 Output?

My input options are Garmin GPS, Garmin VOR/ILS, or None.

EDIT: I suspect this is actually in the GTN config, not the G3X config.
 
Last edited:
To get the additional VNAV information out of the GTN, the GTN GPS A429 output will need to be changed from "GAMA FORMAT 1" to "GARMIN 429". Also, verify that the G3X Touch configuration is set to EFIS Format 2 for the A429 input.

Thanks,
Levi

Levi,

I changed to “GARMIN 429” and lose my VNAV button.

2hz6zww.jpg


do8ns4.jpg


If I switch back to GAMA FORMAT 1 the VNAV button reappears. Do I need to select the “UPDATE CONFIG MODULE” button after changing to Garmin 429?

17tfyo.jpg
 
Levi,

I changed to “GARMIN 429” and lose my VNAV button.

If I switch back to GAMA FORMAT 1 the VNAV button reappears. Do I need to select the “UPDATE CONFIG MODULE” button after changing to Garmin 429?

Hello Anthony,

Your configuration is fine.

When you are using external flight planning with GTN V6.50 and later, the VNAV function is provided by the GTN since it now has this capability built-into the flight planning.

Thanks,
Steve
 
Hello Anthony,

Your configuration is fine.

When you are using external flight planning with GTN V6.50 and later, the VNAV function is provided by the GTN since it now has this capability built-into the flight planning.

Thanks,
Steve


Steve, Thanks for the quick reply- love the excellent support, and the QWERTY keyboard!!:)
 
Hello G3Xperts!

I installed the newest G3X and GTN updates this morning and went out to test them. I fly coupled IFR quite a bit these days so that is the area I am testing at present. I have some questions. GTN650, G3X touch, GX Pilot

First, I am a bit confused on when to switch from VNAV to APPR mode for the coupled approach glide path intercept. For reference, the approach I flew twice today was KBKV RNAV 9. I set up north of the airport at 2500 feet (500 over the approach altitude). I then loaded and activated RNAV 9 starting at DEWIX. Selected autopilot NAV and VNAV on the G3X. Garmin flew me to DEWIX at 2500 turned towards ASKEH and started descent to 2000 as expected with the target altitude right where you said it would be.. Ok, I’m on the approach clicked APPR...and it took me back to 2500. Oops..Garmin didn’t like that, this time I’ll wait until the descents are done and it’s looking for a glide path. Broke off and reset again. Garmin flew me to DEWIX at 2500, turned to ASKEH and descended to 2000, from ASKEH turned inbound to OWAGO and descended to 1800. One thing to note, it waits until it has a 700ish descent rate to cross that point at proper altitude then dives to it. A 200’ descent at 700fpm went pretty quick. I clicked APPR, but had missed the GP so altitude was no longer coupled. Ok, fine...I hand flew it from there. First question is, when are we supposed to switch to APPR mode and why can’t VNAV and APPR be on at the same time and simply perform a handoff inside the box?

Second question, while I understand the safety behind staying high for as long as poissible, can the VNAV descent rate be adjusted in the GTN? Hmm, just occurred to me...is that controlled in the G3X?

Please keep in mind I was limited on time today so only took a couple runs at it. It’s entirely possible I missed something simple and I am happy to take the public flogging if I have. I love the new keyboard by the way!

Cheers!
 
Last edited:
Did the 6.2/6.5 update yesterday and went on a couple flights. I noticed that since the update the beeps seem a bit distorted. I'm talking about the AP disconnect, 1000' and 200' beeps.

Has anyone else noticed this?
 
Changing default flight path angle

Hello G3Xperts!

I installed the newest G3X and GTN updates this morning and went out to test them. I fly coupled IFR quite a bit these days so that is the area I am testing at present. I have some questions. GTN650, G3X touch, GX Pilot

First, I am a bit confused on when to switch from VNAV to APPR mode for the coupled approach glide path intercept. For reference, the approach I flew twice today was KBKV RNAV 9. I set up north of the airport at 2500 feet (500 over the approach altitude). I then loaded and activated RNAV 9 starting at DEWIX. Selected autopilot NAV and VNAV on the G3X. Garmin flew me to DEWIX at 2500 turned towards ASKEH and started descent to 2000 as expected with the target altitude right where you said it would be.. Ok, I’m on the approach clicked APPR...and it took me back to 2500. Oops..Garmin didn’t like that, this time I’ll wait until the descents are done and it’s looking for a glide path. Broke off and reset again. Garmin flew me to DEWIX at 2500, turned to ASKEH and descended to 2000, from ASKEH turned inbound to OWAGO and descended to 1800. One thing to note, it waits until it has a 700ish descent rate to cross that point at proper altitude then dives to it. A 200’ descent at 700fpm went pretty quick. I clicked APPR, but had missed the GP so altitude was no longer coupled. Ok, fine...I hand flew it from there. First question is, when are we supposed to switch to APPR mode and why can’t VNAV and APPR be on at the same time and simply perform a handoff inside the box?

Second question, while I understand the safety behind staying high for as long as poissible, can the VNAV descent rate be adjusted in the GTN? Hmm, just occurred to me...is that controlled in the G3X?

Please keep in mind I was limited on time today so only took a couple runs at it. It’s entirely possible I missed something simple and I am happy to take the public flogging if I have. I love the new keyboard by the way!

Cheers!

ColoRv,

With regard to explaining the exact behavior you saw, I would recommend you contact us via email and provide the datalog from your flight. We can take a look and let you know exactly what was happening.

You can change the default flight path angle on the GTN. To do this, go to the home menu, then select "Utilities", then select "VNAV". On the VNAV page, press "menu" at the bottom of the screen. A page will pop up to allow you to set the default VNAV angle. The default angle is 3.00 degrees. You may want to set this to a more shallow angle.

With regard to arming APPR mode, if you see the ghosted Glide Path (GP) indicator coming down the vertical deviation indicator, you could go ahead and allow the autopilot to capture GP rather than using VNAV for the final descent to the FAF. APPR mode should always be armed prior to the FAF.

At this time, the ability to arm both VNAV and APPR modes is not available in the G3X Touch, but we are considering this as a future enhancement.

Thanks,
Levi
 
Last edited:
ColoRv,

With regard to explaining the exact behavior you saw, I would recommend you contact us via email and provide the datalog from your flight. We can take a look and let you know exactly what was happening.

You can change the default flight path angle on the GTN. To do this, go to the home menu, then select "Utilities", then select "VNAV". On the VNAV page, press "menu" at the bottom of the screen. A page will pop up to allow you to set the default VNAV angle. The default page is 3.00 degrees. You may want to set this to a more shallow angle.

With regard to arming APPR mode, if you see the ghosted Glide Path (GP) indicator coming down the vertical deviation indicator, you could go ahead and allow the autopilot to capture GP rather than using VNAV for the final descent to the FAF. APPR mode should always be armed prior to the FAF.

At this time, the ability to arm both VNAV and APPR modes is not available in the G3X Touch, but we are considering this as a future enhancement.

Thanks,
Levi


Thanks Levi. I?ll attack the next flight with all of that in mind. Just a new buttonology to get used to I suspect. I believe you?re going to want that VNAV/APPR handoff to be automatic if you can work it out.
 
GTN Screenshots?

Unrelated to the latest software updates....how are you taking screenshots of the GTN?

Is this actually a feature or are you guys using some fancy simulator?

If this is already a capability, I must have overlooked it. It would come in very handy.
 
Screenshot

Just press and hold the Menu button (you will get a message that the shot has been taken) and the picture is stored on the SD card.

Andy
 
Just press and hold the Menu button (you will get a message that the shot has been taken) and the picture is stored on the SD card.

Andy

...but first check that you have the Screen Shot option turned on in the setup pages. I don't believe it defaults on.
 
GTN Screenshots

Unrelated to the latest software updates....how are you taking screenshots of the GTN?

Is this actually a feature or are you guys using some fancy simulator?

If this is already a capability, I must have overlooked it. It would come in very handy.

Jeff, our bench software supports GTN screenshots, but I do not believe it is available in the released software. I will follow up with the software team and see if that is a possible future improvement.

Pat/Andy, you are correct in your response for the G3X Touch, but the question was specifically referencing the GTN.

Thanks,
Levi
 
Thanks Levi for all this great information. One question: I'm having trouble finding what you describe as, "the approach vertical guidance is ghosted on the deviation indicator as a gray diamond showing a preview of glidepath (GP)."

I see the white diamond on the vertical deviation indicator on your screenshot, but not a gray one.

I'm sure it's staring me right in the face. Again, thanks for the tutorial.
 
Last edited:
Thanks Levi for all this great information. One question: I'm having trouble finding what you describe as, "the approach vertical guidance is ghosted on the deviation indicator as a gray diamond showing a preview of glidepath (GP)."

I see the white diamond on the vertical deviation indicator on your screenshot, but not a gray one.

I'm sure it's staring me right in the face. Again, thanks for the tutorial.

Spirko, You are on the right path! It looked somewhat gray on the display, but does look mostly white in the screenshot.

Thanks,
Levi
 
I took another run at it today. RNAV 27 at BKV starting at PABBI @ 2500ft. VNAV drops altitude to 2k prior (mostly) to AZBOG. Approaching IGNAQ VNAV is waiting for the last minute descent to 1800 when the white diamond starts down the vertical deviation indicator. Push APPR and shortly thereafter the vertical deviation indicator disappears. GP still in the autopilot bar but it?s no longer coupled. Holds 2k. Next flight I?ll try waiting until the VNAV starts the 200? dive for IGNAQ. I am really glad I didn?t jump into an actual IFR flight with this new update. I?m sure the buttonolgy will get easier once I figure out WHAT IT WANTS, but it is not intuitive, at least not for me. I?ve flown this system in a lot of IFR this year with nothing but wonder at how amazing it is.
 
I took another run at it today. RNAV 27 at BKV starting at PABBI @ 2500ft. VNAV drops altitude to 2k prior (mostly) to AZBOG. Approaching IGNAQ VNAV is waiting for the last minute descent to 1800 when the white diamond starts down the vertical deviation indicator. Push APPR and shortly thereafter the vertical deviation indicator disappears. GP still in the autopilot bar but it?s no longer coupled. Holds 2k. Next flight I?ll try waiting until the VNAV starts the 200? dive for IGNAQ. I am really glad I didn?t jump into an actual IFR flight with this new update. I?m sure the buttonolgy will get easier once I figure out WHAT IT WANTS, but it is not intuitive, at least not for me. I?ve flown this system in a lot of IFR this year with nothing but wonder at how amazing it is.

ColoRv,

Unfortunately, there is just not enough information to determine what is happening in your situation. I have been watching the G3Xpert inbox. Please send us your data log if you would like us to help you determine why the system is behaving in this way.

I think it is worth noting that if you were to fly the system in the same way you did in the past, ignoring all the new VNAV items, the system will function as it did prior to 6.20. In that case, you would typically perform a descent in Vertical Speed mode down to the altitude in which you pick up the glide path and then arm the approach. If you are uncomfortable using the new features, especially in a situation where you are relying on it, I would recommend operating it in the way that you best understand.

One final thought, if you are seeing the white diamond on the vertical deviation indicator, there is no issue with capturing the Glide Path (GP) versus relying on VNAV to descend you the last 200 feet to the FAF. However, if you cross the glide path and now the vertical deviation indicator is showing you as above the flight path, the autopilot will not descend to capture the GP.

Thanks,
Levi
 
I think what he described he did was what this note posted earlier addresses:

“NOTE: If APPR mode is armed prior to capturing the final VNAV descent leg, the autopilot will not capture the final VNAV descent leg.”

I may be wrong but that is how I read it.
 
I think what he described he did was what this note posted earlier addresses:

?NOTE: If APPR mode is armed prior to capturing the final VNAV descent leg, the autopilot will not capture the final VNAV descent leg.?

I may be wrong but that is how I read it.

So just for ref how do you know when the final VNAV leg is captured?
 
So just for ref how do you know when the final VNAV leg is captured?

Not sure, I think when the VNAV indicator turns green. I have not flown it yet. Was going to today but the wind is howling here as the edge of the hurricane has arrived here.
 
I think what he described he did was what this note posted earlier addresses:

?NOTE: If APPR mode is armed prior to capturing the final VNAV descent leg, the autopilot will not capture the final VNAV descent leg.?

I may be wrong but that is how I read it.

I believe that is what is happening as well. Levi said earlier that you can activate approach mode once the diamond starts down but I tried that twice and it failed each time. The issue is the final VNAV is only 200? and the GTN waits till the last minute to make that descent so the diamond is well down the deviation indicator before that VNAV captures. I?ll wait for it on the next flight and see if that does it, but having to time that APPR push that tight seems like something Garmin may want to address. Make the descents less aggressive and therefore further out and let VNAV hand off to APPR automatically.

Or maybe I?m just hamfisting the whole thing. :) I?m sure we will all figure this out, and I will get them the log they requested next time I?m out there. Mostly I?m trying to figure out what the system wants me to do, so that I can do it....then see if it responds as expected. At present, I?m still a bit confused on when the APPR mode should be activated.
 
You are flying to Leadville....

As the VNAV deviation indication centers, the autopilot captures the vertical profile and centers the VNAV deviation through the decent. The ALTV autopilot mode is automatically armed. When the VNAV constraint altitude is reached, the aircraft levels out and maintains altitude until the next VNAV descent leg.

x8CJ4YNleQfXX8yvwoz8PronoZQVr3VZ3xsycgD1_1LP6Ov67kY2-2XzOUqgn8uayBSZRJcYdnRzMR5rCyd_Dzt0JMA9DPBIRkPyQc-IhGUYDqGckb2DZvEEf1itR_WUb3MGAZBgpkJBMF6STFgBXTAnm5s9lnlCetunBrtP16uY1ER58fwmYEPWOaLjnKy3aHjb201Re8Ovj39-QYVghhCI1pcXY8sZ16QzceICQ82B4itUu_iutWQdZr1XtELsxC8L0OCugTM-r2qehKzDXr500IHcIDYJ-29qNrh3xLZBB_sOH_3kZZbEmjhGE9fb_y-BJAyA9VENaba20liEFgLYs1-Xaukj8rXiJBQHMawd3uuv1GI92OnsD6v2HHVeOWk3IhXsM5U8mqVqMvflFLH-EVH8xD6KkAW3unqlqR1dn6cgZFbqXbzFKh24u4hCRopPJYRSsMzGjClaOx_NBWHcdhyBd6ghY1uuO2bDmwMTh_JIbhQQ-iQr9EhWatu1H-wNwSBfrewMd2mh3rRmCH50OZkxKOqe8nauOAT5u-8z_KR0iWT1FF3vLZmqOFzMwKZDot3LFEmW6RsI0JNETc8sKKyi7mdxeXdYxZ_gCogg8pxoZjIDB93RTxKNvaja4oy5yKTDaLYJ0LtsndHoD_UTPJJds-2BKATq8BQKGnuGdUIMltHjqbISLw=w853-h512-no

gBvkrGbUSqUdKqVzVzlXzo9YEF6snHi5xwsESUcR-l0McFsQzDLvg49Q4FRgq9wHdLQ4fucPIaMMKQpfFiKiPert4d2mwnm0OCeCuR7sH1dzotBdPhYqwFd2IRkX92z6wKLscbs628O8VGQS6tyqEgSB9GxYEiAgb5RGpSEaHpOG0key-D5NnTL7wDcorCRXBfrVmVkHms4xsShDnXVB7gp49-J_qn0Q2T2OK3E84cfMoY3G1Jrl7wxFqOK_c954RCc8o8ffq954g1GldaevkmGhcSbYvlJGJNPsx6nSW6TjGXENJ_Beas-ocOGLz_o4p1bn68D-SLTkJd6yapN0QQiGfw5Ef2ph2EUr0vImhfL7rZqP2RQPObP_oZmwuihhHT7rEaWJg4_S2MdMynh7Kh5Wv79cpcLV4uvqYmXh7PAWmoEw7d56KisHP7AKy0863os0XM_gW4PwzpnrQkYGe_Wl_i8NjYNDgkeGqkRma4hOkXE67eIyxkBlVd5dLMF3wtzG8qqFH2vUnmc_07czBqGadvuF4HG6nO_0knFVjTezUZMnKZV48SQk4poLHSOMKNNagYI_J2OShq8wwFmnlzqEZYtzHtDJ-PdhW9YJ9pmX9j92yodS8laLElNOFEZGqujzbDkvbukXkcG0ztfu-DpsRy_MjwyrPVkmcHL7lUv3ekiE5XHtp878Xg=w600-h266-no


.....

Thanks,
Levi

I see that the autopilot will start descent even though the altitude preselect wasn't changed for lower altitude (still at 16000). Would this be an open descent with no altitude restriction?

If the preselected altitude would be 14000ft -will the aircraft level of at 14000ft or will it just follow the vertical path and ignore the preselect if VNAV is active?
 
still not sure how this works

I've flown 3 approaches in the last week and non of them were successful using VNAV to automatically capture and descend down to IAF altitude. Am I correct to assume to this feature is to be used or can be used well before reaching the approach phase of flight? Example, 50 miles out on an airway with certain altitude restrictions, once the white diamond shows up, I can start using VNAV, correct?
I'm feeling a little dumb trying to get this to work but I see I'm not the only one having issues. Maybe Garmin can hold a short training class or do a 15 minute video.

Thanks
AB
 
I see that the autopilot will start descent even though the altitude preselect wasn't changed for lower altitude (still at 16000). Would this be an open descent with no altitude restriction?

If the preselected altitude would be 14000ft -will the aircraft level of at 14000ft or will it just follow the vertical path and ignore the preselect if VNAV is active?

When VNAV mode is selected, the FD/AP follows the VNAV descent profile indicated by the magenta arrow on the vertical deviation indicator on the PFD. The target VNAV altitude is the indicated in magenta above the altimeter and the preselected altitude indicator.

The preselected altitude has nothing to do with VNAV mode.

EDIT: But it does determine which mode is armed for altitude capture during the descent. Either ALTV (VNAV target altitude) or ALTS (Preselected Altitude). Whichever one would be intercepted first on the descent is which one gets armed when VNAV mode is selected.
 
Last edited:
I've flown 3 approaches in the last week and non of them were successful using VNAV to automatically capture and descend down to IAF altitude. Am I correct to assume to this feature is to be used or can be used well before reaching the approach phase of flight? Example, 50 miles out on an airway with certain altitude restrictions, once the white diamond shows up, I can start using VNAV, correct?
I'm feeling a little dumb trying to get this to work but I see I'm not the only one having issues. Maybe Garmin can hold a short training class or do a 15 minute video.

Thanks
AB

Did your GTN's flight plan have altitude values listed beside the flight plan waypoints prior to the IAF? As far as I can tell, only the approach waypoint altitudes are pre-populated when an approach is loaded and activated. If there are no altitudes tied to the waypoints prior to the IAF, the GTN has no idea how to calculate the VNAV profiles. It is my understanding that the pilot can add and manipulate waypoint altitudes manually if they wish.

Assuming an approach has been loaded and is active...When approaching the TOD point just prior to the IAF, you must have VNAV armed or it will not capture it when the magenta arrow starts down the VDI. The magenta arrow is the VNAV indicator. The white (Garmin calls it Grey) diamond is the GP indicator before GP capture. If you fly thru the VNAV calculated profile, it is too late and you have lost the opportunity to use VNAV to get down.

To capture the GP, you must arm APR mode before you fly thru the GP. Once captured, the Grey diamond will turn Magenta and the AP mode annunciator will switch the GP mode from armed (Grey) to active (Green).

If you wait till the the Grey GP indicator is coming down, you have lost the opportunity to use VNAV and should just go straight to arming APR mode. If you fly thru the GP, it is too late to capture it...

I have flown several practice approaches with these new features and so far they seem to work as described by Levi. I have not tried using VNAV prior to the IAF long before the approach starts.
 
Last edited:
SNIP>>>>Make the descents less aggressive and therefore further out <<<<SNIP

You can adjust the angle that the GTN uses to calculate the decent profile. I think the default is 3° which in this case seems to be about the same as the GP on the approach you were shooting which is likely why you had issues with it. You could adjust this variable to better suit the way you normally fly descents by hand.

There is a supplement to the manual for the GTN ver 6.50 here:

http://static.garmin.com/pumac/190-01004-19_A.pdf
 
Last edited:
When VNAV mode is selected, the FD/AP follows the VNAV descent profile indicated by the magenta arrow ....

The preselected altitude has nothing to do with VNAV mode.

If the preselect altitude has no influence on the ap/fd when flying in VNAV -no altitude capture would happen if a lower altitude is preselected (lets say 15000ft in this case)

-is this correct?

-what do you do if ATC tells you to stop descent and level off at 15000? Would you have to change to another vertical mode?
 
If the preselect altitude has no influence on the ap/fd when flying in VNAV -no altitude capture would happen if a lower altitude is preselected (lets say 15000ft in this case)

-is this correct?

-what do you do if ATC tells you to stop descent and level off at 15000? Would you have to change to another vertical mode?

If you are in VNAV mode and ALTV is armed you will level off at 1400 in this case above.

EDIT: Levi added some clarification below see his post for how it really works.

Bottom line, if "ALTV" is armed, it will level off at the "VNAV Target Altitude". If "ALTS" is armed, it will level off at the "Preselected Altitude". In VNAV mode if the pilot moves the "Preselected Altitude" to a value between the current altitude and the "VNAV Target Altitude", the system will automatically switch the armed mode from "ALTV" to "ALTS" and level off at the "Preselected Altitude".
 
Last edited:
If you are in VNAV mode and ALTV is armed you will level off at 1400 in this case above.

If you want to stop descent at 15000, enter 15000 as the preselected altitude, select VS mode to continue descent and this will arm ALTS mode. When the plane gets to the preselected altitude it will capture 150000 and switch the armed ALTS mode to active ALT.

Here is a slight correction to the above statement.

VNAV will descend away from the altitude preselector if you are in ALT mode and have VNAV armed. For instance, if you are cruising at 15,000 feet, AP in ALT mode and altitude preselect at 15,000 feet, and you arm VNAV, the AP will capture VNAV and descend from the cruising altitude. If you leave the altitude preselect at 15000 feet, the VNAV mode will descent to the VNAV altitude constraint.

However, if you move the altitude preselect bug to an altitude below you, the VNAV mode will not descend through the preselected altitude. When you reach your preselected altitude, the autopilot will transition to ALT hold mode.

This behavior is consistent between the legacy simple VNAV and the new GTN VNAV.

Thanks,
Levi
 
Any chance you guys (Garmin) have made a video showing the VNAV descent usage on the GTN/G3X system yet?

I found the other quick how-to videos extremely useful. I haven't flown our plane in a few months so I'm having a hard time visualizing how to do this.
 
I don’t have a GTN

All of this new VNAV stuff being discussed here is GTN enabled by the latest firmware revisions. The built in G3X Touch VNAV function is pretty basic. Similar to what is included in the Garmin handheld GPS units.

Check out page 79 of the user manual for the VNAV function and page 306 for how it can be used with the Garmin AFCS (Autopilot/Flight Director).

http://static.garmin.com/pumac/190-01754-00_K.pdf
 
Last edited:
Sloppy Auto pilot turns

I completed the recent upgrade to both GTN625 and G3X. Upgrade installs went fine, all seems to work as before except autopilot tracking in turns. Just completed a long IFR cross country and every time the course changed more than a few degrees on the heading the GSA 28 autopilot turned too late to make a smooth turn. It over-turned (banked to late) and had to turn back sharply to regain the course track. All this turning caused me to lose altitude and I had to disengage the autopilot on two or three occasions to get back on course.

Never had this issue prior to the updates. Is the any settings to adjust in either the GTN or G3X that will fix this?

Steve
 
I completed the recent upgrade to both GTN625 and G3X. Upgrade installs went fine, all seems to work as before except autopilot tracking in turns. Just completed a long IFR cross country and every time the course changed more than a few degrees on the heading the GSA 28 autopilot turned too late to make a smooth turn. It over-turned (banked to late) and had to turn back sharply to regain the course track. All this turning caused me to lose altitude and I had to disengage the autopilot on two or three occasions to get back on course.

Never had this issue prior to the updates. Is the any settings to adjust in either the GTN or G3X that will fix this?

Steve

Hello Steve,

If you were laterally coupled to the GTN on this trip, it is quite possible that your G3X system is no longer receiving roll steering guidance from the GTN and you would need to re-verify your ARINC 429 settings.

Lateral coupling doesn't have anything to do with altitude hold, so it sounds like you have autopilot adjustments that need to be made there.

It would be best to contact us directly by phone or email shown below.

Thanks,
Steve
 
Just completed a long IFR cross country and every time the course changed more than a few degrees on the heading the GSA 28 autopilot turned too late to make a smooth turn. It over-turned (banked to late) and had to turn back sharply to regain the course track.

Mine has always done something like this. What I think is going on (based on autopilot design courses taken 45 years ago) is that the autopilot *always* goes into course capture mode and initiates at 40 degree intercept course. Only then does it check to see what's really required, and by then, it has overshot when it goes into track mode. What should happen is that the autopilot should see if it is close enough in cross track distance and rate that it can go straight into track mode without doing the 40 degree intercept bit.
 
Back
Top