F1GTN650/750 GPS tutorials request

[AussieMan]

Over the last couple of years aircraft developers have been producing aircraft with integration of the F1GTN650 or 750 GPS for customers who own the said GPS. Most accomplish this by supplying a separate panel.cfg file in the panel folder. Just Flight with the release of their Piper Arrow have come up with a different idea where you can choose the panel from a switch on your desktop. Then when you choose the Arrow you go to the Addons dropdown to integrate it into your panel.

In the past I have been happy to use the default GPS but with so many aircraft being produced with GTN integration I decided to bite the bullet and purchase the GTN750 GPS for P3D.

Now comes the embarrassing bit. When I have it set up in the panel I have no bloody idea as to how to turn it on. I have read the manuals that came with it with a fine tooth comb but have come up empty handed every time. I have tried YouTube but the videos on there all start with the unit turned on and the presenter doing something like creating a flight plan or scrolling through the menus.

Are there any GTN experts out there who can either do a YT tutorial or a written tutorial starting with a cold, dark setup highlighting how to turn the unit on. I have the A2A C-182, Cherokee and Commanche, the JF Piper Arrow the Milviz C-310 and several Carenado/Alabeo aircraft with the GTN setup.

This would be much appreciated.

[Cees Donker]

As far as I know the unit is turned on when you turn on the avionics?


Cees

[AussieMan]

That doesn't seem to happen with me Cees. But that seems logical. Maybe I am missing something in the cfg.

This is the A2A cfg:

// F1 GTN 750
[Window Titles]
Window00=Main panel
Window01=Clipboard
Window02=Mini controls
Window03=Payload and fuel manager
Window04=Map
Window05=Quick radios
Window06=Maintenance hangar
Window07=Pre-flight inspection
Window08=AFK
Window09=none2
Window10=dbg
Window11=none3
Window12=none4
Window13=GTN 750

[VIEWS]
VIEW_FORWARD_WINDOWS=10,20,RADIO_STACK_PANEL,FUEL_ PANEL,40,50,51,52,53,54,100,101,102,103,104,105

//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=1024,768
position=1
visible=0
ident=10
//gauge00=tester!tester, 420, 50, 400, 1000 //Comment for release

[Window01]
Background_color=0,0,0
size_mm=322,615
pixel_size=322,615
window_pos= 0.0, 0.2
position=0
visible=0
ident=20
sizable=0
gauge00=A2A_C182!clipboard, 1,0,322,615

[Window02]
Background_color=0,0,0
size_mm=392,315
pixel_size=392,315
window_pos= 0.51, 0.2
position=0
visible=0
ident=RADIO_STACK_PANEL
sizable=0
gauge00=A2A_C182!controls, 1,0,392,315

[Window03]
Background_color=0,0,0
size_mm=649,689
pixel_size=649,689
window_pos= 0.51, 0.2
position=1
visible=1
ident=FUEL_PANEL
sizable=0
gauge00=A2A_C182!manager, 1,0,649,689

[Window04]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=1
ident=40
sizable=0
gauge00=A2A_C182!mapscreen, 255,1,770,766
gauge01=A2A_C182!map_settings, 1,50,246,232

[Window05]
Background_color=0,0,0
size_mm=187,392
pixel_size=187,392
position=6
window_pos= 0.025, 0.9
visible=1
ident=50
sizable=0
gauge00=A2A_C182!radios, 1,0,

[Window06]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=51
sizable=0
gauge00=A2A_C182!maint_hangar, 1,0,1024,768

[Window07]
Background_color=0,0,0
size_mm=1024,768
pixel_size=1024,768
window_pos= 0.000, 0.2
position=0
visible=0
ident=53
sizable=0
nomenu=1
type=special
gauge00=A2A_C182!walkaround, 0,0,1024,768

[Window08]
Background_color=0,0,0
size_mm=321,321
pixel_size=321,321
position=5
visible=1
ident=54
sizable=0
gauge00=A2A_C182!afk, 1,1,321,321

[Window09]
Background_color=0,0,0
ident=100
render_3d_window=1
nomenu=1
type=special
gauge00=A2A_C182!keys, 1,1,1,1
//gauge01=A2A_C182!cockpitBuilder, 2,2,2,2 //For cockpit builders only.

