From Manuals
Jump to: navigation, search


1 Introduction

1.1 ProSim737 User Manual layout

This manual is divided into different subjects. Please read and follow chapter 1 and chapter 2 to install the software correctly. Before contacting support,please refer to the manual or the interactive forum on our website. The FAQ database is also an option where your answer may be found. (http://prosim-ar.com/support/)

1.2 Introduction

1.2.1 What is the ProSim737 Suite?

ProSim737 is a Professional Simulator Suite that brings accurate flight simulation into your home. Only with ProSim737 can you enhance your simulation experience with: complete and detailed modeled aircraft systems, sophisticated and realistic flight model characteristics, images on the Main Instrument Panels Display Units, extensive Central Display Unit features and easy hardware connection. ProSim737 is Microsoft® Windows™ platform based and is fully compatible with Microsoft® Flight Simulator™ 10, Lockheed Martin Prepar3D® and full Laminar Research X-Plane compatibility is expected mid 2015. ProSim737 is developed by using modern technology resulting in a stable and flexible solution, allowing you to scale simulation exactly to your requirements. NOTE: This software is targeted for home cockpit builders. It is not endorsed by any aircraft manufacturer and may not be used for real world operational training, unless specifically certified by an approved aviation authority.

1.2.2 ProSim737 Suite architecture

All ProSim737 modules communicate with ProSim737 System by using a network protocol and can therefore be freely placed on different computers. There are, however, three modules that need direct access to the Simulator Platform. These are ProSim737 System, ProSim737 MCP and the ProSim737 Flight Model. All other modules communicate with the ProSim737 System module only.

For simulators based on Microsoft® Flight Simulator™ 10 and Lockheed Martin Prepar3D®, the Platform Interface is a combination of SimConnect and FSUIPC by Pete Dowson. FSUIPC must be installed in the Simulator Platform, also see the paragraph on additional software. Because ProSim737 System and ProSim737 MCP need direct access to Simulator Platform, we recommend running these two programs on the same machine that the Simulator Platform is running on.

For Laminar Research X-Plane based simulators, the Platform Interface is the ProSim737 Plugin for X-Plane. For more information refer to the X-Plane section in this user manual.

1.2.3 ProSim737 Suite module overview

The ProSim737 Suite consists of individual modules that connect to the ProSim737 System module. The ProSim737 System and ProSim737 MCP modules interact with your simulator platform (Microsoft® Flight Simulator™ 10, Lockheed Martin Prepar3D® or Laminar Research X-Plane) therefore, run on the primary computer. Distribution of all other modules is possible between multiple computers within your simulator configuration. To improve performance the suite architecture provides flexibility with regard to system load balancing, the number of monitor outputs, cockpit and environmental audio separation. ProSim737 System

Manages the simulation of aircraft systems, acts as a central network hub for all ProSim737 Suite modules, interfaces with your hardware components, configures by graphical interfaces and features a webserver for the Instructor Operating Station (IOS). ProSim737 MCP

Contains the auto flight systems and allows connection to the Mode Control Panel (MCP) in your cockpit or to display a graphical representation without hardware. ProSim737 CDU

The Control Display Unit (CDU) controls the Flight Management System (FMS). This module provides possible connection of the CDU in your cockpit or to display a graphical representation without hardware. ProSim737 Display

Generates all graphical elements such as Primary Flight Display (PFD) and Navigation Display (ND) on the Main Instrument Panels (MIP) Display Units (DU). ProSim737 Audio

Provides genuine cockpit sounds independent from the environmental sound. Default sounds can be customised and new sound events can be added. ProSim737 Panel

Creates a graphical representation of the different panels within the cockpit, can be used to check the state of switches / indicators and displays the panels, also without hardware. ProSim737 IOS

The Instructor Operating Station gives the controllability of the simulator by use of a web interface. ProSim737 Flight Model

Provides realistic aircraft behaviour and a visual model with customisable livery.

1.2.4 Typical simulator computer setup

Example The typical computer layout is describing a Primary Computer and a Client Computers. The Primary Computer is the computer where ProSim737 System, ProSim737 MCP, ProSim737 Flight Model and the Simulator Platform run and should be included.

All items with * are free to configure with no additional requirement. May be installed on any of the simulator computers.

1.2.5 Modules startup

There is no particular order in which ProSim737 modules need to be started. All modules need the ProSim737 System module to operate and will automatically connect to it once it becomes available. ProSim737 System and ProSim737 MCP will automatically connect to the Simulator Platform once it is available. As long as the ProSim737 System module keeps running, all systems and FMS data is retained and all other modules can be freely restarted without loss of data.

1.2.6 Modules shutdown

Any ProSim737 module may be closed at any time. An automatic shutdown feature is available in the IOS, and can be found in the “misc” tab of the “maint” menu. This feature will send a “shutdown” command to all ProSim737 modules. Each module that allows remote shutdown will turn off the computer it runs on.

To allow remote computer shutdown by a ProSim737 module, please confirm this in the configuration screen of the module.

1.2.7 Updates

Regularly new updates will be available. Updates are applicable to licence terms and conditions. Updates will be announced on the website, forum and Facebook.

More detailed description of the updated features can be found in Updates

1.2.8 Support

Support is available in the ProSim737 User Manual, ProSim737 Forum and mail-support.

ProSim737 Forum The ProSim737 Forum is a facility available 24 hours a day and serves as a platform for users to interact, share knowledge, offer support and information. http://prosim-ar.com/forum/

Support mail Support mail is an option when no answer can be found in the manual or forum. support@prosim-ar.com

1.3 Terms & Conditions

All our offers and agreements are subjected to the General Terms and Conditions of ICT~Office, registered at the Chamber of Commerce Midden-Nederland, 30174840. Terms & conditions can be accessed in our website: http://prosim737.com/licensing/terms-conditions/

1.4 Abbreviation list

General abbreviations The following abbreviations may be found throughout the manual. Abbreviations having very limited use are explained in the chapter where they are used.

1.4.1 Abbreviation


AC Alternating Current
ACARS Aircraft Communications Addressing and Reporting System
ACP Audio Control Panel
ACT Active
ADF Automatic Direction Finder
ADIRS Air Data Inertial Reference System
ADIRU Air Data Inertial Reference Unit
ADM Air Data Module
AED Automatic External Defibrillator
AFDS Autopilot Flight Director System
AFE Above Field Elevation
AFM Airplane Flight Manual (FAA approved)
AGL Above Ground Level
AI Anti–Ice
AIL Aileron
ALT Altitude
ALTN Alternate
AM Amplitude Modulation
ANP Actual Navigation Performance
ANT Antenna
AOA Angle of Attack
A/P Autopilot
APP Approach
APU Auxiliary Power Unit
ARINC Aeronautical Radio, Incorporated
ARPT Airport
A/T Auto-throttle
ATA Actual Time of Arrival
ATC Air Traffic Control
ATT Attitude
AUTO Automatic
AUX Auxiliary
AVAIL Available


BAC Back Course
BARO Barometric
B/CRS Back Course
BCS Back Course
BRT Bright
BTL Bottle Discharge (fire extinguishers)
B/C Back Course


C Captain, Celsius, Center
CANC/ RCL Cancel/Recall
CAPT Captain
CB Circuit Breaker
CDS Common Display System
CDU Control Display Unit
CG Center of Gravity
CHKL Checklist
CLB Climb
COMM Communication
CON Continuous
CONFIG Configuration
CRS Course
CRZ Cruise
CTL Control


DC Direct Current
DDG Dispatch Deviations Guide
DEP ARR Departure Arrival
DES Descent
DEU Display Electronics Unit
DISC Disconnect
DME Distance Measuring Equipment
DSP Display Select Panel
DSPL Display
DU Display Unit


ECS Environmental Control System
E/D End of Descent
E/E Electrical and Electronic
EEC Electronic Engine Control
EFIS Electronic Flight Instrument System
EGPWS Enhanced Ground Proximity Warning System
EGT Exhaust Gas Temperature
ELEC Electrical
ELEV Elevator
EMER Emergency
ENG Engine
EO Engine Out
EVAC Evacuation
EXEC Execute
EXT Extend


F Fahrenheit
FAC Final Approach Course
FCOM Flight Crew Operations Manual
FCTL Flight Control
F/D Flight Director
FLT DIR Flight Director
FMA Flight Mode Annunciations
FMC Flight Management Computer
FMS Flight Management System
F/O First Officer
FPA Flight Path Angle
FPM Feet Per Minute
FPV Flight Path Vector
FREQ Frequency
FT Feet
FWD Forward


GA Go–Around
GEN Generator
GLS GPS Landing System or
GNSS Landing System
G/P Glide path
GPS Global Positioning System
GPWS Ground Proximity Warning System
GS Ground Speed
G/S Glide Slope
















2 Installation Prerequisites

2.1 Minimum computer hardware requirements

The ProSim737 Suite is not demanding on hardware, however the following items should be adhered to.

  • ProSim737 System
    The recommended setup for a simulator is to run ProSim737 System on the same machine as the Simulator Platform. For optimal performance, a fast quad core processor is recommended. Typically, on a computer with i7 processor, the CPU load of ProSim737 System is less than 2%.
  • ProSim737 MCP
    The recommended setup is to run ProSim737 MCP on the Primary Computer. No specific computer hardware specifications required.
  • ProSim737 Display
    To run ProSim737 Display it is recommended to use a Secondary Computer. Each physical MIP monitor requires an instance of ProSim737 Display to be running. Within one simulator ProSim737 Display modules may be run from multiple computers.
    ProSim737 Display is the most demanding module. This relies mainly on the computer CPU and memory, it does not use video hardware acceleration.
  • ProSim737 CDU
    Each hardware CDU in the simulator requires one instance of ProSim737 CDU to be run. No specific computer hardware specifications required.
  • ProSim737 Panel
    No specific computer hardware specifications required.
  • ProSim737 Audio
    No specific computer hardware specifications required.

2.2 Software requirements

2.2.1 Operating system requirements

All computers should at least run on Windows Vista but Windows 7 or 8 are preferred. Always make sure the latest Windows service pack has been installed on the computers.

2.2.2 .Net framework

An additional requirement is the availability of the Microsoft® .Net 3.5 SP1 runtime software which is available from the Microsoft® website. https://www.microsoft.com/en-US/download/details.aspx?id=22

2.2.3 Simulator Platform - Microsoft® Flight Simulator™

The preferred version of Microsoft® Flight Simulator™ is version 10 (FSX). Microsoft® Flight Simulator™ version 9 (FS2004) is also compatible but to a slightly less sophisticated level due to technical limitations.

2.2.4 Simulator Platform - Lockheed Martin Prepar3D®

The preferred version of Lockheed Martin Prepar3D® was 2.5 at the time this manual was published.

2.2.5 Simulator Platform - Laminar Research X-Plane

Both the 32 and 64 bits versions of X-Plane 10 are compatible with ProSim737.

2.2.6 FSUIPC

For simulators based on Microsoft® Flight Simulator™ 9 (FSUIPC version 3), 10 and Lockheed Martin Prepar3D® (FSUIPC version 4), a registered version of FSUIPC is required.

2.2.7 SimConnect

For simulators based on Microsoft® Flight Simulator™ 10 and Lockheed Martin Prepar3D®, SimConnect required.

2.2.8 ProSim737 Plugin for X-Plane

For simulators based on Laminar Research X-Plane the ProSim737 Plugin for X-Plane is required.

2.3 Required user rights

To install and run the ProSim737 software, administrator rights on all computer systems are required.

3 Installation

3.1 Download the ProSim737 software from the ProSim-AR website

To download the ProSim737 Suite in a web browser enter the web address of the ProSim-AR website:


Then click Download from the top navigation on the web site. On the Download page the ProSim737 Suite is the top entry as on the example below. The version number may vary based upon the moment of downloading.

The downloaded file has a name in the following format: ProSim737-v1.43.zip

Save the file on a location on your computer that you can easily remember, for instance the root of the harddisk c:\.

3.2 Extracting the ProSim737 Suite zip file

Extract the archive with e.g. default windows zip, WinZip, WinRAR or 7Zip to a directory of your choice, for instance in the root of the hard disk: C:\ProSim737\

The following files will be found:

  • ProSim737 modules
    • ProSim737.zip
    • ProSimAudio.zip
    • ProSimDisplay.zip
    • ProSimMCP.zip
    • ProSimCDU.zip
    • ProSimPanel.zip
  • Updater.zip
    For use by ProSim737 System processes only, never manually edit or remove this file.
  • Xplane.zip
    For use in Laminar Research X-Plane based simulators only as described in paragraph XYZ of this manual.
  • changelog.txt
    The changelog is a description of all changes per ProSim737 version.

The next step is to extract each of the above listed module archives into an individual directory, for instance:

C:\ProSim737\ProSim737\ C:\ProSim737\ProSimAudio\ C:\ProSim737\ProSimCDU\ C:\ProSim737\ProSimDisplay\ C:\ProSim737\ProSimMCP\ C:\ProSim737\ProSimPanel\

After unpacking the archives please proceed with the actual installation of the software described subsequently.

3.3 Installing FSUIPC in Flight Simulator

Both ProSim737 System and ProSim737 MCP need direct access to the Simulator Platform. This is achieved by the FSUIPC utility, which needs to be installed in Flight simulator. Refer to the FSUIPC installation guide to install this software. http://www.schiratti.com/dowson.html

3.4 SimConnect

SimConnect is a program automatically installed when installing FSX or Prepar3D. Often the SimConnect is not correctly installed, a default identifier for a wrong installed SimConnect is limited ProSim737 IOS working function. Mainly the visibility option and the weather tab will not work when the SimConnect is not correctly installed. Prepar3D: To reinstal find the “lib” folder in Prepar3d, below a folder structure overview is given to find the correct location: Prepard3d > redist > Interface > FSX-RTM > retail > lib

Flight (FSX\SDK\Core Utilities Kit\SimConnect ) To reinstall SimConnect open the SDK available in the FSX dvd.

3.5 Lockheed Martin Prepar3D®

3.6 Microsoft® Flight Simulator™ is version 10 (FSX)

Flight Simulator version 10 need direct access to FSUIPC and ProSim737 Suite. Refer to the FSX installation guide to install this software.

3.7 X-Plane

ProSim737 has a X-plane connection,

Installation guidance off the X-Plane plugin

We will continue to use and extend the use of our custom X-Plane plugin, which allows ProSim737 direct access to the X-Plane datarefs. The plugin has recently been upgraded to conform to the "fat plugin" style. This plugin style consists of one folder, housing both a 32bit and a 64bit version of the plugin. The plugin can be found inside the Xplane.zip file, which is in our main distribution. To install the plugin, copy the ProSimData folder into your XPlane plugin folder and restart X-Plane.


When using the ProSimData plugin for X-Plane, ProSim737 system has to be configured to connect to X-Plane. To do this, open the configuration screen and under the Main tab, set "Simulator" in the "Options" box to "XPlane".

Aircraft For now we will be focusing on compatibility with the X737 aircraft, without using the X737 plugin. The X737 plugin contains 737 logic which conflicts with the logic already present in ProSim, so switching off the X737 plugin is required when running ProSim737.

3.8 Antivirus


3.10 =Installing FSUIPC


3.10.1 Configure Flight Controls in FSUIPC

Current release ProSim737 suite 1.xx do not directly support the Flight Controls input. To configure the Flight Controls connect direct in to FSUIPC Flight Controls section.

FSUIPC should be installed including read and write function (paid version). It’s important to deselect the “Enable Controllers” option in FSX or Prepar3D setting area.

On the main horizontal navigation bar select FSUIPC in the Add-On chapter. See image below.

For this example the Elevator will be configured. All analog axis, Elevator, Pitch, Rudder, Brakes and Tiller should be configured like this example. Select “Axes Assignment” tab in the FSUIPC Options and Settings area. To detect a axis move the Joystick axis, automatically the movement off the axis is seen in the input and output value see red box below.

Move the Elevator axis to confirm the correct assignment. Then select a function, in this example the function “Axis Elevator Set” is selected, see example image below.

Last part of configuring the Elevator is to go to “Joystick Calibration” page, next to the “Axis Assignment”. Select on the Elevator box by selecting the “Set” button. After selecting the “Set”button the indication is changed to “Reset”. Check and adjust when necessary the full left, center and right assignment by first moving the hardware Joystock and select the “Set” button according the moved axis.

After the axis is assigned select OK to confirm and save the settings.

4 ProSim737 System

4.1 General description

Foremost, ProSim737 System is the multifunctional module that performs the following tasks:

  • Performs as a central hub for all ProSim737 Suite modules.
  • Manages the simulation of aircraft systems.
  • Features a webserver for the Instructor Operating Station (IOS).
  • Distributes audio and navigational data to relevant modules.
  • Interacts with the image generator.
  • Validation of the user license key for the ProSim737 Suite.
  • Manages geographical databases.
  • Connectivity of cockpit hardware.
  • Performs ProSim737 Suite version update.
  • Automates ProSim737 Suite updates.
  • Provides debugging tools for connected hardware.
  • Extensive hardware and software debugging tools provided.

4.2 ProSim737 System Interface

In order to start ProSim737 System please doubleclick prosim737.exe. First the splash screen appears for a couple of seconds after which the ProSim737 System Interface is displayed.

The ProSim737 System Interface always displays a horizontal top navigation with the items “File”, “Config” and “Help”which are explained in paragraph XYZ.

Below is a horizontal navigation bar dividing the screen in tabs. The main tab displays an overview of cockpit hard and software, the other tabs display the current state of cockpit switches, indicators, gauges, gates, etc. These tabs are not used for making configuration changes, they are only used to display the current state of elements or to change the value of a switch in the software if no hardware switch for that particular function is connected.

4.3 Main

On startup of ProSim737 the “Main” tab is shown which displays an overview of cockpit hard and software. On the left, the box called “IO Modules” contains all currently available input and output devices recognized by ProSim737 System, this can be IO hardware cards, joysticks. The box on the right called “Software” contains an overview of three software items:

  • Database
    Shows the actual state of the databases used by ProSim737. Databases are further described in paragraph 4.8.
  • Simulator connection
    This function shows if ProSim737 System is connected to the Simulator Platform.
  • Core Version
    Displays the ProSim737 version number and built date. Below is a list of enabled drivers.

The other tabs all list the state of the various switches and lights in the cockpit. Switches are represented as dropdown boxes, and lights are represented by their colour and a textual description.

The state shown in the various tabs is always the current active state. If hardware is configured to drive a specific switch, the state of the switch should always be represented here. If the switch state of the hardware is not represented in the software then there is a connection issue.

When ProSim737 System has positively received information from a hardware switch, the corresponding dropdown box will be greyed out. This is an indication that the hardware has been configured correctly.

  • Electric
    This tab displays the current state of the elements of the electrical system as found on the overhead panel.
  • Pneumatic
    This tab displays the current state of the elements of the pneumatic system as found on the overhead panel.
  • Hydraulic
    This tab displays the current state of the elements of the hydraulic system as found on the overhead panel.
  • Fuel
    This tab displays the current state of the elements of the fuel system as found on the overhead panel.
  • Lighting
    This tab displays the current state of the elements of the lighting system as found on the overhead panel.
  • Heating
    This tab displays the current state of the elements of the heating system as found on the overhead panel.
  • Navigation
    This tab displays the current state of the elements part of navigational and communications functions. These systems are located on the overhead and pedestal.
  • Warning
    This tab displays the current state of the master caution system and master fire warning systems located on the glare shield.
  • Fire
    This tab displays the current state of all fire warning elements on the pedestal fire panel except for the master fire warning.
  • Audio
    This tab displays if sounds are triggered to play for the gates listed.
  • MIP
    This tab displays the current state of elements located on the MIP.
  • Throttle/MCP
    This tab displays the current state of elements located on the throttle and MCP / EFIS.
  • Misc
    This tab displays the current state of miscellaneous elements such as ACP, elevator control, ground call, LE devices test, rudder trim, seatbelts signs, yaw damping, weather radar gain / tilt and user defined inputs.

4.4 Modelled systems in Prosim737 System

Modelled systems each have their own tab in ProSim737 System.

4.4.1 Electrical systems

All major buses are simulated. Components in the simulation include:

  • Batteries
  • Three Transformer/Rectifier units
  • Static inverter
  • Cross bus tie relay
  • Bus transfer relays
  • Standby bus relays

Note that electrically operated valves will not function when no power is available. All electrical equipment will draw power from the bus they are connected to. This allows realistic operation of the BAT DISCHARGE annunciator

4.4.2 Pneumatic

The pneumatic system is fed with bleed air from the engines or APU. Engine bleed air uses air from the 5th and 9th stage of the engine. A valve will shut off the high stage on high engine settings. The bleed trip system will monitor the pressure in the ducts and shut off the system when pressure is too high. Bleed trips can be reset with the trip reset button. Leaks in the air ducts are simulated and will overheat the wing body. Temperature is calculated from the dynamic pressure on the wing and the internal bleed air temperature.

Air-conditioning packs will condition bleed air for use in the cabin. Fluid dynamics calculations are used to calculate the cabin pressure. These will drive the Cabin Alt, Pressure differential and Cabin VSI gauges. The cabin outflow valve can be automatically controlled, though can also be operated manually. The outside pressure is taken from flight simulator. In automatic mode, the outflow valve will be controlled according to the flight phase of the aircraft.

The FLT ALT/LAND ALT setting will control the pressurisation of the cabin.

4.4.3 Fuel system

The fuel system contains the tanks and fuel ducts. Based on the pitch and bank of the aircraft, one or more fuel pumps will indicate a "low pressure" warning. This is a dual channel indication, meaning that both lights must be on before a master caution situation occurs. On recall, a single low pressure light will be indicated in the master caution system. Fuel consumption in Flight Simulator is taken from the correct tank, based on the configuration of the fuel system.

4.4.4 Hydraulic system

Both system A and B, and the standby system are modelled. When no pressure is available, control of the aircraft is inhibited in flight simulator. Alternate flap extension is modelled and allows the flaps to be controlled through the overhead panel switches.

4.4.5 Heating system

Probe heats and window heat is modelled. The window temperature is calculated from outside air temperature and dynamic pressure on the window. This will also shut off the window heat power and trigger an overheat condition.

4.4.6 Fire detection

A complete fire detection system is modelled. Both engines have two detection loops, which can have faults. Faulty detection loops will not detect fires. The test switch on the fire panel can test the loops. Turning a fire handle will result in engine shutdown and will inhibit hydraulic low pressure lights.

The cargo fire system is also modelled with independent detection loops.

4.4.7 Master caution system

The master caution system contains twelve lights for indicating new situations on the overhead panel. Pushing the master caution button will reset the lights. The recall button will turn on all lights when pressed down and will show all active indications when released.

4.4.8 IRS system

The IRS system models two independent IRS systems.The units will be subject to drift in both speed/heading calculations and position calculations.

The IRS systems must be aligned prior to flight and use realistic alignment times, which can be bypassed through the instructor station.

Speed and Heading drift can be realigned in flight by turning the switches to "Align". This will start a 10 second quick alignment. Position drift can only be aligned on the ground and will take several minutes, depending on the latitude of the aircraft.

The ATT mode of the IRS systems are fully supported.

There is full support for the IRS keypad on the overhead panel. The FMS uses the IRS data as the main source of position data and when other sources are unavailable, map shift can occur.

4.5 Horizontal top navigation

4.5.1 File

Under the file menu there are two menu options: License Exit

4.5.2 Config

There are two ways of configuring individual switches and indicators in ProSim737 System:

  1. Manually configure hardware the switches and lights are connected to.
  2. Import a ready made configuration that was provided by a vendor.

To manually configure lights and switches, or to check the current configuration settings, open the configuration screen by selecting “Config” and then “Configuration”. Refer to the chapter “Connecting to hardware” in this manual for more information.

All configuration items are stored in a file called “config.xml” in the ProSim737 folder. Normally the ProSim737 configuration screen will be used to make changes, but the config.xml file may also be edited by hand. Also, the configuration file can be copied to a different computer to duplicate the settings. Import configuration

To import a ready made configuration, select “Import configuration” from the file menu. A dialog box will now appear asking for the configuration XML file to import. After selecting the appropriate file, a list of products will be presented that this configuration file supports. Select the products from which the configuration settings need to be imported and press OK. The settings will now be imported and saved to the main ProSim737 System configuration file. Connecting to hardware

Configuration of the IO Elements is done through the configuration window, which can be opened from the “Config” menu. In the configuration window, every type of IO Element has its own tab. There are some variations in configurations between IO Element types, but in general the name of the IO Element are displayed in the first column. The board to connect to is selected in the second column and finally the port or address on this board is set in the third column.

Before configuring any of the IO Elements, it is important to make sure that all the hardware options are checked in the “Drivers” tab that are intended to be used. ProSim737 will then know what to fill in the board selection dropdown menus.

Subsequently, configuration of the different IO Element types is explained. Finally, the different hardware boards and their options are also explained. Configuration Main Options

The correct Simulator Platform should be selected, “MSFS” for simulators based on Microsoft® Flight Simulator™ 10 and Lockheed Martin Prepar3D®, “XPlane” for Laminar Research X-Plane based simulators.

Startup situation
This option is used to define the aircraft switch positions on startup of ProSim737 System. It should only be used for switches for which no hardware is available since connected hardware switches always override the software state of switches. These selections can be made:

  • Cold & Dark - Switches are set as if the aircraft is parked.
  • APU ready - Ready running on APU.
  • Ready - Ready for take off.

Start minimized
This option defines the window state of ProSim737 System on startup. If enabled, the window of ProSim737 System starts minimized and out of sight, it is accessible through the ProSim737 System icon on the taskbar.

Debug mode
Do not use debug mode for normal operations. The debug mode is intended to run and analyse your system. This should be used only when instructed by the ProSim-AR team to debug your software.

Allow -1 as frequency for inactive radios
This checkbox allows ProSim737 System to transmit the special value of “-1” to each radio frequency output to indicate that the radio is switched off. This may be used in scripting to perform special actions. Webserver

The webserver is integrated in ProSim737 System and serves pages such as the IOS and Web CDU. By default the TCP port is set at 8080, the server port should only be changed when the default port is already in use on the Primary Computer. If the server TCP port has changed then it should also be changed in the web address entered on the client system. The address entered on the client should look like this: http://primarycomputeripaddress:8080/

AutoFailures per day
The auto failure option can be enabled by entering a numerical input higher than 0. Auto failure will trigger at random failures during your flight, when a failure occurs it can be seen and removed in the IOS. Logging and Updates

Extra informatie over status van hardware

ProSim737 contains an automatic update system that can help to keep the ProSim737 Suite up to date. The following options are available:

  1. Manual updates. ProSim737 System will never check for updates and the user will have to download a zip file manually and use the “Manual update” function to install the new version.
  2. Ask before updating. ProSim737 System will check for updates automatically but will ask for a confirmation before installing the new version
  3. Automatic updates. ProSim737 System will check for updates and install them automatically without asking. ACARS

Only the tail number can be selected in this page for the ACARS. All other information can be found in the readme.txt file in the ProSim737/ACARS directory and in paragraph 4.14 of this manual. Gauge smoothing

If your configured gauges do move but not smoothly, then manually change this value between 10 Hz to 100 Hz and investigate what value works best. The default value is 50 Hz. LED Intensities

This option is used to set the intensity of LEDs / indicators for both the low and high presets, currently only compatible with Phidgets 1032 LED 64 interface boards.

4.6 Drivers (IO Elements)

ProSim737 System has a width range off Drivers. Drivers are the communication between the hardware interface card and ProSim737 System. Instead of using a plain text xml format ProSim737 is using native supported hardware by using a Driver tab to configure the communication link between the hardware device and ProSim737 System. Depending hardware supplier it can be an connection with USB, Ethernet or a script.

In order to communicate with the outside world, ProSim737 System uses IO Elements. An IO Element is a part of the simulation system that is able to communicate its state to the outside world. There are various types of IO Elements in the system.

How to configure the specific hardware suppliers will be discussed in another chapter.

4.6.1 Configuring hardware

How to connect, configure and use most compatible hardware will be discussed in this chapter. A full compatible hardware list can be viewed at: http://prosim-ar.com/hardware/ CPFlight / FlyEngravity

CPFlight uses daisy chained cables to the MCP, Pedestal and MIP. All boards will be connected to each other, dependable on whether a CPFlight MCP is in use or not, ‘enable’ is an option to connect to the MCP. When this option is enabled, do not connect the COM port in ProSim737 System, connect to the COM port in ProSim737 MCP configuration. When there is no CPFlight MCP available, connect the MIP and Pedestal directly in ProSim737 System configuration driver page, and select the COM port.

CPFlight / FlyEngravity ICS overhead board.
The overhead board can only be selected in the ProSim737 System configuration driver page. Select the COM port and after a reboot of ProSim737 System the board will be configured.

Do not download separate CPFlight or Fly Engravity drivers. The boards will be natively supported without any additional drivers. Firmware updates will not be supported directly in ProSim737.

After connecting the hardware it’s advised to check the hardware connection. For check the connection use the ProSim737 Panel or the input debugger. (ProSim737 System > help > input debugger) When moving a hardware switch, and the ProSim737 Panel or the input debugger is running, the change of the switch is visible either in the ProSim737 Panel or the input debugger. Direct support for Joystick

ProSim737 System has support for all Joystick devices as long it’s recognized in windows as a Joystick input. Input and output may differ per device, and should always be calibrate first in windows. The joystick calibration can be found in Windows search “Game Controllers”. First step is to check if the Joystick is recognised in listed controller. Cockpit Sonic

Cockpit Sonic is using EHID driver to connect the hardware to ProSim737 System. To download the EHID driver, go to (http://www.uweschneider.de/en/downloads.php ) next to the EHID driver, the 737 XML configuration packages should also be installed. The EHID program should be included with a licence. This licence can be requested, see link; http://www.uweschneider.de/en/EHID_endusers.php

All modules except the TQ will automatically be configured after selecting the EHID server port. The EHID server port can be found in the driver setting off the EHID config file.

After connecting the hardware it’s advised to check the hardware connection. For check the connection use the ProSim737 Panel or the input debugger. (ProSim737 System > help > input debugger) When moving a hardware switch, and the ProSim737 Panel or the input debugger is running, the change of the switch is visible either in the ProSim737 Panel or the input debugger.

CockpitSonnic Throttle Quadrant should be configured in ProSim737 MCP.

Tuning EHID Gauges

EHID ID The following Gauges should be manually calibrated.

Apu EGT Brake pressure Cabin VSI Fuel temperature Outflow valve indicator Bleedair pressure left Cabin temperature Flaps Crew Oxygen

yield return new PortOption("Apu EGT", 0x10f81001, 0); yield return new PortOption("Brake pressure", 0x50b81001, 1); yield return new PortOption("Cabin VSI", 0x11081002, 2); yield return new PortOption("Cabin differential pressure", 0x11081001, 3); yield return new PortOption("Fuel temperature", 0x10d81001, 4); yield return new PortOption("Outflow valve indicator", 0x10181001, 5); yield return new PortOption("Bleedair pressure left", 0x10281001, 6); yield return new PortOption("Cabin temperature", 0x10381001, 7); yield return new PortOption("Flaps", 0x50a81001, 8); yield return new PortOption("Crew Oxygen", 0x20481001, 9); FDS / JetMax

All FDS hardware and JetMax Hardware is supported natively in the ProSim737 Suite. Pedestal, overhead and MIP can be configured in ProSim737 System. The FDS MCP should be configured in the ProSim737 MCP configuration page. JetMax MCP can only be configured in ProSim737 System configuration MCP/Throttle page. The FDS / JetMax should be configured in ProSim737 CDU configuration page.

All FDS / JetMax hardware is natively supported, therefore no additional driver, TekWorx drivers, is necessary to instal. Make sure to remove the TekWorx driver if it’s installed before continuing the ProSim737 configuration.

When enabling the FDS selector, the FDS-SYS I/O boards can be used. The specific switches and indicators should still be assigned in the ProSim737 System configuration page switches and indicators.

Pedestal radio elements should be assigned in the FDS advanced radio’s page. When this configuration page is open, the radio’s will give an identification number. Select the different COM port number as indicated in the hardware itself.

MCP/EFIS tuning
FDS has created multiple versions without changing the version name. Therefore, we have created a tuning page ( see below image) in the ProSim737 System driver page. This tuning page is only intended for changing rotary switch direction. If an incorrect direction of the notaries is noticed, manually tune this direction by selecting the appropriate rotary. Flight Illusion

Flight Illusion gauges in the overhead panel can be configured as normal gauges. Select “Flight Illusion” in the first column and the type of gauge in the second column, calibrate as usual.

Flight Illusion gauges are internally identified by an ID. Most overhead gauges and standby gauges come with the correct ID’s set. Some gauges however will have their default value of ‘255’ and need to be setup correctly before ProSim recognises them. The gauge ID’s can be changed with the Flight Illusion GStep software. Refer to the documentation of Flight Illusion for details.

NOTE: If ProSim is programmed to control the Flight Illusion Gauges, do not use the Flight Illusion GStep software.

Below are the assumed ID’s that ProSim uses for the Flight Illusion gauges.

Gauge Location ID
APU EGT Forward Overhead 180
Cabin Pressure Forward Overhead 182
Bleed Air Pressure Forward Overhead 183
Oxygen Pressure Aft Overhead 186
Fuel Temperature Forward Overhead 184
Cabin Temperature Forward Overhead 185
- - -
Standby Airspeed (with barberpole) Main Instrument Panel 100
Standby Altimeter Main Instrument Panel 101
Standby Airspeed Main Instrument Panel 102
Standby attitude (artificial horizon) Main Instrument Panel 103
Clock 1 Main Instrument Panel 104
Clock 2 Main Instrument Panel 204
Wet Compass Main Instrument Panel 105
Flaps Indicator Main Instrument Panel 106
Yaw damper Main Instrument Panel 107
Brake Pressure Main Instrument Panel 160
Standby Speed/Alt (GSA-SBI-P) Main Instrument Panel 254

Additional advanced button is used for the GSA-SBI-P standby Speed/Alt. When using the Speed/Alt combi the advanced button is used to select either altitude only or the speed and altitude combi. FSBUS

FSBUS will not be actively supported any further. GoFlight

GoFlight MCP/EFIS, GF-46 and GF-166 is natively supported. MCP/EFIS can only be configured in the ProSim737 MCP configuration page.

Enable the GoFlight selection in the ProSim737 System configuration driver,and restart ProSim737 System. After rebooting ProSim737 System, open the configuration screen, driver tab and select the GoFlight Advanced option. GF-46

When the GF-46 is powered (USB power would be enough) the GF-46 id unit will identify the units available. On the hardware site the device will show, on the left display, an indication “Unit” and on the right side an identification number. This is depending on the number that is used. First, select the specific unit, in this case “GF-46 unit 1” is selected, visible by the blue marker. The next step is to select the optional function on the lower right part of the screen. In this example Nav 1 and Nav 2 is selected. After selecting the prefered items select the ‘OK’ for the advanced selection and the ‘OK’ for the configuration screen. After this configuration the devices are available to use. The left switch is used for selecting the different function, and on the right the rotary encoder can be used for changing the frequency. GF-166

Configuring the GF-166 is almost the same as the GF-46. Select first the ProSim737 System configuration driver, reboot ProSim737 System, then select the advanced section in the ProSim737 System driver section. Select the unit and select the function of the device. In comparison with the GF-46, the GF-166 allows one single function. For example, only one NAV1 will be displayed. After selecting this function, click OK for the advanced section and again select OK on the configuration screen. IOCP

IOCP server is the connection to Open Cockpit (SIOC) and Sismo scPascal. More detailed information can be found on the specific supplier page 04.05.15 Sismo - scPascal and 04.05.18 OpenCockpits - SIOC Matrix Orbital display Phidget

Phidget cards usually have multiple input and/or output ports. Before a Phidget card can be configured, the accompanying drivers have to be installed and the card has to be plugged into the computer. When ProSim detects and lists the card in the “IO Modules” block in the main window, it is available for configuration. Select the board in the first column and select the output in the second column.

List of supported modules:

1012_2 - PhidgetInterfaceKit 0/16/16 1032_0 - PhidgetLED-64 1014_2 - PhidgetInterfaceKit 0/0/4 1065_0 - PhidgetMotorControl 1-Motor (not for TQ leavers except the trim wheel) 1066_1 - PhidgetAdvancedServo 1-Motor 1061_1 - PhidgetAdvancedServo 8-Motor 1203_2 - PhidgetTextLCD 20X2 : White : Integrated PhidgetInterfaceKit 8/8/8 Pokeys

PoKeys cards come in USB and Ethernet versions. Both versions are supported by ProSim737. Before you can configure a PoKeys card, it has to be plugged into the computer (for USB versions) or the network (for Ethernet versions). When ProSim lists the card in the “IO Modules” block in the main window, it is available for configuration. Select the board in the first column and select the input/output in the second column.

Because the connectors on PoKeys cards can serve as either an input or an output, the card needs to be configured. By default, ProSim737 will configure the card, based on the how it is used in ProSim737. If a port is assigned to an indicator, ProSim737 will configure the port to be an output. If the port is assigned to a switch, ProSim737 will configure the port to be an input. If for any reason, you want to override this configuration, you can disable the checkbox “Autoconfigure PoKeys cards” in the “Drivers” tab of the ProSim737 configuration screen. Poldragonet / FSC

Overhead and MIP is natively supported. FSC CDU should be configured in the ProSim737 CDU configuration page.

Connect the COM port. Select the MIP or the Overhead panel and restart ProSim737 System by selecting OK. The board automatically works without any other configuration, so all switches, indicators etc will be automatically configured. Check the switch functions with ProSim737 Panel (Overhead or MIP). For the MIP an advanced button is available for the Gear leaver. Depending on the version, the Gear lever can be wrongly connected, therefore, the advanced button can be used to change the direction of the Gear Leaver. SimIO

http://hispapanels.com/tienda/en/ Sim System SimWorld

Overhead, MIP, Gauges and MCP is supported. MIP, Gauges and MCP is connected with CAN bus technique. A power cable and a ‘connection’ cable will be connected to a “SimBox”. The SimBox will be connected to ProSim737 System in the configuration driver page. The IO modules will be connected automatically when the SimBox is assigned in the driver page. SimWorld Overhead will be connected on the same tab in the configuration driver page in ProSim737 System. The usb should be connected without any driver installed. To confirm correct behaviour, use the ProSim737 Panels to check the hardware switches and indicators. Sismo Soluciones

scPascal scripts are not supported anymore. Direct native support is available for the following

  • Master board and doughter boards:
    • SimCard Ethernet Motherboard SC-MB
    • Generic Interface Card (GIC)
    • SimCard 10 Analog Inputs
    • SimCard 14 Servos
    • SimCard 32 Displays
    • SimCard 64 Digital Inputs
    • SimCard 64 Digital Outputs
  • Not yet tested
    • SimCard Joystick USB 2.0
    • Solenoid Protection Board V2.6
    • Backlight Dimmer with Electronic Switch-Off Connection setup

The “Motherboard” is using Ethernet connection and using on default the IP address of, using a browser to type in Sismo config page should appear. Makes sure to use the same IP range to connect the hardware, more information is available via the Sismo website. To connect the Motherboard change the config page part “UDP Host IP”. In the “Host IP” type in the IP address of the main computer (See red box in images above). Save the board config.

MAC ADDRESS: xxx.xxx.xxx Hard coded
IP ADDRESS: Default IP address Motherboard, can be changed. Should always be in range of Main computer IP address.
HOST IP: xxx.xxx.x.xxx Main Computer IP address

Open ProSim737 System, open the configuration and select the driver tab. [ProSim737 System > config > configuration > driver > Sismo]. Select Sismo support, and accept the change by selecting ok. Automatically ProSim737 System will be rebooted. After the reboot you're ready to configure the different hardware elements. Switches

Motherboard - Daughterboard - input.

For configuring the switches use the ProSim737 “Auto configuration”. When toggling the hardware switch, automatically in ProSim737 configuration switch page, the moved switch is visible and ready to configure. [Open ProSim737 System > config > configuration > switches]

  • Step 1
    Toggle the required hardware switch.
  • Step 2
    When the switch is toggled, the auto configuration detect the Sismo board and number. All visible in the upper part of the configuration menu.
  • Step 3
    The last digit should always be 1. Do not configure the ‘0’.
  • Step 4
    Select “A”, automatically the board and input number is visible, and stored to the specific function. Indicators

A wizard is used to detect the correct output. Open ProSim737 System > config > configuration > Output. Search the output that you want to configure. Select “F” and automatically a wizard is opened. All indicators will be lighted, in 9 steps you should answer if the hardware indicator is lighted or not lighted. If all steps are answered the indicator will continuously flickering on to off. Select “Use” to configure the indicator. Analog input

Analog input can also be recognised automatically. When the hardware is connected, and moving the hardware analog (potentiometer), you can see the input detected. [ProSim737 System > config > configuration > Analog] Select “A” to configure the specific function for the analog input. The direction of the analog input can be changed by moving either clockwise or anticlockwise. In the auto configuration screen a indication shows if the analog input is configured as anticlockwise. 7 segment displays

Connect the Daughterboard to the mainboard, open ProSim737 System configuration dialog box. [ProSim737 System > config > configuration > Numerical] First search for the numerical output, for example the Radio freq Nav1 (see images below). Next step is to select the hardware Sismo ethernet device then assign the 5 digit for the Nav freq. assign the last digit. The ProSim737 system configuration will only allows assignments from left to right and will be assigned 5 digit at the same time. Gauges

Simcard 16 servo Daughter Board can be connect for servo outputs. To connect servo outputs in ProSim737 System select in the ProSim737 System configuration screen the “Gauges” tab. In the servo output board a number is listed, mapping the id in ProSim737.

4.6.2 Pololu

The Pololu 1393, motor controller, and 1352, servo controller, is supported in ProSim737 suite.

4.6.3 VRInsight

4.6.4 OpenCockpits - SIOC

SIOC is the OpenCockpits scripting language. It uses variables for communications. To use a SIOC variable within ProSim, select “IOCP” in the first column. Enter the number of the variable in the second column. Architecture

There are various panels, IOCards and other hardware available from OpenCockpits. This hardware is usually connected to the computer with a standard USB connector. All OpenCockpits hardware uses the OpenCockpits SIOC program to drive the hardware. ProSim737 in turn, talks with the SIOC program. Generic lights and switches are handled by ProSim737. The EFIS and MCP panels are handled by ProSim737 MCP and the CDU is handled by ProSim737 CDU. SIOC

The SIOC program can be downloaded from the OpenCockpits website. SIOC contains a scripted language which can be used to write SIOC scripts. A SIOC script is a script that tells SIOC what to do with the buttons, knobs and indicators of the connected hardware. SIOC scripts consist of numbered variables and optional codes. The numbered variables are the storage of SIOC and contain all the data that is transmitted between SIOC and its connected hardware.

Whenever a ProSim737 module communicates with SIOC, it does so by sending and receiving the contents of the numbered variables. In ProSim737 inputs and outputs can be assigned to variables by selection “IOCP” and entering a variable number. How to configure IOCards with ProSim737

Use the following steps to enable IOCards in ProSim737

  1. Download and install the SIOC program.
  2. Run the SIOC program
  3. Configure ProSim737 to connect to SIOC by opening the configuration screen. In the field for “IOCP Server”, enter the IP address and port of SIOC. This information is present in the SIOC window.
  4. Press OK.
  5. Assign the SIOC variables that ProSim737 should use for input and/or output. This is done in the configuration screen. In the first dropdown “IOCP” should be selected and in the textbox next to it, a variable number should be used. ProSim737 communicates with SIOC by using these variable numbers. What SIOC should do with these numbers is up to the SIOC script that is used. Any number may chosen, as long as it is unique.
  6. Create the SIOC script.To help in creating your SIOC script, ProSim737 is able to create a stub script. This script lists all the configured variables in ProSim737 with a standard SIOC line. These SIOC lines should be edited in a text editor to set the correct physical ports on the boards that should be used. The subscript is available from the ProSim737 instructor station. While ProSim737 is running, open a web browser and use the following URL: http://localhost:8080/sioc
  7. After the SIOC script has been edited with the correct port numbers, compile it with the SIOC program. To do this, press the CONFIG button in the main SIOC screen. Next, from the Compiler Menu, select “Files” and select the SIOC script that has been edited. The second line should be filled in with required output file. This file usually has an .ssi extension. Next, close the window and press the “Compiler” button.
  8. Configure SIOC to run the script. This can be done by editing the sioc.ini file.
  9. Restart SIOC to complete the process.

4.6.5 Using joystick cards and joysticks

Joystick cards can be used as inputs. “Direct input support for Joystick” should be selected. By rebooting ProSim737 System, the Joystick can be configured as switch or indicators depending version. Flight Controls should be configured in FSUIPC.

4.6.6 FSUIPC

FSUIPC offsets are available as input and output. In the first column, select the type of the offset to use. The second column has a different meaning for inputs and outputs.

ProSim supports three types of FSUIPC addresses:

  • Normal offsets: these are normal whole FSUIPC offsets.
  • Bit offsets: these are specific bits within an FSUIPC offsets.
  • Value offsets: these are specific values of an FSUIPC offsets.


  • Normal offset: the system will test if the offset is zero or nonzero. To use normal offsets, just enter the offset in hexadecimal (e.g. 0x5642).
  • Bit offsets: the system will test if a certain bit in the offset value is set. Enter the offset in hexadecimal, followed by a '.' and the bit number, starting from 0. For example, to test the fourth bit in offset 0x5642, enter "0x5642.3". The input is active when the bit is set.
  • Bit toggle: the system will test if a certain bit in the data is changed. Enter the offset in hexadecimal, followed by a '.' and the bit number, starting from 0 and add a ‘T’. For example, to test changes in the fourth bit in offset 0x5642, enter "0x5642.3T". The input is active for one second when the bit is changed.
  • Bit clear: the system will test if a certain bit in the data is set. After reading this bit, it resets this bit to 0. Enter the offset in hexadecimal, followed by a '.' and the bit number, starting from 0 and add a ‘C’. For example, to test changes in the fourth bit in offset 0x5642, enter "0x5642.3C". The input is active for a single read and the bit is reset by ProSim737 system after reading it.
  • Value offsets: the system will test if the offset contains a specific number. Enter the offset in hexadecimal, followed by a '=' and the value to test for. For example, to test if offset 0x5610 is 2, enter "0x5610 = 2".


  • Normal offsets: For lights, a "0" will be written for "off", a "1" for "normal brightness" and a "2" will be written for "bright". Gates write a “0” for “off” and a “1” for “on”.
  • Bit offsets: The indicated bit will be turned on or off, depending on the state of the output.
  • Value offsets: If the state of the output is on, the specified value is written to the offset. If it is off, “0” will be written.

4.6.7 Using the Generic driver

ProSim737 contains a “Generic” driver that communicates in clear text over a COM port or over a network through TCP port. It allows reading and writing states of switches and indicators quickly and efficiently. The generic driver is available in the “Drivers” tab of the configuration screen of ProSim737 as “Generic COM port/TCP driver”.

After enabling the driver, Switches, Indicators, Analog values and encoders can be configured to work with the driver. In the first drop down menu of the item, select either a COM port or “Generic driver TCP”. Next, use the text field next to the drop down box to enter a label for this IO Element. The name must be unique.

The generic driver has two selectable operation modes: It can use either generic element names, or you can configure each element that you are interested in individually.

Manually configuring elements After enabling the driver, Switches, Indicators, Analog values and encoders can be configured to work with driver. In the first drop down menu of the item, select either a COM port or “Generic driver TCP”. Next, use the text field next to the drop down box to enter a label for this IO Element. The name must be unique.

Using generic element names This mode is only available on the TCP generic driver. This operation mode allows you to communicate through the generic driver without configuring element names. The driver uses generic names, which can be found by using this URL: http://localhost:8080/xml?query=ids. This will show a list of all the available elements. As an example, this is the element S_MIP_FUELFLOW.

<id name="S_MIP_FUELFLOW" type="SWITCH" configName="Fuel flow">

The generic name for this switch is “S_MIP_FUELFLOW”. The value of the switch is one of the values that are in the <state> elements.

Communication with the driver is either through the configured COM port or through the TCP port. The driver listens on TCP port 8091 for incoming connections. The protocol is straight ASCII and consists of reports separated by the newline character. Each report is in this format:

<label> [‘=’ <value>]

Where <label> is the label that was configured in the configuration screen and <value> is the value of the item. If ‘=’ <value> is omitted, the value is assumed to be ‘1’.

Specific instructions per IO element type:

  • Switches: Configure each switch state. To change a switch, send the name of the switch state that is currently active.
  • Indicators: Indicators are reported with value ‘0’ for off, ‘1’ for on and ‘2’ for bright.
  • Gates: A ‘0’ is sent for off and a ‘1’ is sent for on.
  • Analog elements: Send the value of the element to change it.
  • Numerical Output: The output is reported with its current value.
  • Encoders: Send a ‘1’ for a clockwise rotation and a ‘-1’ for counterclockwise. Send this value each time the encoder is rotated.

4.7 Switches

Switches are the various buttons, toggle switches and selectors in the cockpit. Every switch has at least two states. The defined states are:

  • Push buttons: these have 2 states and can be “pushed” or “off”.
  • Toggle switch: these can have 2 or three states, on, off and a centre position.
  • Selectors: can have multiple states. ProSim will list all available states per switch.

It is important to understand that it is not necessary to configure all the states for a switch to make it operational. A push button for example, has only one wire and will connect to one port, but has two states. Only the connected wires need to be configured. For a normal push button, only the “pushed” state will be configured and the “off” state is left as “[Not connected]”. If a switch is controlled by hardware, one state may be left as “[Not connected]”. This state will be the button’s default state and will be active when no signal is received on the configured states.

4.7.1 Auto configuration system

The auto configuration system is a tool to speed up the configuration process.

  • Make sure the switches are wired to the interface card.
  • Make sure the relevant driver card support is selected. (see ???.??? IO Elements)

In the “switches” or “Analog Input” tab of the configuration screen, you will see a box “Auto configuration” at the top.

Every time you move a switch, push a button or move the potentiometer on a panel that supports automatic configuration, it will be reported in this box. Once you see your switch movement reported in the box, you may press the “A” button next to a switch position. The switch you just moved will then be configured automatically in that switch / potentiometer position.

For Open-Cockpit and Sismo Solution I/O cards, it’s not possible to use the auto-configuration.

4.7.2 Switches MCP/Throttle

All switches for the MCP, Throttle and Yoke can be configured on the “Switches MIP/Throttle” page.

4.8 Indicators

An indicator is usually a status light (so called annunciators) on a panel. Indicators can be in three states: Off, Normal and Bright mode. For hardware outputs that support fine brightness control such as the Phidget LED64 boards, indicators can be dimmed with the "light test" switch using the Dim/Bright setting, and can be tuned further with the sliders for individual colours in the configuration screen. Also, most indicators light up when the "light test" switch is placed in the "test" position.

4.8.1 Automatic configuration of indicators

Every indicator can have multiple outputs. Each of these outputs will be controlled by the indicator. To add extra addresses, press the “+” sign.

Next to each indicator in the “Indicators” tab of the configuration screen, you will see an “F” button. The “F” stands for “Find” and opens an automatic finding tool. The tool will turn on all ports on all connected hardware where an indicator may be connected and will locate a specific port by turning off some ports and asking questions about the state of the indicator. Once the port has been located, it will fill in the configuration for the port.

4.8.2 Indicators MCP/Throttle

Breakdown of the full indicator list. All indicators for MCP and Throttle can be selected in this page.

4.9 Gauges

A gauge is a value that is modulated to a number between 0 and 1024. The modulation can be nonlinear and can be fine tuned with sliders. The modulation of the input value allows connecting servos to a gauge IO Element.

4.10 Displays

Displays are small panels that include text information. There are two displays available: The Electric panel on the overhead panel, and the IRS display on the aft overhead panel. The large LCD screens in the cockpit are not configured here, they are handled by the separate ProSim Display program.

4.11 Gates

Gates communicate a state that is On or Off. An example of a gate is the “Overhead Backlight master”, which is ‘on’ when the backlighting should be on, or the stick shaker, which is ‘on,’ when the stick shaker should be active.

4.12 Numerical outputs

Numerical outputs are like gauges, but do not modulate the value. They simply output a number. They can be used to write to an FSUIPC offset or to the Open Cockpits system for further processing. Every gauge in the system, the APU EGT gauge, for example, has a respective numerical output that can be used when the unmodulated value of the gauge is needed.

4.13 Audio

Sounds are audio events that are generated by ProSim737. Sounds can be picked up by the optional ProSim737 Audio program to be played on external machines.

4.14 Analog inputs

Analog inputs are input values from 0 to 255 (Potentiometer). These are used for panel dimmers, display brightness control and other analog inputs, and can be read from joystick axes, FSUIPC or OpenCockpits SIOC.

4.15 Encoders

All encoders should be configured in this Encoders page. Auto configuration option is available, the same procedure as described on page ???.???

4.16 Levers

Levers for non-specific TQ’s should be configured in this page. Depending on the hardware, the position feedback loop can be assigned to the system (potentiometer) and the servo controlled motors. For General DC motors a Pololu 1393 motor control card should be used which is supported by ProSim737.

5 Setting up the navigation database for ProSim737

When the program runs for the first time, it is important to prepare the navigation database. To do this, open the configuration screen with the “Config” item from the “File” menu. Locate the “Database” block and press the “rebuild” button. The location of the Flight Simulator folder has to be entered. Usually, this folder is already pre-selected. Confirm the correct folder with the OK button. ProSim737 will now scan the scenery and extract the navigation database. This process will result in the file “startpositions.xml” being created in the ProSim737 folder. This file contains the extracted data and is loaded by ProSim737 every time it starts.

5.1 Navigation Database

Every aircraft needs a navigation database. In ProSim, the navigation database comes from two sources: In Prosim737 the navigation database is derived from two sources:

  1. Data is extracted from Flight Simulator scenery files. Airports, runways and gate positions are extracted from Flight Simulator, so they always match the currently installed scenery. This extraction can be run any time when the scenery has been updated.
  2. Routes and Terminal Procedures are read from a Navigraph database. This database can be updated to reflect real world navigation procedures. It must be purchased from the Navigraph website. The database can be updated by following the Navigraph procedures.

To see the current state of the installed navigation data, open the ProSim737 configuration screen and look for a block called “Database”. In this block there is also a “Rebuild” button. Pressing this button will scan the Flight Simulator directory and build the first part of the navigation database. The Flight Simulator database is created in a file called “startpositions.xml” in the ProSim737 directory. This file contains all data extracted from Flight Simulator.

If running the full cockpit suite is planned, a Navigraph database should also be installed. This database contains the extra navigation information that is not available in Flight Simulator.

To install the Navigraph database, go to the Navigraph website at http://www.navigraph.com/, and select the “FMS Data” tab. Download the navigation package labelled “Prosim737”. The package comes in the form of an executable that installs the required data. Run the installer on same the machine where Prosim737 is installed. A trial set can also be downloaded from our website; for this, see the downloads page.

To use up to date information, a Navigraph account has to be setup where the data-sets can be bought. For details check the Navigraph website on how to proceed with this.

All navigation data is distributed by the ProSim737 main program to all other ProSim modules requiring them. Therefore, only install and maintain the data on the machine running ProSim737.

When the database has been successfully configured, the database block in the configuration screen should show the picture below, meaning that it is using both Flight simulator data and Navigraph data.

6 Updates

6.1 Software updates

All ProSim737 software can be overwritten by newer versions without problems. Settings, databases and other local files are stored in .xml files and are therefore not part of the distribution. This ensures that they will not be overwritten when upgrading files to a new ProSim distribution.

To make backups of the settings, copy all .xml files from the directory of a ProSim module to a safe location. For more details see also the chapter on Support Files.

6.2 Manual software updates

To update ProSim software, simply copy the contents of the distribution zip file in the same folder as the previous release, overwriting the previous ProSim files. It is advisable to update the software of all modules at the same time.

6.3 Automatic software updates

ProSim contains an automatic update system that can help to keep the ProSim software up to date. The system is configured in the ProSim737 configuration screen. Here the “Logging and Updates” block can be found, from which the desired update mode can be selected. The following choices are available:

  1. Manual updates. ProSim737 will never check for updates and the user will have to download a zip file manually and use the “Manual update” function to install it.
  2. Ask before updating. ProSim737 will check for updates and notify you every time it starts.
  3. Automatic updates. ProSim737 will check for updates and install them automatically.

For normal use, the automatic update feature of ProSim737 is advised. This is enabled by default.

When ProSim detects an update, it will ask the user if updating is required. ProSim will download the new distribution and update its main program if ‘Yes’ is selected. After the main program has been updated, ProSim modules will update themselves to the new version the first time they connect the server.

To see the state of the updates, use the “Updates” function from the “Help” menu.

Here the current installed version and the latest available version can be seen.

There is also an option to manually install a release from a downloaded Zip file. This is practical if the simulator system is not connected to the internet.

7 Support files

Dedicated files are created by all ProSim modules. These files will be in the same folder as the program executed. Therefore, it is possible to move and copy a ProSim module by moving its folder.

Below is a list of files that can be encountered.

7.1 config.xml

All ProSim modules will store their configuration in a file called config.xml. This file contains all the selected options.

7.2 cockpitsetup.xml

ProSim737 stores the various cockpit configurations in this file. The configurations can be changed in the “Cockpit Setup” tab of the instructor station.

7.3 positions.xml

ProSim737 stores preset positions in this file. Preset positions can be stored in the “Setup” tab of the instructor station.

7.4 startpositions.xml

ProSim737 builds this file after scanning Flight Simulator scenery file. This file is a large XML file that contains all airports, runways and gates extracted from flight simulator. It is not advised to edit this file, since rebuilding the database from the configuration screen will overwrite this file.

7.5 translations.xml

ProSim737 stores position translations in this file. Translations can be configured in the “Setup” tab of the instructor station.

7.6 companyroutes.xml

ProSim737 stores all company routes in this file. Company routes are managed in the CoRoutes tab of the instructor station.

7.7 transitionaltitudes.xml

This file contains the transition altitudes for all global airports. It is only read by ProSim737 and distributed in the main package.

7.8 Log.txt

The log.txt file and log_x.txt files contain logging information about the running system. ProSim737 system rotates log.txt into log_1.txt when the file is full, so only the most recent logs are kept.

8 Interfacing with ProSim737

The ProSim737 main program has an internal web server that can be used to control some parts of the system. This can be used to develop add-ons or custom software.

The standard way to interface with ProSim737 is to call the XML gateway URL on the web server. This URL has the format: http://<host>:<port>/xml?query=<action>[&parameter=value]

As a reply to this call, an XML document in sent back in the following format:

<query>[A copy of the query]</query>
<success>[true or false depending on the outcome]</success>
The content of the answer

At the moment, the following queries are available:

fms Retrieve FMS data
aircraft Retrieve basic aircraft data
failures Retrieve a list of supported failures
armedFailures Interact with the failure system
load sheet Retrieve data to generate a load sheet

8.1 Query FMS

Supported parameters: None Retrieves the content of the route in the FMS. Specifications are not finalised.

8.2 Query Aircraft

Supported parameters: None Retrieves a list of basic parameters of the aircraft. Specifications are not finalised.

8.3 Query failures

Supported parameters: None

Retrieves all supported failures in the system. This list is a fixed list of what the instance of ProSim737 supports and need only be retrieved once. The answer contains a sequence of <failure> elements in this format: <failures>
<failure id="f1">
<help>The TransBus1 bus has failed</help>

The ID attribute is used to communicate with the system about this failure through the “armedFailures” query.

The name attribute can be used to display to the user. The domain attribute provides the means to classify failures. The help attribute is a short string that contains additional information about the failure.

8.4 Query armed failures

Supported parameters: failures, remove, ias, alt, altb, min

The armedFailures query is used to interact with the failure system. Armed failures are groups of failures that are either triggered immediately, or are triggered based on certain conditions. Each armed failures entry has an ID that can be used to remove it.

This query will always reply with the current list of armed failures. This list is a sequence of <armedFailure> elements in the following format:

<armedFailure id="0">


The <failures> element contains a comma separated list of failure ID’s that this entry will trigger. The <triggered> element is true when the failures were triggered and false when the armedFailure is still waiting for a condition to become true. The <condition> element will typically be empty, or contain a single condition, but all possible conditions are shown for reference.

To set a new armed failure, the “failures” parameter must be present and should contain a list of failure ID’s, separated by commas. Optionally, the ias, alt, altb, or min parameters may be provided to make the armed failure a condition based failure. When no condition is provided, the failure will be triggered immediately.

  • ias is the speed in KTS above which the failures should trigger
  • alt is the altitude above which the failures should trigger
  • altb is the altitude below which the failures should trigger
  • min is the amount of minutes that should pass before the failure should trigger

To remove a failure, the parameter “remove=<id>” should be used. When an armedFailure is removed, the systems involved will be repaired.

Here are some example URL’s:

8.5 Query ground power

Supported parameters: active

This query is used to read or set the state of the ground power. The query always returns the current state of the ground power in the following format: <groundPower active="true|false"/> To set the ground power, the “active” parameter can be used. The value of this parameter should be “true” or “false”. Please note that ground power will only be provided under the condition that the aircraft is not moving and on the ground.

8.6 Query load sheet

Supported parameters: none

This query is used to retrieve information from the FMS which can be used to create a load sheet. An active PERF INIT page and an active route must be present in the FMS for the query to succeed. A block of XML is returned with all information necessary to build a load sheet.

One way to build a load sheet is to run the XML through an XSLT, which outputs the load sheet. An example XSLT “loadsheet.xslt” is provided in the web folder of ProSim737.

The instructor station url http://localhost:8080/loadsheet uses this XSLT to build a load sheet from this XML query. It uses this XML query and adds an XML processing instruction for the browser to use the XSLT for rendering the XML.

This is an example URL:

8.7 Query acars

Supported parameters: message, content, type

This query is used to uplink or downlink an ACARS message. In both uplink or downlink mode, the “message” parameter is required and should be the ID of the message, as defined in the currently active ACARS profile.

8.7.1 ACARS uplink

In this mode, a message can be uplinked from the ground to the aircraft. In this mode, the “content” parameter is required and contains the actual content of the uplinked message.

8.7.2 ACARS downlink

In this mode, the aircraft is told to downlink a message to the ground station. To activate the downlink mode, specify the attribute “type=downlink”. This mode can be used to trigger the aircraft to send automated status messages. Since the message content is constructed from the definition in the active ACARS profile, no “content” parameter is needed.



9.1 ACARS general description

ACARS configurations are split into profiles. A profile is a set of CDU pages, message layouts and a list of automatically generated messages that are loaded into the FMS. The user is able to configure the active ACARS profile in the Prosim737 configuration screen. An ACARS profile is created with an <acars/> eleme

9.2 ACARS Variables

A number of read-only variables are available to use. These are:

fms.origin Route origin
fms.destination Route destination
fms.flightno Route flight number
fms.tailnumber Tailnumber
fms.flightphase Flight phase (GRND/CLB/CRZ/DES)
fms.heading Magnetic heading
fms.wind Current wind in HHH/SS format
fms.ref_airport Reference airport entered in POS INIT page
progress.from.waypoint Progress from field
progress.from.ata Progress ATA field
progress.next.waypoint Next LNAV waypoint
progress.next.eta Next LNAV waypoint ETA
progress.next2.waypoint Second Next LNAV waypoint
progress.next2.eta Second Next LNAV waypoint ETA
progress.dest.eta Destination ETA
airdata.ias Current IAS
airdata.gs Current ground speed
airdata.altitude Current altitude
airdata.fuel Current fuel (kg)
airdata.mach Current Mach
airdata.oat Current OAT
position.lat Latitude of aircraft
position.lon Longitude of aircraft
radio.com1 COM1 frequency
radio.com2 COM2 frequency
radio.nav1 NAV1 frequency
radio.nav2 NAV2 frequency
radio.adf1 ADF1 frequency
radio.adf2 ADF2 frequency
radio.xpdr Transponder frequency


The <acars> element defines an acars profile. Attributes:

  • name (Optional)
    • The name of the profile. Only profiles with a name show up in the "Profile" selection of the ACARS configuration.
  • id (Optional)
    • The ID of the profile. Profiles with an ID can be included in other profiles by using an <include> element.
  • default (Optional)
    • "true" or "false". When "true", this profile will be the default when the user selects no other profile.


  • title
    • Title shown in CDU
  • pagenumbers (Optional)
    • attribute that controls the usage of page numbers in the top right corner. Set to "auto" to show page numbers when more than one page exists. Set to "true" to force page numbers, even when only one page exists. Default is "auto".
  • titlealign
    • Allows control over title aligment. Default = "left". Other option is "center".
  • subsystem
    • When this attribute is present, the page is an upper level menu that is accessible from the cdu main menu. The value of the attribute is the name that is shown in the CDU menu.
  • id
    • D of page used to link to it. When id's are repeated, the last matching page in the document is used ID's starting with an underscore ("_") are special and result in a specific page like described below:
      • id = "_uplinks": Generate a list of ACARS uplinks
      • id = "_genericUplink": Used as a template for showing ACARS uplinks with no associated page (raw message page)
  • uplink
    • Defines the page as an uplink page, which is used to show ACARS uplinks. The uplink attribute defines the message id that this page receives.
  • subpages
    • Optional attribute that controls how subpages are created. If this is set to "auto", the page will be repeated to fit the content of the message. If this attribute is left out, then <subpage> elements can be used to create extra pages.

A <page> element may contain extra <subpage> elements to create multiple pages. This is optional.


An <lsk..> element defines a line select key. Various types are available:

  • Link elements
    • Link elements link to a CDU page. Specify a link="<target>" attribute. The LSK will link to the page with id=<target>. Optionally, specify set="<variable>=<value>", to change a variable when following the link.
  • Error elements
    • Will proceed to an error message in the scratchpad. Specify an error="<message>" attribute. The LSK will trigger the error in the scratchpad.
  • Send elements
    • Send elements will send an ACARS message. Specify send="<message id>" to set the message id. The message with id=<message> will be sent.
  • Input elements
    • Input elements allow the user to set variables.
    • Specify input="<variable>" to set the target variable of the input.
    • For free form text inputs:
      • Specify size=<size> to set the amount of characters allowed for the input. This will place brackets on the line.
    • A default can be set with the default="" variable. Default attributes may refer to other variables.
    • For choosing between options:
    • Specify selection="<selection1>,<selection2>,..." to set the allowed options. The CDU will show all options with the select one in green. Pushing the LSK will change the selection.
    • For dropdown options:
      • Specify selection="<selection1>,<selection2>,..." to set the allowed options.
    • Add type="dropdown", to make the LSK a dropdown box.
  • Output elements:
    • Output elements show the content of variables. Specify output="<variable>" to show the content of the variable.
    • To span the content across the regular line and the header line, add a lines="2" attribute.

The optional header="<header>" attribute can be used to set the header of the LSK The optional centerHeader="<header>" attribute can be used to set a center aligned header surrounded with dashes on the whole line of the LSK The optional attribute delimiter="<char>" can be used to override the "<", ">" or "*" delimiter at the edge of the display


Conditional LSK's: Use an <if/> block to surround conditional LSK's:

<if variable="<variable>" equals="<value>"></if> OR <if variable="<variable>" notEquals="<value>"></if>


Monitor is used to monitor events and trigger actions. It contains these attributes:

  • action
    • The action to take when an event is triggered. Currently only 'CDUMessage' is available. With CDUMessage, the content of the MONITOR element contains the message to trigger.
  • trigger
    • The trigger value.
  • fsuipc
    • An FSUIPC offset to test. If the offfset has the value in the "trigger" attribute, the event is triggered.
  • fsuipcType
    • The FSUIPC offset data type. Any of "u8", "u16", "s16", "u32", "s32", "f32", "f64"

Example: <monitor fsuipc="0xbc8" fsuipcType="u16" trigger="32767" action="CDUMessage">Parking brake is on</monitor>


A <message> element defines an ACARS message. Attributes:

  • id
    • The ID of the message used to refer to it.
  • code
    • The ACARS code that is used in the ACARS message to identify this message.
  • description
    • The description of this message, used in ACARS programs.
  • title
    • The link displayed in the CDU on LSK6R when an uplink is received.
  • type
    • Optional, default is "acars". Can be "acars" for regular ACARS server processing or "http" for a http request.
  • response
    • For http requests, this contains the message id of the message that will handle the output of the http request.
  • inactiveAdvisory
    • The advisory message in LSK5 that is displayed when this message is being transmitted.
  • chime
    • Optional, when set to "true" a chime sound is played when an uplink of this message arrives
  • EICASAdvisory
    • The advisory message displayed on the upper EICAS when a message of this type arrives.
  • CDUadvisory
    • The advisory message displayed in the CDU scratchpad when a message of this type arrives.

Message elements contain <field> elements that describe the fields inside the message. Attributes of <field> elements are:

  • id
    • The ID of the element. The ID is the variable name the contains the content for this field.
  • size
    • The amount of characters in this field. All but the last field should contain a size attribute.
  • description
    • The description of this field, used in ACARS programs.
  • trim
    • When set to "true", the data that is received will be trimmed to remove all leading and trailing white spaces.

HTTP requests need an <url> element which contains the URL to call

HTTP requests:

To read/write HTTP, you create a new <message> element with type="http". The output from a HTTP request can be used to either trigger an incoming message, or it can placed in variables without triggering a message. The former case uses a "response" attribute to point towards the message describing the output of the HTTP request. The latter case uses a <response> element inside the <message> element to directly describe the fields in the output. The <url> element is used to build the URL. You can use the ${<variable>} format to include the content of variables that were filled in on the page. If the http request is successful and it has output, the associated response message is used to process it. Once the output of the HTTP request has been defined in a <message>, the <message> can be used to display the content on a custom page or the default uplink page.

Here is an example of two messages for processing IVAO weather. It uses a response message to parse the response:

<message title="weather" id="ivaoMetarResponse">
<field id="metar response content"/>
<message id="ivaoMetar" response="ivaoMetarResponse" type="http">

Here is an example of the same weather request, but instead it stores the output directly into a variable: <message id="ivaoMetar" type="http">
<field id="metar response content"/>

10 ProSim737 Display

10.1 General description

The ProSim737 Display module indicates functioning images on the Display Units in the cockpit. These sizeable images can be configured according to the preferred layout by drag and drop within minutes. Not only does the ProSim737 Display module support all cockpit displays, it also contains a number of realistic photographic standby instruments. Network communication makes it possible to run the module outside of the cockpit environment at any location that can access the ProSim737 System module.

10.2 Configure ProSim Display

ProSim737 Display gives access to all the different displays in ProSim737, for example, Primary Flight Display, Navigation Displays and others. Some aircraft have up to six LCD displays. Simulation cockpits often use common computer LCD’s placed behind the main instrument panel to simulate these displays.

The ProSim737 Display module can be configured to show any kind of display or other graphical element in any location and size. An unlimited amount of ProSim737 Display modules can be run on various computers. It can even be used outside of the cockpit to see what the pilots are observing.

10.2.1 Installation

If not already done, unpack from main destribution zip, the software archive Prosimdisplay.zip to a directory and copy the contents of this directory to any computer that needs to run a display. No additional files are needed. All information, including the navigation database, is loaded from the ProSim737 main program. ProSim737 Display does not require FSUIPC of WideFS to run.

Multiple ProSim737 Displays can be used in one computer. The executable name should not be changed, so the default executable is ProsimDisplay.exe. This executable will be update when there is a new ProSim737 suite release update, therefore the name can’t be changed. The folder name can be changed depending on own preference.

Default folder structure when first installed: ….\ProSim737 Display\ProsimDisplay.exe

For multiple ProSim737 Displays on one computer create then multiple ProSim737 Display folders for example: ….\ProSim737 Display Captain\ProsimDisplay.exe ….\ProSim737 Display Display FO\ProsimDisplay.exe ….\ProSim737 Display Upper EICAS\ProsimDisplay.exe ….\ProSim737 Display Lower EICAS\ProsimDisplay.exe

10.2.2 Configuration

Before ProSim Display can show any information, it has to be connected to the ProSim737 System. To do this, run ProSim737 Display and right click anywhere in the window and select “Configuration”. The following screen is presented:

In the configuration window, enter the IP address of the machine running ProSim737.

To check if the program is successfully connected, right click somewhere in the window and check the status label. If it is green, the connection is successful. If the label is red, then there is a connection issue.

ProSim737 Display connected to ProSim737

10.2.3 Setting up displays

ProSim737 Display can show multiple screens in its window. Usually, one ProSim737 Display program will be run per physical monitor connected to the computer. Make sure to use one ProSim737 Display per (LCD/TFT) Display. So when connecting 3 physical displays create 3 ProSim737 Displays with the correct folder name. Enabling multiple screens and placing them at correct positions is an easy task. When the program exits, the position and layout of all screens are stored and will be the same when the program starts next time.

When the program starts for the first time, the captain’s PFD and ND are visible. To change the screens that are visible, right click in the window and select the screens required under the “Displays” menu. To manipulate the size and location of a screen, first select ‘Display Setup mode’. The screen background change to blue. Do this by clicking on the screen, or pressing TAB until there is a green border around the screen. See below for an example.

Now the screen can be moved or resized by dragging the mouse and using the scroll wheel of the mouse to resize. For fine tuning, the keys in the following table can be used. Display image examples can be found on display page examples

10.2.4 ProSim Display Control Keys

Key(s) Action
Cursor keys Move the screen
Shift + Cursor keys Quickly move the screen
Numpad +/- Adjust size of screen
Shift + Numpad +/- Quickly adjust size of screen
[ / ] (bracket keys) Adjust only the width of the screen
Shift + [ / ] (bracket keys) Quickly adjust only the width of the screen
* Reset Height/Width of screen to Square
TAB Select next screen

10.2.5 ProSim Display Mouse Control

Mouse Action
Left click on screen Select screen (green circle indicates)
Right click on screen Select screen and pop-up configuration menu
Press left mouse button and move Move the screen
Roll scroll wheel Adjust size of screen

10.2.6 Displays image examples

10.3 Static Displays

Static Displays should be used outside the cockpit for monitoring during a flight. Do not use static displays for the actual cockpit displays. These static displays will not react with the ProSim737 System switches or power logic.

10.3.1 Sys Display and Secondary Engines Indicators

10.3.2 Captain and F/O PFD and ND

10.3.3 Captain and F/O Inboard and Outboard EFIS

10.3.4 Normal EICAS and EFIS EICAS

10.4 Standby Displays

The Standby Displays can be blended in the actual cockpit display panels together with the PFD, ND or ECAS. Configuring the standby displays are the same as the described method on 05.02.03. The following standby displays are available.

10.4.1 ISIS / ESAI / ISFD

Electronic Standby Attitude Indicator (ESAI)

Integrated Standby Flight Display (ISFD) The switch function is supported in ProSim737 System.

10.4.2 Alt/Speed / RMI

10.4.3 Standby Attitude / Flaps

10.4.4 Brake Pressure / Wet Compass

10.4.5 Yaw Damper

11 ProSim737 MCP

11.1 General description

The ProSim737 MCP (Mode Control Panel) module contains the autoflight logic of the aircraft. The main purpose of this module is to calculate steering commands inputted by the MCP panel and Flight Instrumentation System (EFIS) panels in the cockpit. The steering commands are either fed directly to the aircraft (autopilot system) or sent as guidance information to the pilots through the Flight Director cues on the Primary Flight Displays. A graphical representation of these panels is shown on the screen that is fully functional and controlled by mouse. Many inclusive drivers communicate directly with the MCP hardware, in addition, the module also contains drivers to control throttle quadrants by most manufacturers which in turn, allows realistic autothrottle movement.

11.2 Installing ProSim737 MCP

The ProSim737 MCP module contains the autopilot functions. Its primary control is the Mode Control Panel (MCP). The module also controls two Electronic Flight Instrumentation System (EFIS) panels and the throttle quadrant. In combination with data received from the ProSim737 main module, the ProSim MCP module sends steering commands to Flight Simulator to fly the aircraft when the autopilot is turned on. It will also relay information about the state of the autopilot and flight directors to the ProSim737 main module, so it can be distributed to the displays.

11.2.1 Installation

Installation is straightforward. If not already done, unpack the software archive ProSimMCP.zip to a directory and copy the contents of this directory to any computer that needs to run ProSim MCP. No additional files are needed. All information, including the navigation database, is loaded from the ProSim737 main program.

When ProSim MCP is used in the cockpit, there should be one ProSim MCP program running in this cockpit, preferably on the same computer that runs Flight Simulator. ProSim MCP requires FSUIPC to access Flight Simulator. If ProSim MCP needs to run on a different computer than your main Flight Simulator computer, WideFS is needed. However, this is not a recommended setup.

11.2.2 Configuration

Before ProSim737 MCP can be used, it has to be configured. To do this, right click anywhere in the window and select “Configuration”. Here the IP address of the ProSim737 server is set. Usually this is, if the ProSim737 program is run on the same machine.

To check if the program is successfully connected, right click somewhere in the window and check the status label. If it is green, the connection is successful. If the label is red, then there is a connection issue.

Next, if a hardware MCP panel is used, it needs to configured also. Several MCP types are supported by the software. There are a number of boxes in the configuration screen, each for a specific hardware setup.

The boxes are labelled:

  • “For CP Flight MCP’s”
  • “For FDS MCP/EFIS”
  • “For GoFlight MCP/EFIS”
  • “For OpenCockpits MCP’s and throttle”,
  • “For Sismo Soluciones MCP’s”
  • “For other MCP’s”

Select the box that best suits the actual situation and fill in the items. Leave the other boxes empty. Make sure “Control via FSUIPC” and “Control via ProSim737 configuration” are not enabled if these are not specifically needed.

11.2.3 Tuning

By default the autopilot is tuned to fly correct for most aircraft models. If it is found that the aircraft is rolling left and right slowly it may require some firmer aileron control. This can be set in the “tuning” tab of the configuration screen. The Aileron tuning value shown is in percentage. The default value is 100. Increase to 150 to have firmer control. Keep increasing the value until the aircraft flies correctly.

11.2.4 About the autopilot

The ProSim MCP autopilot is an advanced simulation of a real Autopilot Flight Director System (AFDS). The autopilot has been written from scratch without using any components from Flight simulator. Because of this, it is important that no other autopilot systems are active when ProSim MCP is used.

Some knowledge of this system is required to use the panel to its full potential. Below are some hints on using the autopilot:

  • CMD and CWS mode can only be engaged above 400 feet radio altitude.
  • CMD mode does not know or understand anything about currently active flight modes. Its only job is to fly the aircraft towards the flight director cues.
  • LNAV can be engaged when the Perf Init CDU page has active data (ACT PERF INIT shows as the menu title) and there is an active route (ACT RTE shows on the route page).
  • LNAV can be armed on the ground and will become active at 200 feet radio altitude.
  • Do not look at the lights on the MCP to determine what mode is active. Always look at the FMA display at the top of the PFD for this. The lights on the MCP indicate modes that can be switched off. Active modes that cannot be switched off indicate this by turning off their light on the MCP.
  • VOR/LOC mode uses the NAV1 radio when FCC1 is master (yellow MA light on the left side of the panel). It uses the NAV2 radio when FCC2 is master (yellow MA light on the right side of the panel). When a glideslope capture occurs, both FCC’s will become master and this may cause Flight Director cues to disappear on the side that has not tuned the active ILS frequency.
  • All FMA modes are switched off when there is no master FCC. This occurs when there is no active autopilot and both flight directors are switched off.

11.2.5 CWS mode

CWS mode, or Control Wheel Steering, is a lower operations mode of the autopilot that is used to hold a certain bank or pitch. In the real aircraft, during CWS operations, bank or pitch can be set by applying force to the yoke. When the force is released, the aircraft holds the current pitch or bank. CWS can be active in the pitch axis, the roll axis, or both. The FMA displays the words “CWS P” when CWS is active in the pitch axis and “CWS R” when CWS is active in the roll axis.

CWS can become active in two situations:

  1. CWS mode has been selected on the MCP panel. Both axes will revert to CWS operations.
  2. CMD mode is active on the MCP, but one or both axes do not have an active flight mode. CWS will be active on the axis that has no active flight mode. This happens for example, when flying in HDG SEL mode the HDG SEL button is pressed to disengage the mode.

Because of limitation in the current flight simulator hardware, there is no way to detect pressure on the yoke. ProSim therefore simulates CWS by looking at the position of the yoke. When the yoke is in the centered position, CWS assumes no force is applied and will take over the axis. When the yoke is moved from its centered position, CWS will allow new pitch or bank to be selected. It is therefore important that when the yoke is released, its output is near the (0,0) position. Make sure the yoke is correctly calibrated and when it feels CWS mode is not keeping the aircraft on it current pitch or bank, check the calibration settings.

With a little practice it is quickly found that it is easy to fly CWS in ProSim737. Simply apply little input to the yoke to bring the aircraft to a new bank and/or pitch and release the yoke. Play with this, as it provides interesting ways to fly, especially in bad weather conditions.

11.2.6 Using hardware MCP’s

For details on connecting hardware MCP’s to ProSim MCP see the MCP hardware paragraph.

11.3 Connecting MCP hardware to ProSim MCP

Several hardware MCP/EFIS’s are supported by ProSim. For a list with supported MCP’s refer to the supported hardware list. Thereafter the installation of supported MCP hardware is explained in detail.

11.3.1 Using CPFlight MCP’s and EFIS panels

CPFlight MCP’s usually connect to the computer with a USB cable. Older versions may use a serial cable. In both cases, a COM port (either real or virtual) is used to communicate with the panel. The COM port that is used to connect to CPFlight MCP to is required. Select this COM port in the drop down menu to enable the MCP.

CPFlight EFIS panels are daisy-chained to the MCP and will be automatically detected by ProSimMCP without further configuration. Using CPFlight hardware other than the CPFlight MCP/EFIS

CPFlight hardware is connected to each other with black CPFlight link cables. One of the devices serves as the host and is connected to the computer. This is usually the CPFlight MCP device, but CPFlight also sells panels that have a direct connection to the computer. These panels can be used if no CPFlight MCP is installed.

It is important to check what CPFlight device connects to your computer. This can be either the CPFlight MCP, or some other CPFlight device. Then, choose one of the following:

  1. CPFlight hardware is connected through the CPFlight MCP. Configure ProSim737 MCP with the correct COM port. Open the “drivers” tab in the ProSim737 configuration screen and select “CPFlight boards through MCP”
  2. CPFlight hardware is connected though some panels other than the CPFlight MCP. Only configure ProSim737. Open the “drivers” tab in the configuration screen and select the correct COM port in the line “CPFlight boards direct connection”

All CPFlight panels and boards have specifically labelled switches, buttons and connectors. Because of this, it is not needed to further specify what switches and indicators should be connected and where in the ProSim737 configuration screens. To use CPFlight boards, only the steps mentioned above need to be performed and leave all switches and indicators that the boards should control to “[Not connected]”. ProSim737 will automatically control the correct switches when they are received from the CPFlight hardware.

11.3.2 Simworld MCP

Simworld is using a CAN bus. Therefore it’s not necessary to select the MCP in ProSim737 MCP. There is a Driver selector available in ProSIm737 System > Configuration > config > drivers. After selecting Simworld driver support automatically when starting ProSim737 MCP the hardware will work.

11.3.3 GoFlight MCP

GoFlight MCP should be selected in ProSim737 MCP configuration. Select GoFlight MCP and reboot ProSim737 MCP.

11.3.4 FDS MCP

FDS MCP module will be selected in ProSim737 System and in ProSim737 MCP. Select in ProSim737 System > Configuration > Config > Drivers the FDS support selector. Then depending verion 2 or version 3 select the COM port (v2) or select v3. Reboot ProSim737 MCP, ProSim737 System is rebooting automatically when selecting the support selector. Make sure not to install secondary drivers for this MCP. All is native supported, so no driver is necessary to install. If you already install a FDS driver make sure to remove this driver before connecting the MCP to ProSim737 System or ProSim737 MCP.

11.4 Connecting Throttle Quadrant

11.4.1 Throttle Quadrant

Two direct supported Throttle Quadrants are possible to connect in ProSim737 MCP. General non specific TQ’s can be supported in ProSim737 System > Config > Configuration > Levers.

11.4.2 Using CockpitSonic throttle

To use the cockpit sonic throttle, the EHID driver is required, which can be downloaded from the website of Uwe Schneider: http://www.uweschneider.de/Download.php?lang=en

Download and install the B737_EHID driver. A licence needs to be inserted. At the moment of this writing, these licences can be obtained for free from Uwe Schneider.

After EHID has been installed and the service is running, ProSim MCP can be configured to connect to EHID and work with the throttle. To achieve this, open the ProSim MCP configuration screen and click on the “CockpitSonic” tab. Here an input box “EHID Service” is shown. When you are running ProSim MCP at the same computer as the EHID driver, type “localhost”. The port is automatically filled in. Press “Connect”. When successful, the connect button shows “Connected”. If an error message appears, the EHID driver is not yet running, or the “EHID Service” field is not correctly set up.

If the connection is successful, you will need to calibrate the various levers and servos. Each axis has a grey line that shows the current axis position in red. Each servo has a slider below the axis. Calibrating throttles

Below the throttles, you will see two sliders. These sliders move the servo motors of the throttle handles. To calibrate the throttle levers, first move the sliders so that the throttle handles are both at idle. Find the position in which both levers are equal and are at the lowest possible position, without the servo’s making any humming sound. Now press “Set Idle”.

Repeat this process for full thrust. Find the position where both levers are equal and at the highest position without the servo’s making noise. Now press “Set full thrust”. Reversers

Move the reversers fully down and press “Set Min” Move the reversers fully up and press “Set Max” Flaps

Move the flap handle to each position and press the associated button to mark the location. Spoiler

As with the throttle, don’t move the spoiler handle by hand. Only move it with the servo slider. Move the slider so the spoiler handle goes to each of the three positions and press the associated button. Trim indicator

Move the slider to position the trim indicator to the 0 and the 15 position and press the associated button.

The image below shows the configuration screen with the servo sliders marked in red circles.

11.4.3 Using FSC throttle

Before continuing:

  • Make sure no FSC drivers are installed, in case you do have them installed please uninstall them.
  • The throttle connects to the ProSim737 MCP module, make sure ProSim737 System and ProSim737 MCP run on the same computer and the throttle is wired to this computer. Step by step procedure
  1. Connect the cables.
    • Connect the power cable to the throttle; it has no power switch so it will always be on.
    • Connect throttles USB cable to the same computer where ProSim737 system and ProSim737 MCP run on.
  2. Open ProSim737 System and leave it running through all further steps.
  3. Connect a COM port to the throttle.
    • Open ProSim737 MCP.
    • Open the configuration screen (right mouse click --> click “config”)
    • Select the “FSC” tab.
    • Open the pull down menu displayed right to “FSC throttle COM port”, by default it shows “not installed”, please select your COM port.
    • in case your throttle is motorised, please check the “motorised throttle” checkbox.
    • Close configuration screen by clicking ok.
  4. Check the connections.
    • Open ProSim737 MCP.
    • Check the connection status (right mouse click --> “status”).
      • Two green indications should be visible:
        • Server connection
        • Hardware connection
  5. Calibrate the throttle.
    • Open the configuration screen (right mouse click --> click “config”).
    • Select FSC tab
    • Start calibration by setting the sliders.
      1. Check Throttle slider by moving the throttle to idle, full and back to idle.
      2. Select idle “set idle” (make sure you have not moved the throttle after the previous step).
      3. Move the throttle to full position and select “set full”.
    • Calibrate all sliders in same way as the throttle.
    • Close the configuration screen by clicking ok. Remarks
  • The TOGA and AT disengage switches may be wired serially, if this is the case you should push both of the switches at the same time to use them.
  • Keep the selected COM port reserved for your throttle.
  • In case you connect your throttle to another USB port on the same computer you need to again select a COM port.
  • This step by step guide has been created based on a FSC throttle with type notification 737_TQ_AT_M and serial number 97417-P.
  • FSC throttle compatibility is implemented as of ProSim737 Suite version 1.27.

11.4.4 Using OpenCockpits MCP's and throttle

Opencockpits MCP's use the OpenCockpits SIOC software to communicate with the computer. This software can be downloaded from the OpenCockpits website. The SIOC program needs to be configured with a script that it runs on. This script tells SIOC how to handle all buttons, lights and displays. It will also tell SIOC what variables should contain the panel’s information so ProSim737 MCP can access it.

In order to connect the ProSim737 MCP to an OpenCockpits panel, some ready-to-use SIOC scripts are provided. A number of SIOC scripts can be found in the “Opencockpits” folder in the ProSim737 MCP main folder.

prosim_mcp This script contains support for the OpenCockpits MCP, EFIS and CDU hardware
prosim_throttle This script contains support for the OpenCockpits throttle unit
prosim_mcp_throttle This script includes both of the above scripts

Select the appropriate script for the actual situation. If specific SIOC code needs to be executed for additional functions, the ProSim script needs to be embedded into this script. If this SIOC script is not used for anything else, simply use the provided script. Once SIOC has been configured and recognises the MCP panel, only connection ProSim737 MCP to SIOC by providing the IP address and port of your SIOC program. This is usually port 8092.

Here are the steps again in sequential order:

  1. Optionally download and install SIOC if this has not been done yet.
  2. Copy the prosim_mcp.txt, prosim_throttle.txt or prosim_mcp_throttle.txt SIOC script to the SIOC folder, or embed the script into an own script.
  3. Configure SIOC by editing sioc.ini to run the script and list the MCP panel. Do this by editing sioc.ini and looking for these lines: [ Configuration File ] CONFIG_FILE= <place filename here>
  4. Restart SIOC so it is running the script.
  5. Open the ProSim737 MCP configuration window.
  6. In the OpenCockpits block, enter the IP address and port of SIOC (usually 8092)
  7. Check the box MCP/EFIS if an OpenCockpits MCP is available. Check the box Throttle if an #OpenCockpits throttle is available.
  8. Press OK and restart ProSim737 MCP.

Below is an image of the ProSim MCP configuration screen, configured for SIOC on the local machine, controlling an MCP, EFIS and Throttle unit.

The MCP should now turn on and be usable. Every time ProSim737 MCP is run, make sure SIOC is also running.

11.5 Connecting MCP and EFIS panels

11.5.1 Using OpenCockpits EFIS panels

The OpenCockpits SIOC script provided with ProSim737 MCP also contains the code for two EFIS panels. The script relies on the device numbering to be like this:

  • Device Index 1: EFIS captain
  • Device Index 2: EFIS F/O

When an EFIS panel is connected to a computer, SIOC will show a device number. Using this number, SIOC can be configured to map the device to either Device Index 1 or Device Index 2. This can be achieved by editing sioc.ini and adding a “master=” line.

The image below shows a SIOC screen where the EFIS is not correctly configured:

Note that SIOC says “IDX = *”, indicating that is does not know the device and has not assigned a device index to it.

When everything is set up correctly, SIOC will show the correct device index:

Here shows that the EFIS has been assigned Device index 1, and will therefore be handled as the Captain EFIS by the ProSim737 MCP script.

11.5.2 Using Sismo Soluciones MCP's and EFIS

Sismo Soluciones MCP's and EFIS panels use a system called SCPascal to run a script that tells the hardware what to do. Refer to Sismo’s installation guide to install and configure SCPascal to run the correct ProSim737 scripts.

Next, open the ProSim MCP configuration screen by right clicking somewhere in the ProSim MCP window and selecting Config.

In the Main tab, locate the block that says “For Sismo Soluciones MCP's” and fill in the address of the SC-Pascal server. The second text field is the TCP port to use, which is filled with the default value of 8097.

11.5.3 Using privately built MCP's with OpenCockpits cards

If an MCP has been built using OpenCockpits cards, a dedicated SIOC script must be written. Use the supplied ProSim_mcp SIOC script as a base.

This script lists all variable numbers that are in use by ProSim for various buttons, lights and displays. If the variable numbers are left the same, and the “Link” and “Output” parts of the lines are edited to reflect the particular setup, the script will work with the MCP. Remember that ProSim737 MCP communicates with SIOC with the specific variable numbers listed in the script, so it is important not to change these numbers.

In case a strict numbering scheme for SIOC variables is required, and the provided ProSim variables conflict with the script already written, it may be desirable to relocate the ProSim variable range. To do this, in the ProSim737 MCP configuration screen, there is an item “SIOC Base Offset” available. This number can be used to tell ProSim737 MCP where to start the ProSim range of SIOC variables. For example, entering “1000” here will add 1000 to the normal variable numbers, so ProSim737 MCP will expect the IAS MCP value in variable 1102 instead of 102. Please note that when this configuration item is set to anything different than 0, a dedicated SIOC script must be built so it works with the new variable numbers.

Next, configure ProSim737 MCP to connect to SIOC by setting the IP address and port of the SIOC process in the configuration screen.

11.5.4 Using other privately built MCP's

If the most flexibility in controlling the MCP buttons and switches is required, the main ProSim737 program can be used to assign buttons and switches to the MCP functions. To enable this function, select “Control via ProSim737 configuration” in the ProSim737 MCP configuration window. Now the ProSim737 configuration screen can be entered, and use the “Switches MCP/Throttle” tab to set the MCP and EFIS switches.

11.5.5 Using the software panel

ProSim737 MCP is usually controlled by a hardware panel. If a hardware panel is not available, the program can be used to control the MCP. Click on buttons to push them. Use the scroll wheel of the mouse to change numbers.

Two software EFIS panels can be opened by right clicking anywhere in the windows and selecting “EFIS Captain” or “EFIS F/O”.

11.5.6 Using FSUIPC Offsets Buttons and switches

ProSim737 MCP reads the 8-byte offset 0x5410 for buttons. This area is divided in 64 bits. Toggling a bit will trigger a button push. This means that the bit has to be changed to generate the action. If the bit was “0”, a “1” needs to be written. If the bit was “1”, a “0” has to be written. Mapping of bits to buttons
Bit 12 CWS A (known to PM as Alt 747)
Bit 17 Will set Flight Director 2 to on
Bit 18 Will set Flight Director 2 to off
Bit 19 Will set the A/T to ARM
Bit 20 Will set the A/T to OFF
Bit 21 Will push N1
Bit 22 Will push Speed
Bit 23 Will push CO
Bit 24 Will push Level Change
Bit 25 Will push Heading Sel
Bit 26 Will push VNAV
Bit 27 Will push LNAV
Bit 28 Will push VORLOC
Bit 29 Will push Approach
Bit 30 Will push Alt Hold
Bit 31 Will push Vertical Speed
Bit 32 Will push CMD 1
Bit 36 Will push CMD 2
Bit 37 Will set Flight Director 1 to on
Bit 38 Will set Flight Director 1 to off
Bit 40 Will set the disengage bar to disengage
Bit 41 Will set the disengage bar to normal
Bit 42 CWS B (Known in PM as AP disconnect 747) Indicators

ProSim737 MCP uses the 2 byte offset 0x4f0 to write status information. Indicator bits with their functions
Bit 0 CMD 1 light
Bit 1 CMD 2 light
Bit 2 Vertical speed light
Bit 3 Alt hold light
Bit 4 Approach light
Bit 5 VORLOC light
Bit 6 LNAV light
Bit 7 Heading sel light
Bit 8 Level Change light
Bit 9 Speed light
Bit 10 N1 light
Bit 11 A/T light
Bit 12 Flight director on
Bit 14 VNAV light
Bit 15 Speed is in mach Displays

These are the offsets for displays:

0xc4e (2 bytes) Course 1
0xc5e (2 bytes) Course 2
0x540a (4 bytes) Alt
0x540c (2 bytes) VSI
0x5408 (2 bytes) Heading
0x5406 (2 bytes) Speed IAS
0x540e (2 bytes) Speed Mach

Additionally, the 2-byte offset 0x51c is used to indicate which displays must be off:

Bit 0 VSI display is blanked
Bit 1 Speed display is blanked

11.6 Problems with ProSim MCP

If trouble is experienced with ProSim MCP, please follow these steps in sequence to diagnose and resolve the issue.

Step 1: Hardware connection Run ProSim MCP without running any other program on the computer. Do not start Flight Simulator. If an OpenCockpits MCP is used, please also start SIOC. The hardware MCP should come alive. Check that the software MCP shows the same number as the hardware MCP. If altitude, speed or heading on the hardware MCP is changed, it should also show in the software MCP. If this step fails, the hardware driver for the MCP was not installed correctly or ProSim MCP was not correctly configured.

Step 2: Checking connection with other ProSim modules With ProSim MCP running, start ProSim737 and ProSim Display as would normally be the correct procedure.. Check that the altitude, speed and heading in the PFD and ND in ProSim Display show the same values as set in the MCP. Changing them in the MCP should move them in the PFD and ND. If this step fails, ProSim MCP or ProSim Display have not been configured correctly. Check the ‘status’ label of the programs to find out the problem.

If you an OpenCockpits MCP is used, go to step 4. Otherwise, continue to step 3.

Step 3: Checking for drivers in Flight Simulator Close all programs. The MCP should turn off. If not, reboot the computer. Make sure the MCP is connected, but does not show any numbers before continuing.

Start Flight Simulator, without starting any other programs. Do not start ProSim737 or ProSim MCP. The MCP should NOT come alive.

If the MCP starts up when starting Flight Simulator, it means that there are drivers installed in Flight Simulator. Since only one program can talk to the MCP at once, this will conflict with ProSim MCP. Uninstall any MCP software that was installed in Flight Simulator and repeat this step until the MCP does not turn on when starting Flight Simulator.

Step 4: Checking Flight Simulator connection Start ProSim MCP, ProSim737, ProSim Display and Flight Simulator. MCP hardware should be on. Check the ‘Status’ label that shows up when clicking the right mouse button within the ProSim MCP window. The status label should be green.

If the status label is red, please check the message in the status menu. FSUIPC may not have been installed correctly or it may not have been registered.

Let the aircraft fly and set the heading in the MCP to the heading of the aircraft. Turn on the Flight Director switches and press the HDG SEL button. Check in the PFD that the vertical magenta flight director bar shows up and is more or less centered. If the MCP heading is changed to the left or right, the flight director bar should move left and right.

Now press a CMD button. The CMD light should come on and the text ‘CMD’ should show up in the PFD. The aircraft should follow the selected heading. If CMD does not turn on, make sure you have released the yoke and try again. You cannot engage CMD if the yoke is not centered. Also check the disengage bar in the MCP is in the up position. You can tune the yoke forces in the configuration screen of ProSim MCP. Also check here, if the ProSim MCP registers force on the yoke.

12 ProSim737 CDU

12.1 General description

The ProSim737 CDU module simulates a Control Display Unit that comprises of a small display accompanied by a keypad used to interact with the Flight Management System (FMS). Each unit independently displays and controls data. On startup of the ProSim737 CDU module a fully interactive CDU is displayed and controlled by keyboard and mouse. Inclusive of the ProSim737 CDU module, a web based CDU is also offered as an alternative to CDU hardware, and runs on any handheld device connected to the network. The ProSim737 CDU module does not include FMS logic, merely a device that communicates with the FMS contained in the ProSim737 System module. Network communication makes it possible to run the module outside of the cockpit environment at any location that can access the ProSim737 System module. The module contains drivers to communicate directly with hardware CDU’s from most manufacturers.

12.2 Installing ProSim CDU

The ProSim CDU module simulates a Control and Display Unit. These units are used to access information in the Flight Management System. Each pilot has access to a CDU unit, which is placed in the centre console, next to the throttles. The ProSim CDU module does not distinguish between a “captain CDU” and a “First Officer CDU”. Multiple instances of the program can be started to create as many CDU’s as required. All CDU’s will be linked through the ProSim737 main program and will display the same information. The module can also be used outside of the cockpit, so pre-flight data entry can be completed in a different location.

12.2.1 Installation

Installation is straightforward. If not already done, unpack the software archive ProSimCDU.zip to a directory and copy the contents of this directory to any computer that needs to run ProSim CDU. No additional files are needed. All required data is automatically loaded from the ProSim737 main program when a connection is made. Note: ProSim CDU does not require FSUIPC of WideFS.

12.2.2 Configuration

To open the configuration screen of ProSim CDU, right click anywhere in the window and select “Config”.

Like all other ProSim modules, ProSim CDU needs to know the IP address of the computer running the ProSim737 main program. Fill in this information in the “Server” field. The second box is used to enter the port of the ProSim737 program, which is currently always 8082.

To check if the program is successfully connected, right click somewhere in the window and check the status label. If it is green, the connection is successful. If the label is red, then there is a connection issue.

12.2.3 Options

The following options are available in the “Options” box:

  • Start minimised: This will start the program in its minimised state, in which case the window is not shown.
  • Start full screen: This will start the program in full screen mode. If a CDU with a monitor available that needs ProSim CDU to generate the screen output, use this mode.
  • Preferred host for WebCDU. This will make this CDU the preferred host for web based CDU access. Also see the paragraph “Web CDU”.
  • Show frame: When this option is on, the CDU frame and its buttons will be shown. Turn this option off to display the screen only.

12.2.4 Using hardware CDU's

For details on connecting hardware CDU’s to ProSim CDU see the CDU hardware paragraph.

12.3 Connecting CDU hardware to ProSim737 CDU

For a list with supported MCP's, refer to the supported hardware list. Thereafter the installation of supported CDU hardware is explained in detail.

12.3.1 Using Engravity CDU's

A USB connection is used to connect Engravity CDU's to the computer. A separate driver needs to be installed. For details of this installation, refer to the documentation accompanying the Engravity CDU. When the CDU is connected to the computer, a virtual COM port will be created. The COM port can be found in the hardware tab of the computer system under the ports entry. The name of this COM port is required to configure the Engravity device.

The configuration of the port is done in the configuration screen. The box labelled “For Engravity CDU's” shows the configurable options. When the COM port is identified, configure it in the “COM Port” selector and press OK.

12.3.2 Using OpenCockpits CDU's

OpenCockpits CDU's have two connectors:

  • A USB connector for the keyboard interface.
  • A composite video connector for the display. Preparing the keyboard interface

The OpenCockpits CDU uses the SIOC program to handle the keyboard. This program can be downloaded from the OpenCockpits website. The SIOC program needs a script to tell it what to do with the various inputs and outputs connected to it. ProSim737 CDU comes with a custom made SIOC script that can handle all OpenCockpits hardware. This script is found in the “OpenCockpits” folder.

The SIOC program needs to run in order to communicate with OpenCockpits hardware. In order to connect ProSim737 CDU to the SIOC program, ProSim737 CDU must be configured with the address and port of SIOC. This information will be found in the main window of SIOC under the header “<IOCP> SERVER”. In the image below, the IP address is and the port is 8092.

SIOC works with numbered variables to transport information. By default, the ProSim SIOC script will use variable number 50 to transport the CDU keys and variable 51 for the EXEC light.

If this has to be changed, the ProSim SIOC script will need to be edited and the ProSim737 CDU configuration must be updated to set the new variable offset. For example, if the variable number to 100 in the ProSim737 CDU configuration screen is set, variable 100 will be used for the keys and variable 101 will be used for the EXEC light. This way, a large number of CDU’s can be handled with one SIOC program. Preparing the video output

To use this device, a computer is required that has a composite out video port. Most modern video cards come with adapters that can provide this output.

To set up the video, connect the composite video connector to the video output port on the computer and make sure that the windows desktop is visible on the OpenCockpits CDU. Next, run ProSim737 CDU on the computer and make sure these options have been set:

  • Start full screen: Enabled
  • Show Frame: Disabled

Below is an example of the final configuration of a ProSim737 CDU that runs with an OpenCockpits CDU:

12.3.3 Using the keyboard

The ProSim737 CDU program can be controlled by keyboard. For backwards compatibility, the same key layout as the other software suppliers is available. If this key layout was used before, nothing has to be changed.

The native key layout of ProSim737 CDU is:

Keyboard CDU
. (dot) . (dot)
- (minus) - (minus)
(space) SP
Delete DEL
/ (slash) / (slash)
Backspace CLR
F1 - F6 LSK1 - LSK6
F7 - F12 RSK1 - RSK6
, (comma) RTE
‘ (quote) CRZ
\ (backslash) HOLD
Enter EXEC
` (backquote) N1 LIMIT
 ; FIX
Page down NEXT PAGE

12.3.4 Interfacing other CDU’s

ProSim CDU contains a generic TCP driver to allow external programs to communicate. To enable the generic TCP driver, enter a port number in the “TCP Port” field of the Generic TCP driver box in the Drivers tab. ProSim CDU will then start listening to that port. The protocol is ASCII, described below. Input to ProSim737 CDU

Send the name of the key that needs to be pressed, followed by an enter character. Valid names are: ‘A’ to ‘Z’. ‘0’ to ‘9’, ‘.’, ‘-’, ‘/’, ‘ ‘(space) for regular keys. "LSKL1", "LSKL2", "LSKL3", "LSKL4", "LSKL5", "LSKL6", "LSKR1", "LSKR2", "LSKR3", "LSKR4", "LSKR5", "LSKR6", "EXEC", "CLB", "CLEAR", "CRZ", "DEL", "DEP_ARR", "DES", "FIX", "HOLD", "INIT_REF", "LEGS", "MENU", "N1", "NEXT", "PREV", "PROG", "RTE" for special keys. Output from ProSim737 CDU

ProSim CDU sends XML reports whenever something in the CDU changes. When a connection is made, all CDU states are reported. Possible reports are:

CDU Power state :<power state=”true|false”/> Fail Light :<fail state=”true|false”/> Message Light :<message state=”true|false”/> EXEC Light :<exec state=”true|false”/> Scratchpad content :<scratchpad>[content]</scratchpad> Screen content

<screen> <title>[Title of screen]</title> <pageNumber>[Page number]</pageNumber> <line1>[content]</line1> <line2>[content]</line2> <line3>[content]</line3> <line4>[content]</line4> <line5>[content]</line5> <line6>[content]</line6> </screen> Each line in the CDU is broken up into an upper and a lower part. This is represented in each <lineX> element:

<line1> <upper>[content]</upper> <lower>[content]</lower> </line1>

In the [content] blocks of <upper> and <lower> elements, you may encounter these tags:

Text is in small font  :[content] Text is in large font  :<large>[content]</large> Text is cyan  :<cyan>[content]</cyan> Text is green  :<green>[content]</green> Text is magenta  :<magenta>[content]</magenta>

Inside text strings, some special characters are used which should be replaced according to this table:

Character in content Character that should be shown in CDU
` (backquote) ° (degree sign)
# □ (box for input)

12.4 Using the WebCDU

When at least one ProSim737 CDU program is running and connected to the ProSim737 server, any web capable device can be used to call up a CDU unit. The address of the WebCDU is the main address of the Instructor Operator Station with “/cdu” appended to it. All input keys are sent to a connected ProSim737 CDU program and the screen output will be relayed back to the web browser.

Any running ProSim737 CDU unit can be chosen to handle the WebCDU’s. If a particular ProSim737 CDU instance needs to handle the WebCDU’s , select the option “Preferred host for WebCDU”.

Example of a WebCDU running in browser:

13 ProSim737 Panel

13.1 General description

The ProSim737 Panel module provides a graphical representation of the Forward Overhead Panel, AFT Overhead Panel and Pedestal. The actual state of dials, switches, indicators and gauges displayed on these panels is used to confirm configuration between the ProSim737 System Module and the cockpit hardware. The representations of these panels are fully functional, dials and switches are controlled by mouse or touchscreen.

13.2 Installing ProSim Panel

ProSim737 Panel is an optional program that can be used to view and/or control the panels in the aircraft. The following panels are available:

  • Forward Overhead Panel
  • Aft Overhead Panel
  • Forward and Aft Overhead
  • Pedestal
  • Up MIP (Main Instrument Panel)
  • Lower MIP

13.2.1 Installation

Installation is straightforward. If not already done, unpack the software archive Prosimpanels.zip to a directory and copy the contents of this directory to any computer that needs to run a display. No additional files are needed. ProSim Display does not require FSUIPC of WideFS to run.

13.2.2 Configuration

Before ProSim Panel can show any information, it has to be connected to the ProSim737 main program. To do this, right click anywhere in the window and select “Configuration”. In the configuration window, enter the IP address of the machine running ProSim737. The second box is used to enter the port of the ProSim737 program, which is currently always 8082.

To check if the program is successfully connected, right click somewhere in the window and check the status label. If it is green, the connection is successful. If the label is red, then there is a connection issue

If all panels should be available it is advisable to create a directory for every panel and copy the software into each directory. When configuring the software, the settings are saved in the respective directories and will be used upon start-up of the program.

13.3 Using ProSim Panel

The panel is controlled with the left mouse button only. This way, it is suitable for touch screen displays. When the mouse is moved over an item, the cursor will change into a hand symbol, to indicate a clickable area.

It is important to understand that ProSim737 Panel does not contain any logic. It only displays the state of the switches, selectors and indicators. The actual states are contained and maintained by the ProSim737 main program. Because of this architecture, it is possible to run any number of ProSim737 Panel programs in your cockpit, without interference.

When an area on the panel is clicked, ProSim737 Panel will send a request to the ProSim737 main program to make a change to the switch. ProSim737 will then check if the switch is under hardware control. Switches that are under hardware control cannot be changed in ProSim737 Panel. Clicking them will have no effect.

Pressing and holding an indicator on ProSim737 Panel will trigger a light test of that indicator. This light test also works in connected hardware.

Whenever a switch or indicator changes in ProSim737, all connected ProSim737 Panel programs will immediately reflect the change. This is ideal for checking the hardware overhead panel.

ProSim737 Panel is ideally suited to check how ProSim737 views the state of switches switches while making changes to the hardware of the overhead panel.

14 ProSim737 Audio

14.1 General description

The ProSim737 Audio module is a network enabled audio player that is controlled by the ProSim737 System module. In connection with the ProSim737 Audio module, the ProSim737 System module contains a comprehensive list of sound files, in addition personalised sounds can be added and stored for playback. The ProSim737 Audio module provides selectable playback events related to radio and cockpit sounds that can be heard from either chosen device, headsets or cockpit speakers.

14.2 Installing ProSim737 Audio

ProSim737 Audio is an optional program that can be used to play ProSim737 audio on a different computer than where the ProSim737 program is installed. This allows to build realistic sound configurations. Once configured, the program does not need any attention and will act as a relay to play any sound it is configured to play.

14.2.1 Installation

Installation is straightforward. If not already done, unpack the software archive ProSimAudio.zip to a directory and copy the contents of this directory to any computer that needs to run ProSim Audio. No additional files are needed. All required data, including the audio files, are automatically loaded from the ProSim737 main program when a connection is made.

ProSim737 Audio does not require FSUIPC of WideFS.

14.2.2 Configuration

To open the configuration screen of ProSim737 Audio, right click anywhere in the window and select “Config”.

Like all other ProSim737 modules, ProSim737 Audio needs to know the IP address of the machine running the ProSim737 main program. Fill in this information in the “Server” field.

After connection with the server has been established, the program will display all available sounds from the server. Enable a sound by clicking the button. After exiting the program, the enabled sounds will be stored. This ensures that they are enabled again when the program runs the next time.

After configuring sounds in ProSim737 Audio, all configured sounds will be played when required by the program. There is no configuration necessary in the main ProSim737 program.

14.3 Add Audio

15 ProSim737 Instructor Operating Station

15.1 General description

Instructor Operating Station

Designed for operator use, the Instructor Operating Station (IOS) allows normal and abnormal behavioural conditions within the simulation. ProSim737 IOS is a web based module that allows the user to create these conditions throughout the complete simulated flight. Inclusive of these conditions, the IOS also features:

  • Aircraft repositioning, visibility settings and pushback.
  • Flight and performance parameters.
  • Live position mapping including navigational data.
  • Add and remove conditional failures.
  • Extensive weather settings including real weather import and presets.
  • Alter cargo, fuel and passenger quantities to adjust the weight and center of gravity.
  • Pre flight route planning and storing capability in the FMS.
  • Cockpit setup options and airliner specific preferences.

The IOS operates from a browser connected to the network on any handheld device or computer.

15.2 Connecting IOS

ProSim737 comes with an elaborate instructor station that is accessed via a web browser. This makes it easy to use the instructor station without the need to install any software. To access the instructor station, enter the instructor station URL into your web browser. Click on the “Web Access” item from the “Help” menu in the ProSim737 main window to find the instructor station URL. This will show a list of URL’s that ProSim737 is hosting. The instructor station is listed as the “Base URL”. If multiple lines present are labelled “Base URL”, multiple IP addresses are configured on the machine. Try all of the URL’s to find the one that is working.

Before starting the IOS open ProSim737 System and your Flight Simulator. Parts of the IOS is based on SimConnect. Therefore Flight Simulator 9 is not fully compatible for the new IOS.

15.3 Basic layout of IOS

On the upper position of the IOS you will find on the right side, 4 icons.

  1. Pause
    • Click to pause the simulator. If the simulator is on
    • Click again to continue flying.
  2. Flight freeze
    • During Flight Freeze you can adjust pitch and roll movement without changing your position
    • Flight Freeze can be used to stabilise your current flight or adjust pitch and roll for the next flight.
  3. Browser settings
    • Selecting keyboard input when using a touch screen device.
    • Sound on / off
  4. Day and Night
    • Change IOS colour, for use during night.

15.4 Main

The Main page is to monitor various tasks before and during flight. Various pre-sets can be selected, monitor flight parameters and monitor cockpit setup.

15.4.1 Main - Main

In this page, pre-sets for position, visibility, time and view the check items can be selected.

The pre-set for position is an easy entrance for preset tab “Position”. The 5 slots can be activated by clicking one of the buttons. The “Store” function is intended to store a current position during flight. After clicking on a position slot, confirm the position change by clicking “ok”.
Visibility, during approach you can change the visibility. There are 4 different options.
Check items, Check items is checking the flight phase.

The check items create a list to show that the aircraft is configured according to the flight phase. You can only monitor this list, cockpit configuration should be changed to remove a ‘check item’.

15.4.2 Main - Service

Service allows you to select or deselect ground power, ground pneumatic, push back and door logic. The pushback is divided in left, right and straight forward. Click on one off the buttons to start the pushback to stop the pushback click on “Stop Pushback”. All doors can be opened and closed on this page.

15.4.3 Main - Parameters

Flight parameters displays the current state of the aircraft. Flight parameters can not be added or removed on this tab.

15.5 MAP

Map is a graphical display for your current position. You can monitor the aircraft position during flight and check navigation resources in the vicinity of the aircraft.

You can toggle navigation sources by clicking on the relevant icon. Below a list of icons showed in the map.

-VOR (VHF Omnidirectional Range) -DME (Distance Measuring Equipment) -NDB (Non-Directional Beacon) -ILS (Instrument Landing System) -Airport -Airway (lo) -Airway (hi) -Fix -Airspace -Route

When you have created a VNAV path you can monitor the route by clicking on “route”. Red identifies the route flown and upcoming route.

To change zoom, click + or – on the right side. Auto enables auto zoom during flight. Zoom can be also accomplished by the scroll wheel.

15.6 Failures

The Failures tab is the interface to the ProSim737 failure system. It provides an overview of the currently active failures and allows the selection and arming of new failures. The failures tab always shows the current state of the aircraft. Any failure or situation that may disrupt the normal operation of the aircraft is shown in yellow boxes on the top of the screen. When there are no yellow boxes, there are no operational problems. Pressing the “Remove” button in a yellow box will cause the system to make an attempt to resolve the issue. When a situation can not be resolved (for example, when asking to realign an IRS system that has no power), the box will immediately reappear. To activate or arm a new failure, select the failure from the overview and fill in the conditions form. If no condition is selected, the failure will be active immediately.

15.6.1 Failures - Current / Pending Failures

Current failures provide an overview of the currently active failures and allows the selection and arming of new failures. Pending failures relate to future situations, such as indicated speed and altitude within a certain time frame.

15.6.2 Failures – Engine

Failures connected to the engine Engine fire and failures can be selected by clicking on the relevant failure button. You can select multiple failures

15.6.3 Failures – Fuel

Failures connected to fuel related situations.

15.6.4 Failures – Electric

Failures connected to the electrical system.

15.6.5 Failures – Buses

Failures connected to Buses within the electrical system.

15.6.6 Failures – Pneumatic

Failures connected to pneumatic systems.

15.6.7 Failures – Hydraulic

Failures connected hydraulic systems.

15.6.8 Failures – Navigation

Failures connected to the navigation system.

15.6.9 Failures – Misc

Failures connected to various systems.

15.7 Weather

Local or global weather is created and simulated to provide simulated flight conditions.

15.7.1 Current Weather

Weather conditions can be created by using the presets, Local Weather or Global Weather. These conditions can be stored in a numbered slot on the Current page. The slots will not be saved when ProSim737 System is closed. For default themes and self created themes, these should be stored as Preset.

15.7.2 Presets

Presets include default weather themes and self created weather themes.

15.7.3 Global Weather

Created global weather covers the world with the same theme. There are 5 Vertical layers that can be created to identify wind, clouds, visibility, QNH, temperature and rain,

The created weather themes can then be stored into a slot, (Current), as a theme (Preset) or direct into the simulator.

15.7.4 Local Weather

Local weather is a coded service report for one specific area, known as a Metar.

Metar can be used for real weather. To use real weather, copy the txt file from the link below. http://weather.noaa.gov/pub/data/observations/metar/cycles/23Z.TXT In the link you will find real weather from all metars

15.8 Weight

15.8.1 Weight - Passengers

In the weight tab you can change passenger weight, cargo weight and fuel weight. Also the Zero fuel weight, fuel and gross weight is monitored on this page. The passenger can be add or remove by clicking on the seat’s or via sliders below passenger image. The passenger image is divided in four compartments. The crew weight is always added and cannot be changed via the IOS.

15.8.2 Weight - Cargo

The cargo is divided in two compartments, FWD and AFT cargo, and can be added via the sliders.

15.8.3 Weight - Fuel

Before and during flight Fuel can be adjusted depending own specific requirements.

15.9 Position

The Position menu is used to control aircraft repositioning. Three tabs are available:

  1. Airport
  2. Presets
  3. Edit translation

The ProSim737 IOS positioning system provides five “slots” that can be loaded with positions. These allow the instructor or pilot to quickly position to one of these five positions.

15.9.1 Position - Airport

A copy of the slots can be found in Main tab, Main, for easy access during flight.

The airport tab provides repositioning based on airport runways or parking spots.

For this example we are using Rotterdam (EHRD). Type in EHRD or Rotterdam at ‘Airport’, when using the name of the airport confirm this by clicking on the displayed ICAO code. The next step is to confirm the location within the airport. Default is always the first runway available. You can always confirm your location via the small map on the right side. Change the position within the airport by selecting a runway, parking or gates.

When selecting a runway, an optional translation can be applied. A translation moves the aircraft relative to the threshold of a runway. There are preconfigured translations available; runway start, 10 mile final, left downwind and right downwind. Translations can also be created from the outset.

To add a translation, use the ‘edit translation’ tab from main horizontal navigation.

Finally, load the position by selecting a slot on the bottom of the page, by clicking ‘Load’ or activate direct by clicking on ‘Activate now’.

15.9.2 Position - Presets

Pre-stored positions are positions that are created by flying the aircraft to a certain location and storing it. They are mostly useful for specific locations that are not accessible by the global database, such as holding points or parts of an approach procedure. To create a pre-stored position, fly the aircraft to the desired location and press pause. Next, enter a name in the text box labelled "Store current position in database" and press store. To load a position into a slot, select it from the overview, enter the slot number to load it and press "Load".

15.9.3 Position - Edit Translation

Translations can change the position in five different ways:

  1. Speed: Normally, the speed is 0 kts. For airborne starts, set a desired speed.
  2. Climb: This is the number of feet that should be added to the runway height.
  3. Pitch: This is the pitch of the aircraft.
  4. Rotate: This is number of degrees that the aircraft nose must be turned clockwise relative to the runway heading.
  5. Translation: This allows translating the position a number of miles to the front, back, left and right, relative to the runway heading and threshold.

After selecting the airport, runway or parking and an optional translation, the generated position can be loaded in a slot by typing the desired slot number and pressing "Load".

15.10 Route

15.10.1 Planner

Route is a route planner, intended for planning a route and to store a route in the CDU. Routes can be planned from a departure airport to an arrival airport. Optionally, constraints can be set, such as departure and arrival runways, SIDs and STARs. The planner uses the currently loaded navigation database to find a route over the standard airways.

The route planner is explained with the route: ICAO code EHRD (Rotterdam, the Netherlands) to EDDW (Bremen, Germany)

Enter your origin ICAO code, for this example, EHRD also enter the ICAO code for destination EDDW. Click on “Plan”. The route is created, you can send the route into the CDU by clicking on “Load”.
This created route cannot be changed via the IOS, change is possible via the CDU tab Legs.
After loading the route, always check the route via the CDU.

15.10.2 Company route

After generating a route you can store the route as a “Company Route”. Company route is a full route except SID, STAR and runway. This route can be stored in the IOS to use this specific rout multiple time. On default the company route will have a name starting the departure airport ICAO code and the destination airport ICAO code.

15.11 Cockpit Setup

The Cockpit Setup tab allows to set specific layouts and options. These are known as "Carrier Options", because they usually vary by airline. All changes made in the tab are effective immediately. If the current selection of options needs to be saved, a name can be entered in "Store new configuration" box and saved by pressing the "Store" button. This configuration can be recalled instantly. The "Default" configuration is the configuration used every time the software starts. To store the default configuration, click on "Default" and press "Store".

15.11.1 Cockpit Setup - Audio

15.11.2 Cockpit Setup - Display

15.11.3 Cockpit Setup - Option

15.11.4 Cockpit Setup – Units

15.12 Maint

On the Maint page users can monitor the Hardware IO performance, computer shutdown option and software quick setup settings. The Hardware monitoring page will be only necessary when requested by ProSim737 support questions. On default use the hardware tuning is correctly implemented.

The computer Shutdown option can be selected in the different ProSim737 modules, on the configuration screen of the different modules you can select “allows remote computer shutdown”. This option is available in all modules except the ProSim737 System module. After setting up the separate modules you can shut down the computers via the IOS.

The option “Quick start” setting can only be used when no hardware is connected. Three options can be used, Cold and Dark, Ready and Start APU. The software switches will be changed regarding the setting selected in this option.

15.12.1 Maint - Hardware

15.12.2 Maint - Misc

16 Support

16.1 Support structure

ProSim737 support structure is using the following route:

  1. User Manual
  2. Forum
  3. Support Mail

First step is to use the user manual as the main source of information necessary to setup the cockpit. If the answer can’t be found in the user manual the next source of information will be the forum. In the user forum an enormous amount of questions and answers is available. Next to current answers you can ask new questions in the specific forum topics. ProSim737 community is active to support all the questions regarding the ProSim737 Suite. Last option is support mail. If no answer can be found the last source of information can be obtained via a mail support. For effective communication include a logic question including reference of hardware if there is hardware connected. A mail should contain a description of the problem and a reference of what you had expected.

16.2 Frequently Asked Questions