A320 FMGS B49

[jeehell]

http://www.mycockpit.org/forums/showthread.php?t=27527

[jeehell]

@Jean-Luc: Regarding the CORTE / PIRTE. It looks like the corte.xml file will be loaded when the FMGS Server starts. Would it be possible to read the file with each CORTE request. If users are changing the corte.xml (e.g. by my corteManager4JH) they need to restart the whole server at the moment.

Thank you for your great work!

I 'll see if it's not too performance hungry... If I parse the xml file every time an user accesses the corte functions, this can very quickly be complex. Maybe a better thing would be for you to tell the software there is a need to update the xml database? PM me please.

[OmniAtlas]

Is there an English version of that manuial anywhere? I would really like an english version. (or spanish)

Thanks

Jose

Here you go - https://drive.google.com/file/d/1vUZ...ew?usp=sharing

I used an online pdf translator.

[capt_pero]

Found a new issue with CORTE using this flight from EDDF to EHAM:

  <CORTE ID="EDDFEHAM01" TYPE="CORTE" FROM="EDDF" TO="EHAM" FLTNBR="DLH440" CI="20" CRZFL="NONE">
    <DEPARTURE RWY="25L" SID="MARU4F" TRANS="NONE" />
    <LEG SEQ="0" TYPE="DIR" WPT="MARUN" />
    <LEG SEQ="1" TYPE="AWY" ID="Y152" WPT="ARPEG" />
    <LEG SEQ="2" TYPE="AWY" ID="Z850" WPT="BADGO" />
    <LEG SEQ="3" TYPE="AWY" ID="Z850" WPT="ABILU" />
    <LEG SEQ="4" TYPE="AWY" ID="Z850" WPT="ADEMI" />
    <LEG SEQ="5" TYPE="DIR" WPT="HMM" />
    <LEG SEQ="6" TYPE="AWY" ID="T281" WPT="AMSAN" />
    <LEG SEQ="7" TYPE="AWY" ID="T281" WPT="NORKU" />
    <LEG SEQ="8" TYPE="DIR" WPT="SONSA" />
    <LEG SEQ="9" TYPE="DIR" WPT="ROBIS" />
    <LEG SEQ="10" TYPE="DIR" WPT="OSKUR" />
    <LEG SEQ="11" TYPE="DIR" WPT="ARTIP" />
    <ARRIVAL TRANS="NONE" STAR="NORK2A" VIA="NONE" APPR="NONE" />
    <ALTN ICAO="NONE" ID="NONE" />
  </CORTE>

The arrival changed during flight because of weather. The CORTE caused the MCDU to select RWY36R but only "STAR" has been defined in corte.xml. I tried to change the arrival to another runway but then the MCDU shows "MCDU DISPLAY ERROR | STAR".

After save landing I used the same flight without saving the STAR. Runway was preselected as well but change able.

As this is reproduceable I added a new function "Don' save" in Settings of my corteManager4JH. Here you can select "Don't save = STAR" to avoid this issues until it is verified.

[jeehell]

Found a new issue with CORTE using this flight from EDDF to EHAM:

  <CORTE ID="EDDFEHAM01" TYPE="CORTE" FROM="EDDF" TO="EHAM" FLTNBR="DLH440" CI="20" CRZFL="NONE">
    <DEPARTURE RWY="25L" SID="MARU4F" TRANS="NONE" />
    <LEG SEQ="0" TYPE="DIR" WPT="MARUN" />
    <LEG SEQ="1" TYPE="AWY" ID="Y152" WPT="ARPEG" />
    <LEG SEQ="2" TYPE="AWY" ID="Z850" WPT="BADGO" />
    <LEG SEQ="3" TYPE="AWY" ID="Z850" WPT="ABILU" />
    <LEG SEQ="4" TYPE="AWY" ID="Z850" WPT="ADEMI" />
    <LEG SEQ="5" TYPE="DIR" WPT="HMM" />
    <LEG SEQ="6" TYPE="AWY" ID="T281" WPT="AMSAN" />
    <LEG SEQ="7" TYPE="AWY" ID="T281" WPT="NORKU" />
    <LEG SEQ="8" TYPE="DIR" WPT="SONSA" />
    <LEG SEQ="9" TYPE="DIR" WPT="ROBIS" />
    <LEG SEQ="10" TYPE="DIR" WPT="OSKUR" />
    <LEG SEQ="11" TYPE="DIR" WPT="ARTIP" />
    <ARRIVAL TRANS="NONE" STAR="NORK2A" VIA="NONE" APPR="NONE" />
    <ALTN ICAO="NONE" ID="NONE" />
  </CORTE>

The arrival changed during flight because of weather. The CORTE caused the MCDU to select RWY36R but only "STAR" has been defined in corte.xml. I tried to change the arrival to another runway but then the MCDU shows "MCDU DISPLAY ERROR | STAR".

After save landing I used the same flight without saving the STAR. Runway was preselected as well but change able.

As this is reproduceable I added a new function "Don' save" in Settings of my corteManager4JH. Here you can select "Don't save = STAR" to avoid this issues until it is verified.

I found some issues which I am trying to correct.
However, your route here is wrong. The legs from NORKU to ARTIP should not be defined as they are part of the NORKU 2A arrival. Or you should have used here STAR="NONE".

[capt_pero]

I found some issues which I am trying to correct.
However, your route here is wrong. The legs from NORKU to ARTIP should not be defined as they are part of the NORKU 2A arrival. Or you should have used here STAR="NONE".

Right. I am sorry. My manager did not "cut" the STAR waypoints. I should have seen that. :O)
Will be fixed with next version of corteManager4JH.

[Fritz]

I finally found time to switch also to B49.0.
The good news is, the reverse thrust works again after landing.
The bad news is,the trim wheels of the TQ are no longer driven. Have tested the trim wheels in
Skalarki profiler. There they move. With B49.0 not. I have the Skalarki TQ2012.

[capt_pero]

@Jean Luc: Thank you for fixing the DEP Runway issue within the corte.xml. Now route will be loaded if no DEP RWY is assigned.

Merry x-mas!

[HauptChr]

I finally found time to switch also to B49.0.
The good news is, the reverse thrust works again after landing.
The bad news is,the trim wheels of the TQ are no longer driven. Have tested the trim wheels in
Skalarki profiler. There they move. With B49.0 not. I have the Skalarki TQ2012.

In Version 49.1 is only a checkbox for "trim wheel on/off"
It shuts down complete trim wheel funktion (manual movement and motor)

I would like to have an addidtional checkbox like in my old PM software, where i could disconnect the electric motor of my TQ without loosing the manual trim during trim steiing for t/o, direct law and meck backup. The reason : mechanical problems inside my TQ.

[masterp]

Hi JL,

It seems Open GL error is back with B49.1. My PFD runs on laptop (onboard VGA) is being slideshow again, while B49.0 and previous version had works fine very smooth movement.