-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat(fms): implement TOO STEEP PATH #9680
feat(fms): implement TOO STEEP PATH #9680
Conversation
fbw-a32nx/src/systems/fmgc/src/guidance/vnav/descent/ApproachPathBuilder.ts
Show resolved
Hide resolved
6865f10
to
01585c3
Compare
01585c3
to
ad8f3c2
Compare
ad8f3c2
to
102bf5a
Compare
Quality Assurance Tester Report Discord Username : alexdnzdmb Testing Process:
Testing Results: Negatives: Dont know whether scrolling behaviour was touched by this PR |
102bf5a
to
ebe56b5
Compare
2a06586
to
8b8324b
Compare
Fixes #[issue_no]
Summary of Changes
When the FMS predicts that a segment between two altitude constraints cannot be met, it shows a TOO STEEP PATH marker.
When the aircraft sequences the first of those constraints, the linear deviation (yoyo) will jump, putting the aircraft high on profile. When a vertical profile is predicted to have a TOO STEEP PATH segment, the "TOO STEEP PATH AHEAD" scratchpad message is shown. On the vertical revision page of the legs before and after the marker, the TOO STEEP PATH BEYOND indication is shown.
Screenshots (if necessary)
References
Additional context
Discord username (if different from GitHub):
Testing instructions
This affects both the A32NX and the A380X.
How to download the PR for QA
Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.