April 8, 201511 yr If you own the FLight1 GTN650 gauge, you can install two of them in the Baron. Use the "no 3d knobs" option. Using the RXP "Plate" filler strip at the bottom: //--------------------------------------------------------[Window01]Background_color=0,0,0size_mm=937,390ident=14403position=5window_size= 0.340, 0.260zorder=99gauge00=F1GTN!GTN650, 0,0,937,390,UNIT1.POP[Window02]Background_color=0,0,0size_mm=937,390ident=14404position=8window_size= 0.340, 0.260zorder=99gauge01=F1GTN!GTN650, 0,0,937,390,UNIT2.POP [Vcockpit03]Background_color=0,0,0size_mm=512,512visible=0pixel_size=1024,1024texture=$Panel_baron_3gauge00=F1GTN!GTN650, 173,72,328,166,UNIT1.VCgauge01=F1GTN!GTN650, 173,252,328,166,UNIT2.VCgauge02=rxpgns!plate, 174,430,326,80 ... Bert
April 8, 201511 yr Bert-which Baron, and is it in FSX or P3d or both? Thanks! Forever indebted to the late Michael Greenblatt of FSGS.
April 8, 201511 yr Author I only have the FSX Baron, but I see no reason why it would not work the same in P3D.. Bert
February 27, 20179 yr Bert, thank you so much for all the help, including the 3D Knobs off gauge in separate post. I have now stripped my Baron 58 of all the radio stack including the Audio box, autopilot, transponder and both GNS 430's. I would like to leave the autopilot on the bottom of the stack, and go with a GTN 750 at the top followed on down with a GTN 650, then the autopilot. How can I go about this is it doable ? Alberto Ferracuti
February 27, 20179 yr Author 10 hours ago, ALF1 said: Bert, thank you so much for all the help, including the 3D Knobs off gauge in separate post. I have now stripped my Baron 58 of all the radio stack including the Audio box, autopilot, transponder and both GNS 430's. I would like to leave the autopilot on the bottom of the stack, and go with a GTN 750 at the top followed on down with a GTN 650, then the autopilot. How can I go about this is it doable ? Cannot be done... the radio stack is divided into smaller units and a GTN750 will not fit. 2 X 650 looks quite nice, however. Bert
February 28, 20179 yr Thank you Bert, I have installed and works like a charm, except that the com/nav radios default to com2 and nav2. Thus, the nav radio works only on the lower left CDI below the turn coordinator. I cannot get the HSI to work except for the GPS. In essence I only have one com and one nav. How can I have both radios back ? Alberto Ferracuti
February 28, 20179 yr Author Have a look at the F1GTN.ini file for the airplane. 650.1 set radios=0 650.2 set radios=1 Here is mine: [GTN650.1] Radios=0 Autopilot=1 Mouse=1 Link CRS=1 Auto CRS=1 Fuel=1 Sound=1 Invert Mouse Wheel=0 Active Mouse=1 CPU Core=all Airplane=4 VC Brightness=10 TAWS Voice=1 AVDB=0 [GTN650.2] Radios=1 Autopilot=1 Mouse=1 Link CRS=1 Auto CRS=1 Fuel=1 Sound=0 Invert Mouse Wheel=1 Active Mouse=1 CPU Core=all Airplane=4 VC Brightness=10 TAWS Voice=1 AVDB=0 Bert
February 28, 20179 yr I have Bert's mod in the payware Carenado Baron with the Turbo Charger mod. A really nice plane to fly with the 2 x GTN650's and great for practicing approach procedures. Enroute I always leave the 2nd GTN650 in the "default nav" page which gives a lot of useful information. Also use it to calculate the VNAV path using the VCALC utility from the Utilities menu. Definitely a plus having 2 of these in the cockpit. As always thanks for your mods Bert! p.s. wish I had LNAV+V approaches when I was flying for real. Would have made life so much easier for runways without an ILS. Paul Watts - St Helens, Tasmania, Australia (i7 6700K, 16Gb, GTX 1080, 50" 4K Monitor, 21" Acer touch screen, Windows 10, Prepar3d, X-Plane, ORBX, Rex (All), ActiveSky)
February 28, 20179 yr You are a genius ! The fix was in GTN650.1 set Radios=0 and GTN650.2 Radios=1 Both radios work independent each other. Pressing the Nav1 audio and the nav 2 audio buttons identifies each station separately with its own morse code. The HSI course needle now used for the Nav1 radio on the first GTN650, the other GTN650 works the OBS in the other indicator below the turn and bank. Alberto Ferracuti
February 28, 20179 yr And Bert, changing that VC Brightness to 10 is superb, as is the TAWS voice set to =1 Alberto Ferracuti
March 1, 20179 yr It looks like this Bert [Window Titles] Window00=GPS Window01=Manual Window02=Toggle_Control Window03=Autopilot Window04=INFO //-------------------------------------------------------- [Window00] Background_color=53,53,53 size_mm=500,266 window_size_ratio=1.000 position=0 visible=0 ident=794 window_size= 0.290, 0.248 window_pos= 0.020, 0.720 zorder=15 gauge00=CarenadoG430!GNS430_nc1, 0,0,500,266 gauge01=BB58!Toggle_GPS, 109,37,280,164 //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=700,700 window_size_ratio=1.000 position=0 visible=0 ident=793 window_size= 0.320, 0.560 window_pos= 0.650, 0.045 zorder=0 gauge00=B58Manual!manual, 0,0,700,700 //-------------------------------------------------------- [Window02] Background_color=0,0,0 size_mm=351,153 window_size_ratio=1.000 position=0 visible=0 ident=796 window_size= 0.181, 0.140 window_pos= 0.020, 0.200 zorder=5 gauge00=BB58!Control_windows, 0,0,351,153 //-------------------------------------------------------- [Window03] Background_color=0,0,0 size_mm=872,228 window_size_ratio=1.000 position=0 visible=0 ident=790 window_size= 0.300, 0.146 window_pos= 0.320, 0.820 gauge00=APBK!Autopilot, 0,0,872,228 //-------------------------------------------------------- [Window04] file=info.bmp size_mm=345,157 window_size_ratio=1.000 position=0 visible=1 ident=142 window_size= 0.181, 0.146 window_pos= 0.020, 0.040 //-------------------------------------------------------- [Vcockpit01] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_baron_1 gauge00=BB58!Turn Coordinator, 176,3,164,164 gauge01=BB58!Temp, 175,172,165,165 gauge02=BB58!Fuelflow, 4,3,166,166 gauge03=BB58!Hours, 342,2,165,100 gauge04=BB58!Hours2, 343,105,165,100 gauge05=BB58!deicing_pressure, 343,207,166,153 gauge06=BB58!Alt_Load_Right, 441,362,68,147 gauge07=BB58!Alt_Load_Left, 370,362,68,147 //-------------------------------------------------------- [Vcockpit02] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_baron_2 gauge00=BB58!prop_amps, 372,385,135,124 gauge01=BB58!CHT_EGT, 388,28,119,118 gauge02=BB58!Manifold, 390,265,117,117 gauge03=BB58!Gyro, 126,391,118,118 gauge04=BB58!compass, 231,207,71,46 gauge05=BB58!fuel_indicator_L, 247,388,122,121 gauge06=BB58!fuel_indicator_R, 2,388,122,121 gauge07=BB58!Annunciator_Panel, 2,2,508,25 gauge08=BB58!Panel_annunciator, 3,205,225,84 gauge09=BB582!Radioaudio206, 6,31,353,68 gauge10=APBK!Autopilot, 3,292,353,92 gauge11=BB58!gear_center_light, 273,257,31,31 gauge12=BB58!gear_left_light, 230,257,31,31 gauge13=BB58!gear_right_light, 313,257,31,31 gauge14=BB58!Gear_Transition, 356, 257 ,31,31 gauge15=BB58!RPM Indicator, 392,149,113,113 gauge16=BB58!Oil_Temp_Press, 218,103,99,99 gauge17=BB58!Dme_screen, 2,110,214,83 //-------------------------------------------------------- [Vcockpit03] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_baron_3 To have both GTN do I need to add the lines that separate the next entry or is it not needed?
March 1, 20179 yr Author The //----------------- line does not matter. Anything that starts with // is ignored. The text in the previous post is in the F1GTN.ini file, however, not the panel.cfg file.. Bert
Archived
This topic is now archived and is closed to further replies.