ryanbatcund

Anyone done GTN 750 mods for this?

Recommended Posts

It could fit inside the GNS530 bezel.  I might attempt it if no one has yet.

 

jetpropexterior.jpg

 

jetpropinterior.jpg

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

+1 for this. Would love it if someone could integrate the GTN 750 into this bird and post their panel.cfg here.  Also, the King Air C90B!

Share this post


Link to post
Share on other sites

Ryan - I think it might have been you who managed to integrate the GTN somewhat into the PA46 (from the Flight1 forum) ... if so did you manage to turn off the clickspot GNS530?

 

Regards,

 

Steve

Share this post


Link to post
Share on other sites

What about right side of main screen (sorry not sure how you call it)?

750 would fit perfect there.

I don't have that plane but with 750 working I would probably buy it even though it's careNOTado.

 

6Dx0l6M.jpg

Share this post


Link to post
Share on other sites

I actually did finish this a while back - put it in the GNS530 slot.  But your suggestion would be a good idea.  I'm just not sure how to do that.

 

gpz.jpg

  • Like 1

Share this post


Link to post
Share on other sites

Nice work with what is there to work with, but there is more TAS and supported integration from other available aircraft models from other developers. In the case of this model, and in the case of the topic-mentioned Carenado C90B, sales are being lost because of the developer's complicity. I love the Turbine Duke V2, but beyond it's sheer power it feels a lot like the Beech C90B. But the sales advantage the TDv2 has is that it embraces and provides ease of integration of avionics, most notably the newer Garmin GTN series.

 

Leaving so much money on the table is confusing to me. PA46, C90B, C210T, etc. could all be rejuvenated with a minimum of effort compared to those model's or additional model's initial development costs. 

Share this post


Link to post
Share on other sites

 

 


Leaving so much money on the table is confusing to me. PA46, C90B, C210T, etc. could all be rejuvenated with a minimum of effort compared to those model's or additional model's initial development costs.

 

A lot of airplane devs dont like going back even if there is money at stake. A prime example is the F1 citation mustang. It needs a mod to work in FSX-SE but they wont touch it :blink:

 

I would take a close look at Carenado if it had the GTN 750 in the above models

Share this post


Link to post
Share on other sites

nice job! can you post your panel.cfg so we can insert it into our Malibu's as well?

 

From my simforums post:

 

Run the F1 config first, then see below for added line

 

[Vcockpit02]

Background_color=0,0,0 

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$Panel_2

 

gauge00=WX_Gauge_3D_P46T!WXGauge, 9,9,492,309

//gauge01=GPS_530_3D_P46T!gps_500, 7,337,493,358

gauge01=F1GTN!GTN750VC, 90,304,330,355,UNIT1

gauge02=Radio_P46T!RadioAdf, 524,670,496,100

gauge03=GPS_430_3D_P46T!GNS430_nc2, 517,259,497,258

gauge04=DIGTTRANS_P46T!transponder, 516,529,501,126

gauge05=Radio_P46T!RadioTrans, 520,126,496,112

gauge06=Radio_P46T!RadioAudio, 520,8,498,98

gauge07=GAUGEP46T!Gauge_Anum_R, 381,786,635,229

gauge08=GAUGEP46T!Gauge_Engine_Trend, 14,711,299,298

Nice work with what is there to work with, but there is more TAS and supported integration from other available aircraft models from other developers. In the case of this model, and in the case of the topic-mentioned Carenado C90B, sales are being lost because of the developer's complicity. I love the Turbine Duke V2, but beyond it's sheer power it feels a lot like the Beech C90B. But the sales advantage the TDv2 has is that it embraces and provides ease of integration of avionics, most notably the newer Garmin GTN series.

 

Leaving so much money on the table is confusing to me. PA46, C90B, C210T, etc. could all be rejuvenated with a minimum of effort compared to those model's or additional model's initial development costs. 

It's hard to tell from a customer standpoint if doing a revised GTN integration would be a good idea.  I'm not sure how much actual net profit RA made when they redid the TDuke v2 with GTN integration.  I think there is a bit more development time than people think.  And especially since Carenado is a quantity over quality company I can hardly see them redoing their planes with GTN integration.  Thankfully we do have the RA T Duke (and hopefully the upcoming Super Legacy), and A2A planes.  Also don't forget Milviz with their GTN integration.  I think a C310 GTN750 only integration is coming out as well.  (In case you don't own the 650 you can install the 750 and use the default GPS).

 

I'd really enjoy if Flight1 suprised us all with an older Mooney, with GTN integration.  No one has done a decent Mooney.  There's a few lite ones out there, Carenado's older model, Lionheart "lite" Acclaim, etc.... but we could use one of those.  I suppose there's no market left in the single piston category anymore...  they've been done to death in my opinion...  except maybe a Legacy with Twin Turbos hehe!!

  • Like 1

