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

feat(brakes): Brake To Vacate first simple implementation #8560

Merged
merged 93 commits into from
Aug 26, 2024

Conversation

crocket63
Copy link
Contributor

@crocket63 crocket63 commented Mar 10, 2024

Fixes #[issue_no]

Summary of Changes

This is a first simple implementation that is by no mean "study level", but which should work relatively close to a nominal BTV scenario.

  • Braking scheduler that estimate needed deceleration
  • Runway occupancy time optimisation: braking is delayed as much as possible
  • WET DRY Stop bar computations
  • OANS exit selection
  • OANS ROT prediction
  • Placeholder Runway Overrun Protection

Screenshots (if necessary)

References

Additional context

Discord username (if different from GitHub):

Testing instructions

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, click on the bottom PR tab
  4. Click on either flybywire-aircraft-a320-neo or flybywire-aircraft-a380-842 download link at the bottom of the page

Copy link
Contributor

@Gurgel100 Gurgel100 left a comment

Choose a reason for hiding this comment

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

Maybe adding some comments which values should be transfered via AFDX instead of Arinc429 makes sense.

@crocket63
Copy link
Contributor Author

Maybe adding some comments which values should be transfered via AFDX instead of Arinc429 makes sense.

I have absolutely no clue about this :D Maybe @flogross89 have a better idea from BTV docs?

@flogross89
Copy link
Contributor

Maybe adding some comments which values should be transfered via AFDX instead of Arinc429 makes sense.

I have absolutely no clue about this :D Maybe @flogross89 have a better idea from BTV docs?

I also don't have any references, my gut feeling says that any novel data (between OANS and BTV) is exchanged via AFDX. So the different braking distances, predicted stop distances, and distances to runway end and exit.

@Benjozork
Copy link
Member

Benjozork commented Aug 25, 2024

I think the OANC between the 320 and 380 is the same part, therefore it's probably A429.

@flogross89
Copy link
Contributor

I think the OANC between the 320 and 380 is the same part, therefore it's probably A429.

Do you think it has the same architecture on the a320, and just doesn't offer/display rwy/exit selection and DRY/WET distance input?

@crocket63 crocket63 enabled auto-merge (squash) August 26, 2024 06:26
@tracernz
Copy link
Member

tracernz commented Aug 26, 2024

I think the OANC between the 320 and 380 is the same part, therefore it's probably A429.

Do you think it has the same architecture on the a320, and just doesn't offer/display rwy/exit selection and DRY/WET distance input?

The A320 ROW/ROP does not have anything to do with the OANC. It also doesn’t have BTV. Regarding wet/dry, the 2nd iteration adds the selector switch in the cockpit.

@crocket63 crocket63 merged commit 43f4fe2 into flybywiresim:master Aug 26, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A380X Related to the A380X aircraft Needs Code Review
Projects
Status: ✔️ Done
Development

Successfully merging this pull request may close these issues.

6 participants