A320 FMGS B38

[jeehell]

Hi,

The last version is 38.5.
You can get the full install here:
http://www.jeehell.org/A320FMGS_B38.5.exe
there are auto updates after the full install.

Regards,
JL

[Beaufort]

Hi JL,
THX for the immediate support!
I now installed B38.5 (sry for my mistake, yesterday it was still 38.4) and allowed the Updater to install the additional update on all three PCs.
On my secondary PC the MCDUs, EWD and SD are running. Now the MCDUs ar working as usual. But there was no way to start the SD and the EWD, they don´t appear in the task bar as well. I made a fresh install of B38.5 without the update and now all displays are running.
One special thing of my config: While all other PCs run Win7 64Bit, the secondary PC uses Vista 32Bit. I will soon switch to another Win7 64Bit, so no need to solve the problem for me, if this is the cause.
I will report, if the missing update on the secondary PC leads to any problems.
Regards Rainer

[jeehell]

HI Rainer,

DO you run the starter using admin rights on all PCs? it may be the reason.
It is really best to always use the same version on all computers, very strange things may occur otherwise...

Regards,
JL

[Beaufort]

Hi JL,
affirmative, as admin on all PCs, the only thing is, that I can´t assign admin rights to the EIS.exe, the SD.exe and the EWD.exe on the Vista-PC (on the Win7-PCs its possible and I did so). So perhaps a Vista problem? If so, don´t invest Your time in solving that, I think its my part to switch to Win7 (or 10, when it´s out) soon. But as described: the problem occurs only after the update.
Regards an THX again
Rainer

[jeehell]

If you run the software manually (i.e. without the starter), it's been a long time since there no longer any SD.exe, EWD.exe etc... The 6 EIS display (PFDs/NDs/SD/EWD) have been replaced by a single EIS.exe file. This file must be run with the correct parameter to determine which display it actually represents (the physical display, i.e. the display at a physical position in the cockpit). This allows easy EIS reconfiguration (PFD/ND XFR etc).
The installer should install shortcuts (called PFD, ND, SD etc) which link to the EIS.exe with the correct launch parameter. Windows allows you to force admin right on a shortcut as well (at least 7 and most probably vista as well).

Regards,
JL

[OmniAtlas]

Thanks JL -- flaps 3 seems to have been fixed. I will have to do further testing.

Other things I am also testing --

1. T/O with FD not armed

FCOM 4.05.30 p5 "NO FLIGHT DIRECTOR TAKEOFF"

If a takeoff is initiated without FDs, the system responds as follow:
There are no FD bars.

There is no A/THR arming.

There is no guidance available.

The target speed on the PFD is that selected on the FCU or is defaulted to ​100 kt.

Setting the thrust levers to the CL detent does not activate A/THR.

Note: Do not engage the autothrust prior to selecting a target speed on the FCU.

----

2. Autobrake disarm with one brake pedal, or speedbrake/spoilers disarm after landing.

[immaging]

Thanks JL -- flaps 3 seems to have been fixed. I will have to do further testing.

Other things I am also testing --

1. T/O with FD not armed

FCOM 4.05.30 p5 "NO FLIGHT DIRECTOR TAKEOFF"

If a takeoff is initiated without FDs, the system responds as follow:
There are no FD bars.

There is no A/THR arming.

There is no guidance available.



The target speed on the PFD is that selected on the FCU or is defaulted to ​100 kt.

Setting the thrust levers to the CL detent does not activate A/THR.

Note: Do not engage the autothrust prior to selecting a target speed on the FCU.

----

2. Autobrake disarm with one brake pedal, or speedbrake/spoilers disarm after landing.

Hi Omniatlas,

Confirm this issue read in Fcom..

[OmniAtlas]

Hi Omniatlas,

Confirm this issue read in Fcom..

Have you been able to test this setup with FMGS?

I will also try a take off without V2 input.

[Beaufort]

If you run the software manually (i.e. without the starter), it's been a long time since there no longer any SD.exe, EWD.exe etc... The 6 EIS display (PFDs/NDs/SD/EWD) have been replaced by a single EIS.exe file. This file must be run with the correct parameter to determine which display it actually represents (the physical display, i.e. the display at a physical position in the cockpit). This allows easy EIS reconfiguration (PFD/ND XFR etc).
The installer should install shortcuts (called PFD, ND, SD etc) which link to the EIS.exe with the correct launch parameter. Windows allows you to force admin right on a shortcut as well (at least 7 and most probably vista as well).

Regards,
JL

Hi JL,
well, my fault, as you say, EWD and SD are shortcuts only, that´s the same in my installation.
In fact I cannot assign admin rights neither to these shortcuts not to the EIS.exe, it is greyed in Properties/Compatibility. I can set the checkmark in Properties/Shortcut/Erweitert/Als Administrator ausführen (-dont know the term of english Windows-), but that doesn´t change anything. Seems to be a problem of (perhaps only my?) Vista, I installed the EWD and SD on my primary (Win7-) PC, there all is working fine even after the autoupdate. There admin rights in Properties/Compatibility are also greyed, but different to the situation on the Vista PC the boxes for admin rights are checked.
As I will change to Win 7 soon on all my PCs no need to solve the problem for me.
Regards Rainer

[jeehell]

Hi

this may not be a problem with admin rights. What video card do you have? is it old? do you have drivers up to date or not?

Regards,
JL