Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(fms): use entered fob rather than fqi before start #8664

Merged
merged 12 commits into from
Sep 21, 2024

Conversation

patmack14
Copy link
Contributor

#8639

Fixes #[issue_no]

Summary of Changes

Added 2 lines:
1.A check to see if an engine is running->Pull from sensed fuel tank levels.
2. Engine !Running -> Pull from entered block fuel
3. Also added some class and method comments noting where top level parameters originate from...spent many hours on a wild goose chase on this PR! Recommend inserting into docs somewhere down the line.

Screenshots (if necessary)

References

@BlueberryKing and @BravoMike99.
As previously stated I no longer have access to the pilot Discord channel, unable to use previous verification method.

Additional context

Discord username (if different from GitHub):

Testing instructions

Prior to engine start, the Destination EFOB should be pulling from entered block fuel, after start the figure should switch over to using sensed fuel level in the tanks.

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 or flybywire-aircraft-a380-842 download link at the bottom of the page

@patmack14
Copy link
Contributor Author

patmack14 commented May 27, 2024

Special thanks to @BlueberryKing for helping to knock some rust off(I've been on a dev hiatus) and throwing me a bone for showing me where the FOB is initially injected!

Copy link
Member

@tracernz tracernz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional things to do:

  • Refactor getGrossWeight a little as it duplicates this FQI logic.
  • Check that all the consumers of getFoB can handle it being undefined, as it always returned a number before. Some definitely can not, so some changes will be needed. Perhaps a new getFqiFob function could be created, wrapping the simvar read, and the fuel pred page could call it instead.
  • Check that the AOC actually wants this value, or does it always want the FQI FoB? (Note that the AOC shouldn't actually directly access the FMS, as it lives in a different computer in the real aircraft, but fixing that is out of scope for this PR.)

Fix the PR title inline with https://www.conventionalcommits.org/en/v1.0.0/. Suggest fix(fms): use entered fob rather than fqi before start or something like that. Whatever you put here will become the commit title when this PR is squash-merged later.

In general you always need to be very mindful of type safety when working on the legacy JS code, as unlike typescript there is no automatic type checking.

@patmack14 patmack14 changed the title FIx for #8639 fix(fms): use entered fob rather than fqi before start May 27, 2024
Co-authored-by: Michael Corcoran <[email protected]>
@patmack14
Copy link
Contributor Author

patmack14 commented May 28, 2024

Additional things to do:

  • Refactor getGrossWeight a little as it duplicates this FQI logic.
  • Check that all the consumers of getFoB can handle it being undefined, as it always returned a number before. Some definitely can not, so some changes will be needed. Perhaps a new getFqiFob function could be created, wrapping the simvar read, and the fuel pred page could call it instead.
  • Check that the AOC actually wants this value, or does it always want the FQI FoB? (Note that the AOC shouldn't actually directly access the FMS, as it lives in a different computer in the real aircraft, but fixing that is out of scope for this PR.)

Fix the PR title inline with https://www.conventionalcommits.org/en/v1.0.0/. Suggest fix(fms): use entered fob rather than fqi before start or something like that. Whatever you put here will become the commit title when this PR is squash-merged later.

In general you always need to be very mindful of type safety when working on the legacy JS code, as unlike typescript there is no automatic type checking.

Have a few questions here:

  1. There are getGrossWeight() and getGW() ..are these used for different reasons? seem to have somewhat repeated functionality.I can certainly condense both of these or combine them ( if that makes sense).
  2. Regarding the type:
    Rather than going down a type checking rabbit hole I was thinking of doing something like
//If do a null check rather than just else, it should basically retain the same functionality as original and still be undefined/NaN thus not messing with AOC and/or other unintended consequences?
else if(this.blockFuel){
              return this .blockFuel;
              }

Feel free to message on Discord to bounce ideas/thoughts if above does not work.

@tracernz
Copy link
Member

Part of the job here is understanding the aircraft systems and how things should actually work before we touch the code, as then we can understand how the code should look. That part is unfortunately much more difficult than the code. You happen to have picked an area where the gross weight calculation code is relatively simple, but the systems changes required are definitely not trivial, and spread around quite a wide area of the FMS. All of the consumers of GW/FOB should handle those values not being undefined because they really are not available prior to engine start with no ZFW/FOB entered. Some of the things getGW does look very dubious, especially setting a local var, so there's opportunity for a good clean up there too.

@patmack14
Copy link
Contributor Author

@tracernz
I've been thinking about how to handle this-
Would finding the AOC customers of getFob and put the same if (!engineRunning) ->return type scheme work for everyone?
I agree handling it that way would cut back on unecesssary function calls/bouncing between classes.

@@ -4996,10 +5001,9 @@ class FMCMainDisplay extends BaseAirliners {
//TODO: Can this be util?
getGW() {
let fmGW = 0;
if (this.isAnEngineOn() && isFinite(this.zeroFuelWeight)) {
//Simplified to just checking fuelWeight as GetFOB handles what fuel level to use (block vs tank reading)
if (isFinite(this.zeroFuelWeight)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Careful, what happens if you've not entered a block fuel yet?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm Yes Thanks for catching

Can the way the current aircraft release handles this scenario be used as a "control" or do the IRL pilots need to be consulted for what the behavior is in this situation?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm Yes Thanks for catching

Can the way the current aircraft release handles this scenario be used as a "control" or do the IRL pilots need to be consulted for what the behavior is in this situation?

I'd have to check the places this function is called from, but replicating the current behavior would be a good starting point.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK Sounds good.

Added an additional check to check for block fuel being entered to prevent "A32NX_FM_GROSS_WEIGHT" from being Null
@2hwk
Copy link
Member

2hwk commented Jul 14, 2024

@BlueberryKing to approve as well

@patmack14
Copy link
Contributor Author

@BlueberryKing
Wanted to check in with you on this to see if you have had a chance to review this and see if it needs a few more tweaks or able to move to test?
Thanks!

Comment on lines 106 to 108
if (mcdu.isAnEngineOn()) {
const currentFob = formatWeight(NXUnits.kgToUser(mcdu.getFOB()));
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest we move this if block to the block further down where currentFob is used.

Copy link
Contributor Author

@patmack14 patmack14 Aug 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BlueberryKing
Thinking you mean like this? (Removing line 106->108 and adding to Line 130)

            currentFob = formatWeight(NXUnits.kgToUser(mcdu.getFOB()));
            if (currentFob) {
                fob = `{small}${currentFob}{end}[color]green`;
            }
        }`

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can remove these lines (106-108) now, right?

@@ -4996,10 +5001,9 @@ class FMCMainDisplay extends BaseAirliners {
//TODO: Can this be util?
getGW() {
let fmGW = 0;
if (this.isAnEngineOn() && isFinite(this.zeroFuelWeight)) {
//Simplified to just checking fuelWeight as GetFOB handles what fuel level to use (block vs tank reading)
if (isFinite(this.zeroFuelWeight) && this.blockFuel) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think checking for this.blockFuel works here. With an engine running, the gross weight should be available (since fuel is available from FQI) even if no block fuel is entered.

What I suggest is fetching this.getFOB() and checking whether that's finite instead.

Also, I prefer Number.isFinite over isFinite since isFinite(null) is true which is rarely desired.

Copy link
Contributor Author

@patmack14 patmack14 Aug 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

//Does this work? I removed unnecessary else block for simplicity sake as well since fmGw already is at 0.

getGW() {
        let fmGW = 0;
        const currFob = this.getFOB();
        //Simplified to just checking fuelWeight as GetFOB handles what fuel level to use (block vs tank reading)
        if (Number.isFinite(this.zeroFuelWeight) && Number.isFinite(currFob)) {
            fmGW = (currFob + this.zeroFuelWeight);
        }
        SimVar.SetSimVarValue("L:A32NX_FM_GROSS_WEIGHT", "Number", fmGW);
        return fmGW;
    }

@pilotseyea350
Copy link

Quality Assurance Tester/Trainee Report

Discord Username : PilotEyesA350
Object of testing : #8664
Aircraft : A32NX
Tier of Testing : 1
Date : 20/09/2024

Testing Process:

  1. Power Aircraft Up
  2. Enter EDDF/EDDM in INIT A
  3. Enter random DEP & ARR RWY & random SID/STAR
  4. Delete any discontinuity
  5. Refuel Aircraft through the FlyPad
  6. Enter a higher FOB in INIT B than there actually is in the fuel tanks
  7. Enter data in PERF
  8. Verify EFOB at EDDM
  9. Start any of the 2 engines
  10. Check EFOB at EDDM has decreased compared to EFOB before engine start

Testing Results:
Passed

Negatives:
N/A

Conclusions:
Worked like a charm, thanks for your hard work !

Media:
N/A

@BlueberryKing BlueberryKing enabled auto-merge (squash) September 21, 2024 18:46
@BlueberryKing BlueberryKing merged commit b978453 into flybywiresim:master Sep 21, 2024
7 checks passed
tracernz added a commit to tracernz/a32nx that referenced this pull request Sep 28, 2024
…8664)

* FIx for flybywiresim#8639

* Update .github/CHANGELOG.md

Co-authored-by: Michael Corcoran <[email protected]>

* Update A32NX_FMCMainDisplay.js

removed comments and extra conversion

* adding to make sure an engine is running in AOC

* additional gw safety

Added an additional check to check for block fuel being entered to prevent "A32NX_FM_GROSS_WEIGHT" from being Null

* updates per @BlueberryKing suggestions

Add .isFinite type safety for and isAnEngineOn()  logic instead of currentFoB()

* forgot to remove 106->108..doh!

* Fix formatting

---------

Co-authored-by: Michael Corcoran <[email protected]>
Co-authored-by: BBK <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✔️ Done
Development

Successfully merging this pull request may close these issues.

5 participants