• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA Glide Slope issues!

Messages
1,749
Country
unitedstates
My AP GS variable is staying on but the GS disconnects if i fly below 140 knots. Above 140 knots it works perfect. I tried increasing the lift thinking it can't handle the pitch as the nose increases. After making the plane fly stable even at 110 knots it still disconnects below 140 knots as if the speed is causing the issue and not the flight dynamics. The GS settings in the cfg is the same as the lear 45 and adjusting this had no effect. I am lost on this issue as i have never encountered this before. Any help will be very much appreciated.
 
Last edited:
DG
Although you say the glideslope is disconnecting, the fact that the variable is still on suggests that it is not disconnecting.
If it no longer can hold the slope as speed decreases, you should look at whether it has run out of nose-up trim.
Try these two checks.
First fly it in alt hold and in the landing configuration, slow down and see when, at what speed, it loses alt control.
Second, increase the range of trim in the cfg.

If indications are that it has run out of trim, you can double check by flying it on an approach out of autopilot and checking that you have trim in hand or have to keep the stick back to control it.
If everything points to trim issues and you think you allowed enough movement in the .cfg, you may have forward CG issues.
Roy
 
I agree with you as i was increasing the trim as i noticed it was using too much. That's why i increased the lift to see if this was causing the issue. And i did try increasing the trim in the cfg. So i will try increasing it more on my tests tonight.
 
With everything looking good like trim indication and pitch the system is holding perfect. As i slow from 145 knots to 140 knots it fails exactly at the same speed every test i run. So it has nothing to do with anything way out of limits. Some how reducing speed just kills it. This makes no sense and i have never seen this before.
 
Update: I have narrowed the bug to my AP XML code. Now i just need to find out where and why since my test window shows the same results when i use the XML or use the key commands. The key commands work perfect and my code does not.:tongue-ti
 
Solved: I found that the localizer should not be tied to the nav mode. The localizer mode is auto turned on by the backcourse or the approach hold. The nav mode only needs the nav1 hold as it will auto disable and turn on the localizer when either of these 2 modes i mentioned are on. Also the nav1 mode holds a tuned localizer as well as the nav stations. So there really is no need to use the localizer in my coding as it's an auto feature based on other settings.

And now the approach mode holds perfect at any speed.:yikes:
 
Back
Top