feat: add reset flight plan on DB switch

[Maverickwoe]

Fixes #6216

Summary of Changes

Changed the Data/ "A/C" page on MCDU. You can now press on the secondary database. It will not switch to any other database as there is none available but it will

• erase the flight plan
• all stored data (waypoints etc)
• erase weight and fuel.
• erase cost index, flight level and flight number
  Added also an option to reflect future versions of FMC with confirmation before swapping database.
  Did not implement anything related to FMC position reset, navigation display blank and speed prediction as navigation position has not yet been implemented.

Screenshots (if necessary)

Before:

After change :

References

Entirely relying on documentation that is listed in the issue #6216 (FMC manual)

Additional context

Discord username (if different from GitHub): Garoomf#4683

Testing instructions

Tests on video:
https://youtu.be/7NhjUAVqoa4 - on ground, complete test
https://youtu.be/ndm-00CtlyE - in flight, partial test

Test all combinations of these first steps:

-Setting an origin and destination in MCDU
-Adding additional nav points on the flight plan
-fly or on the ground
-add an additional waypoint in your database (or airport or navaid)
-add flight level, cost index and flight number

Second step
-go in Data/"A/C" page and press on the third button from top on the left.
-a scratch pad message shall appear "CHECK WEIGHT" only if in flight, it should not when on ground
-Verify there is no more any mention of stored data on the same page.
-Verify that the flight plan is blank on the FL PLN page
-Verify that the origin and destination are reset on INIT A, as well as Flight level, index and flight number.
-Verify on INIT B that Weight and fuel data are blanck
-Verify that the speed and heading switch to selected on AP if in flight

Final step:
-Set a new origin/destination in INIT A
-Verify that none of the data listed above reappears.

Side effect :
NOTE that these changes may affect also the STORED DATA erase on the same page.
Verifying that this other feature has not been affected is important too.

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.

1. Make sure you are signed in to GitHub
2. Click on the Checks tab on the PR
3. On the left side, click on the bottom PR tab
4. Click on the A32NX download link at the bottom of the page

[tracernz]

Might be worth looking into setting up vscode for code formatting.

[tracernz]

LGTM 👍

outdated

[mico975]

Quality Assurance Tester Report

Discord : mico#3145
Object of testing: #7781
Tier of Testing : 1
Date : 17/02/2023

Testing Process:
Test all combinations of these first steps:

-Setting an origin and destination in MCDU
-Adding additional nav points on the flight plan
-fly or on the ground
-add an additional waypoint in your database (or airport or navaid)
-add flight level, cost index and flight number

Second step
-go in Data/"A/C" page and press on the third button from top on the left.
-a scratch pad message shall appear "CHK FUEL" - NOT OK, doesn't appear. CHECK WEIGHT appears in flight.
-Verify there is no more any mention of stored data on the same page. - OK
-Verify that the flight plan is blank on the FL PLN page - OK
-Verify that the origin and destination are reset on INIT A, as well as Flight level, index and flight number. - OK
-Verify on INIT B that Weight and fuel data are blanck - OK
-Verify that the speed and heading switch to selected on AP if in flight - OK

Final step:
-Set a new origin/destination in INIT A
-Verify that none of the data listed above reappears. - OK

Side effect:
NOTE that these changes may affect also the STORED DATA erase on the same page.
Verifying that this other feature has not been affected is important too. - OK

Negatives:
CHK FUEL does not appear, otherwise okay.

Testing Results:
Passed

Conclusions:
LGTM, with a small issue

[Maverickwoe]

Quality Assurance Tester Report

Discord : mico#3145 Object of testing: #7781 Tier of Testing : 1 Date : 17/02/2023

Testing Process: Test all combinations of these first steps:

-Setting an origin and destination in MCDU -Adding additional nav points on the flight plan -fly or on the ground -add an additional waypoint in your database (or airport or navaid) -add flight level, cost index and flight number

Second step -go in Data/"A/C" page and press on the third button from top on the left. -a scratch pad message shall appear "CHK FUEL" - NOT OK, doesn't appear. CHECK WEIGHT appears in flight. -Verify there is no more any mention of stored data on the same page. - OK -Verify that the flight plan is blank on the FL PLN page - OK -Verify that the origin and destination are reset on INIT A, as well as Flight level, index and flight number. - OK -Verify on INIT B that Weight and fuel data are blanck - OK -Verify that the speed and heading switch to selected on AP if in flight - OK

Final step: -Set a new origin/destination in INIT A -Verify that none of the data listed above reappears. - OK

Side effect: NOTE that these changes may affect also the STORED DATA erase on the same page. Verifying that this other feature has not been affected is important too. - OK

Negatives: CHK FUEL does not appear, otherwise okay.

Testing Results: Passed

Conclusions: LGTM, with a small issue

Thanks for your verification @mico975
I got lazy and didn't double check the exact message before writing it down in the test procedure, sorry for that.
I updated the test procedure to reflect your results on this item as it is what was expected.
Sorry again !

[beheh]

@Maverickwoe I've added a reference image to the ticket for the H4 confirmation message. Please make sure your implementation matches it (if it doesn't already). Thanks!

[Maverickwoe]

@Maverickwoe I've added a reference image to the ticket for the H4 confirmation message. Please make sure your implementation matches it (if it doesn't already). Thanks!

Thanks for the image @beheh . Yes, I was aware of it and it is implemented as shown but disabled by config in my code for now.
We'll have to change
const confirmDataBaseSwitch = true
in the IdentPage.js to see the double step confirmation and this specific message.
As the version of MCDU we're targeting does not include this message, I purposely disabled it until we change our target.

Note that I just committed a change to display the date in amber instead of red. I was shown an image that suggested it was red, not amber but will take yours as reference.

[tracernz]

Looking at the testing instructions, I don't beleive a CHECK WEIGHT message should be generated. Perhaps there is something not quite right with it's logic.