CDI scaling with GNS430 as the nav source
-
With the nav source set to the GNS430, the CDI on the EHSI and the little CDI on the EADI seem permanently fixed at 10NM scale. They don't change scale to match the GNS. I confirmed that it is not simply the "10NM" annunciations...the CDI deflections do not match the GNS.
-
I haven't confirmed this, but looking at the code, here are two ideas: Did you have the autopilot in approach mode, or NAV mode? If the AP was in approach mode, then it might mean that the GNS is not properly setting the GPS APPROACH MODE variable. I've seen these GPS variables become considerably stuck in MSFS 2024. Which version of the sim are you running?
-
I haven't confirmed this, but looking at the code, here are two ideas: Did you have the autopilot in approach mode, or NAV mode? If the AP was in approach mode, then it might mean that the GNS is not properly setting the GPS APPROACH MODE variable. I've seen these GPS variables become considerably stuck in MSFS 2024. Which version of the sim are you running?
@Black-Square
NAV mode. I did not attempt an RNAV approach because of the scaling issue. I can try it out a bit later.I will note that the GNS's enroute CDI mode is 5NM, so I wouldn't expect the EFIS to indicate a 10NM scale ever. That said, I'm sure there are some nuances to the way the Garmin is integrated with the Starship avionics.
MSFS 2020. (Sorry, I should have thought to include that.)
-
I haven't confirmed this, but looking at the code, here are two ideas: Did you have the autopilot in approach mode, or NAV mode? If the AP was in approach mode, then it might mean that the GNS is not properly setting the GPS APPROACH MODE variable. I've seen these GPS variables become considerably stuck in MSFS 2024. Which version of the sim are you running?
@Black-Square
More testing. I tried to shoot an approach with LPV available. When engaging APR mode on the AP, the CDI scaled down to a fixed 2NM scale and EFIS displayed a glideslope. However that G/S never budged from full-up deflection, and the AP never descended.Also, the TOGA button & binding don't function when I have the GNS selected as the nav source, seems to be the case in all modes of flight. As soon as I switch back to the FMS, it functions normally.
-
@jmarkows said in CDI scaling with GNS430 as the nav source:
TOGA is infamously not implemented in the WT avionics, so that's not surprising.
I've been back and forth with WT in the past regarding the TOGA which they feel is not important in MSFS for the aircraft utilizing the WT GNS navigators. I am a pilot of small single engine aircraft and when equipped I use the TOGA with FD on every takeoff and especially on a missed approach. For me it certainly limits the usefulness of using the WT GNS for any IFR practice... I'll just choose a different aircraft. Fortunately the Cirrus SR22T does include the programming for the TOGA to work. The Bonanza/Baron and/or Duke I'll fly without the GNS and in the Duke I can use the lovely simulation of the KNS90B and have the TOGA work.
-
The funny thing is that TOGA was in the original Asobo GNS units, and when WT took them over is when it stopped working! I went through a long back and forth with FSW in their 414 because it had stopped working for me, and eventually they told me the new, mandatory WT GNS units did not support the TOGA Kvar and as they used the avionics AP instead of coding their own, there was nothing they could do about it until WT put it back in.
I was pleasantly surprised to find it working in the Starship, where I have the GNS disabled, as Nick has also traditionally relied on the AP of the underlying avionics (I think). For me, that has meant the WT GNS units, as I am not interested in using the various flavors of giant touchscreens, so for most things I've given up having TOGA work at all.
However, it seems like this latest batch of nonsense has him just doing the whole thing himself, which I imagine will eventually work its way back from Starship to the Dukes, TBM, and Professional series.
