I've recently started to fly the 414 after buying it some time ago (due to time issues). Absolutely loving it, and far from the beta product I remember.

However, during climb, cruis and descend I constantly have a ghost GS/LOC signal coming and going. I am in cruise right now, FL220, on the TDS GTN (but also got it on the GNS with Navomatic), AP in GPS/ALT mode. Suddenly a glideslope appears in the HSI and horizon, always 1 dot high, not changing, and a LOC signal one dot left, not changing. Then the whole thing is disappearing again.. before the procedure repeats itself after 10 to 30 seconds.

The FD and AP is unaffected of this. I use the TDS, both units show GPS. Switching to VLOC when the ghost signal is active, the indications remain the same. I use the Honeycomb Alfa/Bravo combo.

Any idea how to fix this issue? or is it a known bug? It's kinda driving me crazy..

-Matthias

 

1 hour ago, MatzeH84 said:

However, during climb, cruis and descend I constantly have a ghost GS/LOC signal coming and going. I am in cruise right now, FL220, on the TDS GTN (but also got it on the GNS with Navomatic), AP in GPS/ALT mode. Suddenly a glideslope appears in the HSI and horizon, always 1 dot high, not changing, and a LOC signal one dot left, not changing. Then the whole thing is disappearing again.. before the procedure repeats itself after 10 to 30 seconds.

I have not seen any other reports of this so my guess is there is some issue with your setup/install. Couple of things to check:

1. Make sure you only have one ver of the C414 in your Community folder, and the Win10 Program and Features shows only your latest 2.9.0 install. Some users had two ver of the plane installed because when FSW initially changed over to a new installer the new installer could not uninstall the previous version which it now does from here on. If you do have two C414 installs, use Program and Features to uninstall the old ver, then rerun the new installer which will first uninstall a possibly bad current ver, and then will reinstall the current version.

2. Make sure you are using a default livery at least for test purposes. Ver 2.9.0 required that some liveries be updated.

3. Make sure you have the latest version of the TDS GTN750.

4. If none of the above applies, you could try temporarily removing all addons from your Community folder to eliminate some weird conflict possibility.

Al

Hey Al,

 

great to read from you again. I made again sure the old version was deinstalled properly, 2.9.0 is installed, and the liveries support this version. I also re-checked and made sure I got the latest update of the TDS, which I have.

I tried the same livery with the PMS GTN+WT, and the issue did not come up. So I guess it's on the TDS side.

 

-Matthias

3 hours ago, MatzeH84 said:

Hey Al,

 

great to read from you again. I made again sure the old version was deinstalled properly, 2.9.0 is installed, and the liveries support this version. I also re-checked and made sure I got the latest update of the TDS, which I have.

I tried the same livery with the PMS GTN+WT, and the issue did not come up. So I guess it's on the TDS side.

Hi Matthias,

I use the TDS GTN and don't get the problem you are reporting, and you also mentioned above that you also get it with the GNS 530 with the Navomatic AP.  So that would seem to eliminate an inherent problem with either the TDS GTN or the Garmin 605 AP.

At this point I just don't have any suggestions other than what I posted above.

Al