Possible GTN650 integration?

Black Square

You can fix the electrical problem by adding the following lines of code to Starship_Interior.XML, after 0 (>L:var_ManualExtensionHandleFailure, bool)

@GpsCircuit(&gt;L:TDSGTNXI650U1_ElectricalCircuit, number)
@GpsCircuit(&gt;L:TDSGTNXI650U2_ElectricalCircuit, number)

HOWEVER: I still suspect the unit will not know when to turn on and off, or when to control the autopilot without some more code changes. You're welcome to have fun for the time being, but please be aware that you are changing things that were never meant to be changed in Starship if you have crazy autopilot problems.

MarkS

@Black-Square the lvars you provided look to be for the TDS GTN unit, I'm using the PMS50 GTN. Since the PMS requires AVIONICS MASTER SWITCH for power, it seems reasonable to have that switch track the value of var_AvionicsCoPilotSwitch so that it powers with the copilot avionics like the GNS does, something like this (RPN is not my strongest language) in the interior xml:

(L:var_AvionicsCoPilotSwitch, bool) (A:AVIONICS MASTER SWITCH, bool) != if{ 
   (L:var_AvionicsCoPilotSwitch, bool) (&gt;K:AVIONICS_MASTER_SET)
}

I've done several flights to test the interaction with the autopilot. No issues so far with power or switching between FMS and GNS. Is there a particular scenario where you think things could go sideways?

Black Square

Ah. You should be able to solve that too by adding these sections to all the panel.XML's. I might not have that 100% correct, but give it a try.

	<Instrument>
		<Name>GTN650_INT</Name>
		<ComIndex>1</ComIndex>
		<NavIndex>1</NavIndex>
		<Electric>
			<Simvar name="CIRCUIT ON:135" unit="Boolean"/>
		</Electric>
	</Instrument>

	<Instrument>
		<Name>GTN650_INT</Name>
		<ComIndex>2</ComIndex>
		<NavIndex>2</NavIndex>
		<Electric>
			<Simvar name="CIRCUIT ON:135" unit="Boolean"/>
		</Electric>
	</Instrument>

I will also try to fix the "avionics switch" problem. I've fixed that in other aircraft, but I guess it never made it to Starship. Often, hardware will still fight with those events.

MarkS

I added those sections to the panel.xmls but then something was preventing livery selection (weird), so I took them out. On the plus side, the code snippet to have the avionics master track the copilot avionics switch works, so the GTN power behaves the same as the GNS.

Black Square

I'll have the avionics switch fixed for you in the next update too. Did you rebuild the Layout.json after making those changes, if you're testing in MSFS 2024? That might have caused the livery problem.

Dingle

Did you observe a loss of the flight plan when the Power goes off and on aswell as in the GNS430?

MarkS

@Black-Square I did rebuild the layout file. I'll hold off on publishing this until after your update, so we don't inadvertently step on each other's work.

@Dingle no loss of flight plan in the GTN on power cycle or switching between FMS/GNS.

steveonatorer

@Dingle
@Black-Square

I have the same issue with the standard GNS. I wanted to try to utilize a hybrid system, switching to the GNS for RNAVS, but whenever I change the fd source to GNS it restarts and deletes all the inputs. Please let me know if you found a solution to this! Otherwise phenomenal aircraft!

Dingle

@steveonatorer I don't have a solution, nor an idea if it can be fixed. But it would be very cool of it kept the input.

MarkS

The GTN650 mod is working well in Starship version 1.1 in both 2020 and 2024. Barring any issues, it will be released on flightsim.to following FSExpo on Monday 30 June.

I don't have image posting privileges but here's a link to a preview pic: https://i.postimg.cc/xTgfRpJq/Starship-GTN650.png

You will also need to have the following folders installed in your Community folder:

PMS50 GTN750: "pms50-instrument-gtn750" from https://pms50.com/msfs/
JayDee's GTN750 mod: "ZZZ JD 00 GTN750 MAIN MOD 2.3 - PMS FIX" from https://flightsim.to/file/13415/jds-gtn750-on-gns530-mod

Jan Nek

Cool, thank you.

SebAvi

Hello, next will be perfect with TDS650 integration if it is possible please

MarkS

@SebAvi sorry, I don't own the TDS unit, someone else will have to take that on.

Rhinozherous

@MarkS You are my Hero! I was already at the point of despair because it seems I just hate the WT GNS430 (it is the first time I really had to deal with it). Cant wait for the release! Do you need a tester?

SebAvi

@MarkS thanks for info, for me defauld 430 is so bugged that alternatives will be great to have

MarkS

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.

Rhinozherous

@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.

This sounds bad. I hope the problem is not that severe as it sounds. Wish you all the best!

Dingle

@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.

Dingle

@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,702

Probably I am missing some important steps.

Cheers

MarkS

@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