A320 FMGS B34

[filippoporcari]

ben, adonis is talking about 2 different things:
SEVERE TURBULENCE procedure ( QRH, abnormal procedures and of course FCOM abnormal procedures) requiring the PF to disconnect auto thrust, following the severe turb proc applying to any phase of flight not only approach.
STRONG CROSSWIND at landing: as well explained by adonis the 320 is certified for a 38kt max cross wind for landing (don't remember the max cross wind for autoland) meaning that if u have a cross wind component above 38kt u simply CANNOT and SHOULD NOT land but diverge to an alternate or ask for a different rwy if available. the strong crosswind operations if not associated with severe turbulence does not prescribe to switch the auto thrust off.
all the best
fil

[jeehell]

Hi,

@Christian: I will try to correct that ASAP.


@Adonis: I will try a few legs with high altitudes airport this week.

Regards,
JL

[OmniAtlas]

ben, adonis is talking about 2 different things:
SEVERE TURBULENCE procedure ( QRH, abnormal procedures and of course FCOM abnormal procedures) requiring the PF to disconnect auto thrust, following the severe turb proc applying to any phase of flight not only approach.
STRONG CROSSWIND at landing: as well explained by adonis the 320 is certified for a 38kt max cross wind for landing (don't remember the max cross wind for autoland) meaning that if u have a cross wind component above 38kt u simply CANNOT and SHOULD NOT land but diverge to an alternate or ask for a different rwy if available. the strong crosswind operations if not associated with severe turbulence does not prescribe to switch the auto thrust off.
all the best
fil

Ah thank you fil, i will look up those references. It is always a challenge to land in a crosswind -- I heard the A320 is not as 'sensitive' as a 737?

[jeehell]

Hi all,

There were some bugs corrected lately, here a full package for those who prefer a complete installation:

http://www.jeehell.org/A320FMGS_B34.1.exe

Regards,
JL

[jeehell]

Adonis, I tried a departure from SECU.
There is a bug in the MCDU display: it will truncate the last digit for THR RED above 10000ft, so your THR RED of 12500ft shows up as 1250/12500. However, the actual THR RED taken into account to trigger the LVR CLB is correct, I did not have any issue there.

I'll make a quick fix in a few minutes to correct that display bug...

Regards
JL

[OmniAtlas]

Thanks JL -- website updated, the URL it can now be reached at is -- http://flightsystem.wix.com/airbus

[OmniAtlas]

For some reasons I can't be in managed mode with the FCU...I think I may have configured my sidesticks incorrectly.

Pressing the autopilot disconnect on the sidestick I get Priority right sound...wrong assignment?

Right now it is CPT_APTO -- anyone know the correct assignment for A/P disconnect? (I know I asked this question before, but I forgot! My apologies). Should this even be assigned as a 'push' or 'toggle' event?

Thank you.

[Space]

1) Have you got the subfolder Airbus_A321 in folder AIRPLANES?
2) If yes, open it and you should find the subfolder \Sound
3) There you should find a lot of wav files among them engine sounds as well.
4) If that is the case go to \A320 FMGS JH Project Airbus A320-214\Sound
5) Open sound.cfg and remove the semicolon at the beginning of the line alias=Airbus_A321\sound

Regards
René

done, but nothing Happens, it is still quite....

[Jerec]

Hi JL,

after doing some flights with new version i mentioned some smaller issues:

- Voice callouts from radaraltimeter (2500ft) and other cockpitsounds sometimes do not appear, when sound on network machine.
- EFIS items produce heavy impact to machine, so TERR isnt further displayed and ND is stocking (machine is i7 with 3.5GHz)
- Do you have any plans for reimplementing CO ROUTE?

Regards Henrik

[OmniAtlas]

For some reasons I can't be in managed mode with the FCU...I think I may have configured my sidesticks incorrectly.

Pressing the autopilot disconnect on the sidestick I get Priority right sound...wrong assignment?

Right now it is CPT_APTO -- anyone know the correct assignment for A/P disconnect? (I know I asked this question before, but I forgot! My apologies). Should this even be assigned as a 'push' or 'toggle' event?

Thank you.

Well, managed to fix the FCU problem by also programming the release button to CPT_APTO.
So it seems with the new joystick logic, if you do not program a release, the button will just hold indefinitely.