Update QA Page

From FlightSimmer7700

QA, how to download a pr needs to be updated as github has changed things round

[META] Create Beginner's Guide

Description

META guide for the A32NX beginners guide section for the docs site. This guide is meant to be beginner friendly and equally as simple to understand for a complete novice. It aims to get the pilot from a cold & dark state to performing an ILS landing.

Each "page" of beginner's guide is listed below with a basic idea of what should be mentioned within the page. Additional content (provided it is within scope) is welcomed by authors.

Images may be required for certain guides to assist in readability and to provide visual references for the end-user.

The lists provided below can be tackled non-sequentially. As this project develops additional information/requirements for the pages included within are subject to modification.

For a basic guide and requirements to assist in this META issue, see the beginner-docs-readme.md in beginner-guide branch.

Legend

PR status = Page Status
❗ = PR - Requires Media / Images

Page Roadmap

This is a basic roadmap of what should be included in the beginner's guide.

Starting the Aircraft - (#123)
Essentially a Cold and Dark guide. Can reference FBW GS Series.
Preparing the MCDU - (#58)
DIFSRIPP
Engine Start and Taxi - (#82)
Basic guide to engine start and taxi procedures (including aircraft behavior)
Takeoff / Climb / Cruise - (#90)
How to perform a takeoff, climbing to cruising altitude, and maintaining cruising altitude.
Descent (Planning up to Final) - (#92)
Inserting a STAR, relative MCDU features
Approach and Landing (ILS only) - (#94)
Performing and accomplishing an approach into an ILS landing.
On the Ground (After landing up to the gate) - (#54)
Powering Down - (#96)
~~Glossary of Definitions~~ Retooled into Abbreviations - (#98)
Providing definitions about Airbus features / commonly used terms in aviation.

To Do

Perform Cleanup
Final Review

Additional Context

If you require assistance feel free to ping or DM on Discord: Valastiri#8902

Create Flex / TO Speeds / THS Setting Summary

Probably include these in the pre-flight section and explain why no takeoff calculator is available for the A320neo.

Issue was brought up by Donbikes.

Throttle calibration guide possibly confusing with T.16000m, joystick only

Hi, i just went through throttle calibration with a T.16000m. Joystick only, the more recent edition with the orange light.

I got stuck at step 5 of the section with the big red DO NOT SKIP warnings

Test
Do not go on with the guide without successfully testing the following:

The throttle in the cockpit should now move in the correct direction.
The throttle in the cockpit should move to TOGA when you set your controller to full thrust.
The throttle in the cockpit should move to IDLE when you set your controller to idle.
The throttle should move to full reverse if you activate reverse thrust on your controller. See Reverser Setup on how to engage reverser when you throttle does not have a reverser range.

Specifically the

The throttle in the cockpit should move to IDLE when you set your controller to idle.

part. At this point i had followed the guide step by step duplicating the default control profile to make a dedicated one for the Airbus, added a keybind to toggle reversers, and set all axes to fully linear as described in the guide. Despite this, when setting my physical throttle to idle, the aircraft throttle would go to full reverse, with the reverse toggle acting as a mere idle button like F1, it would just bring the throttle to idle with no changes to throttle behaviour.

Help from Discord made me find the issue, i had to continue to the EFB part of the setup to set the detents and deactivate the "reverser on axis" toggle. This is basically opposite to what the guide says, that you should repeat the DO NOT SKIP part if you do not meet the throttle behaviour "The throttle in the cockpit should move to IDLE when you set your controller to idle.". But to get that behaviour i needed to ignore that warning and continue to the EFB part of the guide.

Anchored links do not work on Discord mobile

Anchored links do not work on Discord mobile. Page stays at top.

Test these in a message on the Discord mobile app
Example:
https://docs.flybywiresim.com/start/reported-issues/#msfs-live-weather

Wikipedia works though:
https://en.wikipedia.org/wiki/Microsoft_Flight_Simulator_(2020_video_game)#Technology

As Wikipedia anchor links work there seems to be an issue we could potentially fix on our side.

Create autoland advanced guide

See docs thread for discusssion.

PR: #390

Fix broken admonition in pilot briefing

Noticed this in pilot briefing -- EFIS Control Panel

Tiller Page - Assistance off note to the top

Move the note to the top and rephrase to emphasize that it is required in legacy and realistic mode.

[BUG/ERROR] Old mod folder name in the "reported known issues page"

What is the bug/error?

On the "reported known issues" page, the mod folder name still refers to the old naming convention (A32NX).

Expected functionality

It should refer to the new folder name: "flybywire-aircraft-a320-neo".

Steps to reproduce

Additional information

Expand and clarify information in landing calculator pages

Copied from the Discord #docs channel provided by donbikes

Hey all, here is some new information that should be provided in the documentation for using the landing performance calculator. https://discord.com/channels/738864299392630914/754130199804772372/925605355919138816 NOTAMs and ATIS should contain runway condition codes whenever the runway is not dry. This message identifies how to go from the code to the runway condition identifiers in the calculator (good, good-medium, etc.) (We should add the code in parentheses after the descriptor in the calculator.) Also, the link to the SkyLibrary article and the use of the term "Landing Distance Required" is inappropriate for this calculator. The required landing distance is based on different parameters and applies at takeoff where it can limit the takeoff weight. It would be included in a takeoff performance calculator. This landing distance is an "operational landing distance" that is used to perform a landing distance assessment prior to landing. It is mostly for addressing wet and contaminated runway conditions.

Recommendations from Mav -> Inclusion into the flyPad Landing Calculator Page

Update ECAM A320 Briefing

Would be best to link the old system display pages on the instrument panel to either direct to the ECAM section or provide a link to the new pages.

[META] Update - Common Issues / FAQ

Summary

Simple tracking issue to ensure that our common issues page https://docs.flybywiresim.com/fbw-a32nx/support/faq/ is up to date and not duplicating information.

Another consideration is to move this out of the support directory and directly under -- versions and features --

This would sort of provide an easy way for people to quickly look up something they need to read up on and we can internally link to OR offload.

Changes / Considerations

Remove duplicate / out of date questions
Ensure page is in sync with Discord / does not overlap Discord #faq channel
Consider new format (or keep current one)

Please put suggestions in this meta issue. A PR will be open shortly.

Reported Issues: MSFS Anti-ICE vs. De-ICE

Add an issue for the below:
Something you all might want to know about. Just confirmed with Asobo that there is no anti-ice capability in MSFS and no plans to add it anytime soon. The anti-ice systems work as deice systems rather than anti-ice systems. What this means is that the auto probe/windshield heat will not always prevent ice from forming on the windshield or the pitot probe. The ice should melt fairly quickly (and no need to switch from auto to on), but the windshield can still freeze over and you can lose airspeed information upon first entering icing conditions if they are severe enough. The same goes for wing and engine anti-ice - turning them on before ice actually forms may not prevent ice from forming there, but it should melt fairly quickly.

MCDU Web Access Documentation Page

A32NX PR:
flybywiresim/aircraft#3467

Advanced Guides

For advanced A320 features and topics after the beginner guide.

Could take in some of the feature guides (FIX INFO, etc.)

Possible topics see META Documentation Status Quo #73

Pilot Briefing: Glareshield & Instrument Panel - Accuracy Check

Summary

Hope this makes it easier for you to track the issues.

Glareshield -> Flight Control Unit -> Usage -> A/THR pushbutton

The flight crew uses this button to arm, activate, or disconnect the autothrust (A/THR). Lights up in green if the A/THR is armed or active.

Same as above. Normal way to disconnect is by pushing the instinctive disconnect pushbutton on the thrust lever (or retarding the levers to idle). See 22_30-90 Autothrust -> A/THR Disconnection

Glareshield -> Warning Panel -> Usage -> 1. SIDE STICK PRIORITY

Green CAPT and F/O lights : Both lights flash will flash if the pilots are attempting to move both sidesticks at the same time and neither pilot takes priority.

a) Space between lights and : b) Typo/Careless mistake: flash will flash

Glareshield -> Warning Panel -> Usage -> 3. MASTER WARN

Provides an audible warning (repetitive charms, sounds, or a synthetic voice).

Chimes ;)

Glareshield -> Warning Panel -> Usage -> 5. AUTOLAND WARNING LIGHT

3x LDC. Should be LOC (as in localizer)

Instrument Panel

Instrument Panel-> Accumulator Pressure Indication -> Description

ACCU PRESS: Pressure in the yellow hydraulic system brake accumulators.

There's only one brake accumulator.

Instrument Panel-> Accumulator Pressure Indication -> Description (2)

BRAKES: Yellow hydraulic system pressure delivered to the brakes. Measured upstream of the alternate servo valves.

Change to: Measured downstream of the Direct Drive Valves.

Another situation where the FCOM is to blame. The alternate brake system underwent a major overhaul in 2005-2006 and since then the "servo valves" in the alternate brake system are called Direct Drive Valves. The pressure transmitters are downstream of these valves. Everything else doesn't make sense because otherwise they would indicate brake pressure as soon as the NWS switch is selected to off, without the pedals being pushed. I cross checked this with the AMM.

Instrument Panel-> Autobrake and Gear Indications -> Usage -> L/G LEVER

UP: The brake system brakes the wheels of the main gear and a brake band in the nose gear well brakes the nose gear wheels.

The brake band doesn't exist anymore in aircraft built since 2006. The NLG wheels just spin around until they stop eventually.
Even my latest NEO FCOM still has this paragraph, but it's just not true anymore.

Instrument Panel-> Autobrake and Gear Indications -> Usage -> A/SKID & N/W STRG

ON: Lost green hydraulic pressure: Anti-skid remains available, while Nose wheel steering is lost.

Remove while Nose wheel steering is lost.
Nose wheel steering has been changed to the yellow hydraulic system in aircraft built since 2006, so you don't lose NWS with green hydraulic loss.

Instrument Panel-> Autobrake and Gear Indications -> Usage -> AUTO/BRK

It has 4 settings: OFF, LO, MED and MAX.

Can we add a note that MAX can only be selected for takeoff and not when airborne? I get this question quite often (even from colleagues messing around with the flight sim "Hey komp, you know, the fbw Airbus you're working on... I found a bug: I can't select Auto Brake MAX for landing...")

I think we need to double check the parameters for auto braking. I remember there have been changes with the introduction of NEOs. I have these values in my FCOM (which includes both NEO and CEO). If the current values are the values we are using for our model, then everything is fine though.

Instrument Panel-> Clock -> Description

The A320neo has a build-in independent clock which sends time data to several systems. It has redundant electrical supply and is also directly connected to the aircraft's battery hot bus.

Hot Battery Bus, please :)

That's it again. Pedestal will follow in a separate issue.

Update beginner guide with VNAV and Constraints

At the time of writing the A32NX did not have VNAV and ignored speed and altitude constraints when in CLB/DES.
BG needs an update to cover this.

[REQUEST] Remove all unwritten documentation

I feel like having unwritten documentation is an eye-sore and really puts people off from looking further into our documentation as it's a matter of guessing which ones have content.

I say at least archive ones that are not written so you can keep up with what topics we wish to write about.

Server load for assets in beginner guide

Issue

Alleviate server load for serving assets

Possible Solution

Utilize { loading=lazy } on beginner guide pages to alleviate server load on production. In addition to stop-gap measure provided by (#146)

We can explore other issues later.

Sample:

![Placeholder](https://dummyimage.com/600x400/eee/aaa){ loading=lazy }

Clean Install Steps image contains an outdated directory

The image on the "Clean Install Steps" Page https://docs.flybywiresim.com/fbw-a32nx/installation/#clean-install-steps contains an image that has only the directory shown at the top outdated.

While its main purpose is to show which type of files to look at and the directory is mentioned below the image. I was stubborn to look at the image containing the directory than scrolling down for the right information.

Current image on the website:

What the image should look like:

PFD Briefing Corrections - Review in #117

Simple typos. Looks like one too many ~ for VMO (for subscript) and missing subscript entirely for MMO.

Originally posted by @donstim in #177 (comment)

Other comments in #177

[META] Document breaking changes and fixes to support mkdocs-material v8.0.0

Tracking Meta for issues found with the beta version mkdocs-material

Current Version in testing: 8.0.0b1

Custom footer no longer displays "powered by Vercel"
Custom footer has margin errors
Announcement bar center styling is now left-aligned
Tabbed feature -- breaking change

Approach Guide: Conflicting Flaps recommendation

Hi,

in the Approach and ILS Landing guide, there are conflicting flaps recommendations. Or maybe I'm reading them wrong, I'm still learning, hence I might be a good dummy for the beginners guide.

Chapter "Intercepting the ILS localizer", quote: "Set FLAPS to 1 at about VFE -15 knots (but never before speed is below VFE) for the first slat/flap configuration (CONF1). The aircraft will then decelerate further to prepare for the next flaps configuration. Our target is to be CONF 1 at S speed by the time you get to the glideslope intercept."
Chapter "Intercepting the ILS Glideslope", quote: "There is different guidance when to set FLAPS 2 but for beginners we recommend to go to FLAPS 2 before starting the glideslope descent."

The first chapter talks about the point arriving at the GS, the second chapter about before starting the GS. So for me that sounds like the same point-in-time, but with two different flaps recommendation: 1 or 2. Let me know what you think.

Best

MSVF

A few minor comments on the A320neo Pilot Briefing - PFD- Flight Mode Annunciations pages

The strip at the top of the PFD is the Flight Mode Annunciator. The separate columns contain separate flight mode annunciations. In keeping with this concept, you might consider changing the link to this page in the left column of Pilot's Corner list of contents to Flight Mode Annunciator (assuming you are referring to the display itself). If you are referring to the annunciations, then no need to change. But the top of the linked page should not be "Flight Mode Annunciators." Flight Mode Annunciator should always be singular as it refers to the display. The separate columns on that display are "annunciations," not "annunciators." Most of the text on the page uses the correct nomenclature, but the final two paragraphs and the links to the separate chapters mistakenly refer to annunciators rather than annunciations. This same convention should be used correctly in each of the separate chapters.
Autothrust Mode Annunciators [sic] page. In addition to the above issue, I suggest changing the description to, "This will display the autothrust modes that are armed or active, as well as any requested pilot actions."

For the MAN FLX XX description, the other thrust lever must be at or below the MCT/FLX detent just like for the MAN MCT description. For example, if one thrust lever is in the MCT/FLX detent and the other is in the TOGA detent, you would get the MAN TOGA annunciation.
Since the MCT description refers to this being the maximum thrust that the engine can be set to for an extended period of time, do you want to say that TOGA and FLX can only be used for no more than 5 minutes at a time with both engines operating, or 10 minutes with one-engine-inoperative? (Just a suggestion - no need if this would be too complicated or too much information).

[META] Documentation Status Quo and Plan

Description

The task list below represents pages from the FlyByWire Documentation website.

It shows existing pages (marked complete), pages in development (with PR) and planned pages (marked incomplete).

Contributors can tackle any planned page, create a PR with an empty page describing their intention and start working.

Please read our documentation for contributing: Documentation Project

Documentation Status Quo and Plan

Suggestions for documentation sections or pages are very welcome. See below for Discord contacts or simply comment on this Issue.

Other activities and potential tasks:

Potential translation into other languages - on hold for now

Additional Context

If you require assistance feel free to ping or DM on Discord:

Valastiri#8902
Cdr_Maverick#6475

Documentation for Stored Waypoints

flybywiresim/aircraft#6144

File missing to Thrustmaster TCA Quadrant Airbus Edition

Hi there,

firstly I am BLOWN away what you people are doing @flybywiresim and I deeply appreciate your efforts and creativity.

On page https://docs.flybywiresim.com/fbw-a32nx/a32nx-api/hardware/#thrustmaster-tca-quadrant-airbus-edition there is a duplicate link to the quadrant add-on at both the quadrant and the quadrant add-on.

There is no link to the pdf of the quadrant module itself. I was searching for the file in this repo, but could not find it.

Kind regards,
Volker

Nose Wheel Steering / Tiller Documentation

feat(hyd): Nose wheel steering and separate hand tiller axis #6187
flybywiresim/aircraft#6187

How to obtain IFR Clearance at Preparing the MCDU activity

Hello,

The A32NX dcument has the following prerequisites at the Preparing the MCDU activity.
Below are a few Prerequisites before programming the MCDU.

Visit Starting the Aircraft to learn more.

Make sure the aircraft is powered up.
External Power OR APU
Make sure the ADIRS are set to NAV.
Have a valid flight plan.
Ensure IFR clearance has been obtained.

The last one says to ensure IFR clearance is obtained.
If using the built-in ATC, how can we do this before entering a Flight Plan.

Where am I missing the point?
Thanks
Ananth

Instruct how to make built-in ATC give IFR options

I suggest a small addition to the beginner guide Preflight section so pilots know how to make the built-in ATC give IFR options.

The Preflight page's Flight Planning section says:

We highly recommend not using the built-in MSFS flight planner (World Map).

From what I can tell, if you want built-in ATC to offer choices relevant to IFR, you must use the World Map a little! You must select departure and arrival airports and set the flight mode to IFR.

Without this, built-in ATC behaves totally differently (VFR options only?). You cannot correctly perform many steps from later in the guide.

Can someone confirm that my understanding is correct? If so, I'd be happy to work on a small PR for review.

Pilot Briefing: Overhead panels - Accuracy check

Preface

Hey docs team! Here is the first part of my review of your Pilot Briefing. This is the overhead only. The rest will follow in a separate issue. I already told you: You did a fantastic job! I'm impressed. Please take the following list as an offer, a suggestion, not as criticism. I know it looks huge, but it isn't, compared to the overall size of the Pilot Briefing.

Things I didn't explicitly watch out for:

grammar
punctuation
other language-related stuff.
I'm not a native speaker, and I think we have more qualified people for the job.

General

The explanation of the FAULT lights is often accompanied by a reference to ECAM cautions. Technically, the ECAM caution is completely independent from the so called "local warnings". Ideally they occur at nearly the same time, but there can be situations in which the FAULT light comes on without any ECAM event. I'll leave it up to you.

Summary

Hope this makes it easier for you to track the issues.

Overhead Aft

Overhead Aft -> Emergency Locator Transmitter Panel

Emergency Locator Transmitters are mounted in the back of the aircraft, and are designed to be triggered upon impact or may be manually activated using the remote switch and control panel indicator in the cockpit.

There is only one ELT mounted in the back of the aircraft. An option for a second ELT used to exist, but it’s not common anymore. Instead, there is an additional handheld ELT mounted in the cockpit wardrobe.

An audio alert starts and a distress signal is transmitted for search and rescue upon activation.

The audio alert (i.e. the distress signal) is only audible when the correct frequency (in this case 121.500) is selected in the RMP (and the corresponding reception knobs of the ACP are set accordingly).

Overhead Aft -> Maintenance Panel -> CVR Headset

Headphone output to monitor the Cockpit Voice Recorder, e.g., for testing.

Scratch the "e. g.". It's the sole purpose of this jack.

Overhead Aft -> Maintenance Panel -> BLUE PUMP OVRD

OFF: The blue electric pump is off

That's correct as long as the AUTO condition isn't fulfilled (at least 1 engine running). I'd change it to something like "OFF: The blue electric pump is controlled by the the automatic logic".

Overhead Aft -> Pedestal Light and Audio 3 Switch -> 3rd Audio Switch

Audio from the 3rd radio can be switched to either jump seat (NORM), CAPT or F/O.

a) I don't like the title "3rd Audio Switch" and would prefer something like AUDIO SWITCHING, like the legend on the panel. b) This switch has essentially nothing to do with the radios. It switches the ACP and transfers its output to the Captain's or FO's headphones. If set to CAPT 3, the captain can control their volume through the ACP3:

Overhead Fwd

Overhead Fwd -> Air Condition Control Panel -> APU BLEED pushbutton

FAULT: Amber Light and an ECAM caution, when the system detects an APU leak.

I'm not 100% sure and don't have the time to confirm right now, but I think there are also other conditions for the FAULT light to come on. This is more a reminder to myself to verify again. If anyone else wants to pick it up, feel free!

Overhead Fwd -> ADIRS Panel -> Operation

ON BATT will then flash as a self-test at the start of alignment. If one or more of the ADIRU's are running on battery power, ON BATT will display constantly.

Can we replace "flash" with something like "come on for a defined time" or something? Flashing sounds to me like it goes ON-OFF-ON-OFF... continously.

Overhead Fwd -> Auxiliary Power Unit-> MASTER SW

APU fuel pump operates if fuel pumps are not in operation.

To be precise, one fuel pump in the left wing tank is sufficient. The control depends on fuel pressure availability, not the status of the fuel pump. Could be renamed into "if at least one fuel pump in the left wing tank is in operation".

OFF: Air inlet flap closes at 7%

7% of what? Make it 7% N or N = 7%. (I prefer the latter, because later on you use N = 60% in a different context)

FAULT lt: [...]

Do we need to list every possible malfunction? 99% of our users won't understand it anyway.

Overhead Fwd -> Auxiliary Power Unit-> START

ON: When N = 60%. The APU starter is de-energized. The ignition is turned off.

According to my docs it's 55%.
At 55% the backup start contactor opens (from this moment there is no more power supply to the starter) and 5s later the start contactor opens (coincidence: this is at around 60% then).

Overhead Fwd -> Cabin Pressurization-> MODE SEL

FAULT: Appears in amber and the ECAM caution light, when both automatic systems are faulty.

The part with the ECAM caution light sounds weird.

Overhead Fwd -> Calls Panel -> Description

The flight interphone system is used for communication between the cockpit and the external service interphone panel, located at the nose gear.

I know what you mean, but the panel is not located at the nose gear. It's somewhat close to it, but it's in the fuselage. Airbus calls it the External Power panel.

Overhead Fwd -> Calls Panel -> Usage -> MECH

The cockpit call light will illuminate on the external service interphone panel, and an external horn will sound. When the button is released, the horn is silenced. The cockpit call light will remain illuminated until the reset switch, located on the external service interphone panel, is pushed.

Same as above. The term "external service interphone" is especially problematic, because this jack is associated to the flight interphone system.

Overhead Fwd -> Calls Panel -> Usage -> FWD/AFT

A "CAPTAIN CALL" message will appear on the corresponding flight attendant indication panel.

Can you double-check your references for that? I'm pretty sure it says COCKPIT CALL (or CKPT CALL?), although I can't find any reference right now. If needed, I can check that out next time at work.
In general, I'm missing a note in this paragraph that explains that voice communication is established between the FAs station and the cockpit when the FA picks up the handset. But maybe it's not really needed...

Overhead Fwd -> Cargo Smoke Panel -> Usage -> SMOKE light

Both channels need to detect smoke, or one channel detects smoke and the SDCU finds that the other channel is faulty.

a) Reference to "both channels", without explanation what these channels are. An uninformed user could interpret this as "both the forward and aft cargo compartment need to sense smoke before the warning comes on".
Question: Does the user really need to know what happens on such a detailed level? Isn't it enough to know "there is most probably smoke in the cargo"? If the answer is yes, then we should spend more words on explaining how the system works.
b) SDCUs don't exist in aircraft built after 2006. This function is now integrated in the CIDS, called CIDS-SDF (Smoke Detection Function).

Overhead Fwd -> Cargo Smoke Panel -> Usage -> DISCH light

Amber light comes on, indicating that the agent bottle has fully discharged.

Can we scratch "fully"? Because it comes on when the pressure drops below a certain threshold and it's rather far from "fully discharged".

Overhead Fwd -> Electrical System Control Panel -> Usage -> AC ESS FEED

Can we add a paragraph that in case of normal AC ESS Feed failure, the AC ESS Bus is automatically fed from AC BUS 2 after 5 seconds, regardless of the pushbutton position. This is correctly implemented in our aircraft by the way.

Overhead Fwd -> Emergency Electric Power Panel -> Usage -> GEN 1 LINE

OFF: GEN 1 line contactor opens. The AC BUS 1 channel is supplied from GEN 2 through bus tie contactors. This is used for smoked drill.

I saw that you mostly copy&pasted this paragraph (including the typo ;) ) but I think we should point out the main function of this pushbutton a bit more. This is not incorrect, but pretty much fails to describe what makes this pushbutton so special.
I can provide a more accurate description later and will open a separate issue for it, if that's ok for you.

Overhead Fwd -> Fire Control Panel -> Usage -> APU FIRE

close low-pressure fuel valve and APU fuel pump.

[...] and turn off APU fuel pump
(I know, but... you know... the fuel pump isn't "closed" ;) )

Overhead Fwd -> Fire Control Panel -> Usage -> APU AGENT

Pushing it will discharges the respective fire bottle.

Discharge. Typo.

Overhead Fwd -> Fire Control Panel -> Usage -> APU TEST

When presses there is a continuous repetitive chime sound

pressed. Typo.

Overhead Fwd -> Fuel Control Panel -> Description

Each engine is fed by their corresponding centre and wing tanks

AE vs. BE. You use center everywhere else.

Overhead Fwd -> Fuel Control Panel -> Usage -> CTR TK PUMP 1 + 2

This is just a reminder for the future, not something that is actually wrong. And you probably know already. NEOs don't have center tank pumps anymore. They have been replaced by transfer valves. Our current aircraft model has the wrong legends, which makes it kind of correct again.

Overhead Fwd -> Fuel Control Panel -> Description

Only the last 30 minutes of recording is retained.

Aircraft built after 2003 have a 120 min recording time requirement. Airbus installs CVRs capable of 25h of recording since the end of 2020.

Overhead Fwd -> Fuel Control Panel -> Usage -> CVR ERASE

GND CTL must be on additionally.

Feature Guide: PostIt Notes Documentation

flybywiresim/aircraft#6410

Documentation for Wheel Chocks and GSE Safety Cones

Wheel Chocks and GSE Safety Cones
flybywiresim/aircraft#6286

mkdocs-material generator notice no longer displayed

Missing the Made with Material for MkDocs after v7.3.0. (Seen on production and any recent PR).

Seems to be a regression from v7.2.6 since the ace-navdata branch still displays it and was built on that version of mkdocs-material.

Beginner Guide - Possible error in Preparing the MCDU

I'm in no way being an expert so sorry if I'm mistaken, but in the Beginner Guide on your website in the Preparing the MCDU section PERF page setup: you are talking about a CG of 30.5 and then you say:

Take a look at your throttle quadrant and look for the CG markings on next to the trim wheel. We need to set a nose down trim of about 0.8.

I believe this should be 0.8 nose up trim instead and if I'm right, then the next sentence needs to be corrected too, so:
Using the keypad type in /DN0.8 and press LSK3R
should instead be:
Using the keypad type in /UP0.8 and press LSK3R

Add issue in French MSFS version to tiller doc.

Axe du mélangeur 4
This seems to not be there in the French version - user had to change to English to set it.

Taxi Guide: Add Tiller Link

Hi,

little improvement idea: The Taxi-Guide mentions in the chapter "During Taxi", that the tiller is not implemented yet ("Use the tiller (currently not implemented) or rudder pedals to steer the aircraft)".
That changed recently (and btw. I love it), so you might want to add the link to the new tiller function (+ the hint that is currently only available in the dev version).

Best

MSVF

Add "Ctrl+E not supported" to Reported-Issues

Add/Change Flight Deck API

Commit to check:
flybywiresim/aircraft@ce73183

Feature Guide: TCAS Documentation

TCAS documentation

feat(tcas): TCAS TA/RA logic and annunciations (ReactJS/TS) #5934

flybywiresim/aircraft#5934

docs: Update EFB Settings Page

fix: Added new tab to EFB "Realism" #6382
flybywiresim/aircraft#6382

Check TCAS Mode and TCAS Traffic API

https://docs.flybywiresim.com/pilots-corner/a32nx-briefing/a32nx_api/#atc-tcas

Throttle calibration--a new way to mess up

Apparently it's possible to mess up the calibration of a one axis hardware throttle in such a way that the in-cockpit throttles operate independently of one another causing asymmetric thrust. I know, I did it. That's probably a UI problem that should be pointed out to the developers, but I thought it might be useful to include this possibility in the Troubleshooting section of the documentation. As far as I could figure out, the only way to address this is to delete the throttle config .ini file, which worked fine. Not a big deal, but it would save some people some time and frustration.

(tracking) Remote MCDU Known issues and (some) fixes

The remote MCDU was merged into dev recently, and while it's working fine for most, there are many users experiencing issues with it. This issue will keep track of the issues raised in the support channel and the remote MCDU thread. I'll be adding more issues/fixes here as they appear in the discord.

Hopefully, the fixes to these issues can be found and can be added to the docs.

MCDU shows up, but only shows a black screen (Discord issue 1; Discord issue 2)

When does the issue show up: When connecting either by remote (ip) or via localhost

Fix: Open the port 8080 via the Windows firewall as per the docs.

Links: Discord issue 1; Discord issue 2; Docs; Github Issue

Port is in use (Discord issue)

When does the issue show up: When running server.exe. It can show in 2 ways:

Either with an error message like: Error: listen EACCES: permission denied 0.0.0.0:8080 or Error: listen EADDRINUSE: address already in use :::8125
server.exe gets stuck on waiting for simulator (Discord issue)

Fix: Change the port in the EFB and in server.exe to an unused port (the EFB setting and the server.exe port must be the same). See the docs

Links: Discord issue 1; Discord issue 2;

Strange text with no resemblence of the MCDU (Discord issue)

Image:

When does the issue show up: When connecting remotely. Works on localhost.

Fix: Under investigation...

Node spits an error when starting `server.exe` (Discord issue)

When does it happen: when starting server.exe

Fix: Make sure the Print Spooler service is running.

Links: Discord issue; Discord issue resolution

Create pre-flight section for Beginner Guide

Copied verbatim from our #docs channel on Discord from donbikes

Should the beginner's guide start with how to start a flight, rather than how to start the aircraft? What I'm thinking is upfront discussing the use of Simbrief vs the MSFS flight planner, how to load the airplane payload and fuel, when to do these tasks in the overall flight timeline, etc. To me, the Simbrief integration, Fuel and Weight, and flyPad EFB sections are kind of hidden in the "Feature Guides" section, whereas pilots need to incorporate a lot of that info into their startup procedure. To me, these items are at a different "level" than other items in the Features section, such as the Custom AP, FMS, and Camera Views, Free Text, and MCDU keyboard.

Pre-flight should solve this problem and be a good organizational starting point for users.

Inaccuracies on Airliner Flying Guide-Approaches

https://docs.flybywiresim.com/pilots-corner/airliner-flying-guide/approaches

The Airliner Guide on Approaches has some inaccuracies and omissions.

All references to CAT 1/2/3 should use Roman Numerals (CAT I/II/III) as that is the official classification.
The guide explains MDA and DH, but not DA. At least in the US, these are 3 distinct altitudes.
The links to example approach plates are broken, at least on PC on Chrome

Issue 2 means that several portions of the guide are inaccurate:

The section explaining the different ILS categories refers to CAT I (and it's variants) using MDA, when they actually use a DA.
The section explaining MDA and DH needs to include an explanation for DA. I propose the following addition, straight from the FAA Instrument Procedures Handbook (FAA-H-8083-16B, Chapter 4):

MDA—the lowest altitude, expressed in feet MSL, to which descent is authorized on final approach or during circle-to land maneuvering in execution of a standard instrument approach procedure (SIAP) where no electronic glideslope is provided.

DA—a specified altitude in the precision approach at which a missed approach must be initiated if the required visual reference to continue the approach has not been established.

DH—with respect to the operation of aircraft, means the height at which a decision must be made during an ILS, MLS, or PAR IAP to either continue the approach or to execute a missed approach. CAT II and III approach DHs are referenced to AGL and measured with a radio altimeter.

The table in the MDA vs DH section should thus look something like this (also included references to Barometric and Radio):

Minimum Type	Defined As	Approaches Used in
MDA (Minimum Descent Altitude)	Barometric Altitude Above Mean Sea Level	LOC, LDA, SDF, VOR, NDB, LNAV, ASR, Visual
DA (Decision Altitude)	Barometric Altitude Above Mean Sea Level	CAT I ILS, LNAV/VNAV, LPV, RNP, PAR, GLS
DH (Decision Height)	Radio Altitude Above Ground Level	CAT II/III ILS

Feature Guide: Custom Views

Documentation for our built in Custom Views with numbering and screenshots for each.

Potentially

how to change or create new ones (camera.cfg).
how to define custom views with MSFS

Related: flybywiresim/aircraft#6158

A new Standard Operating Procedures is in use and a new checklist!

Here is the link to the new SOP:

pdf/A32NX Documentation/FBW A32NX SOP.pdf

https://github.com/flybywiresim/manuals/blob/f13e14402bd029c960f712c8ac493a030a372a9b/pdf/A32NX%20Documentation/FBW%20A32NX%20Checklist.pdf

Update Version Comparison

As discussed to update the page -- I'll be tackling this soon.

[META] A32NX Pilot Briefing

A32NX Pilot Briefing

This shall give the FBW users a good overview of the A32NX cockpit and its functionality as a Flight Crew Operational Manual (FCOM) would.

Preview Link; https://docs-git-a32nx-briefing-flybywire.vercel.app/pilots-corner/a32nx-briefing/

Strategy:

To quickly bring value and content to our users we should:

Release early, release often
Continuously improve and extend the content

In simple terms this means get a reasonable MVP (minimal viable product) published quickly then continuously improve based on ideas and feedback from the team and our users.

Iteration Plan

1. Iteration (MVP):

All pages with a high level overview of the panel/instrument and usage description of buttons/switches/knobs, etc.
- Rephrasing of texts (#176)
- Doublecheck which buttons work in the FBW mod and add note if not
- redo clickable image (new textures from cockpit and background color)
- Better Tooltips on Flight Deck image map
- Mobile View does not work with fixed size image
- StdBy instruments only contains one standby instrument though...the DCDU is for communicating with atc, and the EFIS terrain radar button is for the ND display ==> change map to SAI only, new for DCDU, and include Terrain in EFIS

2. Iteration

Add sections for Cockpit Instruments:

Add additional features to flight-deck:

Sidestick and Tiller
Cross linking of panels (e.g. buttons to screens or messages)
Cross linking with Beginner Guide etc.
Add LVARS/EVENTS for each button/switch/lever

3. Iteration

Add details to important aircraft aspects like:

flybywiresim / docs Goto Github PK

docs's People

Stargazers

Watchers

Forkers

docs's Issues

Description

Legend

Page Roadmap

To Do

Additional Context

What is the bug/error?

Expected functionality

Steps to reproduce

Additional information

Summary

Changes / Considerations

Summary

Instrument Panel

Issue

Possible Solution

Description

Documentation Status Quo and Plan

Additional Context

Preface

General

Summary

Overhead Aft

Overhead Fwd

MCDU shows up, but only shows a black screen (Discord issue 1; Discord issue 2)

Port is in use (Discord issue)

Strange text with no resemblence of the MCDU (Discord issue)

Node spits an error when starting server.exe (Discord issue)

A32NX Pilot Briefing

Strategy:

Iteration Plan

1. Iteration (MVP):

2. Iteration

3. Iteration

Recommend Projects

Recommend Topics

Recommend Org

Node spits an error when starting `server.exe` (Discord issue)