Skip to content

Conversation

@flogross89
Copy link
Contributor

@flogross89 flogross89 commented Oct 18, 2025

Fixes #9705
Fixes #10043

Summary of Changes

  • add INOP SYS: BTV, ARPT NAV, ROW/ROW, RWY OVERRUN PROT
  • add LIMITATIONS: LDG DIST AFFECTED, LDG PERF AFFECTED
  • add BTV/ROW/ROP failure states to FCDC
  • add BTV/ROP/ROW deactivation in Rust for failure states
  • add triple clicks for BTV disarming/deactivation
  • add ROW/ROP automatic runway detection in fbw-common
  • Fix: [A380X] BTV top message not hidden after landing and auto brake disengagement #10043: Hide BTV message when deactivating, delete BTV data

Note: The arming/disarming and reversion logic might not be 100% accurate yet, but it brings us closer to where we want to be.

Screenshots (if necessary)

References

Additional context

Discord username (if different from GitHub): floridude

Testing instructions

Regression tests:

  1. Perform BTV landing with Navigraph linked and exit selected through OANS (normal landing)
  2. Perform approach with Navigraph linked and runway selected through OANS (long flare, wait until "RWY TOO SHORT" triggers)
  3. Perform BTV landing with Navigraph not linked (i.e. fallback), selected landing distance through OANS control panel (normal landing)
  4. Perform BTV landing with Navigraph not linked (i.e. fallback), selected landing distance through OANS control panel (long flare, wait until "RWY TOO SHORT" triggers)

New features test:

  1. Don't set any FMS destination airport or FMS landing runway. Approach arbitrary airport, perform low approach without landing. At the end of the runway, "RWY TOO SHORT" should be visible in the PFD and audible
  2. Confirm that BTV RWY indication does not reset #9705 and [A380X] BTV top message not hidden after landing and auto brake disengagement #10043 are fixed
  3. Set up aircraft for BTV landing selected through OANS; Fail BTV (either by pulling ARPT NAV reset knob or disabling one PRIM), BTV should downgrade to BRK HI and shouldn't activate on landing

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

add LIMITATIONS: LDG DIST AFFECTED, LDG PERF AFFECTED
add BTV/ROW/ROP failure states to FCDC
@flogross89 flogross89 added QA A380 Only QA only for A380 required A380X Related to the A380X aircraft labels Oct 18, 2025
@flogross89 flogross89 added this to the v0.15.0 milestone Oct 18, 2025
- triple click when deactivation on ground or disarming in flight below 700ft RA
- BTV fault conditions to Rust
- ROW/ROP fault conditions to Rust
- add LGCIU bus publisher
- refactor BtvPublisher to account for the above
- set airport when landing RWY detected by ROPS
… communication to Rust BTV from one place (in systems-host)

still doesn't work
# Conflicts:
#	fbw-a380x/src/systems/systems-host/PseudoPRIM/BrakeToVacateDistanceUpdater.ts
#	fbw-common/src/systems/instruments/src/OANC/Oanc.tsx
#	fbw-common/src/systems/instruments/src/OANC/OansBrakeToVacateSelection.ts
#	fbw-common/src/systems/oans/OansMapProjection.ts
#	fbw-common/src/systems/shared/src/publishers/OansBtv/FmsOansPublisher.ts
Copy link
Contributor

@BravoMike99 BravoMike99 left a comment

Choose a reason for hiding this comment

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

Some minor comments, also, you forgot to take it out of draft I believe

@flogross89 flogross89 marked this pull request as ready for review November 8, 2025 01:59
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.

Just reviewing the ARINC bus publishers only.

@flogross89 flogross89 requested a review from tracernz November 9, 2025 00:09
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.

Thanks for the fixes! I scanned over the rest and note a couple of small suggestions. Otherwise LGTM with the import that's failing the build fixed up.

Copy link
Contributor

@BravoMike99 BravoMike99 left a comment

Choose a reason for hiding this comment

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

Some more minor things

Copy link
Contributor

@BravoMike99 BravoMike99 left a comment

Choose a reason for hiding this comment

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

Some minor things

Copy link
Contributor

@Jonny23787 Jonny23787 left a comment

Choose a reason for hiding this comment

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

Just for future consistency

# Conflicts:
#	fbw-a380x/src/systems/systems-host/CpiomC/FlightWarningSystem/FwsCore.ts
#	fbw-a380x/src/systems/systems-host/CpiomC/FlightWarningSystem/FwsLimitations.ts
@Jonny23787
Copy link
Contributor

Jonny23787 commented Dec 9, 2025

Quality Assurance Tester Report

Discord Username : jonny_23
Object of testing : #10372
Aircraft : A380X
Simulator : 2020
Tier of Testing : 1
Date : 09/12/2025

Testing Process:
All testing conducted without Navigraph

  1. Tested BTV manual landing, BTV activated.
  2. Performed a long flare with RWY in FMS, RWY TOO SHORT message appeared on PFD.
  3. Performed a long flare without RWY or airport in FMS, RWY TOO SHORT message appeared on PFD.
  4. BTV top message did not disappear after landing.
  5. Setup BTV landing, pulled ARPT NAV reset switch, braking reverted to HI and triggered correctly upon landing.

Testing Results:
Not Passed

Negatives:

  1. Runway length did not appear on the manual control / fallback page.
  2. BTV message did not hide after landing with either full or downgraded BTV
  3. After performing BTV landing an arbitrary distance was inserted in the BTV STOP DISTANCE field, I did not insert this value at any time.
  4. After performing a long flare without RWY or airport in FMS, runway appeared as a top message, is this correct behaviour?

Conclusions:

Media:
Screenshot 2025-12-09 173219
Screenshot 2025-12-09 172346

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 QA A380 Only QA only for A380 required QA Failed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[A380X] BTV top message not hidden after landing and auto brake disengagement BTV RWY indication does not reset

4 participants