A320 FMGS B31

[Leonidas]

Hi,
@Leonidas: I'll have a look at your issues if I can find them.
The latest version:
http://www.jeehell.org/A320FMGS_B31.1.exe
Regards,
JL

Will it be available via live update?

[jeehell]

Hi Leonidas,

No, I need to change aot of code in the updater. I'll work on that soon, bu for now no auto update.


JL

[filippoporcari]

hi jl,
may we update "on top" of the old b31? or do u suggest an unistall of the previous version?
cheers
filippo

[jeehell]

Just install over the B31.0

[Leonidas]

Just install over the B31.0

Most my problems solved with B31, except this very annoying one: "FLAPS NOT IN T.O CONFIG" red message on EWD and MASTER WARN with aural alert, just after landing, if I put flaps to 0 position. Pushing MW, its light turns off (the message on EWD remains) and stops for a while, but then it starts again during taxiing to the gate.

Best Regards

[stefangr]

Most my problems solved with B31, except this very annoying one: "FLAPS NOT IN T.O CONFIG" red message on EWD and MASTER WARN with aural alert, just after landing, if I put flaps to 0 position. Pushing MW, its light turns off (the message on EWD remains) and stops for a while, but then it starts again during taxiing to the gate.

Best Regards

Hi Leonidas,

which hardware do you use to simulate the T/O Config Test button on upper pedestal?

Regards
Stefan

[Leonidas]

Hi Leonidas,
which hardware do you use to simulate the T/O Config Test button on upper pedestal?
Regards
Stefan

Hi Stefan.
I use Cockpitsonic ECAM CP USB.
Regards

[romeow]

Strange! I've got the same FLAPS NOT IN T.O CONFIG "problem" after landing but using fscockpit hardware.
Regards
René

[stefangr]

Strange! I've got the same FLAPS NOT IN T.O CONFIG "problem" after landing but using fscockpit hardware.
Regards
René

OK, then it obviously has nothing to do with the hardware. I had this idea because I had this problem also some time ago, and it was about assigning the actions for the hardware buttons within the setup of the hardware.

Regards
Stefan

[jeehell]

Hi

The hardware theory is very likely to be the answer in fact. The TO CONFIG button requires the pushed IN and OUT actions to be sent to the software as it has to be kept IN for the warnings to come up on the EWD. I probably missed than when writing the EHID driver. And FSCockpit developper as well.
I'll have a look right away.

JL