fix: do not crash pfd when ls frequency = 0 #6856
Merged
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 #[issue_no]
Summary of Changes
For a short moment, NAV FREQUENCY:3 can return 0 which crashes the PFD as it tries to split that frequency for displaying. This PR adds a check that the frequency is splitted correctly and aborts further execution if it's invalid.
Screenshots (if necessary)
References
Additional context
Discord username (if different from GitHub):
Testing instructions
Enable the LS info on the PFD and enter different ILS frequencies (in range, out of range, valid and invalid combinations) and make sure the PFD stays on all the time and shows valid information.
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.