A320 FMGS B31

[jeehell]

Hi,

@Arnab: Hard to tell what you're doing wrong. Probably an engine or system not started correctly...

@Rob: I'm aware of this issue, I'll have a look.

@Umberto: You must NOT change the default folder where aerosoft's navdatapro isntalls the navdata for my software. It has to be c:\users\your_user\appdata\roaming\jeehellware (where "your_user" is of course your username under windows...).

JL

[Arnab]

@Arnab: Hard to tell what you're doing wrong. Probably an engine or system not started correctly...

JL

Hi JL,

This is a what I did:

1. Install FSX+SP1+FSX acceleration (Program Flies (x86))
2. Install Level-D (Program Files (x86))
3. Install JLFMGS B30. It asked for Nav Data - and everything seemed fine on install
4. When the Joystick calibration window came, I cancelled it as I dont have joystick or throttle. - only mouse and keyboard.
5. Install FSUIPC4 (4.92) (not registered)
6. Restart
7. Run FSX (at minimal graphics) - select JL A320, VIDP as airport.
8. After the aircraft loaded, reduced the window size and kept it on the desktop. (Disabled pause while switching window)
9. Launched A320 FMGS.

The panels open and the a/c engines shut down in FSX.

From OVHD -
1. Both batts ON
2. All fuel pumps ON
3. APU Master ON and APU Start ON.
4. After the APU is AVAIL, the PFD shows in red (the tapes are in red and no info) and the ND says No data. E/WD shows OK but the green parts of Flaps and Slats dont show.
5. ADIRS 1,2,3 - ON
6. ADIRS Knob - NAV, then off and then back to NAV. Repeat for all three.
7. APU Bleed - ON
8. Strater Mode - IGN Start, and then ENG2 Master ON.
The E/WD shows the engine starting. After the engines are stabilized, repeat for ENG1.
9. GEN 1 and GEN 2 - ON
10. All electrical Korry switches - ON.
By this time all three ADIRS ALIGN indications go out.
The PFD is still red and the ND still showing NO DATA.

The sound dialog box says 'Not connected to FMGS server'.
Is there anything I am missing out?

I uninstalled B30 and deleted the A320 folder in C:. Then installed B31. But no change.

Arnab

[jeehell]

Hi,

You need to have a joystick installed and configured, otherwise the FMGS Server won't start.
From version B31 on, the navdata tailored to my software from Aerosoft is needed. I have to update the user guide about that.

Regards,
JL

[Leonidas]

Hi to all.
Jean Luc thank you for this update. Great job! Allow me to report some issues I noticed after the very firsts flights:

1. I don't see VORs, WPTs etc on ND
2. "FLAPS NOT IN T.O CONFIG" message after landing for long time with aural signal.
3. If I close server first, the two clients (PFD-ND) can't shut down, because FMGS client is frozen.
4. Backlight on Cockpitsonic's ECAM CP doesn't turn on every time, but only one out of three flights.
5. Header dot turns off without a reason on CPflight's FCU

Thanks a lot

[AirFan]

Hi Leonidas,

1. I don't see VORs, WPTs etc on ND -
i had the same issues after installing over the existing b30. After a clean install it worked fine. Copy the nav data file to the clients as well.

2. "FLAPS NOT IN T.O CONFIG" message after landing for long time with aural signal. -
I dont have that issue.

3. If I close server first, the two clients (PFD-ND) can't shut down, because FMGS client is frozen.-
Confirmed. Something keeps running which need to be forced to shut down.
EDIT: This only happens in case I want to shut down the client PC before I quit the client application. So I can quit the client Software correctly but if I try to shut down the PC without quitting, I get an error from Windows if I want to force to close the app. a minor thing...


Robert

[Leonidas]

Copy the nav data file to the clients as well.

Thanks Rob, but still nothing.

[buentead]

Hi

there is a logfile in FMGS server folder.

JL

Thanks, JL. I couldn't reproduce the crash on the FMGS server since I reported it. I'll come back with the logs if it happens again.

Adrian

[buentead]

Hi Adrian,
I had the same problems with B30 (B31 isn't installed yet). I assume it was my WLAN which didn't run stable enough. Since I connected server and client with LAN all these disconnections have stopped.
René

Hi René
Thanks a lot for your comment. Since I connect all PC's through LAN, I couldn't reproduce the error either. It looks like the problem is solved when running all on LAN.
Cool, thanks
Regards
Adrian

[romeow]

Your're welcome! Nice to hear that you solved the problem.
Regards
René

[jeehell]

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