A320 FMGS beta 26

You try in "fmgs config" (joystick button):

For FCU AP:
FCU_AP1 and FCU_AP2

For sidestick priority:
CPT_APTO and FO_APTO

Hi,

The AP OFF/stick priority are labelled CPT_APTO and FO_ APTO (or very similar).
I'm quite sure they exist ;-)


Oops totom replied before me :-)
Just one thing, AP1 & 2 on the FCU should only be used for engagement of the AP. For disengagement use APTOs.
Same goes with the ATHR and the ATHRTO pb.
Cheers,
JL

Hello Mr. Jeehell,

great work -

however I´m experiencing some problems in my setup…

I´m running fs9, FMGS Server, AP/FBW and Sound modules on one machine,
all other modules on a second.

I did set the IP adress for the server on both machines.

After a while (something like 20 sec) first the EWD disconnects from server, after that the MCDU. The MCDU sometimes reconnects for a short period, EWD stays disconnected.

All other modules stay connected

OS is WIN 7 64

Does anyone have an idea what could be the problem ?

BRgds Toulouse

Hi Toulouse,

When you say they get disconnected, is it only because the FMGS server says so or it is as well visible on the related software itself (for example, pushing keys on the MCDU has strictly no effect)?

Regards,
JL

FMGS server says so and EWD + MCDU freeze on second computer. Tried disabling Firewall - same problem.

Are they freezing to the point you cannot use the right click on them?

No, I can close them with right click.

Did you check your widefs configuration? Are you running the modules as administrator? Sometimes Norton Sonar Auto Protect disables the modules. Then you need to exclude the modules from scanning.

This is really weird, the EWD uses the same TCP port than the PFD and OVHd... I think also there is a trouble elsewhere with a protection software??

Hello again,
sorry for my question on a late sunday afternoon - great forum, thank you again for so much support.
I disabled every protection - firewalls, virus scanner.

I´ll have to check Fritz´s suggestion - I´m using the starter program to call the modules.

I´ll try to start the modules separate, as administrator (i´m logged in as as such anyway, but this has given me problems before).

Strange however, it´s only these two modules, for the MCDU the FO´side shows the same behavior. All other modules work fine.