曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

• FAF, the range of the Final Approach Fix can be entered here
• MIN AGL LNAV, the minimum altitude for LNAV engagement
• TIME, select either system or MSFS Zulu time
• QNH, select your preference
• FUEL, select your preference
• Autobrakes – enables you to set AB from MCDU
• PREFLIGHT, if set to on will require a full Pre-Flight Set-up of the MCDU
• FLUSH, will flush all data from the MCDU after the aircraft has landed or upon each re-start of the
MCDU.
The MCDU is now in a basic configuration for use.
Other user settings that can be select are self explanatory:
• NAV/COM/XPDR, you can enter radio frequencies
• EFIS selectors can alter GC displays via the MCDU
• SPD PROTECT, artificial simulated flap and speed protection
• EXTRAS, simulator rate and freeze modes
If you require resetting or gathering information about your current NETDIR status, this can be done by
going to the INDEX page of the MCDU, and selecting MAINT. Then select the NETDIR option.
Step 5 Airbus MCDU Flare Altitude
If running the MCDU the flare altitude must be set. If you do not change a/c types then this only needs to
be set once. The flare altitude will determine at what point on an Auto Land the aircraft will start the Flare.
The flare altitude will probably be set at 30 by default; you may want to change this value depending on
what a/c type you are using. The flare altitude can be set by entering a new value in the MCDU ini file.
Project Magenta Revision: 26-May-07
48
Airbus-Type FCU
The Airbus FCU can be run on your system connected to specific FCU hardware and can then reside
minimized as a background process, or it can run as a point and click devise using the software graphic. If
you are intending to run the FCU connected to hardware, you need to set the hardware connection via the
mcp.ini file in the main FCU program folder. Please look at the mcp.ini file to see if your hardware is
supported or contact Project Magenta for further information about specific connections.
The Airbus FCU currently covers the following aircraft types:
• A319
• A320
• A321
• A330
• A340
By pressing the ESC key whilst the FCU is the active program, a user Menu of basic options will appear.
This includes FCU type and some basic specific mode options. There are other options in the FCU.ini file
which is self documenting.
To alter the size of the FCU graphic simply drag at the sides or corners with the mouse. There is an option
in the user interface to reset the size or press CTRL R.
Generally, the Glass Cockpit is designed to run as a whole system with every element of the PM software
running. For accurate Autoland the AP needs to know the specific Flare altitude. Normally, this is defined
by the MCDU program if it is running. If it is not going to be used, then you must define your Flare Altitude
in the FCU.ini file. Note that if you run the MCDU at a later date what is set in the MCDU will become valid
data. (See the MCDU section for setting the Flare Altitude).
To set the Flare Altitude in the FCU.ini (if you are not using the MCDU software) edit height above ground
you wish the AP to commence the flare on an AutoLand (any value, 20, 30, 35, 40, and 52 etc):
Flare=40
There are many self documenting other settings in the FCU.ini file which can be set by the user if required.
Project Magenta Revision: 26-May-07
49
pmSystems
Typical System Requirements
• 1.2ghz PC & Above
• Fully Compliant OpenGL Graphics Card / Colour Depth 16mb
• WideFS and FSUIPC (full version / Registered)
• Windows Operating System
• MSFS
• Flight Model of your choosing with default MSFS panels
PmSystems Introduction
pmSystems can simulate the complex system logics found in heavy transport aircraft. It can be used both
as a pure software interface and / or to provide logics for custom hardware.
Switch positions, indicator lights, are given offsets (and variable names) to give users full flexibility when
implementing their hardware requirements. It is also fully expandable and almost anything within the
systems can be defined by users themselves.
Offsets and varibles are listed within the system file sysvar.txt in the main program folder and will allow
users to connect and control their own hardware with the appropriate I/O board.
It is important to understand that pmSystems becomes the central interface for control of what aircraft
systems there are in FS and not FS itself. Once pmSystems is in the loop you must use it as your central
interface to start engines etc and your hardware must be talking directly to pmsystems (if you are using
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料12(103)