March 13, 20215 yr Hi, appologies if this is a really supid question but if I'm in a plane with dual GTN 750 & 650 I manually enter a flight plan into the 750 is there any way to automatically syncrhonize with a 650 so the plan gets a copied across to that unit as well ? I can see you could pre-build the flight plan and load it from the catalogue onto each device but I'm wondering if there's a more ad-hoc way of doing it. Cheers
March 13, 20215 yr Hi, The feature you're looking for is named "cross-fill" and this is only available in our GNS V2 at this time.
March 13, 20215 yr This may help... The GTN trainer units do not have cross fill at this time. Make your own by importing the same flightplan into both units manually. Follow below. Flight plan storage locations are... ---------------------------------RXP GTN 750/650 X-Plane Virtual datacard folder for storage of flight plans ".gfp" and user waypoints ".wpt" must be initially created as FPLN and located here.. C:\ProgramData\Garmin\Trainers\Databases\FPLN -----------------------------------RXP GNS 530W/430W V2 X-Plane Virtual datacard folder for storage of flight plans ".fpl" and user waypoints. This folder must be initially created, named FPL and be located in the GNS Trainer Data folder... C:\ProgramData\Garmin\GNS Trainer Data\GNS\FPL ------------------------------------ 1] Use a program like Littlenavmap to create the flightplan. This can be from scratch or a copy of the plan in your avionics. 2] Export the flightplan as .gfp for GTN, .fpl for GNS V2, .fms for X-Plane, etc to the appropriate storage locations. Note...Littlenavmap now has one button export for many types of flightplans. 3] Import the flightplan .gfp into your RXP GTN units...one unit at a time. Now the GTN 750 and GTN 650 have imported the same plan. https://www.avsim.com/forums/forum/780-little-navmap-little-navconnect-little-logbook-support-forum/
March 14, 20215 yr Author Thanks for the information. To honest it's slightly reassuring that I wasn't being a fool and missing something complete obvious 🙂 Edited March 14, 20215 yr by Matchstick
March 14, 20215 yr 2 hours ago, Matchstick said: Thanks for the information. To honest it's slightly reassuring that I wasn't being a fool and missing something complete obvious 🙂 If you start the routine of importing flight plans into the GTN I highly recommend you look through "pinned" topics to head off some frustrations. There is one near the top of the list in the RXP FSX/P3D GTN forum here but it applies to the xPlane version as well as the potential issues are filters or rules built into the Garmin Trainer, which is common to both. In essence the two major issues are waypoint names with duplicates in the Garmin database, and approach procedures such as arrivals, departures, and sometimes even runway numbers. The arrivals and departures names sequence over time (CHICKN3 becomes CHICKN4) and runway numbers change due to geo shift. 30 becomes 29. In essence, the more complexity you add in to the flight plan with an external flight planner, the more likely it will fail to import. Adding airways, arrivals, or departures is very quick and simple once a more simple plan has been imported successfully. Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
March 14, 20215 yr I find it not that difficult if you follow a few rules...some people create the difficulty for themselves. 1) If creating a flightplan for an aircraft where a FMC will be used, I use Simbrief which makes it easy to remove discontinuity and then export a valid flightplan. This is made easier with a Navigraph subscription and recognized/updated avionics. 2) If creating a flightplan for GA with GTN 750/650...use the database that you have in the Garmin to advantage. The GTN is a treat when you zoom in as it will display the named waypoints that it recognizes as valid. Do a rough plan with minimal waypoints, note the waypoint names and use the same waypoints in Littlenavmap, if still valid. There are plenty of waypoints to choose from if a couple are not recognized in Littlenavmap, if it's database is slightly off. Then you can set the rest of your parameters, in Littlenavmap prior to export. When you import the flightplan, the Garmin will recognize the waypoints because that is where you got them from. Each person has their own way...the above works well for my use. Edited March 14, 20215 yr by Draggendrop
Archived
This topic is now archived and is closed to further replies.