Share this post


Link to post
Share on other sites

 

 


I'd really enjoy if Flight1 suprised us all with an older Mooney, with GTN integration.  No one has done a decent Mooney.

 

Boy do I fully agree with that! The recent A2A Commanche is the high performance, carrying-capacity, alternative,  I need to build a new system in the next six months and am limiting my purchases, watching FSX-S and P3D in interim.

Share this post


Link to post
Share on other sites

I wish RA would do a killer Meridian but I don't suppose there are many of those in the RW with steam gauges which would be optimal IMHO with GTN integration - T. Duke style. I could handle the glass if it worked right and didn't kill performance. I just described the GTN though, so for a GTN owner the ultimate airplane is steam gauges/GTN integration and that usually means something less than cutting edge in the real world.

 

This could work though (I mean swapping the GNS for GTN or maybe integration for both):
http://www.airliners.net/photo/Piper-PA-46-500TP-Malibu/0966294/L
http://www.airliners.net/photo/Piper-PA-46-500TP-Malibu/1127420/L
http://www.airliners.net/photo/Piper-PA-46-500TP-Malibu/1008967/L

 

(I guess you can't link a page on airliners.net. Copy & paste I guess.)

Share this post


Link to post
Share on other sites

From my simforums post:

 

Run the F1 config first, then see below for added line

 

[Vcockpit02]

Background_color=0,0,0 

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$Panel_2

 

gauge00=WX_Gauge_3D_P46T!WXGauge, 9,9,492,309

//gauge01=GPS_530_3D_P46T!gps_500, 7,337,493,358

gauge01=F1GTN!GTN750VC, 90,304,330,355,UNIT1

gauge02=Radio_P46T!RadioAdf, 524,670,496,100

gauge03=GPS_430_3D_P46T!GNS430_nc2, 517,259,497,258

gauge04=DIGTTRANS_P46T!transponder, 516,529,501,126

gauge05=Radio_P46T!RadioTrans, 520,126,496,112

gauge06=Radio_P46T!RadioAudio, 520,8,498,98

gauge07=GAUGEP46T!Gauge_Anum_R, 381,786,635,229

gauge08=GAUGEP46T!Gauge_Engine_Trend, 14,711,299,298

It's hard to tell from a customer standpoint if doing a revised GTN integration would be a good idea.  I'm not sure how much actual net profit RA made when they redid the TDuke v2 with GTN integration.  I think there is a bit more development time than people think.  And especially since Carenado is a quantity over quality company I can hardly see them redoing their planes with GTN integration.  Thankfully we do have the RA T Duke (and hopefully the upcoming Super Legacy), and A2A planes.  Also don't forget Milviz with their GTN integration.  I think a C310 GTN750 only integration is coming out as well.  (In case you don't own the 650 you can install the 750 and use the default GPS).

 

I'd really enjoy if Flight1 suprised us all with an older Mooney, with GTN integration.  No one has done a decent Mooney.  There's a few lite ones out there, Carenado's older model, Lionheart "lite" Acclaim, etc.... but we could use one of those.  I suppose there's no market left in the single piston category anymore...  they've been done to death in my opinion...  except maybe a Legacy with Twin Turbos hehe!!

 

Ryan,

 

I got the (FSX) GTN750 display in the VC but pressing any GTN button brings up the default Garmin?

 

So, I have to use Shift + 9 to get the GTN750 popup to make selections, like to get the map to display.

 

 

The large default 530 bezel takes away part of the GTN's normal screens?

 

Also, does the flight plan on the GTN show up on the P46T's MFD?

 

If this GTN750 is supposed to be fully operational in the VC then my setup is missing something.

 

Actually I wanted to use this also in P3D because Reality XP cannot be used there.

 

 

GTN-problem_zpswnbsbezb.jpg

 

Share this post


Link to post
Share on other sites

 I'm not sure how much actual net profit RA made when they redid the TDuke v2 with GTN integration.  

 

They got a purchase from me (FSX version) near a time when I need to build a new system and consider a move from FSX to P3D or SE. i.e I am not in the mood to purchase more items for my current FSX system. Their efforts also were a key influence for me to snag the GTN 750. Guess that's an example of trickle-down economics!

Share this post


Link to post
Share on other sites

Ryan,

 

I got the (FSX) GTN750 display in the VC but pressing any GTN button brings up the default Garmin?

 

 

 

You'll have to email me or pm me... I'm off to work the night but maybe I can help tomorrow

Share this post


Link to post
Share on other sites

You'll have to email me or pm me... I'm off to work the night but maybe I can help tomorrow

