En - Installation Guide
En - Installation Guide
Installation Guide
Version 54.x
Version 54.x
CONTENTS
Click on a chapter in the table below to jump directly to its page.
Recent additions/modifications are marked with the ◄ symbol.
1. Foreword ..................................................................................... 4
2. Read carefully before installation ............................................. 6
2.1 - One or more Computers? ........................................................................... 6
2.2 - Compatible Operating Systems ................................................................. 6
2.3 - Interface to Microsoft ® FSX or Lockheed Martin Prepar3D ◄ ............. 6
2.4 - NavData ........................................................................................................ 6
2.5 - Flight Simulator A320 Flight Model ........................................................... 7
2.6 - If an older version is already installed ...................................................... 7
2.7 - Displays Fonts ............................................................................................. 7
3. Basic installation ........................................................................ 9
3.1 - FSX(P3D) / FMGS Server computer ........................................................... 9
3.1.1 - JeeHell A320 FMGS software components ...................................................... 9
3.1.2 - Other components .......................................................................................... 10
3.2 - The other computers ................................................................................. 10
3.2.1 - Five computers possible configuration ........................................................... 10
3.2.2 - Possible configurations with less computers .................................................. 10
3.3 - Installing the FMGS server on a networked computer .......................... 13
3.4 - Installing joysticks / pedals on networked computers .......................... 13
4. Installing the software ............................................................. 16
4.1 - Installer ....................................................................................................... 16
4.2 - Axis Calibration – Buttons Setup ............................................................. 23
4.3 - FMGS_Server and FSX / P3D on separate PCs ...................................... 28
4.4 - NavData Installation .................................................................................. 30
4.5 - Simpatcher manual installation ............................................................... 30
5. Starting the software ............................................................... 32
5.1 - Starter and StarterENGRUN ..................................................................... 32
5.2 - How to configure the security softwares on your system ◄ ............... 32
5.3 - Updates ...................................................................................................... 32
5.4 - Minimized applications ............................................................................. 33
5.5 - Navdata loading ......................................................................................... 33
Version 54.x
1. Foreword
A320 FMGS software is a freeware solution to replicate the real Airbus A320's Flight
Management & Guidance System (FMGS) and main electronic instruments for Microsoft's
Flight Simulator® and Lockheed Martin Prepar3D®. My aim with this software is to achieve
the greatest realism possible, given the limitations of FS, my free time and my
programming skills. As of this writing, the following systems are modeled:
FMGS
AP/FD & FBW
Primary Flight Display (PFD)
Navigation Display (ND)
Flight Control Unit (FCU)
Multifunction Control & Display Unit (MCDU)
Engine /Warning Display (E/WD)
Status Display (SD)
Overhead panel and subsequent ACFT systems
Brakes triple indicator
Stand-By instruments,
The 3 RMPs, the 3 ACPs, and ECAM Panel,
Thrust levers, flaps, spoilers, landing gear handle + A/BRK Panel,
I started this project to fit my home-cockpit hardware. The commercial alternatives are very
expensive, their price tag is prohibitive regarding the money I want to spend on a FS
hobby.
All commands can be interfaced with hardware through FSUIPC.
The Software can be interfaced with the following hardware (non exhaustive list):
OpenCockpits IOcards,
Flight Deck Solutions (including FCU Glare3 and MCDU),
CPFlight (FCU / EFIS / Glare Wings),
CockpitPassion,
Skalarki I/O,
CockpitSonic.
Check the manufacturer guide, and also the Hardware Module folder after installation.
When installing, you will need to select the hardware options necessary for your simulator,
which will install then in the « Hardware Modules » folder.
Version 54.x
If you have any questions, remarks or anything you want to say, you can do so either via
e-mail ( jeehell “at” jeehell.org) or through MyCockpit.org forums
This Guide details how to install the software on one or more computers.
DISCLAIMER:
This software is by no means related to Airbus, EADS or any affiliated group. It is
intended to use only as a recreational software together with Microsoft Flight
Simulator. Do not use as a part of training toward any kind or aeronautical
certification, be it private pilot or commercial pilot training.
This software should cause no harm to your computer. In the very unlikely event
damage occurred to your system, I won't take any liability. Use at your own risk.
The use and distribution of this software in any professional environment is
prohibited without a proper licence. Check the License.txt file to know what are the
rights you have with this version.
R
R 2.3 - Interface to Microsoft ® FSX or Lockheed Martin Prepar3D ◄
R
R
R FSX / P3D (V1.x to V5): the communication with Flight Simulator is based on
R «SimConnect » (you do not need any third party software). Note for FSX: you need both
R
R Service Packs 1&2 for FSX (or « FSX Acceleration »).
R
R The software is no longer compatible with FS9 (FS2004).
R
R
R
R
R 2.4 - NavData
R
R
R Before launching installation, you should install the navigation database (navdata).
R
R Both Navigraph and Aerosoft NavDataPro support the navdata format, they each have
R
R
R
R
R
Version 54.x
3. Basic installation
The various software modules are meant to work in a networked environment. This
chapter will describe a simple architecture: one computer is dedicated to FSX/P3D and
FMGS server; other applications will be run on remote computers, depending on your
needs.
Of course not all configurations/combinations could be tested…
You will find two diagrams below, showing:
An installation without hardware (but still including a joystick, a single throttle lever,
and an axis for the rudder).
An installation with full hardware.
4.1 - Installer
It is necessary to run the installer package « A320FMGS Bxx.exe » with administrator
rights, on all computers.
Avoid installing in a folder such as C:\Program files! It is recommended to keep the
default path: C:\A320FMGS .
First, you need to specify which version of FSX or P3D you use :
If you scroll down the list, you will notice several sections. First the « Applications »
section, followed by the « Modules Hardware » section and finally the « Software panels »
section.
On each computer, select which component(s) you need, as was discussed in preceding
chapter.
Version 54.x
“Main Application” :
If you install FMGS Server on the PC running FSX / P3D (chapter 3.1 and 3.2) : Install
“Master FSX/P3D PC” and “FMGS Server and AP/FBW” modules on this computer (and
only on this computer).
If you install FMGS Server and FSX / P3D on separate PCs (chapter 3.3) : Install
“Master FSX/P3D PC” on the PC running FSX / P3D, then “FMGS Server and AP/FBW”
modules on the separate PC (and only on this PC).
“EGPWS logic” module : Installation of terrain data "EGPWS" is changed for a better
management of the data load.
“EGPWS Logic” module must be installed ONLY ON ONE COMPUTER of your
simulator : check the corresponding box “EGPWS Logic” on the computer on
which you decide to install it, and be careful to uncheck the same box on all other
computers (your choices will be remembered for all future installations).
Version 54.x
“Hardware Modules” :
If you install FMGS Server and joysticks / pedals on separate PCs (chapter 3.4) :
Install “Remote Joysticks Support” module on every PC where joystick and/or pedals are
connected.
« FMGS Server and AP/FBW » and « Remote Joysticks support” can’t be installed
on the same PC.
Software interfaces are grouped in the « Software panels interface » list : These are the
thrust levers, flaps, spoilers, landing gear handle + A/BRK Panel, the 3 RMPs, the 3 ACPs,
and ECAM Panel. Install these software modules according to your simulator configuration
(however, only install what is necessary on each computer).
Version 54.x
Continue with the installation process to get next window (usual installations leaves the
next 4 checkboxes checked) then an installation summary:
Version 54.x
Once the installer has finished copying the files, you will get another important window:
Version 54.x
This step is very important. If you do not enter correct data, the software will not
work !
“This computer is running FMGS Server” : This box is automatically checked when
FMGS_Server is installed on this PC (and FMGS Server IP address is grayed out).
This box is unchecked when FMGS Server is not installed on this PC ; so you must
enter the IP address of the PC where FMGS Server runs.
“This computer is running FSX/P3D” : Same as just above.
“This computer is running EGPWS” : This box is automatically checked when EGPWS
Logic is installed on this PC, and unchecked when not.
Server ports : Do not change the default ports, unless necessary in your network
configuration. The button « Default values » will restore the default values for you.
“EGPWS” ( chapter 5.10 ) and « WX Radar » » ( chapitre 5.11 ) : The content of the
folders C:\A320FMGS\WXR (on P3D computer) and C:\A320FMGS\EGPWS\EGPWS (on
the PC where you install EGPWS module), will have to be used from the others PC where
the ND modules run. So you will have to share these two folders (sharing rights to
configure into Windows).
“WX Radar path” : Click on the indicated path. Windows will open an Explorer box, where
you have to indicate the real (eventually networked) path to the shared WXR folder.
“EGPWS Output path” : When “This computer is running EGPWS” box is NOT checked
(and so EGPWS module is not installed on this PC), you have to indicate (as just above)
the real networked path to the shared EGPWS folder.
“EGPWS Data path” : When “This computer is running EGPWS” box IS checked (and so
EGPWS module is installed on this PC), here is indicated the path to this folder. When not
(unchecked box above), no need to indicate anything (this box remains grayed out).
Note : You will not be able to indicate any networked path above, as long as the sharing
rights are not (or bad) configured into Windows. In this case, it would be better to let the
installation go on till the end, before configuring the sharing rights into Windows.
Afterwards, look after “Configure.exe” file and run it : you will get the same windows to
rightly complete.
Now you only have to click on « Done » button to finish the installation.
Take care to leave « Setup Joysticks » box checked, particularly if you are a
beginner with the software. It will make the installer launch the axis configuration
tool when exiting the installation process, to calibrate your joystick axis.
Version 54.x
If you uncheck it, the calibration tool is located in the FMGS Serve folder, and is
called « FMGS_Config.exe ». You may launch it later, but please note that
FMGS_Server and FMGS_Config can’t simultaneously work (you will get an error
message).
If you chose to install your joysticks / pedals on separate computer(s) from FMGS Server
PC chapter 3.4, you must run “RemoteJoyApp” (as an administrator) on the
computer(s) where joysticks / pedals are connected, in order to allow FMGS Server to
detect them through the network.
Important : “RemoteJoyApp” module may be blocked or deleted by security
softwares (anti-virus / firewall or even Windows firewall ). It would be a wrong way to
deactivate your security softwares ; the best way to deal with them is to configure them
to allow the use of “RemoteJoyApp” module.
Version 54.x
To calibrate an axis, click in the corresponding white box, then move the joystick axis you
want to configure until it is detected.
If not detected, click on the little arrow on the right on the corresponding window : a scroll
menu will display all detected axes. Choose the one you want to calibrate.
A window pops up to allow calibration: you have to move the axis to the max/min/middle
positions and click on the button corresponding to the position the axis is in.
Version 54.x
The cursor indicates the current position of the axis and the blue area is the neutral zone,
in which the axis has no effect.
Do not hesitate to fill in relatively big neutral zones (around 10% is usually OK for regular
joysticks)
AILERONS is the roll axis,
ELEVATORS is the pitch axis,
RUDDER is the yaw axis,
TILLER is the nose wheel steering axis.
LEFT BRK et RIGHT BRK are the differential braking axis.
CPT is for Captain side, FO for First Officer side.
Regarding the Thrust Levers (THR LVR 1 & 2 for engine 1 & 2), click on THR LVR1:
lower left area of the application becomes active, and allows you, depending on your
setup, to configure a single axis for both levers or one axis for each lever.
For the thrust levers, you will need to input an absolute error around each detent. Let’s say
the TOGA detent corresponds to a value of x=30000, while the max reverse detent
corresponds to a value of y=3000. The total course is 30000 - 3000 = 27000. I suggest to
use 5% for the detents error margin, so this would be 1350, you can round that to 1000
here (you would later on fine tune that after trying in the simulator how the levers respond).
In your hardware setup, « x » and « y » will probably largely differ, but the principle is the
same : using « ( x – y) * 5 % » for the margin value is a good first approximation you can
later fine tune.
Version 54.x
Clicking on « Save Controls Configuration » will save the settings you've applied already. It
is a good idea to save regularly your work when configuring.
SPOILERS axis is configured on the same principles as ailerons or elevators axis. There
is an added feature to make the ARM position part of the analog course (some hardware
need that feature). In that case, the same neutral zone is applied bot hfor the ARM position
and RET (FWD) position.
FLAPS axis is a bit different (see next picture): the window offers five positions. Put the
lever in each position then click the button corresponding to it. Do not forget to put an error
zone again !
Version 54.x
Joystick Buttons: you can also use joystick buttons to operate almost any
switches/buttons of the cockpit.
Click on “Joystick Buttons” button, a new window appears (see next picture).
Push a joystick button, its joystick name and button number will appear.
You can now select an action for when you push the button, and another action
when you release the button.
An action ID (i.e. which switch of the cockpit is used) can be selected by double
clicking on gray boxes (marked by the arrows N°1 on the picture). A list with all
actions will be displayed.
You can then select which event is associated (either Push, Release or Toggle
events) (arrows N°2). Most events DO REQUIRE both events to work correctly.
Version 54.x
In most cases, you should only use the same action ID and associate a
Push/Release event to the joystick Push/Release actions (as on the picture).
Don't forget to save the entire configuration by clicking on « Save Controls
Configuration » on main window.
1 – On your FSX / P3D computer (example given for P3D V4), run :
C:/Programmes/Lockheed Martin/Prepar3D V4/redist/Interface/FSX-SP2-XPACK/retail/lib/
SimConnect.msi
Version 54.x
2 – On your FSX / P3D computer (example given for P3D V4), look after :
C:/Users/YourSession/AppData/Roaming/Lockheed Martin/Prepar3D v4/Simconnect.xml
Its content should look like the one below (depending on your installation); if not, create it
with the help of a publisher (192.168.x.xx corresponds to your PC IP address).
3 – On your FMGS Server computer, open your Windows Notepad, write the following
below, and save it as “simconnect.cfg” on your “My Documents” folder (192.168.x.xx
corresponds to your FSX/P3D PC IP address) :
Version 54.x
Caution : in both cases, the navdata is not usable by itself. You must let the FMGS
Server compile them in another file format on the first run, and this process will need to
take place on every cycle update, or FSX/P3D sceneries change.
See chapter 5.4 for more details.
<Disabled>False</Disabled>
<Path>C:\A320FMGS\Simpatch\SimPatcher.dll</Path>
</Launch.Addon>
To check proper installation of simpatcher, while the whole FMGS software is running, go
to your FSX/P3D addon menu, and look for a simpatcher entry. If there is none, then it is
not working/installed properly.
R
R 5.2 - How to configure the security softwares on your system ◄
R
R
R Some of the software included in A320FMGS may be blocked or deleted by security
R software (Avast, Norton,…) and even by Windows Firewall. The best way to deal with this,
R
R is to configure them to allow the use of JeeHell A320 softwares.
R
R UDP protocol : From now, JeeHell A320 FMGS modules are using UDP protocol for a
R
R
better communication with each other. Security softwares or firewall might block these
R communications. In this case, on each computer running JeeHell modules, you have to
R
R
configure firewall to allow UDP protocol on ports from 8000 to 9000.
R
R Generally depending of the security softwares you use, this only might be one or
R several firewall messages, asking you to allow the first launching of each module.
R
R
R
R
R
R
5.3 - Updates
R
R The starter will automatically launch an update tool which checks online if a new update is
R
R available.
R
R “Updater.exe” may trigger firewall alarms (see no above on security software).
R
R Follow the instructions of the application to download the new version if available.
R
R Note: if you installed the software on more than one computer, you need to run the update
R
R
on each computer of your network. Otherwise, you may get errors while running the
R
R
R
R
Version 54.x
software.
When you save the settings, they are stored in a file called « XXX.ini », where XXX is the
instrument name. Delete that file to restore “manufacture” settings.
The picture above shows some sounds unselected (that will not be played), and others on
various sound cards of the computer. Also, note you can adjust the volume of each sound
independently!
Do not forget to click the save button!
Note JeeHell A320 FMGS does not contain any aircraft sound (engines, aerodynamic
sounds etc...). Those sounds are played by FSX/P3D, and you must install your own
addon sounds.
Version 54.x
For each flight deck crew seat, you can select the audio I/O for the relevant headsets,
microphones and speakers possible (as on the real aircraft). It is not possible to add more
headsets or microphones, but you do not have to plug all of them (if you only use a single
headset per seat then it is fine).
For each microphone, you can select a “squelch” value, which is a detection threshold. If
the sound volume going through the mike is below the threshold, the mike will stay mute.
For each speaker/earphones, you can use either stereo, or L/R mono channels. This can
be useful to reduce the number of required outputs from sound cards (but requires
modifying the jacks and cabling of your headphones…).
There are two added I/O, external radio in/out. They are used to connect the software to
an online flying voice client (such as TeamSpeak). However, it is NOT possible to map
directly the External radio in to the voice client output, and vice versa, it is only possible to
use hardware I/O. Two solutions are possible:
Use the voice client on another computer, and cross-over the output/inputs
Version 54.x
Use a virtual sound card driver, which can create “virtual” sound cards I/O, which can be
cross-over’d by the driver itself (such as Virtual Audio Cable 4).
After downloading, you will need a software such as 7-zip to unarchive the files twice
(there is a.tar file compressed in the .gz file). Each tile gives 8 files, as you can see in the
picture bleow.
Version 54.x
You must put all these files, from all tiles in the same folder to process them.
Choose the quality you want (I think 2 or 3 is OK, 1 makes a pretty big database which
slows down the EGPWS, 4 and above are too poor). Only integer numbers.
Click "Open Header file", then browse to the location of all unzipped GTOPO files.
Click on any .HDR file.
Wait. The whole process is quite long, around 10 minutes for one tile so don't be in a hurry
if the window freezes. You can check if the software is still working if new folders appear
periodically int he EGPWS data sub-folder.
Once the database has been created, you can launch A320 FMGS.exe as usual.
Go in the "MCDU MENU" page and press 2nd LSK to activate "TERR on ND".
EGPWS represents an heavy load on the CPU. Even with a fast computer, you might
notice the other instruments slowing down, and even lose control of the aircraft. If it
happens, you'll have to fly without EGPWS.
Version 54.x
The WXR detects preiciapation and turbulences associated to precipitations. It will only
display data when there is rain/snow/hail.
Setting up the WXR is a rather complex operation:
You need to have a working ASN / AS16 / ASP4.
On the FSX/P3D computer, you will be prompted to declare the WXR path (see
chapter 4.1). I suggest leaving the default path.
You MUST then share this folder. Usually, you will need to right click on that fodler
and select sharing options. This guide is not a Windows tutorial, you can find plenty
of help on internet. Just make sure you do not need login/password to access the
shared folder remotely.
It is possible to use network mapped drives. HOWEVER, due to the security
features of windows, and particularly sandboxing features, a mapped drive created
even with an admin session will not be accessible by my software running with
admin rigths. The mapped drive must be created by a batch file … So only for
VERY advanced users.
On all PCs running either PFD or ND applications, you must set in the WXR path
the shared folder (it might look like, for example, “\\YOURP3DPC\WXR” ).
Some addons use FSUIPC to retrieve WXR image from AS16/ASN.This has the
effect of disabling WXR access to other addons (AS16/ASN only gives one access
to one addon at a time). You need to remove that feature in FSUIPC.ini file.
The WXR relies on the module called Simpatcher, provided with the FMGS
software. If it is not correctly installed, you need to install it manually (see
chapter 4.5). When Simaptcher is running correctly, and ASN16/ASN interface
works, the WXR folder will be populated with files at regular intervals.
To operate the WXR, you can go in the “MCDU MENU” page of each MCDU. You will then
get some controls on the WXR.
Version 54.x
As on the picture above, pushing RSK2 on that page will help you set the WXR/EGPWS
image brightness (independently of the actual ND brightness). You can enter here any
value from 0 to 255.
LSK3 will get you to the specific WXR controls:
LSK1 turns the WXR on/off. Even if ON, the WXR image will be displayed only if
onside EGPWS is turned off.
LSK2 is on AUTO by default. Setting the gain to MANUAL, you can then change the
gain value in the RSK2 field. (see next picture)
LSK3 is on MULTISCAN by default. Setting the tilt to MANUAL, you can then
change the tilt value in the RSK3 field. (see next picture)
LSK4 is used to turn PWS (predictive windshear) ON/OFF.
RSK1 is used to cycle between 3 modes:
WX + T: precipitations + associated turbulences.
WX : only precipitations.
T : only turbulences.
Version 54.x
On the real aircraft, these features are set on the WXR panel, on the pedestal. The MCDU
access is only to let people use them without any hardware.
If you do not see any picture, even after all the steps described here, it can be because
simply you are not in an area with precipitations to be displayed.
To make a test, find a location with heavy thunderstorms (or set ASN/AS16 to heavy
thunderstorms).
The WXR image will present a color coded image.
Black means no precipitations
Green is low precipitations
Yellow is medium precipitations
Red heavy precipitations
Magenta means high turbulence (so heavy precipitations usually near a very active
Cumulonimbus).
Clear air turbulence is NOT detected by the weather radar.
Other options : We advise you to leave the default choices if you do not have sufficient
knowledge of the A320 and its features.
Version 54.x
5.15 - Uninstallation
You just have to run “Unist000.exe”, located in the folder C:/A320FMGS. Some files and
folder will remain, in order to a further installation.
If you want to remove these elements to start from a complete installation, but have
already configured your axes and screen positions, you can save the following files,
copying them into another place :
Acontrols.cfg and JoySW.cfg (Joysticks and pedals buttons and axes),
• ".ini" or ".cfg" terminated files with the name of the modules (PFD.ini, ND.ini,
OVHDvisual.ini, configMCDU.cfg, configFCU.cfg, configFOEFIS.cfg…
Do the same for the files from EGPWS data extraction.
Naturally, you will then put all them in their respective folders after your new installation.
Q2. I move my joysticks and throttle levers in all directions, but nothing moves
inside FSX/P3D?
A. You first need to setup your Controls in the FMGS Config.exe software ! Check
chapter 4.2 of this guide.
Q4. Is it mandatory to have analog axis for the sidesticks and thrust levers?
A. If you want to actually fly, this is mandatory for the sidesticks. B46+ provides now
a graphical software panel for the thrust levers, but an actual hardware is still much
more accurate.
Q6. I use FSUIPC to command the OVHD inputs, do I nevertheless need to launch
the OVHD software?
A. The OVHD logic is part of a different application than the graphical interface. This
means the graphical interface is not needed at all, but the logical one (on the FMGS
Server) still is.
Q8. The instruments are ON, but PFD and ND only show red flags such as HDG or
ATT?
A. You need to align the IRS. To do so on the upper OVHD:
switch on the ADRs on the upper OVHD
Version 54.x
Switch the IRs selectors on NAV (normal alignment, for a quick alignment, select
them back OFF then back NAV again quickly)
When IRS alignment is complete, you need to initialize the IRS position through
the MCDU INIT A page, after departure and destination fields are filled.
Read the User Guide for more information.
Q11. I've just aligned the IRS1 and initialized the position on INITA page in the
MCDU. The captain ND is showing the map but the FO one is still displaying red
flags.
A. Under normal operations, CAPT ND receives data from IR1, whereas FO ND
receives data from IR2. The IR3 provides data for both sides as a backup. It is good
practice to align the three IRS at the same time, before engine start.
Read the User Guide for more information.
Q12. I've upgraded my preexisting installation to the latest beta release of the suite.
When I launch an instrument (FCU, ND, etc) it shows the error “--- is not a valid
Boolean value” or a similar error.
A. You probably forgot to update some of the instruments. All .exe files have to be
replaced, even on client computers.
Q14. I try to use F5-F8 keys for the flaps, but it does not work?
A. Almost all controls must be assigned from FMGS_Config.exe application. The
A320 being very complex, FSX systems are somewhat too simple, and I had to
bypass most of FS internal systems. This way, FSX is merely the aerodynamics
model and visual system.
Also, all configurations suggested here may not have been fully tested, and are not
forming hardware/configuration specifications.