fix(nd): Added method to handle Groundspeed display logic #9553
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #9545
Summary of Changes
Added method to handle GS display logic
Added method to handle TAS display logic
Set logic for both GS and TAS display - Dashes if NCD, blank if FW, and normal otherwise
Screenshots (if necessary)
References
Picture and discussion on issue 9545
Additional context
Discord username (if different from GitHub):MrJigs
Testing instructions
Spawn on the ground with engines running and observe TAS value being dashed on ND
Takeoff, TAS will display data >60kts
Trigger failure such as ADIRS, TAS and GS will be blank
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.