feat(a380x/fms): FMC reset through overhead reset panel

[flogross89]

Summary of Changes

Enable resetting FMCs through overhead reset panel. Lays ground work for future system resets.

• Add XML templates for overhead reset panel buttons for FMCs
• Add logic for FMS re-initialization when pulling C/Bs or rather reset P/Bs
• Display "FMS PAGE NOT AVAIL" and "MAP NOT AVAIL" when appropriate

Screenshots (if necessary)

Disclaimer: Even when the ND shows "MAP NOT AVAIL", the route is still shown. Either it's the new BACKUP TRAJ feature, or I simply didn't refactor the ND yet (out of scope for this PR, needs larger flight guidance/AFS CP adaptions likely):

References

Additional context

Discord username (if different from GitHub):

Testing instructions

1. Set up FMS using SOP
2. Pull FMC-A, FMC-B and FMC-C reset push buttons (on overhead panel), FMS should be reset as soon as all three buttons are pulled out - but not earlier
3. Try resetting or failing (via EFB) different combinations of FMCs, and play around with the FMS switching knob. The MFD system selector ("FMS x") should behave as expected, i.e. display FMS 1, FMS 2, FMS 1-C or FMS 2-C depending on the configuration.

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.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, find and click on the PR Build tab
4. Click on either flybywire-aircraft-a320-neo, flybywire-aircraft-a380-842 (4K) or flybywire-aircraft-a380-842 (8K) download link at the bottom of the page

[tracernz]

Just checked the XML.

[BravoMike99]

Quality Assurance Tester Report

Discord Username : bruno_pt99
Object of testing : #9685
Aircraft : A380X
Tier of Testing : 1
Date : 05/01/2025

Testing Process:
Setup FMS:

• Pulled reset buttons of each FMC individually. FMC resets after all 3 have been pulled ✔️

• Pushed the reset buttons to bring the FMCs back to life and route flickering happened on ND & on pfd target speeds, in addition, the MFD pages still show data and stop doing so after a page change/refresh ❌

Testing Results:
Not Passed

Negatives:
Weird stuff happens on PFD & ND after FMS is reset. As visible, the route appears flickering despite no route being present on MFD, target speeds on PFD flicker etc (check media).
I would also go against resetting the FMS data immediately after power is lost. Chances are there's some kind of internal battery which stores the data for some time like the A320.

Media:
https://github.com/user-attachments/assets/5c2181e1-5523-479e-8033-c2bb6c6c970e

[flogross89]

Quality Assurance Tester Report

Discord Username : bruno_pt99 Object of testing : #9685 Aircraft : A380X Tier of Testing : 1 Date : 05/01/2025

Testing Process: Setup FMS:

• Pulled reset buttons of each FMC individually. FMC resets after all 3 have been pulled ✔️
• Pushed the reset buttons to bring the FMCs back to life and route flickering happened on ND & on pfd target speeds, in addition, the MFD pages still show data and stop doing so after a page change/refresh ❌

Testing Results: Not Passed

Negatives: Weird stuff happens on PFD & ND after FMS is reset. As visible, the route appears flickering despite no route being present on MFD, target speeds on PFD flicker etc (check media). I would also go against resetting the FMS data immediately after power is lost. Chances are there's some kind of internal battery which stores the data for some time like the A320.

Media: https://github.com/user-attachments/assets/5c2181e1-5523-479e-8033-c2bb6c6c970e

Thanks! Three changes with the latest commit:

• Don't destroy and re-init FMC, but rather reset
• Only reset when buttons are pulled, not when power is lost
• Improve reset logic, fix another bug

I didn't implement a reset when power is lost for a longer period of time, it just never resets when power is lost (i.e. change nothing compared to previous behavior, keep that for another PR)