OPERATIONS MANUAL

Simulator Handling
User Files – Overview:
User files that can be saved and loaded through the Instructor
Situation files store situational and aircraft model variables. These are variables
that are also transmitted across the simulator’s main network when connected.
Model files store aircraft model variables only. Loading such a file will load an
aircraft model only, and will not change other situational data, unless it is forced
to do so; for example, if the loaded aircraft’s fuel tank capacity is smaller than the
fuel quantity currently on board, the quantity will be reduced accordingly.
Layout files store user defined zoom, pan, and subframe divider settings of the
flight deck frame. Each layout file stores nine layouts; the keys 1 to 9 on the
numeric keypad, for example, will switch between the nine layouts.
Preferences files store computer specific data, such as the preferred USB and audio
selections, mouse functions, and so on.
Other user files
Route files, located in the Routes folder, store FMC company routes. They can be
stored through the Instructor, and loaded in the simulated FMC which accepts
two file formats: the Aerowinx format, and the PFPX format by flightsimsoft.com.
A track plot file, located in the Logs folder, stores the aircraft lateral track of the
past 20 hours. The plotter pauses when the aircraft is stationary. The data can be
completely erased on the Instructor.
METAR files, located in the Weather folder, store world-wide METAR data
downloaded from the Internet. During every simulator start, all METAR files
stored in this folder, except for the latest two files, will be deleted.
Databases:
The simulator contains some primary databases, each feeding one or multiple
simulator components. The next page illustrates which database feeds which
component. The green ovals indicate the actual, physical (primary) databases. On the
real aircraft, each component—like the FMC or EGPWS—uses its own individual
database; whereas the components in the simulator just simulate their individual
databases because, in fact, they are all supplied by the same primary database, and just
hide certain variables (hiding the NDB frequencies in the FMC database simulation,
for example, because the real FMC does not store these frequencies).
— Page 15 —
For preview only. Not for sale. Many pages are intentionally removed.