I have the same problem is there any solution that I can apply?

Share this post


Link to post
Share on other sites
Quote

I got the (FSX) GTN750 display in the VC but pressing any GTN button brings up the default Garmin?

vonmar  Just on [Vcockpit02]  add the comment to gauge07   //gauge07=PA46350P!ToggleCAR530,      7,337,493,30

:blink:

Share this post


Link to post
Share on other sites
Quote

alexcunille: ... Just on [Vcockpit02]  add the comment to gauge07   //gauge07=PA46350P!ToggleCAR530,      7,337,493,30

you refer to a different aircraft: PA46 350 piston. 
Here is P46T Jetprop topic.

My suggestion:

  • GTN750 inside GNS530 bezel
  • GTN650 inside WX radar bezel
  • GNS430 original gauge: Unable to set GTN650 here

 

mgI56NI.jpg

[Vcockpit02]

Background_color=0,0,0 

size_mm=1024,1024

visible=0

pixel_size=1024,1024

texture=$Panel_2

 

gauge00=WX_Gauge_3D_P46T!WXGauge,  9,9,492,309

gauge01=Radio_P46T!RadioAdf,  524,670,496,100

gauge02=DIGTTRANS_P46T!transponder,  516,529,501,126

gauge03=Radio_P46T!RadioTrans,  520,126,496,112

gauge04=F1GTN!GTN750VC,  90,304,330,355,UNIT1

gauge05=GAUGEP46T!Gauge_Anum_R,  381,786,635,229

gauge06=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298

gauge07=F1GTN!GTN650VC,  579,295,448,181

 

 

Regards

Stefan

  • Like 1

Share this post


Link to post
Share on other sites

Correction for the above panel.cfg for P46T Jetprop:

[Vcockpit02]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_2

gauge00=Radio_P46T!RadioAdf,  524,670,496,100
gauge01=GPS_430_3D_P46T!GNS430_nc2,  517,259,497,258
gauge02=Radio_P46T!RadioTrans,  520,126,496,112
gauge03=Radio_P46T!RadioAudio,  520,8,498,98
gauge04=GAUGEP46T!Gauge_Anum_R,  381,786,635,229
gauge05=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298
gauge06=F1GTN!GTN650VC,  50,57,456,209,UNIT2
gauge07=F1GTN!GTN750VC,  90,304,330,355,UNIT1
gauge08=DIGTTRANS_P46T!transponder,  516,529,501,126
 

sorry

  • Like 1

Share this post


Link to post
Share on other sites
On 9/29/2017 at 0:28 PM, wildtomcat said:

Correction for the above panel.cfg for P46T Jetprop:

[Vcockpit02]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_2

gauge00=Radio_P46T!RadioAdf,  524,670,496,100
gauge01=GPS_430_3D_P46T!GNS430_nc2,  517,259,497,258
gauge02=Radio_P46T!RadioTrans,  520,126,496,112
gauge03=Radio_P46T!RadioAudio,  520,8,498,98
gauge04=GAUGEP46T!Gauge_Anum_R,  381,786,635,229
gauge05=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298
gauge06=F1GTN!GTN650VC,  50,57,456,209,UNIT2
gauge07=F1GTN!GTN750VC,  90,304,330,355,UNIT1
gauge08=DIGTTRANS_P46T!transponder,  516,529,501,126
 

sorry

Stefan,

Thanks.

Edit: I added the lines above to the panel.cfg. The 750 works fine but I cannot bring it up by clicking on it .The 650 does not work. I only see part of it inside the gns430 "frame" and clicking on it brings up the carenado gns430

Share this post


Link to post
Share on other sites

I see. The clickspots in the GNS530 and 430 bezel are kind of hardcoded in the model, no gauges we can change. So the GTNs can´t be opened with clicks on them but with shift+4 and shift+5. Or by the GTN stack. I use buttons on my goflight panels for it.

Maybe I changed something in the other parts from panel.cfg, too. this is my complete panel.cfg:

[Window Titles]
Window00=G500
Window01=Toggle_Manual
Window02=Toggle_Control
Window03=Flight1 Garmin GTN750 U1 - DO NOT MODIFY
Window04=Flight1 Garmin GTN650 U2 - DO NOT MODIFY
Window05=INFO
Window06=GP430


[VIEWS]
VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

//--------------------------------------------------------
[Window00]
Background_color=0,0,0 
size_mm=1024,1024
window_size_ratio=1.000  
position=8
visible=0
ident=MAIN_PANEL
window_size= 0.500, 0.666
window_pos= 0.010, 0.310
no_luminous=1

