-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autothrottle shouldn't need FDs to be engaged #591
Comments
hmm, can you find a reference for this, because its definately not "that" independant - turning both the fds off and on is required for several at states. |
Turning off Flight Directors is required at times to get rid of the magenta bars on the PFD as they can distract and confuse pilots for example on a visual raw data approach. This doesn't have anything to do with the autothrottle. |
it clearly says you have to reengage the autothrottle after turning both the flight directors off without touching the at arm switch and that turning off both flight directors deactivates all modes. so any change there will need a reference that something different happens |
"all modes" disengaging the AP does not disconnect the AT, or change the flight mode |
Now,it could be that only the bars go off when turning both flight directors off with the autopilot engaged, but again - really need a reference of some kind. |
bars go off when FDs go off
By all modes, they mean all autopilot modes on the FMA and MCP like LNAV, VNAV, HDG, HDG HOLD, VS, ALT etc. The autothrottle is not connected to that. Again, second pic is a procedure, not a system description, that tells the pilots to turn the FDs off and on to get into ATT and VS mode, nothing to do with the autothrottle or autopilot. No, the PMDG is not bugged. I get what you mean but that's not the way it works. AFDS modes on the FMA are still displayed because the autopilot is engaged with those modes active, and the FMA shows that info. The FMA purely supplies info on what modes are active for both the Flight Directors and the autopilot. Again, all modes doesn't mean what you think it does, and doesn't have anything to do with the autothrottle either. I ask you to please take another look at this: It literally says the only results of turning off the Flight Directors is "steering indications do not display", which are the magenta bars |
Yeah the flight directors isnt connected to the autothrottle in any plane and shouldnt be affected by it |
Boeing doesnt recomend flying with just AT but you should be able to have the autothrottle on even with FD off, there are several video on youtube showing this. |
The only job for the FD is to show a magenta flight director on your PFD guiding the pilot in HDG, LNAV, VNAV or APP etc.. |
It does, because in the ils sidestep as it is written in the fcom the autothrottle is disconnected when the fd's are turned off. - which is wrong. |
that's not what I was talking about, you said "it currently resets all modes per picture with fcom saying all modes deactive with fd and ap off" so I said that with all modes the fcom means lnav, vnav, hdg, hdg hold, alt, vs, loc, gs etc and not the autothrottle |
yes. currently it resets all modes and as per the ils sidestep procedure you have to re engage both the autopilot and autothrottle after turning the fds off then on. when this issue gets fixed it will not be possible to follow the ils sidestep procedure as it is written, but thats ok because the sidestep procedure as it is written is wrong. the post I was replying to said doing it this way "made no sense". |
for future reference, that still wouldnt have been enough to deternine the official 747-400 documentation is wrong. |
The original issue is now fixed, everything we talked about after isn't. but since so much AT related stuff just changed its better to make them as new issues, collect them under an "AutoThrottle" milestone and deal with them for the 3rd release. |
In the sim the Autothrottle need the FDs to be engaged. When you turn the FDs off, all the FMA data disappears so it looks like the Autothrottle is disengaged while it actually is still engaged. In real life the Autothrottle works completely independant from the Flight Directors. When the Autothrottle is engaged and Flight Directors are off, the FMA should still display whatever speed mode is active as also the FMA works independant from the FDs and just displays information about it. Linked with #573 which I now closed as this explanation is easier to understand and more complete.
The text was updated successfully, but these errors were encountered: