Possible GTN650 integration?
-
Drat, I spoke too soon. I've hit a snag, and it could be a show stopper. The GTN looks great but it won't couple to the autopilot in anything other than HDG mode. In NAV or APPR it just flies in circles. Investigating.
@MarkS said in Possible GTN650 integration?:
Drat, I spoke too soon. I've hit a snag, and it could be a show stopper. > The GTN looks great but it won't couple to the autopilot in anything other than HDG mode. In NAV or APPR it just flies in circles. Investigating.
That's what happened to me when I was hotswapping the GTN in the Dukes. Maybe that helps you.
-
@MarkS Would you be able to summerize the steps you did to get you so far? I would really like to play with that stuff too and do not really know where to start. I looked at JayDees mod and I got it to work that in the virtual file tree the panel.cfgs are overloaded, but it kept showing the GNS430. Can you point me at what i am missing?
That is what I put in the mod panel.cfg:
[VCockpit16] size_mm = 960,702 pixel_size = 960,702 texture = GNS530 htmlgauge00=NavSystems/JD_GTN650_GNS430/JD_GTN650_GNS430.html?index=1, 0, 0, 960,702 [VCockpit17] size_mm = 960,702 pixel_size = 960,702 texture = GNS530 htmlgauge00=NavSystems/JD_GTN650_GNS430/JD_GTN650_GNS430.html?index=1, 0, 0, 960,702Probably I am missing some important steps.
Cheers
-
@MarkS Would you be able to summerize the steps you did to get you so far? I would really like to play with that stuff too and do not really know where to start. I looked at JayDees mod and I got it to work that in the virtual file tree the panel.cfgs are overloaded, but it kept showing the GNS430. Can you point me at what i am missing?
That is what I put in the mod panel.cfg:
[VCockpit16] size_mm = 960,702 pixel_size = 960,702 texture = GNS530 htmlgauge00=NavSystems/JD_GTN650_GNS430/JD_GTN650_GNS430.html?index=1, 0, 0, 960,702 [VCockpit17] size_mm = 960,702 pixel_size = 960,702 texture = GNS530 htmlgauge00=NavSystems/JD_GTN650_GNS430/JD_GTN650_GNS430.html?index=1, 0, 0, 960,702Probably I am missing some important steps.
Cheers
@Dingle you need to keep the original texture names, as below. The dimensions you have are proportioned for a 530 bezel, for the 430 you want 700 x 380.
I found that there are many changes to the CDU Javascript code between 1.0 and 1.1, and I suspect the contortions poor Nick had to go through to work around the default autopilot anomolies are causing the disconnect with the GTN650.
[VCockpit16] size_mm = 700,380 pixel_size = 700,380 texture = $GNS430Screen_ApEnabled htmlgauge00=NavSystems/JD_GTN650_GNS430/JD_GTN650_GNS430.html?Index=1, 0, 0, 700,380 [VCockpit17] size_mm = 700,380 pixel_size = 700,380 texture = $GNS430Screen_ApDisabled htmlgauge00=NavSystems/JD_GTN650_GNS430/JD_GTN650_GNS430.html?Index=2, 0, 0, 700,380 -
@MarkS Great, thanks. So what you are saying is that changing the panel.cfg and adding jaydees Module should actually do the Trick. Or anything else required. As soon the gtn650 would show I could use Events to Power it on, right?
-
@MarkS you also mentioned you had issues with the liveries, I was modifying all panel.cfg, but so did you probably. Which livery did you get too work? The 2000s?
@Dingle my livery problems were entirely self-inflicted. Initially I could only get it to work with the 2000A livery, but I've got the GTN appearing in all liveries now.
That said, if you have livery from a 3rd party, you'll need to make the same edits to its panel.cfg file.