ILS with 750gtnxi
-
I’ve just found out that if you press the APPROACH button it will actually fly the app but it doesn’t light up the mode on the autopilot annunciator maybe @Black-Square can confirm this
-
@ramonesg I'm leaving my desk at the moment, but the short answer is: That should not happen, and is indicative of some hot-swapping GPS tomfoolery.
-
@Black-Square I’ve been using the TDS since I bought the airplane I’ll try with the PMS
-
Sorry I made just a short post earlier. I'm more than happy to help you troubleshoot this. The tech support guys are also much more practiced at identifying and solving GPS/AP issues than I am, actually. We haven't met one that couldn't be solved yet. Are you familiar with the WT GNS SU14 bug? Even though you're using other GPS software, it can still affect you, which is why I was originally hoping to delay the release of the Dukes past SU15.
-
I watched my video of a ils landing I did I use the pms 750 and for the approach I had selected approach in the auto pilot and then I had to select vloc 1 in the 750 that was done when I was on final . I hit gs in the auto pilot that sent the autopilot into heading mode I then hit approach only that then set the hsi to vloc then I had no problem capturing the ils but also I’m using sim 15 beta.
-
@Black-Square no worries and for the delay I couldn’t wait any longer so thanks for the release, this is just some minor issue and doesn’t bothers me at all
-
Any update on diagnosing this APPR engage issue for ILS? Using the TDS it rarely works, so I thought I give the KLN90b a go, good retro fun with that one. First time I added and switched to it, the ILS at the end worked fine. Second flight (not the same sim session), it had the KLN90b still configured, flew just fine on GPS, but the ILS approach mode wouldn't engage again. And flying into Edinburgh I was off the NAV mode and on HDG vectors for quite a bit before I was given a nice gentle intercept of like 25 degrees and below the GS. APPR light would illuminate but the plane never turned to intercept the localizer, went right through it. Got it back on track using HDG, same with glideslope - never engages. The needles tracked just fine as I flew the approach manually, which is a nice challenge but with this complex aircraft where you have to follow the checklist to not forget something it makes it quite hard to fly the raw ILS accurately while looking around the cockpit flipping switches.
-
Also after completing the flight I wanted to do another leg with an RNAV approach but using the TDS again ... and that just outright crashed the sim when clicking apply on the tablet. And not for the first time, something about switching from the KLN90 to the TDS is causing a crash. Don't think it was a problem at the beginning of a flight.
-
Loving the Duke Turbine and have now completed over 35 flights / 42 hours. My only issue is I have not managed to complete even one ILS approach in the aircraft. RNAV works flawlessly every time. I have the PMS50 750 and use the Logitech Flight Multi Panel , Flight Switch Panel. These again work perfectly with the Black Square TBM 850 (over 200 hours). The 750 is set up the exact same as I use with the TBM 850 for ILS approaches but it never engages with the glide slope. Hope you can find a solution or provide an exact guide for the Duke’s.
-
Problem solved, I watched the attached YouTube video.
I have now made several ILS approaches in the Turbine Duke without any issues.
Outstanding!
-
Just wanted to bump this back up, this issue is NOT fixed. Finally had some time to do two flights with the turbine duke and the TDS GTNXI750 yesterday. On the first flight I didn't touch the avionics settings in the tablet and it defaulted to the 750. On that flight the HDG mode light on the AP itself and the extra panel on the main panel never light up. It was still following the heading bug when you moved it, but the light was off. Nav mode worked and the light was on, but approach wouldn't even engage.
So after landing I swapped the avionics to a different unit and back to the 750, this the the HDG light came on. Did another small hop over to another airport with an ILS and when initially pressing APPR that light and the GS light both came on. Tracking closer I looked back at it, the GS light had gone out. I was on VLOC mode and and flying an assigned HDG by ATC, the plane just went right throuch the localizer even though APPR was still on, GS never came back and didn't track either.
-
Maybe my experiences are different from what you're describing, but... I use the PMS50 750 unit. Once I've made my final turn toward the runway, the VLOC light comes on (turning off the GPS light. I then press the APPR button and that light comes on. I then, right or wrong, next press the ATT button and its light comes on. Often times the GS button's light comes on. Sometimes it stays on, sometimes it goes back off after a few seconds. The GS light seems to turn off when the yellow flag on the HSI shows that it has picked up the ILS signal, but the flag has not yet begun to descend, indicating I'm still below the glide slope. As the yellow flag on the HSI begins to descend, I again press the ATT button. Again the GS button lights up, and my descent then performs as expected.
Sorry if this is not quite on-topic for your issue, but for my flights, pressing the ATT button a couple of times seems to be what gets the GS button light to 'lock' on. -
I too am unable to get the plane to capture either localizer or glideslope during an ILS attempt. Most of the AP selections do not light up either, except for NAV ATT and ALT. HDG will track but won't light up. APP and GS don't even try to track the ILS bars. I've tried swapping AP's and it doesn't seem to do anything.
Happy to help troubleshoot this out if someone wants to throw me some scenarios to report back on...
Still love the plane but of course would like the ILS to work.
-
@foxtrot789 I very rarely copy-paste a post I've made elsewhere, since I like to give everyone a personal message, but I answered another user just yesterday with very similar symptoms. Please take a look at this post and my reply to it for my suggestions on dealing with this issue. These are some of the most common symptoms that arrive through the Just Flight support ticket system, and we have not found one that we couldn't solve yet by ensuring that all the GPS packages are up to date, installed correctly, and nothing else is conflicting with them. Please stay in touch and let me know how it goes.
-
Awesome, thank you. I'll read your linked post in that thread. (Apologies for asking something that you've already answered, I don't think I ever looked in that thread as I wasn't familiar with the acronym CWS and didn't think it would have had to do with the AP.)
-
Absolutely no worries! I often answer the same questions every day, but that doesn't stop me from treating every report of an issue as a new one, because you never know when something strange and unique might present itself in the world of software. This sort of GPS/AP package issue is the only one I have considered writing a standard response for, since we see the same symptoms in all my aircraft when something isn't quite right on the user end. That's the drawback of trying to offer so many hot-swapping options. Good luck, and let me know how it goes!
-
Just wanted to share my fix with anyone that might be experiencing the same/similar issues. I deleted the tds-gtnxi-gauge folder and re-installed a fresh, updated copy and that did the trick for me...