[Window10]
Background_color=0,0,0
size_mm=330,450
pixel_size=330,450
position=5
visible=0
nomenu=1
ident=101
sizable=0
//gauge00=dbg!panel, 144,0 //Comment for release

[Window11]
Background_color=1,1,1
ident=102
window_size=1.000,1.000
nomenu=1
zorder=100
gauge00=A2A_C182!blackout, 0,0

[Window12]
Background_color=0,0,0
size_mm=650,624
pixel_size=650,624
position=3
visible=0
ident=103
nomenu=1
zorder=99
gauge00=A2A_C182!engine_details, 1,1,650,624

[Window13]
Background_color=0,0,0
size_mm=937,887
ident=14401
window_pos= 0.660, 0.160
window_size= 0.340, 0.580
zorder=99
gauge00=F1GTN!GTN750, 0,0,937,887,UNIT1.POP

//--------------------------------------------------------
[Vcockpit00]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle
gauge01=A2A_C182!code_c182t_r, 1,1,1,1
gauge02=A2A_C182!status1,2,2,2,2
gauge03=A2A_C182!damage, 3,3,3,3
gauge04=accusim_xml!code_s, 4,4,4,4
gauge05=A2A_Accusim!lua, 5,5,5,5
gauge06=A2A_Accusim!AVS, 6,6,6,6
gauge07=A2A_Accusim!events, 7,7,7,7
gauge08=A2A_Accusim!random, 8,8,8,8
gauge09=A2A_Accusim!storage, 9,9,9,9
gauge10=A2A_C182!code_c182t_m, 1,1,1,1
gauge11=gps!gps_500, 0,0,1065,675
gauge12=C182!avionics, 0, 576, 1024,447
gauge13=A2A_C182!annunciator, 1, 454, 854,120
gauge14=A2A_C182!number, 794, 0, 228,77
gauge15=A2A_C182!aoa_indexer, 993, 79, 29, 58
gauge16=A2A_C182!GPS_F1_750, 1, 1, 1, 1

[Vcockpit01]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$reticle1
gauge00=C182!lightmap, 0, 576, 1024,447

[VCockpit02]
size_mm=1024,1024
pixel_size=1024,1024
texture=$GTN750
background_color=0,0,0
gauge00=F1GTN!GTN750VC, 0,0,677,794,UNIT1