gauge00=G500_P46T!g500_config,  0,0,1,1
gauge01=G500_P46T!g500,  0,0,1024,1024
gauge02=PA46T!ToggleCARG500,  0,0,1024,50


//--------------------------------------------------------
[Window01]
Background_color=0,0,0 
size_mm=713,1000
position=0
visible=0
ident=793
window_size= 0.351, 0.817
window_pos= 0.520, 0.020
zorder=5

gauge00=PA46TManual!manual,  0,0,711,998


//--------------------------------------------------------
[Window02]
Background_color=0,0,0 
size_mm=500,261
position=0
visible=0
ident=796
window_size= 0.198, 0.137
window_pos= 0.010, 0.145
zorder=5

gauge00=PA46T!Control_windows,  0,0,500,261


//--------------------------------------------------------
[Window03]
Background_color=0,0,0 
size_mm=937,887
position=7
visible=1
ident=14401
window_size= 0.340, 0.580
window_pos= 0.000, 0.420
zorder=99

gauge00=F1GTN!GTN750,  0,0,937,887,UNIT1.POP


//--------------------------------------------------------
[Window04]
Background_color=0,0,0 
size_mm=937,390
position=7
visible=1
ident=14404
window_size= 0.340, 0.260
window_pos= 0.338, 0.740
zorder=99

gauge00=F1GTN!GTN650,  0,0,937,390,UNIT2.POP


//--------------------------------------------------------
[Window05]
file=info.bmp 
size_mm=419,181
window_size_ratio=1.000  
position=0
visible=1
ident=142
window_size= 0.250, 0.120
window_pos= 0.010, 0.020

//--------------------------------------------------------
[Window06]
Background_color=0,0,0 
size_mm=524,310
position=7
visible=0
ident=10010
window_size= 0.310, 0.300
window_pos= 0.525, 0.715
no_luminous=1
zorder=7

gauge00=GPS_430_3D_P46T!GNS430_nc2,  0,0,528,310
gauge01=PA46T!ToggleCAR430,  117,6,292,232


//--------------------------------------------------------
[Vcockpit01]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_1

gauge00=GAUGEP46T!Gauge_Eng13D,  768,343,256,343
gauge01=GAUGEP46T!Gauge_Eng23D,  768,0,256,343
gauge02=GAUGEP46T!Gauge_Volts_Amps,  7,521,318,279
gauge03=GAUGEP46T!Gauge_Anum_L,  87,805,328,212
gauge04=GAUGEP46T!Gauge_Button_Anum,  422,803,600,217
gauge05=GAUGEP46T!Gauge_Clock,  332,518,279,279
gauge06=PA46TJ!GPSVSI,  0,0,2,2


//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_2

gauge00=Radio_P46T!RadioAdf,  524,670,496,100
gauge01=GPS_430_3D_P46T!GNS430_nc2,  517,259,497,258
gauge02=Radio_P46T!RadioTrans,  520,126,496,112
gauge03=Radio_P46T!RadioAudio,  520,8,498,98
gauge04=GAUGEP46T!Gauge_Anum_R,  381,786,635,229
gauge05=GAUGEP46T!Gauge_Engine_Trend,  14,711,299,298
gauge06=F1GTN!GTN650VC,  50,57,456,209,UNIT2
gauge07=F1GTN!GTN750VC,  90,304,330,355,UNIT1
gauge08=DIGTTRANS_P46T!transponder,  516,529,501,126


//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$Panel_3

gauge00=GAUGEP46T!Gauge_Autopiloto,  0,0,512,119
gauge01=GAUGEP46T!Gauge_Anum,  0,120,384,177
gauge02=GAUGEP46T!Gauge_Anum_APSEL,  0,299,384,174
gauge03=P46T_Cabin_alt!C340_PRESS,  0,0,1,1


//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_4

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$Panel_5

gauge00=G500_P46T!g500_config,  0,0,10,10
gauge01=G500_P46T!g500_3D,  0,0,768,515


Day=255,255,255
Night=223,255,255
Luminous=246,115,119

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

  • Like 1

Share this post


Link to post
Share on other sites

For anyone wondering, this plane works fantastic with the Flight 1 G500/600 Garmin gauge/trainer replacement with the above panel mods for the Flight 1 GTN-750.

Simply add the GTN750 using the Flight 1 GTN panel config.
Then, swap the Carenado G500/600 with the Flight 1 Garmin G500/600 using the F1GNS panel config tool.
Finally, make the edits to the panel.cfg that displays the GTN750 inside the 530 screen. Works awesome, excellent plane.

Did anyone ever figure out how to get around the hard coded bezel click spot for the default 530 gps? I guess not all addon aircraft are as easy to modify as the amazing RealAir addons. 😉

Edited by Jocko Flocko

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now