-
-
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
fix: fix ETA of TO waypoint display on ND #8252
fix: fix ETA of TO waypoint display on ND #8252
Conversation
Hi, on Honeywell FMGS aircraft which the FBW is simulating, the ETA becomes available as soon as the FMS transitions to the takeoff phase (GS greater than 90kts assuming takeoff power is set) while on rollout it seems to disappear somewhere below 100kts. The behavior you implemented seems to be the one of the Thales FMS which is the case on the videos you provided. In case you want to change that, here are a few videos with Honeywell: https://youtu.be/8EHTmIsz1oI https://youtu.be/UQE-g7yrY3w https://youtu.be/A1D2X9KELkM |
Additionally, the value transmitted from the FMS should be changed rather than the ND code (it already transmits -1 when some other conditions that make the ETA not computed are present). |
PPOS and MANUAL shouldn't have any predictions too, so no bearing track or distance. |
@pinatacolada Can you, please, explain what MANUAL is in this context? |
It's when the current leg is a MANUAL leg, the to waypoint is displayed as MANUAL without any prediction |
FM/VM legs. |
d723791
to
38d3535
Compare
Hey all, I've refactored a bit:
|
5cc4ac2
to
df31e26
Compare
* fix: ETA of TO waypoint is not displayed prior to takeoff and after landing in real aircraft * doc: changelog
* Move the logic to guidance controller, outside of ND and LnavDriver This allows to update Efis after the are no more active legs
c81bf85
to
438e597
Compare
QA Report Discord: alepouna Testing Process:
Testing Results: |
@@ -112,6 +115,8 @@ export class GuidanceController { | |||
|
|||
verticalProfileComputationParametersObserver: VerticalProfileComputationParametersObserver; | |||
|
|||
lastActiveLeg: Leg | null; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this used for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is used to update efis with the data based on the active leg computed by the LnavDriver.
If there's no more active leg, ETA, bearing and distance will be updated not to appear on the ND.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, my apologies, I missed that somehow 😄. Nevertheless, I think the property is redundant because we already store activeGeometry
and activeLegIdx
in the GuidanceController
, so we can just derive the active leg there, rather than having it set in LnavDriver
. This is just a minor thing though, so let me know if you have a different opinion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no worries, probably you're right on this one.
I've made the change, have a look.
Co-authored-by: BBK <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
QA Report Discord: alepouna Testing Process:
Negatives: Testing Results: Edit: |
There's some confusion here :)
Update: |
It might also be a good idea to update the summary of changes & testing instructions to the honeywell behavior (GS based) as they still refer the Thales behavior/before the changes. |
You're right, I should've updated instructions. |
I have downloaded the artifact provided by the GitHub action as it is the same (to my knowledge) artifact that is provided to the end users. I have re-downloaded the artifact and still can reproduce the issue. PS: My mistake earlier for the confusion on the issue, I "ate" a step on the testing instruction report. Have updated my comment. |
Can you, please, provide the flight plan you’re using? I’ll try to replicate it. I’m not sure why it’s not working for you. |
Quality Assurance Tester Report Discord: Mack674#2274 Testing Process:
Negatives: N/A Testing Results: Passed Conclusions: Works as intended, great job! |
Fixes #8200
Summary of Changes
Fixes an issue where ETA of TO waypoint is visible on the ND prior to take-off and landing.
I decided to display it when the aircraft is detected to be off the ground and turn it off when it's on the ground (nose wheel pressure detected).
Screenshots (if necessary)
On the ground before the flight plan entered
On the ground after the flight plan entered
Take-off before rotation
Take-off after rotation
Approach
Roll-out with main gear on the ground
Roll-out with nose wheel on the ground
References
Take-off
https://www.youtube.com/watch?v=8DLYoj6S_lw&t=884s
Landing
https://youtu.be/rhI5XGwlnaI?t=269
Additional context
Discord username (if different from GitHub):
alexm1987
Testing instructions
How to download the PR for QA
Every new commit to this PR will cause a new A32NX artifact to be created, built, and uploaded.