[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c1_l
gauge00=C182_Illumination!c1, 0, 0, 1024, 1024

[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c2_l
gauge00=C182_Illumination!c2, 0, 0, 1024, 1024

[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c5_l
gauge00=C182_Illumination!c5, 0, 0, 1024, 1024

[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c7_l
gauge00=C182_Illumination!c7, 0, 0, 1024, 1024

[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$c182_c9_l
gauge00=C182_Illumination!c9, 0, 0, 1024, 1024

[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$vc_gxml_l
gauge00=C182_Illumination!vc_gxml, 0, 0, 1024, 1024

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

[Martyn]

If installed correctly (do you definitely have the Garmin GTN trainer installed?), the GTN units should power on as soon as the battery master switch is turned on.

[AussieMan]

If installed correctly (do you definitely have the Garmin GTN trainer installed?), the GTN units should power on as soon as the battery master switch is turned on.


Hi Martyn, The Garmin GTN Trainer is installed in the ProgramFlies folder with a start icon in the desktop. All I get when I turn the battery master on is a black screen.

[doublecool]

AussieMan,

as I understand the directions, it must be installed on the same drive as your Flight Sim
but not in the flight sim... I put it (the folder) in the flight sim the first time and I had the black panel.

hope this helps

[Tim-HH]

If installed correctly (do you definitely have the Garmin GTN trainer installed?), the GTN units should power on as soon as the battery master switch is turned on.

That is not correct. The Flight1 GTN is activated by turning on the the avionics master switch.

Greetings
Tim

[AussieMan]

AussieMan,

as I understand the directions, it must be installed on the same drive as your Flight Sim
but not in the flight sim... I put it (the folder) in the flight sim the first time and I had the black panel.

hope this helps

I have my flight sims on my D; drive and had the GTN trainer installed in my Flight Sim Utilities originally but read on the F1 forums it should be in the ProgramFiles folder so I reinstalled it there.


Tim HH: That is not correct. The Flight1 GTN is activated by turning on the the avionics master switch.

Tim, If I could find an Avionics master switch I would be happy. Even the PDFs showing the panel switches does not identify one.

[Martyn]

Apologies, I meant to say, "In the Arrow, the GTN units should power on as soon as the battery master switch is turned on", as the Arrow doesn't have an avionics/radio master switch.

It should definitely power up in the Arrow with the battery on, as long as the GTN unit is selected (visible) in the VC. If it doesn't then that'd point to an issue with the GTN gauge itself, or its ability to access the Garmin trainer software. Flight1 support might be your best bet in the case.

[lownslo]

I have my flight sims on my D; drive and had the GTN trainer installed in my Flight Sim Utilities originally but read on the F1 forums it should be in the ProgramFiles folder so I reinstalled it there.

When you try turning on the GTN at its Program Files location (not in the sim; not in an airplane) does it come alive? You should be able to go to the install location in Program Files and turn on the GTN and set-up a flight plan, configure it, and move through the numerous screens just as if you were sitting in the cockpit of a plane doing the same. If you can't do all this then it is installed in the wrong location... and it MUST be installed just as the instructions note (something I dislike but you can't do much about it).

Greg

[Pat Mussotte]

I have my flight sims on my D; drive and had the GTN trainer installed in my Flight Sim Utilities originally but read on the F1 forums it should be in the ProgramFiles folder so I reinstalled it there.



Tim, If I could find an Avionics master switch I would be happy. Even the PDFs showing the panel switches does not identify one.

Hi AussieMan!
I installed the GTN Lite Trainer in my C disk outside of "Program Files"and my flightsims, FSX-SE, P3D and Xplane are in my D disk and it works fine since ever . Concerning the avionics switch as you know some planes don't have one, BUT you need to "activate it via the ingame default mapping(or re-map it, I did it with CTRL+A)this is the case for example for the Alabeo C207. If you don't do that, you have no avionics.

Regards

Pat

[lownslo]

Hi AussieMan!
I installed the GTN Lite Trainer in my C disk outside of "Program Files"

Cool! I bought the F1 GTN750 back in Dec. 2015 and tried installing the GTN PCTrainer Lite outside of its default location but it wouldn't work in the sim (I had a black screen in the gauge just like Pat describes). Also, in my install package is a Notepad txt file that says:

IMPORTANT!!! The Garmin GTN PCTrainer Lite must be installed in its default directory before installing the GTN gauge in the FSX directory. Download the current PC TRainer Lite software from the Garmin site.

And I believe the same is mentioned during the install process (not sure... been a while since I installed the GTN). The Default directory is C:\Program Files (x86)\Garmin\GTN Trainer. I'd like to move the app from its default location... could you explain how you did it?

Thanks,

Greg

[Pat Mussotte]

Cool! I bought the F1 GTN750 back in Dec. 2015 and tried installing the GTN PCTrainer Lite outside of its default location but it wouldn't work in the sim (I had a black screen in the gauge just like Pat describes). Also, in my install package is a Notepad txt file that says:

IMPORTANT!!! The Garmin GTN PCTrainer Lite must be installed in its default directory before installing the GTN gauge in the FSX directory. Download the current PC TRainer Lite software from the Garmin site.

And I believe the same is mentioned during the install process (not sure... been a while since I installed the GTN). The Default directory is C:\Program Files (x86)\Garmin\GTN Trainer. I'd like to move the app from its default location... could you explain how you did it?

Thanks,

Greg
I don't care what Garmin says about the default location, I select a different one here the C disk. I have the GTN now for more than 2 years and they work fine with this install.
Concerning the problem of AussieMan, he should login at simforums and see if someone has the same problem. In fact there are some problems with the GTN that require to upload 2 beta dll(to replace the dll in gauges folder). I had a trouble recently with my GTN650 after the install after puchase. Installing the dll cured my problem.

Regards

Pat

[AussieMan]

Finally got it partially working. Downloaded a new file and now it is working with the A2A aircraft. Now need to get it to work with the Arrow.