A320 FMGS B47

[jeehell]

Hello JL,

the next problem i have is: the throttle lever don`t work!
In the fmgs_config i cannot assign the joystick axis ! it`s a bodnar controller!
in the last version it works fine !

regards Peter

what happens exactly? I cannot guess errors and bugs, I need detailed information on what you attempted or I cannot help you.

[jeehell]

Hello JL,

i start to fill up first the two int pages, then i will go to the pref page to fill in V1 VR and V2 and then this errormessage is in the display of the mcdu!

Regards peter

Did you rebuild the navdata?

[pete_fuss]

Did you rebuild the navdata?

Hello JL,

sorry, i just rebuild the navdata, but i forgot to copy it to the client pc where my mcdu`s are running!
Now it works as bevor, great support!

now i run also the fourst time the fmgs_config program and at this time, i don`t no why, i can calibrate my throttels, it also now works fine!

Sorry for the circumstances!

Regards Peter

[Leonidas]

Did you rebuild the navdata?

Same to me. PROG and PERF pages
Rebuild navdata and copy bin files yesterday. After that it was OK, but today MCDU DISPLAY PROBLEM...

[EDIT]
It's OK, I fix it

[jcostabal]

Fixed!, I had to set all the flight controls again and it worked.

Already tryed the B47.3 and is working perfectly so far!

Thanks JL

[jeehell]

Same to me. PROG and PERF pages
Rebuild navdata and copy bin files yesterday. After that it was OK, but today MCDU DISPLAY PROBLEM...

[EDIT]
It's OK, I fix it

wait I am lost now.
You rebuilt the navdata a second time and now it works correctly??

JL

[Leonidas]

wait I am lost now.
You rebuilt the navdata a second time and now it works correctly??
JL

No, I have a problem with my THR LVR every time I setup FMGS with clean installation. I decide to run fmgs-config (eventhough I have config backup file) to setup THR LVR again. So, after that THR LVR indeed worked and the 2 MCDU pages worked at the same time. It is mabe just coincidence. I don't know

[pete_fuss]

Hello JL,

one very little thing, the starter.exe shows the version number 47.2!

nice weekend

regards Peter

[OmniAtlas]

Hi JL -- thanks for the update. Managed to finally test it this weekend -- here are my findings:

1. Database loading screen on startup (MCDU) -- this persist, although after ADRS alignment I can still load departure and arrival ICAO and even a flight plan. I have not rebuilt the database -- are we suppose to for each new version?


2. There is a line drawn on the aircraft ND symbol YBCG depart -- this line was present for most of the simulated flight.



3. Despite having an analogue arm switch for the speedbrake I am still unable to arm - I believe this is because the arm state does not have a threshold on an axis (it is either arm, or disarm -- and the axis numbers jump around) - is it possible to set a range for the brake arm, or an error % ?

4. On climbing I got a message 'MORE DRAG' -- this was after I changed the altitude from FL160 to FL150 as I intended it to be as I input on the MCDU. I did not see the MORE DRAG message when descending even when I was above the donut.

5. Managed flight plan route is....strange. This is an ILS straight in approach.

[jeehell]

Hi JL -- thanks for the update. Managed to finally test it this weekend -- here are my findings:

1. Database loading screen on startup (MCDU) -- this persist, although after ADRS alignment I can still load departure and arrival ICAO and even a flight plan. I have not rebuilt the database -- are we suppose to for each new version?


2. There is a line drawn on the aircraft ND symbol YBCG depart -- this line was present for most of the simulated flight.



3. Despite having an analogue arm switch for the speedbrake I am still unable to arm - I believe this is because the arm state does not have a threshold on an axis (it is either arm, or disarm -- and the axis numbers jump around) - is it possible to set a range for the brake arm, or an error % ?

4. On climbing I got a message 'MORE DRAG' -- this was after I changed the altitude from FL160 to FL150 as I intended it to be as I input on the MCDU. I did not see the MORE DRAG message when descending even when I was above the donut.

5. Managed flight plan route is....strange. This is an ILS straight in approach.

1. I think the XXXX are clear enough that you need to rebuild the database... I cannot say on every release it is required (it hasn't been for some time). But it's always bets, and it will be in the few next I think due to some changes in the format.

2. weird, never seen that. report if it happens again.

3. the same % range as the retracted position is used.

4. Doing that you changed your FMGS from CLB mdoe to DES mode (probably closer than 200NM from DEST). You can change again to CLB or CRZ in the MCDU PROG page by forcing the CRZ FL in the 1L field.

5. Probably linked ot navdata ...