ILS not captured
-
I have not had any issues, just tested ILS at 6 different airports with duke and baron using tds 750. I have heard issue may be pms related somehow. Aside from that some reports may be user error...
Hmm, it seems I misunderstood the OP here. It looks like he's using the nav 1 radio for ILS approach, while I thought he was using the KNS 81. I haven't had any problems with ILS approach using any other equipment aside from the KNS 81, so I don't have the same problem.
@kityatyi my advice, if you haven't tried it yet, is if you have the PMS 750, uninstall that and try the ILS approaches again. Maybe try uninstalling the KLN 90, too. The PMS 750 in particular has caused me problems at least once in the past, even when I don't have it loaded into the plane. Another thing to try, if you use Navigraph navdata, would be uninstalling and reinstalling the navdata.
-
Hi,
I do not have the PMS. Only have what comes with the Black Square purchase. It's completely a matter of hit or miss. The same config sometimes yields to a successful ILS capture, sometimes the ILS does not capture. Yes, the indications are fine, the needles move as they should, but HDG mode remains active, APP remains armed but not activated. So far I only noticed this behavior when I was using a config which included the KNS81 RNAV computer, in which case, the issue happened more than 50% of the time. Yes, I always use the NAV 1 radio for the ILS approach, change the NAV source well in advance, change HSI source, the DME source. Everything is well prepared for the capture. I also tend to use HDG mode to intercept the localizer, even when my RNAV waypoint could achieve the same, I switch to HDG mode and expect the LOC to take over - but it does not happen consistently. I never noticed this before I started to use the RNAV computer. In the early BS days, the RNAV computer wasn't working with the autopilot and so I never chose a RNAV panel config - never experienced the problem of non-captured ILS either. But since I bought the new Baron, and since then the Duke, knowing the RNAV can be used with the autopilot, I actually use it a lot - and interestingly, the issue with the ILS appeared. Therefore, I dare to say this behavior is somehow related to the RNAV system and its methods of utilizing the autpilot. Perhaps 3rd party scnery also play a role here (I only fly to 3rd party scenery, never use stock ones, except for those "enhanced" ones). So it may be more than just one thing. -
I did four flights in the Baron today, and on the last one I used the 3rd Party KLN90B GPS. The flight was to EGGP. ATC gave me vectors for the ILS RWY 27 approach. As I no longer needed to follow the GPS, I switched the NAV source from GPS to NAV. I had the ILS tuned into NAV 1 (111.75) and the course set on the HSI. The ILS was identified and the needles started to creep in. I was in HDG mode, with APP armed. But the localizer was never captured, the Baron continued in HDG mode. I tracked the localizer in HDG mode, then disengaged HDG mode, clicked APP but nothing happened. Turned off the F/D and the A/P completely, back on, hit APP, nothing. I eventually landed manually.
It would appear to me this issue does not occur with the GNS 530/430 but it does occur when either the Black Square RNAV system or the KLN90B panel config is used. I am yet to fully verify if the GNS 530/430 aren't affected but I can't recall this happening with that GPS config.
I will download the free PMS and see if the issue happens with it.
-
Yeah I'll try a PMS flight later today and see what happens to me, because I had the same with the KNS yesterday (no ILS capture after switching to Nav 1). Then I'll probably open a ticket with JF support.
-
I've encountered some unrelated PC issues and need to figure those out before I can address the ILS issue. Hopefully installing a new PSU will solve it, but we'll see...
-
I finally got back to this. I know Nick has said in some other places that, in his experience, the sim's default autopilot system is to blame for this issue. But in my case, it seems to be some kind of compatibility bug with the PMS50 750. This is the 4th or 5th time I've experienced nav interference from the PMS50, even when it's not in use, so I'm probably going to finally bite the bullet and buy the TDS -- which I've never heard such complaints about.
I discovered I was having ILS capture issues in the default 747, the BAe 146, the HU-16 Albatross, and all Black Square planes. I removed the PMS50 from my installation and immediately had 3 successful ILS captures in the Bonanza. These captures occurred after using simple VOR-to-VOR navigation, as well as the KNS 80. I didn't test the KLN 90B because, while I want to learn the unit, I haven't yet, and because I ran out of time.
So in each instance, I transitioned from either regular VOR conventional nav to heading to ILS, or from RNAV to heading to ILS, and it was successful. This doesn't rule out the sim's default autopilot being a factor, but it does (for me anyway) clearly indicate that the PMS50 is, once again, the culprit.
-
I finally got back to this. I know Nick has said in some other places that, in his experience, the sim's default autopilot system is to blame for this issue. But in my case, it seems to be some kind of compatibility bug with the PMS50 750. This is the 4th or 5th time I've experienced nav interference from the PMS50, even when it's not in use, so I'm probably going to finally bite the bullet and buy the TDS -- which I've never heard such complaints about.
I discovered I was having ILS capture issues in the default 747, the BAe 146, the HU-16 Albatross, and all Black Square planes. I removed the PMS50 from my installation and immediately had 3 successful ILS captures in the Bonanza. These captures occurred after using simple VOR-to-VOR navigation, as well as the KNS 80. I didn't test the KLN 90B because, while I want to learn the unit, I haven't yet, and because I ran out of time.
So in each instance, I transitioned from either regular VOR conventional nav to heading to ILS, or from RNAV to heading to ILS, and it was successful. This doesn't rule out the sim's default autopilot being a factor, but it does (for me anyway) clearly indicate that the PMS50 is, once again, the culprit.
@RPGamerous I think the TDS is a way better product imo since it uses the actual Garmin trainer software, so its basically just a real gtn750/650 in your aircraft. They've also added a bunch of aircraft specific setting to configure (if you understand how to use them) to get the most realistic implementation of the unit in what ever plane you're flying.
The only downside is no "NEXRAD", but with black square you have a weather radar (although its currently basically just "NEXRAD" sim data on a weather radar screen...)
-
It is not the default autopilot. I never experienced any issues like this with any default aircraft, nor 3rd-party aircraft utilizing the aforementioned systems. In fact, I haven't encountered any ILS issues before I bought the Baron/Bonanza Pro recently.
And it is most certainly not limited to the PMS750, as the issue is present with the Black Square RNAV system as well as the freeware KLN90 GPS. I can't speak for the TDS as I don't have it. Whether one is better than the other is irrelevant in terms of the ILS problem.
I am wondering if the ILS issue is somehow related to the new code/functionality that enables to aircraft to follow the RNAV route using the A/P.
-
I've had the Baron/Bonanza Professional combo since day one and have had no issues whatsoever with glideslope/glidepath capture and stable descent in 2020. I recently (finally!) moved over to 2024, installed the '24 versions and am now also struggling with capture as well.
It's probably 50/50 for me as to whether I'll capture the glideslope in the first place, but if I do I've also found that even when captured the AP seems to struggle stabilizing, oscillating between above and below path until finally damping down. If I put in the final notch of flaps after stabilizing, it will once again oscillate before either stabilizing or me giving up and hand flying the approach.
Again, these are issues I never had with the 2020 versions. For reference, long time simmer and RW GA pilot. We all make mistakes, but I'm pretty sure this isn't user error. I'm using the TDS units exclusively.