fix(a380x/sfcc): slats/flaps cruise baulk display fixes #10425
+196
−123
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.
Summary of Changes
Previously overspeeding CONF 1 would cause the slats/flaps cruise baulk to trigger, leading to an erroneous ECAM message of
F/CTL FLAP LEVER NOT ZERO, instead of the overspeed warning.Previously the slats/flaps cruise baulk would display
1+Fon the lower PFD. Logically I think either0or1would display on the actual aircraft, I have changed it to1in this PR following a discussion on Discord.Screenshots (if necessary)
Overspeeding before:
a380_flap_retr_before.mp4
Overspeeding after:
a380_flap_retr_after.mp4
Lower PFD in cruise baulk (not 100% sure it would display this, but it's better than it was before at 1+F):

References
Additional context
Discord username (if different from GitHub):
fozzie
Testing instructions
F/CTL FLAP LEVER NOT ZERO.CONF 1VFE or above 22,000ft, move the flaps handle to 1. Check thatF/CTL FLAP LEVER NOT ZEROdisplays on the ECAM, and that CONF1is displayed on the lower PFD.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.