A320 FMGS B45

[OmniAtlas]

@totom: Thanks, I mixed a none up in.

@OmniAtlas: Also thanks, but to say it carefully: The thumbnail is incorrect. Just trust the FCOM .

Greets
Michael

l

Hi Michael, what does the FCOM say? Do you know which reference page I should be looking at?

Thank you.

Ben

[Migelito]

Hyi Ben!

It is hidden in FCOM DSC (aircraft systems) under DSC-27-20-30, called "Lateral Consoles".

Greets
Michael

[OmniAtlas]

Cheers, TY Michael, will have a look.

[tuomasho]

Hi,

any ideas how to get those ils alignments to work? Also many times mcdu reports "MCDU DISPLAY PROBLEM PLEASE REPORT ISSUE" and this comes always when you write some route to mcdu. I believe, that some route points doesn't work with the mcdu?

Yours

Tuomas

[romeow]

Hi,
I often get the following messages in MCDU and ND since Version 45.3

Nav Accur Downgrade
or
Nav Accur Upgrade


What does it mean and what do I have to do?
Regards, René

[Migelito]

Please see post #101!
Greets
Michael

[romeow]

Hi Michael,

thanks for the hint! Although I'm always following the actual version threads I missed your post - probably because I upgraded to V 45 with some delay.

@ Jeehell
I like to repeat what Miguel mentioned in his post #101: You did a great job with v45! Everything works fine, start up and shut down sequences are fantastically simulated. Thanks a lot again!

Greets René

[OmniAtlas]

Hi,
I often get the following messages in MCDU and ND since Version 45.3

Nav Accur Downgrade
or
Nav Accur Upgrade


What does it mean and what do I have to do?
Regards, René

From Eric Parks Airbus notes

RNAV (LNAV- VNAV) Approaches (Managed Non-ILS)

•  All non-precision approaches must be flown with autopilot and flightdirector unless no ILS is available and both autopilots have failed, then amanual non-precision approach is permitted.
  
•  Only use approach from database
  
•  Do not manually build approach
  RNAV approaches that are listed as LVAV-VNAV are designed to providevertical guidance and will utilize a DA(H).
  When cleared for the RNAV approach press the APPR pb on FCU. Do NOTselect the LS pb! LS pb will disable the RNAV indications and flash amberV/DEV on the PFD. CSTR pb should be ON as well.
  Enter 0.3 for required accuracy on PROG page (make sure the new value showson both sides). This lowers the FMGC “tolerance” from an enroute value to anapproach value. RNAV approach must have a HIGH nav accuracy showing with0.3 nm value on the PROG page before beginning the approach to ensure thatthe FMGC accurate enough for an RNAV approach. Less than required accuracywill create a NAV ACCURACY DOWNGRADE message on MCDU. You mayalso get a GPS PRIMARY LOST message which indicates that the GPS signalfrom an MMR has been lost. If you get either message you must select theautopilot on the side of the operative FMGC. This will allow you to continue theRNAV approach. If both FMGC’s display an error message or you get anFM/GPS POS DISAGREE ECAM you must go around.
  Ensure HIGH is showing on PROG for nav accuracy. Ensure the “hockey stick”(descent arrow symbol) is visible on ND for start of descent. Ensure APP NAVand FINAL are showing on FMA. Remember “High Hockey Finals”
  

[romeow]

Thanks a lot!
Greets, René

[SSO]

Hi All,

First of all. The B45 is fantastic.
The transponder issue I resolved by assigning buttons to Transponder on/standby. Using the MCDU page alone was not working.

I stumbled upon another problem during the past few ILS approaches.
Everything works fine until decelleration to Approach speed on the glideslope.
at this point the A_THR seems to be inactive although being ON.
the thrust remains at IDLE even when decellerating below the red markers on the tape. Speed is in managed mode.
i have to switch off the A_THR and adjust thrust manually.

any idea?