The user interface in the Instructor Operator Station (IOS) allows the user to customise several functions, in addition to enabling or disabling specific options. Whilst most of the functions are straightforward, there are several options that are unconventional and therefore, probably not clearly understood.
Read More
No matter which avionics suite is used, the navigational database and approach charts will need to be kept up-to-date. Navigraph (the company) have for many years been the mainstay in supplying accurate navigational data to the flight simulator community.
The navigation database and monthly updates can be downloaded from the Navigraph website, and can either be manually installed to Flight Simulator, or alternatively you can use Navigraph’s FMS Data Manager software to install the files.
This short article will benefit only those using the ProSim-AR (ProSim-737) avionics suite Version 3. ProSim-AR Version 2 uses a different file structure and navigation path.
Database Files and Installation
Navigraph is the navigation database used by ProSim737. The database is purchased separately to ProSim-AR and navigation updates (AIRAC cycles) are released monthly.
The correct navigational database for ProSim737 to download from the Navigraph website is: ProSim737 2.24b1 (and above).
When installed the database consists of three files:
cycle.json;
cycle_info.txt; and,
nd.bb3.
Cycle-info.txt is a text file that indicates which navigation database has been installed. This is the file you need to open if you are unsure of which AIRAC cycle has been installed. The other two files relate directly to the database.
Once the database is installed or updated, the ProSim737 main module (.exe file) must be run, and the database rebuilt.
To rebuild the database, open the ProSim main module, select Config/Database and Build Database. The process to rebuild the database will take around 5 minutes. When completed, the installed database AIRAC cycle number will be displayed.
Database Fails to Update
If the database does not update, there is a possibility that either the downloaded file is corrupt, or more than likely the database has been installed to the incorrect folder structure within ProSim-AR.
In this case, download the required files from Navigraph, uncompress the files to your computer desktop (or anywhere else) and copy the three database files to:
C:/Program Data/Prosim-AR/Navdata.
FMS Database Manager Mapping page. This is where you select the folder structure to upload the AIRAC cycle to
FMS Data Manager
Navigraph have an installer (FMS Data Manager) which is a standalone program that is free to use. The Data Manager is quite a powerful program and it’s worth the effort examining what this software can do.
When setup correctly, the installer will download, uncompress, and install the Navigraph files to the correct folder structure with ProSim. The installer also will create a backup of the existing database (if selected).
Navigraph FMS Data Manager main front page. This is the page where you select Update to update the navigational database with the latest AIRAC cycle
To ensure that the database is installed to the correct folder on your computer, the Data Manager must be configured correctly. This can be done a number of ways, however, the easiest and most straightforward way is to setup the folder structure manually.
Open the FMS Data Manager and select Addon Mappings.
Select the black coloured folder adjacent to the purple coloured box named Manual.
Select the correct folder in your computer (C:/Program Data) and save the configuration.
To update the database, navigate back to the front page of the manager and select the check box adjacent to ProSim737 2.24b1 and select update.
ProSim-AR (ProSim737) main menu showing the Config page open with the Build Database page overlaid
Important Points:
Whenever you install or update the Navigraph database, rebuild the database and check the AIRAC cycle.
Final Call
Maintaining the navigation database is important if you are to get the most from Flight Simulator. Navigraph AIRAC cycles are released monthly, and it stands to reason that the FMS Data Manager should be used to streamline the installation process. Problems, when they do occur, usually relate to the FMS Data Manager trying to install files to the incorrect folder structure.
OEM 737-800 font style (courtesy Mick.C ©). An interesting point about this picture is the condition of the flightdeck which is far from the pristine appearance of many simulators
This article will discuss how to change the font style displayed in the Control Display Unit (CDU). Although the ProSim737 avionics suite comes with a default font style, many enthusiasts wish to change the font, colour and size to more closely mimic the font used in the OEM CDU, or so the information can be more easily read (not all of us are 20 years old…)
The font styles displayed in a simulator are linked to the fonts that have been installed in the computer’s operating system. Any font style can be displayed in the CDU – as long as the font style has been included in the style library used by Windows.
important Parameters
There are two parameters which depict how a font style is displayed: the actual font style itself and the CDU config file.
The location of the font style library is C:\\Windows\fonts (Windows 10/11).
Any of the fonts located in this library can be used to display parameters in the CDU. Likewise, if you have a preferred font that is not in the library then it can easily be added to the library (copy/paste).
The location of the config file is the CDU folder of the ProSim737 avionics suite.
To edit the config file, you must right click the file and select edit, otherwise the file will open in read only (HTML text). Once the config file is opened, it will become apparent that all the settings related to the CDU: screen location, screen size, font style, display parameters, etc are recorded in the file.
With a little experience, it is often easier to make setup changes to the CDU by opening and editing the config file, rather than opening the options box from the CDU display window. If editing the config file directly, always make a back-up copy of the file prior to making and saving any changes.
ProSim737 options box. The options box is opened by right clicking the CDU screen and selecting config
Selecting a Font Style and Colour
How to initially configure the CDU (line setting, screen position, frame settings, etc) is addressed in the ProSim737 manual (2012 edition) or in the wikipedia manual.
To alter the font style, open the options box by right clicking the CDU screen and selecting config; the options box is linked to the Windows style library discussed earlier. To change a font style, scroll through the styles available. Once a style has been selected, you can change the font size by either changing the size variable associated with the font, or by selecting +- in the ProSim options box.
Another way to change the font style is to open the config file and edit the line entry that relates to the small and large font sizes. If this method is used, ensure you transcribe the font style and size accurately to avoid errors.
To alter the font’s colour, the config file must be opened. Once opened search for the following two lines:
<smallFontColor>Lime</smallFontColor>
<largeFontColor>White</largeFontColor>
Type the required colour replacing the bolded section above.
ProSim737 CDU config file. The lines that need to be altered to change the style and colour are in red. With experience, other attributes can also be altered, however, always make a copy of the file prior to changing anything
OEM
OEM is an acronym for original equipment manufacturer. It refers to the hardware and software used in the real aircraft. In the Boeing aircraft the font colours displayed in the CDU can be readily changed.
The font style is more or less standardised across the Boeing fleet, however, variations to the font style can be found, and in part depend upon the software option selected by the airline when the aircraft was initially purchased, the U version in use, and the manufacturer of the CDU (Smiths, Collins and Honeywell).
Colour Conventions
The FMC software supports 5 colour conventions: green, cyan, magenta, white and amber. Bill Bulfer examines the text displayed for each colours in the FMC Guide. The information provided is from U10.2.
Final Call
Changing the font style, size and colour can be easily accomplished by editing the config file either directly from the CDU display or by opening the config file itself. If a specific style is needed, then this can be added to the Windows style library.
I have rewritten the previous article relating to IAN (published in 2015). The new article is more in-line with current practices, has been streamlined. and I hope is easier to read and understand. The original article had been linked to several outside websites, and to maintain the links and url, I have only replaced the content.
Analogue meter mounted to the lid of the Throttle Interface Module (TIM). The meter, powered by 12 volts, records whenever power travels through the 12 volt system to the module
How many times have you underestimated the use of an item, to discover that the last time you changed the oil in the lawn mower was 15 years ago!
Aircraft, boats, heavy machinery and many other items, that require regular servicing, have an hour meter to provide an accurate time that a piece of equipment, such as an engine has been operating.
A flight simulator is made from many components. Some components will last for many hundreds, if not thousands of hours use, however, other parts have inbuilt obsolescence and will eventually fail.
Failing Power Supply
Recently, I had a problem whereby the internal hub in the Throttle Interface Module (TIM) would intermittently disconnect. The cause of the problem was the fluctuating output of the 5 volt mini power supply (MeanWell RS-15-5 Volt 3 amp) that amongst other things, powers the hub.
I was perturbed by the failure as I was sure the power supply was only a few years old. However, after consulting the service booklet I maintain for the simulator, I noted the unit had been installed 5 years ago and had been operating for 2054 hours. The part had, in my opinion, well and truly provided excellent service life considering the hours it had been operational.
Hour Meter
At the onset, when I designed the framework upon which the simulator would operate, I included two hour meters that would 'tick on endlessly' whenever power was turned on to the simulator or to specific systems within the simulator.
One meter resides in the Throttle Interface Module (TIM) and records the hours of use for the interface cards, motor controllers, power supplies, relays and other components that operate the throttle and autothrottle system. A separate, but similar meter records the overall use of the simulator (the time that the simulator has been receiving power).
An hour meter is straightforward to install and can be connected directly to a 12 volt power supply (or busbar) that is always receiving power. The meter (s) can easily be mounted anywhere on the simulator, whether it be inside the center pedestal, the rear of the Main Instrument Panel (MIP), or to a standalone module.
The meters I am using are analogue, however, digital meters can also be purchased. The downside of using an analogue meter is that as each increment moves through its cycle it generates a clicking sound; depending upon the location chosen to mount the meter the clicking sound may be annoying. However, an advantage of an analogue meter is that once the hours have been recorded on the meter, the information cannot be lost; a digital meter can loose the information if, for example, the backup battery fails.
Final Call
Memory for the most part is fickle, and unless trained, most people underestimate the time that a component has been used. An hour meter connected to the simulator, enables an accurate record to be kept to how long specific parts have been operating.
OEM 737-500 CL CDU
Specific information must be entered into the Control Display Unit (CDU) if the Flight Management Computer (FMC) and Flight Management System (FMS) is to function correctly. To ensure that all the appropriate data is entered, a flow sequence is usually used by a flight crew to enter data into the CDU.
Each aircraft is normally equipped with two Control Display Units; one on the Captain-side and one the First Officer-side. Each CDU can be used either in tandem or independently of each other.
In this article, I will discuss the preferred flow sequence that should be used to enter information into the CDU pre-flight. It should be noted that, like many aspects of aviation there are usually several ways to achieve a similar if not identical result. Often airline policy will dictate the sequence that the CDU is configured, and by which pilot. Therefore, the below information should be treated as a guideline rather than an inflexible set of rules.
The information used comes in part from the aircraft’s flight plan and load sheet.
The content of this article has been reviewed by a Boeing 737 Captain for accuracy.
FMC Software
The Flight Management System (FMS) is controlled by software and the software version used is often dependent on the age of the aircraft; not all software is identical. The information in this article refers to Software Version U10.8A. U10.8A is the version used by ProSim737 (other simulation avionics suites may differ). An earlier article discusses software variants.
Which Pilot Does What And When Is It Done
It is not uncommon for the pilot’s to share the task of setting up the CDU. Usually the pilot flying (PF) will enter parameters that are essential to flight, while the pilot not flying/monitoring (PM) will enter information pursuant to the route.
However, the hierarchy in a flight deck is that the Captain is the Pilot In Command (PIC), and it is assumed that the First Officer will complete most of the mundane, albeit important, navigation tasks leaving the Captain to deal with other matters.
CDU Verification and Cross Checking Procedure
The CDU is nothing more than a ‘glorified keypad’ and the maxim of ‘rubbish in rubbish out’ applies. Until execution (pressing the illuminated execute button on the keypad), none of the information entered into the CDU will be reflected in the FMC and FMS. Therefore, it is important that prior to execution, each pilot review and confirms the other’s inputs. Cross checking and verification minimises the chance that incorrect information has been entered.
At a minimum, a flight crew should compare the filed flight plan with the airways and waypoints entered on the ROUTE pages. The flight plan total distance and estimated fuel remaining at the destination should also be reviewed on the progress page of the CDU. If a discrepancy is noted, the LEGS page must be updated to ensure it is identical to the airways and waypoints in the filed flight plan. A cross check using the Navigation Display in PLAN mode and the CDU in STEP function (LEGS page) will aid is verification of the flight plan and in determining if there are any discontinuities that need to closed.
Taxi and Flight
Before taxi, the Captain or First Officer may make CDU entries. However, when possible, CDU entries should be made prior to taxi or when stopped. If CDU entries must be made during taxi, the pilot monitoring makes the entries and the pilot flying concentrates on steering the aircraft.
In flight, the pilot monitoring usually makes the CDU entries, however, the pilot flying may make simple CDU entries, but only when the workload allows. Essentially, the pilot flying concentrates on flying the aircraft and if they wish to enter data to the CDU, then the responsibly of flying the aircraft should be transferred to the First Officer.
The pilot flying is responsible for setting up the approach page in the CDU. To do this, the pilot flying will transfer command of the aircraft to the pilot not flying, and then make any amendments to the approach in the CDU. Upon completion, the command of the aircraft will be transferred and the pilot not flying will check the information.
Which Page in the CDU is Opened During Takeoff
The pilot flying usually will have the takeoff reference page displayed to enable the crew to have immediate access to V-speeds. This is to counter against the rare event that the V-speeds are inadvertently removed from the airspeed display on the Primary Flight Display (PFD) due to a display failure. Alternatively, the pilot flying may also elect (following the takeoff briefing in the Before Takeoff Procedure) to display the CLB page for takeoff.
The pilot monitoring normally displays the LEGS page during takeoff and departure to allow timely route modification if necessary.
CDU Sequence Flow
There are numerous ways to flow from one CDU function to another. The two commonly used methods are to use the Alpha Keys or the Line Select Keys (i.e. LSKL6). For example, LSKL6 refers to line select key left 6 or the sixth lower button on the left hand side.
As stated, the pilot flying will enter any information relevant to the takeoff of the aircraft, while the pilot not flying will enter information pertaining to the route of the aircraft (i.e. route, legs).
Bold CAPITALletters indicate that the command is an ALPHA menu key.
PILOT NOT FLYING (PM)
INIT REF / INDEX (LSKL6).
POS (LSL2) – Enter airport identifier into Ref Airport.
RTE or ROUTE (LSKR6) - Enter airport identifier (origin and destination), flight number (Flt No) and runway.
DEP ARR – Enter departure information (DEP LSKL1) - SID and runway.
LEGS– Enter airways, waypoints and navaids as required to a build a navigation route.
DEP ARR – Enter arrival information (ARR LSKL2) - STAR, approach, transition and runway.
On the EFIS, select PLAN and using the STEP function (LEGS Page) or PREV-NEXTPage, cycle through the waypoints checking the route on the Navigation Display. Check the route and close any route discontinuities. Return EFIS to MAP.
ACTIVATE (LSKL6) / EXECor RTE / ACTIVATE (LSKR6) / EXEC.
PILOT FLYING (PF)
INIT REF – Enter Zero Fuel Weight (ZFW), Fuel Reserves, Cost Index, Cruise Altitude (Crz Alt), Cruise Wind (Crz Wind), ISA Deviation (ISA Dev), Outside Air Temperature (T/C OAT) and Transition Altitude (Trans Alt).
N1 LIMIT (or LSKR6) – Enter Derates as desired.
LEGS / RTE DATA (LSKR6) – Enter wind (this determines fuel quantity on progress page). Note #1.
INIT REF / displays TAKEOFF REF page – Enter Flaps setting for departure and Centre of Gravity (Flaps and Trim). Go to page 2/2 and input data to various fields as and if required.
EXEC– Press illuminated execute key (this triggers the V-Speeds to be displayed on the TAKEOFF REF page).
To select V-Speeds, press Line Select keys beside each V-Speed to activate (LSR1, 2 & 3). Note #2.
Notes:
NOTE #1: Wind direction and speed (point 3) can be addedprior to or after the EXEC button has been selected. The flow sequence will alter dependent upon when this information is added. If the winds are not added, the flow will alter and TAKEOFF (LSKR6) will be selected instead of INIT REF.
NOTE #2: If V-Speeds on the Takeoff page are not displayed, it is because either the EXEC key has been pressed prior to the Takeoff Page being opened and data entered. If this occurs, cycle the QRH (LSKR6) on and off. The V-Speeds will then be displayed. Another reason that the V-Speeds may not be displayed is failure to input other essential pre-flight information.
There is often confusion to what the QRH designation means. When QRH is not selected (turned off) the V-Speeds will be automatically promulgated. If QRH is selected (turned on) the V-Speeds will be shown in green beside the appropriate line. This enables the flight crew to change the V-Speeds prior to executing them (note that ProSim-AR enables this to be altered in the IOS/Settings).
Additional Information
I usually do not link to outside resources, however, this U-Tube video from Mentour Pilot demonstrates the procedure quite well. Scroll to 0:31 seconds to begin video.
For those interested in reading more about how the CDU, FMC and FMS and how they interrelate concerning information input, Randy Walter from Smiths Industries has put together a very good article called Flight Management Systems.
Final Call
The CDU is an essential item that must be configured correctly if the aircraft’s internal navigation database is to be used. Likewise, LNAV or VNAV will only operate if the information has been entered into the CDU correctly.
The sequence you enter the information into the CDU is important, and although some latitude to the flow is accepted, a correct sequence flow will ensure all essential variables are inputted. Finally, cross verification of data, or any change to the data, ensures correct and accurate information is being entered.
Acronyms and Glossary
ALPHA Menu Key - Refers to the menu function keys.
CDU - Control Display Unit (the keypad).
FMC - Flight Management Computer.
FMS - Flight Management System.
LSK - Line Select Key. Used to enter lower level pages.
QRH - Quick Reference Handbook.
Trip Reminder Indicator. A small OEM part that is easily installed to any simulator
The trip reminder indicator (TRI) is a mechanical device installed to the right hand side of the yoke; it’s an airline option. Basically, the device is three separate digits that can be rotated in any combination, from zero to nine.
The trip indicator is a memory device from which the crew historically used to record the flight number; the pilot uses his thumb to move the three digits to indicate the flight number. However, over time flight numbers became longer than three digits and the use of the trip indicator, for it’s intended purpose, wanned
I use the trip indicator to dial in the Vref, as it’s often easier to quickly glance at the trip indicator to remind you of the Vref speed rather than look at the PFD or CDU. Some dial in the Vref + wind speed.
Background
The trip indicator has a very long lineage beginning with the Boeing 707 aircraft. The device was then ported to the 717, 727 and finally the 737 Classic and Next Generation airframes.
Installation and Backlighting
Because the OEM yoke already has the correctly shaped hole, installation of the trip indicator is straightforward. If you are using an OEM yoke, you probably will need to carefully remove the blanking cover from the hole.
If a reproduction yoke is used, and the hole is not present, a circular hole will need to be cut from aluminium or plastic to enable the trip indicator to fit snugly into the yoke. As the three dials are mechanical, there is no requirement to connect the device to an interface card.
Each of the digits on the indicator is backlit by a 5 volt incandescent aircraft bulb.
The design of the trip indicator is ingenious, in that after the trip indicator has been removed from the yoke (two screws at the front of the yoke secure the indicator), a transparent acrylic slide can be unlocked to slide laterally from behind the three digits (see picture). The acrylic slide accommodates three 5 volt bulbs, each in its own compartment.
To enable the backlighting to function requires two wires (positive & negative/common) to be connected to the appropriate connection on the rear of the trip indicator, and then to a 5 volt power supply. The amperage draw from the three bulbs is minimal. The wiring should be run through the yoke and down the control column so that it comes out at the bottom of the column.
In the aircraft, the backlighting for the trip indicator is connected to the panel light knob located on the center pedestal. This enables the backlighting on the trip indicator to be turned on and off or dimmed.
Final Call
The trip reminder indicator is but a small and unobtrusive item, however, it’s often the small things which add considerable immersion and enjoyment when using the simulator. The trip indicator is also an OEM part that can be very easily installed to a reproduction yoke with minimal experience in fabrication and wiring.
Glossary
OEM - Original Equipment Manufacture.
BUO0836A Joystick Controller card with wires from the string potentiometer (ailerons)
Nearly every flight simulator has hardware devices that need to be connected to the server computer, whether it be to control the buttons and levers on the throttle quadrant, flight controls, or any other add-on device.
Most enthusiasts can recall a time when they experienced a problem with a hardware device. Perhaps the device couldn’t be calibrated, or when calibrated, the settings were not maintained. Worst case scenario was the device didn’t function and wasn’t recognised by the computer. Many of these potential problems can be minimised by ensuring that the firmware on the card is the latest version release.
In this article, I’ll discuss how to update the firmware the BU0836A 12-Bit Joystick Controller card. The same process can be completed to also update the Button Box BBI-32 or 64 card. Both cards are manufactured by Leo Bodnar Electronics.
Background
To connect a device to the computer, so that it can device can be recognised by Windows (and subsequently ProSim737 and flight simulator), requires an interface card of some description.
Often, there isn’t much thought to addressing the firmware for the selected card. The premise is if it works leave the card alone, and often this is the case, until you purchase replacement computer, upgrade your operating system, or install updates to the operating system. Then, all of a sudden telltale symptoms emerge such as calibration issues, or in the worse case scenario, the computer fails to recognise the card.
Firmware
Any advanced interface card requires firmware. The firmware at its simplest, is a basic set of instructions to enable the card to communicate with the computer’s operating system (think double helix, chromosomes and DNA).
When a card is purchased, the firmware is usually up-to-date so that the card will function with the latest operating system. However, with time many aspects relating to the computer change (hardware, drivers, operating system, etc). However, rarely is the firmware on the card updated. Some manufacturers don’t update the firmware; instead preferring to sell another card. However, a reliable manufacturer will nearly always offer upgraded firmware, from time time, especially after a period of time in which there has been major evolutionary computer change (for example, WIN XP/7 to WIN10).
At the time of writing, the latest release for the BUO086 card was Version 1.26.
Screen grab of the User Interface from the HID flash tool
Upgrading Firmware (flashing)
The process of upgrading the firmware on either of the above-mentioned cards is called ‘flashing’, and if done correctly is a straightforward process.
Prior to a card being flashed, it’s necessary to download (from the Leo Bodnar website) the HID flash tool and the firmware versions for the card.
The flash tool is a standalone program and is used to read any Leo Bodnar card connected to the computer. Once a card has been read by the software its firmware version number can be ascertained.
Important Point:
The latest version of the firmware for the BU0836A and BBI cards, and the HID flash tool, can be downloaded from the Leo Bodnar website (towards bottom of page).
Important Suggestions:
Do not install the HID flash tool to the computer used by flight simulator. Rather install the program to another computer. Disconnect the card requiring flashing from the flight simulator computer and reconnect this card to the second computer.
Only connect one card at a time to the computer. Looking at multiple cards simultaneously can be confusing, and you may inadvertently ‘flash’ the wrong card.
Always try and use the shortest USB cable possible when flashing a card.
How To 'Flash'
In this example, we will discuss upgrading the firmware to a BU0836A Joystick Controller card. The process is identical for the BBI 32/64 cards. As this article is quite short, including diagrams is difficult. Therefore, a copy of the instructions including screen grabs can be downloaded in the Documents Section.
1: Download the HID flash tool and firmware version zip files from the Leo Bodnar website and unzip the files to your desktop.
2: Connect the Leo Bodnar card to the computer and open the HID flash tool as Administrator (mouse right click/open). The software will open at the User Interface that displays various information for the selected card. Take note of the firmware version number. If it’s the latest firmware, then there is no need to flash the card (unless you suspect a problem with the firmware).
3: If more than one card is listed, select the correct card and click the 1. Bootloader tab. This will place the card into flash mode. The interface will display the word boot or bootloader.
4: Click the 2. Browse file tab and navigate to where you downloaded the various firmware versions. Select the correct firmware upgrade version. The firmware is documented as .bin files. I am told that all the bin files are identical, other than the number (more on this later).
5: Once the file is selected, click 3. Flash firmware. The firmware will be flashed to the new version.
Important Points:
If it’s not possible to update the firmware (old or damaged card), then the User Interface will indicate the card is still in boot or bootloader mode. In this case, an updated card will need to be purchased.
Renaming Cards
if you use mulitple cards. Flashing can be a good way to change the name of the card to avoid confusion when looking at the card names in ProSim737. Therefore, in Point 4 above, if you use .bin3, the card will be renamed to BU0836A_3 and if you choose .bin7, the card name will be BU0836_7 (and so forth).
Calibration Settings
It’s not uncommon for some calibration settings to be lost when a card is flashed. Whether the settings are lost, depends upon how the card was used in the first place. It's very likely the various axis will require re-calibration (ailerons, elevators, trim wheel and rudder), however, button settings should remain stable (because buttons are on/off and are connected to the terminals on the card).
Final Call
Computer hardware, operating system, and Windows updates can cause problems with various interface cards, especially if these cards are dated. Fortunately, many manufacturers offer firmware that can update the card to enable it to operate flawlessly with a new up-to-date system.
Additional Information
Every flight simulator uses input devices, and these devices must be initially registered and calibrated in the Windows Operating System, prior to advanced calibration in ProSim737 or FSUIPC.
Occasionally, the User Interface used to register and calibrate the devices fails or crashes. One potential reason for the interface becoming unresponsive, can be caused by Windows 10 updates, that are automatically downloaded and installed to your computer.
While most updates are benign, some will tamper with settings that otherwise were thought to be ‘set in stone’.
In this article, I’ll discuss how the corruption of the joy.cpl file can lead to problems when attempting to register and calibrate joystick controllers.
Note that I use the word input device, game controller, joystick controller, and hardware device interchangeably. Also be aware that the joy.cpl file is used in all late Windows operating systems (XP onwards).
Background
Flight simulator uses several hardware devices. A basic list of the most commonly used is listed below:
Flight controls (aileron, elevators, steering tiller, rudder).
Yokes (buttons and elevator trim).
Throttle Quadrant (buttons, flaps lever, speedbrake lever, thrust levers, cut-off levers, parking brake).
Often, but not always, the items mentioned above are connected to the computer by a Leo Bodnar Joystick Controller or Button Box card (BU0836A and BBI-64 or similar). These cards must be registered, and the connected potentiometers calibrated in Windows, prior to more advanced calibration in ProSim737 or FSUPIC.
Registration and calibration occurs in the Windows Joystick Calibration User Interface (Game Controller Interface).
It's often easier to think of calibrating controls as a two-stage process - Primary Registration and Calibration (in Windows) and Secondary Calibration (in Prosim737, flight simulator, or FSUPIC).
Joystick Calibration User Interface displaying opening menu and calibration menu
Registration and Calibration (Primary Calibration)
By way of an example, let’s assume a yoke is being connected to the computer via a Leo Bodnar BU0836A 12-Bit Joystick Controller card. The movement of the ailerons and elevator (potentiometers) will need to be initially registered and calibrated in Windows.
To begin the registration process, open the Joystick Calibration User Interface and follow the prompts. During the registration and calibration process, each of the end points for the movement of the potentiometer will be recorded, and an axis assigned to the aileron and elevator. Initial calibration of each axis then occurs. This information is saved into a file called joy.cpl.
Important Point:
Calibration of any axis must involve moving the hardware device as far as possible (left, right, forward or backward). This ensures that the full range of movement from the potentiometer is recorded during the registration process.
A .cpl file is a .DLL file that stores information for other programs to access. It’s part of the game controller applet and creates an entry in the Windows registry. I don’t want to dwell any longer than necessary on the Windows infrastructure, as this information is readily available from the Internet.
Handy Shortcut:
There are several ways that the User Interface can be accessed: press 'WIN key and R' and then type either ‘joy’ or 'joy.cpl' into the search bar. Another way is to type ‘joy’ or 'joy.cpl' directly into the Cortana search bar (Windows 10).
Corruption of joy.cpl File.
Initially you may not realise there’s a problem, until you discover it’s not possible to calibrate a device accurately in ProSim737 or in FSUPIC. Or, if registering a new hardware device, the registration and calibration fails. Corruption of the joy.cpl file will usually cause the Game Controller Interface to crash.
How the joy.cpl file becomes corrupted is unknown (by me). I’ve read that Windows updates to sound drivers can sometimes cause an issue. However, when I recently experienced a problem when attempting to register a new joystick controller card, removing and replacing the sound drivers didn’t rectify the problem.
The Solution
Thankfully, the solution to this problem is relatively straightforward. The joy.cpl must be deleted and replaced with a fresh copy.
Important Points:
The corruption of the joy.cpl file is one of the most common reasons for registration and calibration problems, however, it may not be the only reason.
While Windows 10 updates can cause corruption of the joy.cpl file, there are other reasons that may cause this file to be corrupted.
Screen grab of the Sytem32 folder showing joy.cpl file
How to Repair the joy.cpl File
Rectifying the problem is a two-part process involving deleting the joy.cpl file and replacing it with a fresh copy (non-corrupted) copy.
The joy.cpl is located in the Windows System32 folder (C:\Windows\System32).
Each computer system is slightly different, and depending on the file’s protection status, deleting the file may be difficult. When attempting to delete this file, always log in as Administrator.
If the file still can’t be deleted, a standalone unlocking program will be required. As the name suggests, this program ‘unlocks’ the file (or any other file selected) so that it can be deleted. There are several free unlocking programs available from the Internet. I used a program called UnLocker.
Install UnLocker to the computer and follow the prompts after which the joy.cpl file should be able to be deleted.
Next, open the SysWOW64 folder (C:\Windows\SysWOW64). Scroll downwards and find the file joy.cpl file. This is a copy of the file keep by Windows. COPY this file and paste it into the System32 file.
After this has been done, registration and calibration of any hardware device should be possible.
Important Points:
It’s standard practice to always make a copy of any file prior to deletion (so you can rollback if necessary).
Always COPY the file from the SysWOW64 folder. NEVER cut and paste.
When you replace the joy.cpl file, any settings previously held in registration may no longer exist. If this occurs, registration and calibration will need to be done again for ALL hardware devices.
Backup Configuration Settings
The file that contains the configuration settings is the joy.cpl.
This file contains the information Windows needs to be able to load the settings obtained during Primary Calibration. This file should be backed up.
Important Point:
If a problem develops at some point, it's an easy matter to replace the joy.cpl file with the backed up copy. if the problem persists, then replacement of the file (from the SysWOW64 folder may be necessary).
Although Secondary Calibration has not been addressed in this article, it's recommended to backup these settings (included for completeness). Recommended files to backup.
C:\Users\Your_Name\AppData\Roaming\Lockheed Martin\Prepar3D v4\Controls\Standard.xml, controls.xml and/or joysticks.xml
P3Dv4\modules\FSUIPC.ini
Prosim737\config.xml (located in ProSim737 main system folder)
C:\Windows\System32\joy.cpl.
Final Call
Not being able to register a hardware device in Windows can be frustrating and time consuming. The registration and calibration information of any hardware device is recorded in the joy.cpl file. If this file is corrupted, initial registration and calibration of hardware devices won’t be possible. Prior to troubleshooting elsewhere, the first point of call should be to delete the corrupted file and replace it with another copy.
OEM NG style thrust lever
The throttle quadrant for many enthusiasts is the ‘holy grail’ of the simulator, and many individuals strive to ensure that the throttle operates as close as possible to its real world counterpart.
The automated systems in the 737 aircraft drive the movement of the thrust levers in a coordinated manner, and it’s the accuracy, speed, and synchronised movement that enthusiasts try to replicate.
Historical Context
Individuals often use Leo Bodnar Joystick cards, PoKeys, Arduino, and Phidget Advanced Servo cards to interface the throttle quadrant (and other hardware) with some using SIOC (a programming language) to connect propriety throttle quadrants. Calibration, more often than not, was done via FSUPIC, or in a rudimentary way through ProSim737.
Although the throttle quadrant functioned, the position of the levers didn’t match the correct position for the commanded thrust (%N1), and the thrust levers would often be offset against each other and not move in a synchronised manner. These shortcomings lead to the throttle being used only in ‘manual mode’, as the feedback from the software to the throttle didn’t generate consistent and reliable results.
Two innovations have changed this – the introduction of Direct Calibration in ProSim-AR, and the development of the Pololu Jrk Interface Card.
In this article, I’ll explain how to the calibrate the thrust levers using Direct Calibration in ProSim737. I’ll also show you how to initially calibrate, and then fine-tune the Pololu Jrk card, to enable seamless integration with ProSim737. Finally, I’ll discuss some advantages that using a Pololu card brings.
Important Point:
The calibration settings displayed in the various figures (Figures 1-5) are specific to one simulator. The Pololu card settings in your simulator will be similar, however, some settings will be different because of subtle differences in the hardware being used.
ProSim-AR - Direct Calibration
ProSim-AR enables direct calibration of the various flight controls and surfaces directly within ProSim737. This has been inline with their philosophy of trying to keep everything in-house (homogeneous) within ProSim-AR. This not only enables ProSim-AR to maintain control of how the calibration process occurs, but it also aids in troubleshooting should a problem occur.
Direct Calibration is a step forward in keeping ‘everything under one roof’ as opposed to using FSUPIC or another programming language to connect aircraft-related assignments. It’s possible to use direct calibration for the: throttle levers, flaps lever, tiller, speedbrake, aileron, elevator and rudder.
On a side note, Direct Calibration is one of the strengths of ProSim-AR, in addition to built-in native support (via their SDK and generic driver) for various interface cards (which includes the Pololu card).
Pololu JrK Interface card
Pololu Jrk Interface Card
The Pololu Jrk Interface card is a powerful and highly configurable 12v12 brushed DC motor controller, that provides a stable and robust solution to interface the automated movement of the thrust levers in a simulator environment. Not only are the cards small, but they have been trialled extensively in robotic assignments; NASA uses an upmarket version of the Pololu JrK card to control aspects of the Mars Lander.
The card comes packed with a number of advanced features that enable you to tweak the interaction of the card with ProSim737 which, when combined with a quality 12 volt DC motor and string potentiometer will guarantee higher accuracy and better performance than when other calibration methods are used.
Using ProSim737 and a Pololu Jrk Card to Calibrate Thrusts Levers 1 and 2
The engineering required to enable movement of the thrust levers is comparatively simple.
Each thrust lever is connected with a string potentiometer that in turn connects with a Pololu JrK card. The Pololu card then connects directly to the computer by a USB connection. This creates a closed loop system in which the Pololu card reads the movement of the potentiometers and sends this information to ProSim737 and then to flight simulator.
Obviously, two Pololu cards and two potentiometers are needed; one for each thrust lever, and the calibration of each thrust lever must be carefully done to enable both levers to move together in unison. Additionally, two 12 volt DC motors are needed to provide the power to move the thrust levers.
To connect and calibrate a Pololu JrK card requires three steps (in sequential order):
(i) Download and install the Pololu software;
(ii) Turn on Pololu support in ProSim737 (Configuration/Drivers);
(iii) Configure the initial settings in the Pololu Configuration Utility (PCU);
(iv) Calibrate the thrust levers in ProSim737 (Configuration/Levers); and
(v) Fine-tune the calibration in the Pololu JrK card using the Pololu Configuration Utility (PCU).
Once Pololu support has been selected in ProSim737, the Pololu card will be read automatically by ProSim-AR, and the calibrated settings sent to flight simulator.
Important Point:
Initial configuration in the Pololu card (iii) must be done prior to calibrating the thrust levers in ProSim737 (iv).
Subtle Differences (Hardware)
Every throttle quadrant is different as we use different hardware, potentiometers, and DC motors. It’s important to understand that, subtle differences in the hardware used in the throttle quadrant, will affect which settings are used to configure the Pololu card.
The following may have a direct effect on the accuracy, speed, synchronisation, and movement of the thrust levers.
(i) Type of 12 Volt DC motor used;
(ii) Variable output between DC motors;
(iii) Type of potentiometer and the manufacturing variance (+/-) between units;
(iv) The friction generated by each of the thrust levers; and,
(v) The manufacturing variance (+/-)between each of the Pololu cards.
The type of potentiometer used will make a difference to how accurately the Pololu card can read the movement of the thrust levers. If an inexpensive linear potentiometer is used, then the accuracy will continually degrade as the carbon trail on the potentiometer is slowly destroyed. This will lead to frequent recalibration and fine-tuning of the settings. Using a string potentiometer will resolve this issue as contamination leading to loss in calibration is minimal. Use of a Hall sensor will deliver an even greater degree of accuracy (as these sensors are extremely accurate), although it’s debateable to exactly how much more accuracy will be achieved in the movement of the thrust levers, and whether this will be noticed.
High-end string potentiometers and Hall sensors are often used in the medical industry where the tiniest input movement needs to be accurately measured. In comparison, the movement of the thrust levers (input) is quite rough.
Performance can also be affected by the type of 12 volt DC Motor used. If the motor has an amperage either too high or low, or the incorrect gear ratio, the thrust levers may be over or under powered, and no matter what finesse in calibration, the results will be less than optimal.
Also, depending on the type of throttle you’re using, the friction caused by the thrust levers moving will also be different; some levers move relatively easily while others require additional torque from the DC motor to move.
Interestingly, if you’re using an OEM throttle, there may also be differences between throttle unit builds, as each throttle quadrant is manufactured to be within a range of specific tolerances (manufacturing variance). For example, the friction needed to be overcome to move the thrust levers is often different between throttle quadrants, and even respective levers on the same quadrant.
RAW data from thrust lever 1 during automated flight. The upward and downward spikes signify major departure from acceptable operation. The red line demonstrates how the spikes can be flattened when a Pololu card is used
Calibration of the thrust levers in ProSim737 without using a Pololu card does a reasonable job, however, the output is often quite rough – think of a graph with lots of upward and downward spikes.
For consistent smooth operation the spikes shown in Figure 6 must be smoothed down. A Pololu card enables fine-tuning of this output to achieve a consistent and repeatable output
Installing the Pololu JrK Card Software and Initial Configuration
Although ProSim-AR will automatically read the Pololu card, you’ll still need to install the Pololu software to enable access to the Pololu Configuration Utility (PCU).
Two Pololu JrK cards installed to Throttle Interface Module (TIM). The compact size of the cards is readily apparent. These cards deliver a big ‘punch’ for such a small size
After downloading the software from Pololu, open the ZIP archive and run ‘Setup.exe’. If the installer fails, you may have to extract all the files to a temporary directory, right click ‘Setup.exe’, and select ‘Run As Administrator’.
The installer will guide you through the steps required to install the Pololu Jrk Configuration Utility, the JrK Command-line Utility (JrkCmd), and the JrK drivers on your computer.
Once the software has been installed, there should be an entry for the JrK in the ‘Pololu USB Devices’ category of the Device Manager. This represents the card’s native USB interface, and it is used by the configuration software.
The software can be downloaded directly from the Pololu website.
To read the Polulu user guide: Pololu JrK User Guide.
Recommendation:
Create a shortcut to the Pololu Configuration Utility (PCU) and save this shortcut to your desktop or menu system. This will enable quicker and easier access to the utility.
Limitation
For brevity and simplicity, I haven’t discussed every configuration setting in the PCU. Instead, I’ve included several screen captures (Figures 1-5) that show the various configuration settings for reference. These settings should provide a benchmark to enable you to configure the card.
Notwithstanding this, I have enlarged on the two most important settings in the PCU that have a direct influence on the accuracy, and synchronised movement of the thrust levers.
Confirming the Pololu Card Connection
After the initial configuration settings in the Pololu card have been configured, it’s a good idea to test the card’s functionality to confirm connection with ProSim737. This is done by opening the Pololu Configuration Utility (PCU) and setting a manual target speed (Figure 1). To engage the target speed, select ‘Apply’.
Pressing ‘Apply’ will command the card to determine the position of the thrust lever as indicated by the potentiometer. If the thrust lever is not at the same position on the throttle arc as indicated by the settings in the PCU (and it probably won’t be), the thrust lever will move to the commanded position. If this movement occurs, it’s a good sign that everything is functioning correctly.
Calibrating Thrust Levers in ProSim737
Assuming everything is working, the next step is to calibrate the thrust levers in ProSim737.
Calibrating the movement of the thrust levers is comparatively straightforward. Each thrust lever must be calibrated independently of each other, otherwise both levers will not move in unison when the automation (aircraft autopilot) is selected.
(i) Enable Pololu support in Configuration/Drivers tab in the ProSim737 User Interface;
(ii) Open the Configuration/Levers tab and assign for each throttle lever the Pololu input and output;
(iii) Select the appropriate Pololu card for the analogue input and select ‘Feedback input’(1);
(iv) Select the appropriate Pololu card for server output and then select ‘Motor output’(1); and,
(v) Move the virtual sliding tab with the mouse (you should see the respective thrust lever moving).
(1) Located in adjacent drop down box.
To calibrate each thrust lever the virtual sliding bar is moved with the mouse device. To register the position the ‘Min’ and ‘Max’ is selected.
Slide the bar until the physical thrust lever rests in the idle position (the physical thrust lever should move as you slide the bar). When the thrust lever is in the idle position select ‘Set Min’. Next, move the virtual sliding bar until the position of the physical throttle lever rests in the fully forward position. When it does select ‘Set Max’.
For calibration to occur, the minimum and maximum positions must be registered. This process must be completed for both thrust levers.
Important Points:
On some set-ups the ProSim737 software reads the throttle movements backwards. In other words the position of the thrust lever will move in the wrong direction. If this occurs, reverse the order - press ‘Set Max’ instead of ‘Set Min’ and ‘Set Min’ instead of ‘Set Max’.
Calibration occurs when the virtual sliding bar is moved with the mouse device. Calibration is NOT done by physically moving the thrust levers.
To improve accuracy, select ‘Min’ and ‘Max’ only when the physical thrust lever has reached the end of its movement cycle. This task may need to be done a few times to ensure the most accurate position is registered by the calibration process.
Ensure the option ‘closed loop autothrottle’ is NOT selected within the ProSim737 MCP software (right click the virtual MCP to open the MCP Config menu.
It’s recommended to use string potentiometers or Hall sensors to register the incremental movements of the thrust levers. These will provide a greater degree of accuracy.
Always calibrate the thrust levers in ProSim737 prior to fine-tuning the Motor and PID in the PCU Interface.
It’s at the discretion of the user to calibrate and fine-tune the Pololu card to a level of accuracy they believe is a reasonable compromise between the position of the thrust levers on the throttle arc, and the speed at which the thrust levers move.
Fine-tuning Using The Pololu Configuration Utility (PCU) Tabs
To fine-tune the outputs from the throttle quadrant, the PCU must be opened. The two tabs that are used to determine the accuracy, position, speed, and synchronisation of the thrust levers are the Motor and PID tabs.
The Motor Tab in the PCU (Figure 4) can be used to alter the current (amperage) and the duty cycle. Both settings affect the output of the motor (which in turn alters the speed that the thrust levers move).
If the motor has an amperage either too high or low, then the speed that the thrust levers move at, may either be too slow or too fast. Furthermore, DC motors often exhibit manufacturing variances (+/-)and it’s common to have 2 identical motors with slightly differing output.
If the output is not equalised between the two motors, the position of the thrust levers will be staggered and synchronisation between each of the levers won’t be possible. Likewise, a different power output may be required to overcome the internal friction of the thrust lever, to enable movement of the lever to occur, .
Tweaking the motor duty cycle will help eliminate these differences enabling synchronisation of the thrust levers.
The PID Tab in the PCU (Figure 3), an acronym for proportional coefficient, enables in-depth fine- tuning to be applied to the already completed calibration done in ProSim737.
Depending on the power (torque) of the DC motor and the hardware used in the throttle quadrant, the thrust levers may jitter (backward and forward movement when a constant %N1 is set). To eliminate jitter, the PID is fine-tuned until a happy medium is discovered.
Consistency and Reliability
For the most part, Pololu Jrk cards are manufactured to a high quality and are very reliable; you shouldn’t experience a problem with a card. Even so, there may be manufacturing variance (+/-)between respective cards. However, because of the nature of the card, any subtle differences in output can easily be controlled through fine-tuning.
The above said, the calibration of the thrust levers includes many variables that are interrelated, and to achieve consistent results, the components that provide information to the card, in particular the potentiometers and DC motors, must be of the highest quality.
Important Point:
If something doesn’t work as expected, try again using different variables.
Advantages Using a Pololu JrK Card
The benefits of using Pololu Jrk cards cannot be underestimated.
(i) Direct support (reading of card) by ProSim-AR;
(ii) Small size enabling mounting almost anywhere; and,
(iii) Fine-tuning and increased accuracy through use of the PSU User Interface.
Will I Notice A Difference Using a Pololu JrK Card
The question frequently asked is: ‘will I see a difference if a Pololu card is used’ The answer is not straightforward, as there are several interrelated variables (already discussed). If the calibration is done carefully in ProSim737 and the variables tweaked in the Pololu PCU, there is no reason why there shouldn’t be a marked improvement.
Final Call
Evolution is rarely static, with change being positive, negative or neutral.
Direct calibration has enabled greater accuracy in calibrating the various control surfaces within ProSim737 and, in concert with using an advanced card such as the Pololu JrK card, has been a evolutionary step forward. This has lead to greater accuracy in the position of the thrust levers on the throttle arc, and almost perfect synchronisation, when automation is selected.
Further Information
This is but a short introduction to calibrating the throttle quadrant (thrust levers) directly within ProSim737 using the Pololu Jrk interface card. For further information concerning the Polulu Jrk card and it’s use with ProSim-TS navigate to the ProSim737 forum and search Polulu. The Polulu website is also worth reading at Pololu.
Acronyms and Glossary
Manufacturing Variance (+/-) – This is where identical items, although appearing exactly the same are very slightly different. Usually the tolerance is so small that it’s indiscernible. However, manufacturing variance in electronics often is the reason why some parts function and some fail soon after first use. An acceptable tolerance will be defined at the point of manufacture. Usually, if an item requires a higher (tighter) tolerance this leads to a higher manufacturing and purchase price. Often, but not always, there is a direct relationship between the price paid for an item and the reliability and longevity of that item.
MCP – Mode Control Panel
PCU – Pololu Configuration Utility
Throttle Arc – The curved piece of aluminium that the thrust levers move within.
Figures 1–5 display the settings for each of the tabs in the Pololu Jrk Configuration Utility (PCU). Note that these settings are generic to all throttles, however, the variables will differ slightly depending upon hardware used.
Engines, landing gear, spoilers and drag all create noise and vibration. To ensure an immersive environment is created, these sounds (and others) must be replicated as closely as possible to the real sound (Ian Gratton from Sutton-n-Craven, North Yorkshire, England, JET2 Boeing 737, G-GDFY, 'Jet2 Kefalonia' (25453408186), CC BY 2.0)
The definition of immersion is a perception of being physically present in a non-physical world. This perception is created by surrounding the user in images, sound and other stimuli that provide an engrossing total environment.
When this is done correctly, the illusion is complete. However, the immersion effect is downgraded when something doesn't replicate or mimic its real-world counterpart effectively.
Flight simulator enthusiasts go to exuberant lengths to create the illusion of flight. Purpose built flight decks, aircraft shells, real aviation equipment and stunning external visuals all add to the immersion effect. But, what about sound – in particular realistic aircraft, cabin and environmental sounds.
SimSounds
SimSounds is a small standalone program developed by Thomas Langenkamp in Germany. The design of the program is very simple in that it enables you to preselect and configure a number of add-on sounds that are often missing in Flight Simulator. This is in addition to playing airline cabin announcements and cabin calls at pre-defined phases in a flight.
By its inclusion of airliner cabin announcements, SimSounds has targeted the airliner market (in particular Boeing and Airbus). However, there is no reason why SimSounds can't be used for general aviation aircraft and other airliner types.
To increase immersion further, several sounds used by SimSounds can be sent to Butt-Kicker to generate vibrations when a particular sound is played.
SimSounds can be configured to work alongside several avionics suites and other programs such as ProSim-AR (737 & A320), Sim Avionics, PMDG (NGX), P3D and FSX.
Review Limitations
The software generates numerous sounds, and the conditions in which the sounds are played is quite exhaustive. To delve into each sound and occurrence condition would take longer than one article.
Therefore, I will concentrate on the main aspects of the software that are of particular relevance to the flight deck builder. I will also include a few screen captures of the program’s User Interface which is more or less identical across all pages. This review will not include how SimSounds interacts with Butt-Kicker. (I do not own or use a Butt-Kicker).
This review addresses SimSounds V3.1
If you wish to read other user reviews of SimSounds, I suggest you navigate to SimMarket. A video created by the developer can also be viewed on U-Tube
What Does SimSounds Do
In essence SimSounds provides the following:
(i) Cabin crew announcements (automatic phase flight detection for cabin announcements);
(ii) Cabin calming mood music;
(iii) Aircraft sounds (some speed dependent);
(iv) Cabin sounds;
(v) Environmental sounds (some speed dependent); and,
(vi) Sounds that are compatible for use with Butt-Kicker (vibrations).
Let’s examine some of these sounds more closely.
Cabin Announcements (crew)
A prerecorded cabin announcement (CA) and cabin intercom call (CIC) will play during the following flight phases:
(i) CA: Boarding complete;
(ii) CA: Welcome with flexible Captain's name and dynamic local time detection;
(iii) CA: Safety instructions;
(iv) CA: After takeoff information;
(v) CA: Cruise (service and duty free);
(vi) CA: Seat belt sign on during cruise;
(vii) CA: Decent information;
(viii) CA: Approach information (placeholder only);
(ix) CA: Landing information (placeholder only);
(x) CA: After landing (with dynamic airport detection based on useable airports);
(xi) CA: Parking Position;
(xii) CIC: 'Passengers fastened'; and,
(xiii) CIC: 'Cabin is ready'.
The nationality and sex of the voice is selected from the User Interface: English, French, German, Dutch or Portuguese. English and German are the default languages, and other language packs (crew packs) can be purchased separately. There is also an option to add your own voice (prerecorded .wav file).
The Approach and Landing information (viii & ix) will only be played for preinstalled airports (at the time of writing there are 92 defined airports worldwide that can be used). SimSounds automatically detects the airport in use, and provided the option is selected in the User Interface, the airport name will be used in all airport-related cabin announcements.
The cabin announcements and intercom calls are automatically generated and are triggered by the aircraft’s phase of flight (SimSounds refers to this as 'Automatic Flight Phase Detection'). There is no calibration or setup required for this to occur. The logic a has been embedded into the program.
Aircraft Sounds
The following aircraft sounds, some which are speed dependent, are included:
(i) Roll and wheel bump sounds for main gear and nose wheel (speed dependent);
(ii) Touch down sounds for main gear and nose wheel (vertical speed dependent);
(iii) Landing gear up sound;
(iv) Landing gear down sound;
(v) Falling rain sound (speed dependent);
(vi) Wind sound (speed dependent);
(vii) Flaps sounds (speed dependent);
(viii) Opening and closing front door sounds;
(ix) Turbulence;
(x) Engines;
(xi) Reverse thrust (engines);
(xii) Tail Strike;
(xiii) Parking Brake activation and deactivation;
(xiv) Spoilers (speed brakes);
(xv) Auto brakes lever sound (as speed brakes deploy on landing); and,
(xvi) Wind sound enhancement when landing gear is deployed.
You can individually select these sounds from the User Interface. Furthermore, speed dependent sounds have the flexibility of being preset to only become audible when a specific speed has been reached. All sounds have independent volume control.
Cabin Sounds
Cabin sounds include the following:
(i) Cockpit fans;
(ii) Doors opening and closing;
(iii) Seat belt chime;
(iv) No smoking chime;
(v) Passenger background noise and boarding (mainly low talking and scuffling) ;
(vi) Cabin calming music (boarding, after landing and parking);
(vii) Clapping sound; and,
(viii) Screaming sound.
For the seat belt and no smoking chime (iii & iv) to function correctly, it’s necessary to define a FSUIPC offset (discussed later in this article).
For the cabin calming mood music (vi) to play you will need to correctly map and configure the doors of the aircraft. Failure to do this will result in the music not playing.
The clapping and screaming sound (vii & viii) is an audio of people clapping or screaming. Both sounds and their volume can be adjusted to play following a landing at a specific vertical speed (V/S).
Flexibility - Independent Volume and Speed Dependency Functionality
It’s important to note that SimSounds is VERY flexible in how, when, and at what volume any sound is played. Each sound has independent control enabling the user to turn the sounds on or off, alter the sound’s volume, or adjust when the sound will become audible (sounds with speed dependency).
Speed dependency is when a sound will play only when the simulator aircraft reaches a certain airspeed or ground speed. In the User Interface for the specific sound, a sliding tab is used to preset the speed at which the sound will play. Similarly, another sliding tab will allow you to preset the volume of the sound. It’s this flexibility in how and when sounds are played that makes SimSounds rather unique.
User Interface / Aircraft Sounds / Wind. The active button is selected, meaning that the sound is active. The 'wind' sound file will play when the ground roll of the aircraft reaches 80 knots (the timing which the sound is played is linked to the ground speed of the aircraft). The sound will then slowly increase in volume, reaching the maximum volume (as indicated by the maximum volume % slider tab) at 201 knots)
Installation, Setup and Before Purchase Evaluation
The Installation is VERY easy. Once downloaded, the program is installed to either one or more computers (server and clients). FSUIPC and WideFS is required if you wish to run SimSounds from one or more client computers.
The program is standalone and can be installed anywhere on your computer system. It’s not a requirement to install the software to your main C Drive; it can easily be run from the desktop or from a second drive. If required, a shortcut can be made from the executable file, or the command line can be added to a batch file (for automatic opening of all programs with one mouse click).
SimSounds does not require extensive calibration and setup to function. With the exception of indicating what sounds are to be played and their parameters, the following will need to be done from the main page of the User Interface:
(i) SimSounds/License Key – Enter license key (after purchase).
(ii) Settings/Common – Select either PMDG offsets, PS737/A320, or leave blank.
(iii) Settings/Sound Cards – Select sound card for aircraft sounds, cabin sounds and flight deck sounds.
Additionally, for full functionality (music and chimes) you will need to synchronise the door logic to flight simulator and define a FSUPIC offset for the no smoking and seatbelt signs.
A complete and fully functional SimSounds is available as a free download from the SimSounds website. The evaluation period is a generous 30 days.
System Requirements
SimSounds requires the following to function correctly:
(i) An active internet connection;
(ii) Windows 7, 8 or 10 operating system;
(iii) Microsoft Flight Simulator 10 (FSX) or Prepar3D Version 4.1 to 4.5; and,
(iv) FSUPIC and WideFS.
ProSim-AR Users (ProSim737 Avionics Suite)
Thomas (the developer of Simsounds) has worked closely with the developers of ProSim-AR to ensure that the software is 100% compatible with the ProSim737 avionics suite.
SimSounds does not replace the sounds in the ProSim audio folder used by ProSim737, but rather uses its own dedicated folder. However, some sounds are duplicated. Therefore, it’s a matter of choosing which specific sounds (.wav files) you wish to use (select sounds from either SimSounds or ProSim Audio).
For the cabin calming mood music to be automatically played when the aircraft doors are open, ProSim737 users will need to correctly map and configure the doors of the aircraft. The process to do this varies between proSim737 releases.
Similarly, for the seatbelt and no smoking chime to function correctly (when you manipulate a switch), a FSUIPC offset will need to be defined. The offset is defined in CONFIG/MISC menu of ProSim737 using a GATE.
Seat belt sign – FSUIPC offset 8 bit U: 0x341D.
No smoking sign – FSUIPC offset 8 but U: 0x341C.
Program/Software Manual, Help and Updates
The developer has elected to not provide a comprehensive manual. However, a very basic on-line manual and Frequently Asked Question section can be found on the website.
To be frank, I prefer reading a manual prior to using any program. But, considering the program’s flexibility and exhaustive content, writing a manual would be very time consuming and would probably be confusing and counterproductive. This software is very much a ‘hands-on’ learning experience.
To learn what the program can do, you must install the software and experiment with the various sounds and cabin settings.
SimSounds does not have a dedicated forum. However, the developer is very active on the ProSim737 forum and is eager to provide help to anyone needing assistance. He is also open to suggestions and recommendations to improve the software.
Improvements to the software and beta releases are published on the SimSounds website. If the 'check for updates' is selected from the User Interface, the program will alert you to when an update has been released.
Important Point:
The best way to test this program to determine its usefulness is to install the software and trial the various features.
User Interface (UI)
SimSounds is a relatively powerful program and it's control centre is the main page and sub-pages accessible from the menu-style tab system.
The control center of the SimSounds program is the User Interface. The main page displays setup information, current state of buttons and sounds, and pertinent flight parameters. Each of the tabs is interactive which enables individual sounds to be activated ‘on the fly’
SimSounds will always display the main page (front page) of the User Interface. This page (Figure left) is important in that, in addition to providing an interface to enter into the program’s sub-pages, it also displays setup information and various flight parameters. The flight parameters are ‘live’, meaning the parameters are continually updated during a flight.
Also displayed are the active continuous sounds that have been configured to play (continuous sounds play all the time). This is in addition to the current state of the no smoking and seat belt buttons, and the door state. There is also a pause button to pause flight simulator.
Interactive Coloured Tabs
The dozen or so tabs located at the lower right of the main page provide a visual indication to what sounds have been configured to play in SimSounds. These tabs are interactive, meaning that by pressing the tab, the sound can be manually turned on or off, or if the sound is currently playing, it can be cancelled (paused).
Three colours and the use of solid-filled text are used to indicate various sound states:
(i) Neutral (no colour) text solid filled – sound configured to play.
(ii) Neutral (no colour) text not filled – sound not configured to play.
(iii) Blue colour – sound currently playing.
(iv) Pink colour – Sound configured to play, but has been manually turned off (by pressing the tab/button with your mouse).
The use of interactive tabs enables configured sounds to be turned on, off, or paused 'on the fly'.
Sub-pages (User Interface)
Each page is well laid out and easy to follow. I will not explain every page as many are self explanatory.
As an example, we will examine the Aircraft Sounds / Roll page (Figure 1 below).
Aircraft Sounds / Roll Page (an example)
This page has several interactive tabs that align with the top of the main page. Each tab relates to a specific sound.
At the upper left of the page is a check box named ‘active’(on/off). This is where you can either turn the sound on or off.
User Interface / Aircraft Sounds / Roll. The active button is selected meaning that the sound is active (turned on). The 'aircraft roll' sound file will play when the ground roll of the aircraft reaches 12 knots. The sound will then slowly increase in volume, reaching the maximum volume (as indicated by the maximum volume % slider tab) at 97 knots. All the tabs in the User Interface have a similar graphical interface which is very easy to understand and manipulate
The box named 'Sound File' is the location of the sound file that is to be played.
The three sliding blue-coloured tabs are self explanatory. One slider sets the maximum volume that the sound will play at, while the other two sliders relate to speed dependency. One slider is used to set the speed at which the sound will begin to play, and the other is used to alter the speed at which the sound will reach full volume (as set in the maximum volume slider).
The ‘Add’ (so many knots) box enables the user to fine tune the volume of the played sound. For example, the volume (of the 'roll' sound) increases with increasing speed. If you want the 'roll' sound to start earlier, this value can be altered in the ‘add’ box resulting in a higher volume of the 'roll' sound at lower speeds.
Changing Sound File and Location
Any sound or cabin announcement can be replaced with another customised sound or recorded cabin announcement. To replace a sound it’s a matter of replacing the sound in the SimSounds sound folder and linking the new sound file to the software.
To do this, the two boxes to the right of the 'Sound File' box are opened. This reveals a dialogue box that enables you to select a new file location and sound file. The small speaker icon enables the sound to be played to check the volume prior to saving the configuration (‘Apply and OK’).
Important Points:
Any of the pre-selected sounds can be cancelled (paused) from the front page of the User Interface. This is done by pressing the appropriate tab. This can be done ‘on the fly’.
The User Interface is very intuitive and straightforward to use.
Test Mode
The developer has had the forethought to include a test mode in the program (‘Test’). The Test Mode is accessible from the main page and includes a list of all configured sounds. Each sound can be individually played at the configured volume. This is very handy if you want to review (and hear) what sounds you have configured in SimSounds.
Reliability and System Resources
During my testing, the software was very reliable and robust. The software played all sounds as configured and I didn’t experience any drop outs or failure of the software to open correctly (I use a batch file).
SimSounds works out of the box with minimal computer configuration.
Concerning system resources. During my testing, I didn't note any depreciable use of system resources running SimSounds on a server and client computer.
Accuracy of Sounds - Artistic License
There has been a certain amount of artistic licence taken in relation to the accuracy of some of the sounds.
For example, when sitting in the flight deck of a real Boeing 737 aircraft, you cannot hear the flaps move when the flaps lever is manipulated (apart from anything else, there is too much ambient noise in the flight deck). Nor can you hear air whistling, or increased whistling, as the flaps are deployed from flaps UP to flaps 40.
Similarly, you cannot hear the speed brakes (aka spoilers) when they are moved to the up position (you do, however, feel the increased drag).
The use of these sounds should not be seen as a shortfall, as many enthusiasts like to hear these sounds (like they can hear in the cabin), and it’s an easy matter to turn the sounds off in the User Interface if they are not wanted.
Also, bear in mind that SimSounds has been developed for a broad audience. Light aircraft users will want to hear these sounds, as in a light aircraft you will hear the flaps move, and hear the wind whistling over the flap surfaces as the flaps are deployed.
Not all the sounds have been recorded from a real 737; some sounds have been fabricated. For purists, it’s a straightforward process to remove the fabricatedsounds and replace them with genuine sounds.
The following sounds have been recorded from a real Boeing 737:
(i) Wind (without flaps sound);
(ii) Roll sound;
(iii) Bump sound;
(iv) Touchdown sound;
(v) Doors opening sound;
(vi) Doors closing sound;
(vii) Landing gear up sound; and,
(viii) Landing gear down sound.
Sound Configuration (my simulator)
No setup is identical when it comes to sound; what works for one individual may not work for another.
The beauty of SimSounds is that you can run multiple instances of the program and select multiple sound cards. This allows you to select to which speakers the sound is directed, enabling considerable flexibility in generating sound from differing directions. This adds to immersion.
In my simulator, I have two instances of SimSounds running; one from the server and one from client computer I always have the main User Interface open on the client computer and positioned in such a way that it's easily viewable on the client's display along with the instructor station (FS Flight Control). This enables me, if necessary, to cancel (pause) specific sounds. Note that in newer ProSim737 releases the use of the FS Flight Control instructor station is not necessary as ProSim737 has its own dedicated IOS.
Each instance of SimSounds is linked to a dedicated speaker system that is mounted in different areas of the flight deck. This ensures two things. First, that cabin announcements, cabin intercom calls, and mood music (generated by SimSounds) is heard from a different speaker to avionics call outs, and second, the other sounds generated by SimSounds (aircraft, cabin and environmental sounds) are played from a speaker, and at a location, that is different from the speaker that plays the engine sounds.
Location of Speakers
I’m not a big user of cabin announcements. However, when selected, all cabin announcements are played through a dedicated speaker mounted behind the Captain’s seat, while specific speed dependent sounds, such as the 'wheel rolling' sound and 'rolling bump' sound are played through another speaker mounted forward of and under the platform (for the nose wheel landing gear), and behind and under the platform (for the main landing gear).
I also play the variable volume 'wind' sound from a speaker mounted forward of the flight deck (to mimic the wind blowing over the nose of the aircraft).
I particularly like the easily adjustable 'wind' sound, 'nose wheel rolling' sound, and 'rolling bump' sound, which if set to a reasonable volume and speed (speed dependency), greatly improve sound immersion.
Other sounds I use are the ‘clapping’ sound that plays to indicate a landing at a very low vertical speed, and the 'tail strike' sound. The speed dependent 'rain' sound, if the correct volume is configured, is also very realistic.
Another attribute I find useful, is the display on the User Interface of the vertical speed (V/S) at landing. This is useful in determining if a landing has been made within safety parameters.
he Butt-Kicker tab is selected from the main User Interface. When opened, the sub-menu allows various sounds to be activated within the Butt-Kicker program
Butt-Kicker
Although this article does not discuss the butt-kicker functionality, the figure below shows the page used to configure what sounds are used by Butt-Kicker.
Final Call
The use of sound should not be underestimated when trying to create an immersive environment; it’s often the small nuances that a sound brings to a simulation that makes the experience more pleasing and enjoyable.
SimSounds is a small but powerful program that, when setup correctly, greatly enhances the sound capability of the simulator. The program is reliable, robust, seamless in its application, and very flexible in when, and at what volume the sounds are generated.
It’s obvious from the onset, that Thomas has designed SimSounds to encapsulate a number of parameters (sounds, announcements, cabin calls and flight data information) that have previously only been available by using multiple programs. This, and the ability to easily configure a speed dependency sound, is what makes this program worthy of investment.
Finally, the developer of SimSounds is proactive and is open to suggestions on ways to improve his software. The software is available for trial at https://www.simsounds.de/ or purchase at SimMarket.
Flaps lever set to Flaps 30. The throttle quadrant is from a Boeing 737-500 airframe. The flaps lever arc is the curved piece of aluminium that has has cut-out notches that reflect the various flap positions. It was beneath this arc that micro-buttons had been installed
There are several ways to enable the flaps lever to register a particular flaps détente when the flaps lever is moved to that position on the flaps arc.
In the earlier conversion, the way I had chosen worked reasonably well. However, with constant use several inherent problems began to develop.
In this article, we'll examine the new system. But before going further, I'll briefly explain the method that was previously used.
Overview of Previously Used System
In the earlier conversion, nine (9) micro-buttons were used to register the positions of the flaps lever when it was moved (Flaps UP to Flaps 40).
The micro-buttons were attached to a half moon shaped piece of fabricated aluminium. This was mounted beneath the flaps lever arc and attached to the quadrant. Each micro-button was then connected to an input on a PoKeys 55 interface card. Each input corresponded to an output.
Calibration was straightforward as each micro-button corresponded to a specific flaps position.
Problems
The system operated reasonably well, however, there were some problems which proved the system to be unreliable. Namely:
(i) The vertical and lateral movement of the chain located in the OEM throttle quadrant interferred with the micro-buttons when the trim was engaged; and,
(ii) The unreliability of the PoKeys 55 interface card to maintain an accurate connection with the micro-buttons.
Movement of OEM Chain
The chain, which is similar in appearance to a heavy duty bicycle chain, connects between two of the main cogs in the throttle quadrant. When the aircraft is trimmed and the trim wheels rotate, the chain revolves around the cogs. When the chain rotates there is considerable vertical and some lateral movement of the chain, and it was this movement that caused three micro-buttons to be damaged; the chain rubbed across the bottom section of the micro-buttons, and with time the affected buttons became unresponsive.
First Officer side of a disassembled throttle quadrant (prior to cleaning and conversion). The large notched cog is easily seen and it's around this cog that the OEM chain rotates (the chain has been removed)
It took some time to notice this problem, as the chain only rotates when the trim buttons are used, and the micro-buttons affected were primarily those that corresponded to Flaps 5, 10 and 15. The chain would only rub the three micro-buttons in question when the flap lever was being set to Flaps 5, 10 or 15 and only when the trim was simultaneously engaged.
The cog and chain resides immediately beneath the flaps arc (removed, but is attached to where you can see the four screws in the picture).
Although there appears to be quite a bit of head- space between the cog and the position where the flaps arc is fitted, the space available is minimal. Micro-buttons are small, but the structure that the button sits is larger, and it was this structure that was damaged by the movement of the chain (click to enlarge).
An obvious solution to this problem would be to move the chain slightly off center by creating an offset, or to fabricate a protective sleeve to protect the micro-buttons from the movement of the chain. However, the design became complicated and a simpler solution was sought.
To read more about the earlier system: 737 Throttle Quadrant - Flaps UP to 40; Conversion and use.
Replacement System
Important criteria when designing a new system is: accuracy, ease of installation, calibration, and maintenance. Another important criteria is to use the KIS system. KIS is an acronym used in the Australian military meaning Keep It Simple.
The upgraded system has improved reliability and has made several features used in the earlier system redundant. These features, such as the QAMP (Quick Access Mounting Plate) in which linear potentiometers were installed, have been removed.
String Potentiometer Replaces Micro-buttons
Single-string potentiometer enables accurate calibration of flaps UP to flaps 40. The potentiometer is mounted on a customised bracket screwed to the First Officer side of the throttle quadrant superstructure. The terminal block in the image is part of the stab trim wheel system
A Bourne single-string potentiometer replaced the micro-buttons and previously used linear potentiometers. The string potentiometer is mounted to a custom-designed bracket on the First Officer side of the throttle quadrant. The bracket has been fabricated from heavy duty plastic.
A string potentiometer was selected ahead of a linear potentiometer because the former is not limited in throw; all the flap détentes can be registered from flaps UP through to flaps 40. This is not usually possible with a linear potentiometer because the throw of the potentiometer is not large enough to cater to the full movement of the flaps lever along the arc.
A 'string' is also very sensitive to movement, and any movement of the string (in or out) can be accurately registered.
Another advantage, is that it's not overly important where the potentiometer is mounted, as the string can move across a wide arc, whereas a linear potentiometer requires a straight direction of pull-travel.
Finally, the string potentiometer is a closed unit. This factor is important as calibration issues often result from dust and grime settling on the potentiometer. A closed unit for the most part is maintenance free.
To read more about string potentiometers and their advantages: String Potentiometers: Are They Worthwhile.
The end of the potentiometer string is attached to the lower section of the flaps lever. As the flaps lever moves along the arc, the string moves in and out of the potentiometer.
The ProSim737 software has the capability to calibrate the various flap détentes. Therefore, calibration using FSUIPC is not required. However, if ProSim737 is not used, then FSUIPC will be needed to calibrate the flap détente positions.
Advantages
Apart from the ease of calibration, increased accuracy, and repeatability that using a string potentiometer brings, two other advantages in using the new system is not having to use a Pokeys 55 card or micro-buttons.
Unreliability of PoKeys 55 Interface Card
The PoKeys card, for whatever reason, wasn't reliable in the previous system. There were the odd USB disconnects and the card was unable to maintain (with accuracy and repeatability) the position set by the micro-buttons.
I initially replaced the PoKeys card, believing the card to be damaged, however, the replacement card behaved in a similar manner. Reading the Internet I learned that several other people, who also use ProSim737 as their avionics suite, have had similar problems.
Micro-buttons can and do fail, and replacing one or more micro-buttons beneath the flaps arc is a time-consuming process. This is because the upper section of the throttle quadrant must be completely dismantled and the trim wheels removed to enable access to the flaps arc.
Registering the Movement of the Flaps Lever in Windows
The movement of the flaps lever, prior to calibration must be registered by the Windows Operating System. This was done using a Leo Bodnar 086-A Joystick interface card. This card is mounted in the Throttle Interface Module (TIM). The joystick card, in addition to the flaps lever, also registers several other button and lever movements on the throttle quadrant.
Final Call
The rebuild has enabled a more reliable and robust system to be installed that has rectified the shortfalls experienced in the earlier system. The new system works flawlessly.
This article displays links to the majot journal posts concerning the 737 throttle: OEM Throttle Quadrant.
Acronyms and Glossary
OEM - Original Aircraft Manufacture (real aircraft part).
The backbone of the simulator is the avionics suite, and for the simulator to run effectively this software must be reliable, feature rich, and robust.
There are several avionics suites available to simulate the avionics and functionality of the Boeing 737; Project Magenta, Sim Avionics, and ProSim-AR being the most popular. I have not mentioned Precision Manuals Development Group (PMDG), as PMDG is marketed as a desktop simulation not used widely in a hardwired simulation.
Many virtual flyers assume, that when they purchase an avionics suite, the software will replicate all the aircraft systems, be compatible with their computer and simulator hardware, and probably not need to be updated. Unfortunately, this is rarely the case.
In this article, I will discuss the following:
The ProSim User Interface;
The ProSim Version Manager;
Various troubleshooting protocols;
Other potential problems;
Updating the Navigational Database; and,
Updating the Flight Model.
Version 3
This article was primarily written for Version 2.30. ProSim Version 3.00 introduced several new features to the Version Manager which enhance troubleshooting and backing up specific files. Some of the more important changes have been added into this article.
The Reason and Need for Updates
Technology is rarely static, and developers if they are to encapsulate new technology must provide updates to their products. This evolution can be likened to a game of ‘leap frog’; as something new is released, developers ‘tweak’ their software to take into account new technology while (hopefully) still maintaining compatibility with legacy systems.
Another reason for updates is that there is not an avionics suite that completely encapsulates 100% of all systems (and functionality) used in the B737. A possible close exception is PMDG, but as mentioned earlier, this is a desktop simulation (I am not including Level D/Type 7 simulators).
Each company that produces an avionics suite has a specific method to how its software is installed, maintained, and lastly kept up-to-date with improvements, fixes and software upgrades. For example, Sim Avionics beta test changes and improvements themselves (or to a select group of individuals) and then release a version update. This is in contrast to ProSim-AR, who release a beta for client appraisal. Then, after bugs and shortcomings are rectified, release a final release.
ProSim-AR - frequent updates
The avionics suite developed by ProSim-AR for the Boeing 737 Next Generation is feature rich, easy to install and run, and the software is for the most part very robust. The company ‘appears’ to be committed to ensuring that their software operates across a wide range of computer hardware, and interfaces with as many mainstream hardware components as possible (for example, CP Flight, SimWorld, Open Cockpits, Flight Deck Solutions, etc.). In my opinion, the company is very proactive in interfacing with new technology to gain the maximum benefit that new technology brings, which includes increased market share and profitability (for ProSim-AR).
With this in mind, ProSim-AR release updates to their software on a very frequent basis.
Understanding the Basics of the ProSim737 File Structure
It is important to understand the basics to how the ProSim737 file structure is set out, as this will provide guidance to the best way to install an update, and if a problem occurs, troubleshoot.
The ProSim737 suite contains the following modules, located in a folder of the same name.
(i) ProSim737 (main system module);
(ii) ProSim-CDU;
(iii) ProSim Audio;
(iv) ProSim Display;
(v) ProSim MCP (Version 2.30 only);
(vi) ProSim Panel; and,
(vii) ProSim737 Hardware Connector;
NOTE: In Version 3.00 the ProSim MCP module has been amalgamated into the main ProSim 737 main module.
The folders can be installed to either a server (the computer that has flight simulator installed) or any number of clients (computers networked to the server computer). Duplicate instances of the same module with the exception of the main system and MCP module, can also be installed.
When installing duplicate modules (instances) of the same name (for example Captain and First Officer CDU or ProSim Display) to the same computer, do not rename the .exe file. Rather, create a shortcut to the .exe file and rename the shortcut to a specific name (for example, CDU Capt and CDU F/O).
The ProSim737 folder and MCP folder (Version 2.30 only) must be installed to the server computer for optimal performance. The other folders can be installed to the server or client computer, either as single or duplicate instances.
The ProSim737 folder contains the main system module and this is the module that interfaces with all other modules.
The folders can be installed anywhere on the computer, however, it’s not recommended to place them in the same folder (ROOT folder) where flight simulator is installed.
Important ProSim737 Files
Each ProSim737 folder contains a configuration (config) file. The configuration file contains information pertaining to screen position, functionality, IP address, etc. The most important configuration file is located in the main ProSim737 folder. This file, amongst the things, holds the information that relates to specific hardware, functionality and button assignments. All configuration files are named config.xml.
Important files, located in the main ProSim737 folder, are the:
(i) Companyroutes.xml;
(ii) Config.xml;
(iii) ConfigMCP.xml (Version 2.30 only);
(iv) TransitionAltitudes.xml; and the,
(v) Cockpitsetup.xml.
The configuration files are important. These files should be regularly backed up.
Other files that relate to the update process are the updatelog.txt and changelog.txt. The updatelog.txt contains information concerning to the latest update, while the changelog.txt provides a list of changes that has occurred in the various ProSim737 releases.
Important Points:
The most important configuration file is the config.xmlfile located in the main ProSim737 folder. This file contains all information that relates to configuration, customization, and hardware. It should be regularly backed up.
For optimal performance it's recommended to install the main ProSim and MCP module to the server computer.
When installing duplicate modules to the same computer, always create and rename a shortcut to the .exe file. Do not rename the actual .exe file.
User Interface and Version Manager
The User Interface enables you to customise the avionics suite, configure hardware components, update, and troubleshoot problems.
The interface is straightforward to use and I urge you to become familiar with its tab /page layout and content. I will discuss some of the troubleshooting features of the interface later in this article.
Included in the interface is a Version Manager that can be used to update the avionics suite. When connected to the Internet, the Version Manager compares the release date of the currently installed avionics suite to the latest available release.
The Version Manager enables the avionics suite to be updated from within ProSim737. It's accessible from the User Interface (help/updates).
The Version Manager has three tabs: Releases, Add-ons and Pre-releases.
Releases tab will display a list of final ProSim737 releases (along with release information and the date it was available). To install the latest release, or to roll back to an earlier release, you select the install link in the Actions title. This will cause the selected release to download and be installed to your computer copying over (and updating) a previous release installed.
Add-ons tab displays various add-ons that ProSim-AR have made available. An example being the ProSim737 aircraft flight model.
Pre-release tab will display a list of beta releases. Operation is identical to the releases tab discussed above.
One of the advantages of the Version Manager is that it enables you to quickly update the avionics suite to a beta pre-release, final release, or roll backwards to an earlier release. It also provides information concerning the beta release (Release Notes tab), in addition to enabling you to monitor respective updates to the 737-flight model (Add-ons tab).
Three methods can be used to update the ProSim737 avionics suite:
(i) Download the latest release from the ProSim-AR website (standalone requiring installation);
(ii) Download the latest release from the Version Manager (zip file); or
(iii) Download and install from the Version Manager a beta pre-release or final release.
There is no preferred method, however, option (iii) is the easiest way.
Version 3.00 Improvements to the Version Manager
In Version 3.00 additional improvements have been made to the Version Manager to aid in troubleshooting and the backing up of important files.
Opening the main ProSim menu and selecting Options (located beneath Connected Hardware) will open a Configuration File Manager & Mapping page. This page displays the hardware family, type and mapping and whether the hardware is in use or not by ProSim (denoted by the colour).
Highlighting an item (text will change to red) and clicking the mappings section will open an additional table that displays a description of each function and its output port number for that particular interface card. If you click the mappings table number a page opens displaying what function that card is connected.
Finally, at the bottom of the table are two tabs that enable you to create or restore a backup of the config.xml file (discussed in detail later on).
A backup of the file is saved to C:\Program Data\ProSim-AR\ProSimB738\Backup\. The config.xml backup is date named enabling consecutive backups of this file to be made and saved.
Beta Pre-release or Final Release ?
ProSim-AR regularly adds functionality and improvements to their avionics suite via beta pre-releases. A beta pre-release enables users to test their hardware set-up with a release prior to it being finalised. As such, beta pre-releases often have bugs, shortfalls and other problems associated with them.
ProSim-AR have a dedicated web-based forum, and request that beta users provide feedback on a pre-release. This enables issues to be rectified prior to making available a final release via the Version Manager.
The Updating Process
The ProSim737 Version Manager (if used) is smart enough to replace all files within the ProSim737 folder system, with the exception of configuration files and any file ending in .xml (these files are kept intact).
However, if a release is downloaded from the ProSim-AR website, or the ZIP file option is used, then it will be necessary to manually insert the configuration files to their respective folders.
ProSim737 updates in sequence. This means, that after the software has been downloaded, the main ProSim737 module will be installed and run first. Then as each .exe file for each additional module is run, that module will update.
A pop-up box will display 'updating configuration' as each module updates its content and synchronises with the main ProSim737 folder. When an update to a module has been completed, the software will generate the updatelog.txt file (as discussed earlier).
The time taken to update across a network between server and client computers depends upon your network speed; usually less than 30 seconds.
Although theoretically not required, the Scenery Database (config/database) should be checked to ensure it's path is connected to the correct folder in Flight Simulator. It also doesn't hurt to rebuild the database. Rebuilding the Database following an update ensures that the link between the database, ProSim737 and Flight Simulator has not been corrupted.
Important Point:
Configuration files are generated in each folder as the .exe for each module is opened (run).
Customising How ProSim737 Updates
There are three ways that the User Interface can be set-up to update the avionics suite:
(i) Manual updating;
(ii) Ask before updating; and,
(iii) Automatic updating.
The method is customised in the User Interface, accessible from the drop down box (config/configuration/updates). The interface also has a box that an be checked/ticked if you want the interface to monitor when a beta release becomes available; a screen pop-up will be displayed when you open the avionics suite.
Backups and Install from Backup
I recommend keeping a complete copy of each ProSim737 folder from the server and client computer. By backing up the complete folder, you are also backing up the configuration and other important .xml files.
Theoretically, the Version Manager negates the necessity to maintain a backup of ProSim737 (or the configuration file), as the configuration and other .xml files are maintained intact. However, by keeping a complete copy of the last ‘working’ release, it’s easy to ‘change out’ between releases (roll back or forward).
All you need to do is delete the ProSim737 folders from the computer, and then copy/paste the earlier folders to the same locations. All the files are intact and ProSim737 will load whatever release has been installed.
If you don't want to keep a complete copy of the folders and files, then it's also straightforward to roll back to an earlier release by using the Version Manager. The manager will download the selected release from the ProSim-AR server and install it overwriting the newer release on the computer.
My preference is to keep a complete copy the release and copy/paste if you want to roll back.
Automatic Backup of Config.xml File
The Version Manager has a handy tool automated within the software. It will now examine and compare the config.xml file during the updating process. If the file is different between the two copies, the Version Manager will create a back-up copy called config-old.xml.
The auto backup provides a second level of protection to this important file.
Version 3.00 introduced the ability to easily backup and restore the config file. Open the User Interface and select the small arrow (adjacent to options). This will open a second window that examines what interface cards and hardware ProSim is connected with. At the bottom of the page there is a command that enables you to save the config file or restore a backed up config file. The file is saved within the ProSim file structure or you can select a preferred folder.
Important Points:
Always make a backup up your configuration (config.xml) files. The config.xml file is the most important file in ProSim as it records your configuration and various user selected settings.
If downloading and installing a fresh copy of a release from the ProSim-AR website, then the configuration files will need to be manually added to each folder (from your backed up files).
Updates using the Version Manager replace all files within the ProSim737 folder system, with the exception of configuration files and any file ending in .xml.
The Version Manager displays the current release of ProSim737 you have installed.
A good idea to backup a copy of all the ProSim737 folders on both server and client computers. Doing so allows you the option to easily replace a ProSim737 release with an earlier release number.
After running any update, the ProSim737 Scenery Database should be rebuilt.
Troubleshooting Updates
This section is not the ‘Holy Grail’ to resolve all problems. Rather, it’s what should be done prior to requesting help from the ProSim-AR Development Group. Some of the methods used to troubleshoot are quite simple, yet effective.
Occasionally there may be a problem with an update. The update may cause one of the module’s .exe files to loop continually (open/close/open/close), or there may be limited functionality, or perhaps the ProSim737 main module will continually crash.
Recommended Initial Troubleshooting Protocols
Before spending valuable time in advanced troubleshooting, I suggest you check/do the following:
(i) Shutdown all computers and restart;
(ii) Ensure that all modules within all folders on the server and client computers have been updated to the new release (check the update file in the folder or check the release version number by right clicking the screen display and selecting configuration);
(iii) Close and open all ProSim737 modules on the server and client computers;
(iv) Check to ensure that the correct IP address is recorded for each display window opened. To check this, right click the opened screen and select configuration. This will open the screen’s user interface. Check that the correct IP address recorded in the server box;
(v) Check the version of .Net Framework on your client and server computer (discussed later);
(vii) Replace the configuration file (config.xml) in the main ProSim737 folder with a copy of your backup configuration file;
(viii) Delete all ProSim737 folders from your server and client computers and download/install from the ProSim-AR website a fresh copy of ProSim737 (remember to replace the configuration files in the ProSim737 folders to maintain your functionality settings and screen position); and,
(ix) Open the User Interface (config/configuration) and confirm that the correct simulator (ie: FSUPIC, Sim Connect, MSFS) is listed in the options box. Also ensure the enable embedded MCP beta is not selected, all installed I/O modules and software are operational, and the simulator is connected. Furthermore, check that all appropriate drivers have been selected for the add-on components and software you are using (config/configuration/drivers).
Usually problems are resolved by restarting your computer, reinstalling the config.xml file, or reinstalling ProSim737 from a fresh download.
On rare occasions, the configuration file in the main ProSim737 module may have become corrupted during the update process (jumbled and altered assignments). If you suspect a problem with the config.xml file, copy/paste your backup configuration file to the main folder.
Often, the easiest and fastest method to alleviate issues and save considerable time is to DELETE all instances of ProSim737 from the server and client computers and reinstall. Before doing this make sure you have a backup of any files you may wish to keep (configuration files, etc.).
Download the latest release of ProSim737 from the ProSim-AR website. Copy the folders to the same location and add a copy of the respective configuration file to each folder. Then, download the beta release (if required).
A quick word when trying to detect where a problem may be occurring. Always test with a minimal or vanilla setup. By this I mean deactivate on-line weather and winds and do not connect any add-ons other than those installed into the flight simulator platform (P3d, etc). Test with a minimal setup; if everything is OK, then add the next program and so forth.
Advanced Troubleshooting, Log Files and the Input Debugger
If the above-mentioned ideas have failed, or the problem relates to a switch, toggle or USB disconnection of hardware, then the next option is to use some of the features available in the User Interface. Namely the: System tabs, Driver tab, Input Debugger, Logging features, and Debug Mode. (config/configuration/main tab/drivers tab). Let's look at each in turn.
Main Tab
After opening the User Interface, the first tab that is usually seen is the Main tab. The Main tab displays a list of registered and connected interface cards. It also displays the add-on software components that are specific to your simulator configuration. This screen is ‘live’ meaning that as you add or remove a device or interface card from the computer the connection (and list) will be updated.
The main tab is particularly helpful in identifying hardware USB disconnects (Windows USB disconnect ding-dong sound).
In the case of USB disconnects, note any interface cards that you have connected that are either not displayed in the list, or flash on and off simultaneously with the ‘ding-dong’ sound; this will most likely be the offending card/device. Often removing and replacing the USB connection will resolve a problem.
If the problem is a connection or functionality problem that relates to an add-on component (for example SimWorld MCP, CP Flight, Flight Deck Solutions, etc.). Click the + symbol adjacent to the name of the device in the software list. This will expand the selected folder for the item in question. Components not operating correctly, or not connected will be highlighted in red.
Enlarging on the above. if you select option under I/O modules (located in the main menu) you are presented with 'storecurrentlistasrequired'. This is a very handy feature in that it saves, as a profile, the interface cards used. If at anytime the cards connected to ProSim737 do not match this list, the disconnected card/harware will be displayed in red.
Important Point:
The list displayed in the Main tab includes all legacy components (for example, interface cards that previously may have been used but are now not connected). To reflect the most up-to-date items, the configuration file in main ProSim737 folder must be edited. This post in the ProSim-AR forum explains how to remove these entries: Removing Old Entries in Config File.
Drivers Tab
One of the advantages in using ProSim-AR, is that the developer has pre-installed and checked the connectivity of drivers for several add-on hardware components. This removes the need to regularly update drivers.
The Drivers tab displays a list of all drivers that can be used with ProSim737. For an add-on component to function, the driver specific to that component must be selected (checked/ticked/turned on). If it isn't then the component will fail.
If you have updated ProSim737 to a newer release, and have not used the Version Manager (manual update from the website), then there is a possibility that the correct drivers for your components have not been selected.
Functionality - Checking Inputs and Outputs (System Tabs and Input Debugger)
There are two ways that the User Interface can be used to check whether the movement of a component (input/output) is being registered by ProSim737 and operating correctly: the System tabs and the Input Debugger.
System Tabs
The System tabs correlate to various aircraft and simulator systems, and when opened will display a list detailing the functionality of that particular system.
If the switch, toggle or whatever component in question is manipulated, there will be a corresponding indication shown in the Systems tab for that component.
I'm unsure if the System tabs were designed with problem troubleshooting in mind. Nevertheless, the various tabs can provide useful and helpful information and should form part of your troubleshooting system.
Input Debugger
The Input Debugger (help/input debugger) is very easy to use, and the information it generates in its text box may help determine where a problem may reside.
The first time the Input Debugger is selected, a display window (debugger window) will open showing dozens of entries; the list can be confusing to read. It's recommended to clear the list to make the debugger easier to use (press the clear list tab).
With the Input Debugger open, you physically move the component in question (switch, toggle, lever, etc). As soon as you move the component, you will note that its input, output and other related information is displayed in the debugger window.
The use of the Systems tab and Input Debugger is an ideal way to check that ProSim737 has registered the movement (input/output) of a component.
There is also a MCP debug option located in the config file of the MCP module (Version 2.30). Opening the debug option in the MCP only displays information concerning the MCP.
Debug Mode
The debug mode is an advanced option that should only be used when requested by the Development Group (config/configuration/main/debug mode). Some explanation of the mode is needed.
ProSim737 will only generate a crashlog.txt that relates to problems within its own software; it will not generate a crashlog.txt file if the problem is located outside of its software. In such circumstances, the debug mode can be used to force ProSim737 to generate a crashlog.txt file. This may aid in troubleshooting.
The debug mode will generate a large volume of entries, which to anyone but a software developer will be nonsensical. The generated files should be sent to the Development Group.
A further debug mode is located in the MCP tab (config/configuration/main/MCP). As the name suggests this debugging tool should only be used when there are problems occurring with the MCP.
Important Points:
If the problem you are experiencing does NOT generating a crashlog.txt file (after deleting the file), then the problem is NOT related to the ProSim737 software, but rather to an outside source.
The debug mode should ONLY be used to generate the crashlog.txt file, after which it should be turned off. Furthermore, it should only be used if requested by the Development Group.
Log Files
ProSim737 generates a number of log and crashlog files that can be examined to determine problems.
The two primary files, which are located in the main ProSim module folder are the log-System.txt and crashlog.txt files.
Further log files (log-Display.txt, crashlog,txt, log-Audio.txt, etc) can be found in the various ProSim modules (for example, display folders, CDU folder and audio folder). Secondary log files can also be generated for LNAV and VNAV using HTP protocols. Scrutinizing these files can often provide incite to the cause of a problem.
The log files, with time can become quite voluminous. This is because additional information is added to the log every time ProSim737 is opened. Often it’s easier to view a file that displays information that relates to the last simulation session. Therefore, when trying to troubleshoot an issue, it's a good idea to delete the log-System.txt and crashlog.txt files; the software will automatically generate both files from scratch when ProSim737 is re-run, and the resultant entries will only record the data from the last simulator session - this makes for easier reading.
Sometimes more detail is required in a log file. To select more detailed (aka verbose) logging, open the User Interface (config/configuration/main/logging). In the Main tab, beneath Logging and Updates, there is a drop down box - select either normal or verbose logging.
It’s recommended, when using the simulator, to leave logging set to normal (unless testing). The reason for this is because the verbose option will generate a significant increase in the number of entries to the various logs with a subsequent increase in system resources.
If a crash log file is not generated for some reason, navigate to the Windows Event Viewer. The Event Viewer may provide further information (Google Event Viewer if you are unsure what this is).
In addition to the primary log files, secondary log files can be used to harvest information pertinent to a specific system; for example, VNAV and LNAV. These files should only be enlisted when requested from the Development Group.
LNAV log files can be viewed by opening your web browser and selecting 127.0.0.1:8080/lnav or vnav (you replace the address with your own address).
An additional log, that more or less duplicates the information found in the system-log.txt file can be viewed by accessing the web-based URL (help/web access URL's) - http//10.1.1.6 8080/log. A shortcut to this can be found under the help tab in the ProSim User Interface window. Web-based URL's were used in earlier versions of ProSim
Important Points:
ProSim737 will generate a new log-System.txt and crashlog.txt file if either of the files are deleted.
Whenever posting to the ProSim-AR forum a question concerning a problem, its a very good idea to attach the log-System.txt and crashlog.txt files to the thread. These files can then be perused by the Development Group.
Other Potential Causes of Problems
The list could be infinite! However, the following 'potential culprits' seem to regularly cause problems for some users.
Opening Sequence of ProSim737 Modules and Flight Simulator
Sometimes following an update, ProSim737 will crash (drop-out). If this should occur, there may be an issue with the sequence that the various programs are opened (run).
Theoretically, all the ProSim737 modules should connect automatically with the main ProSim737 module no matter what sequence they are opened. This said, changing the sequence that the ProSim737 main module is opened can resolve the issue.
Some users have reported that opening P3d/FSX before ProSim737 resolves drop-out issues, while others indicate the opposite. Likewise, some users report that the main ProSim737 module should be opened prior to opening the other ProSim737 modules.
Whatever the sequence, changing the sequence that programs are opened should form part of your initial troubleshooting regime.
Important Point:
Always start of the ProSim737 System module using 'Administrator Rights'.
Windows Power Management Settings
If a USB device disconnect occurs after a period of elapsed time, then the computer’s Power Management Settings should be checked.
The Power Management Settings enable the computer to turn off a device to save power; this is done following a period of elapsed time, or after a device has not been used for some time (for example, USB devices and display monitors).
Earlier operating systems maintained the settings established in Power Management, however, Windows 10 has a nasty habit of changing the Power Management settings without warning. Therefore, the first check should be the device manager to check that the settings are as they should be.
In the Device Manager dialog box, expand the Universal Serial Bus controllers tab, right-click each USB Root Hub, and click Properties. In the USB Root Hub Properties dialog box, click the Power Management tab. The setting that allows the computer to turn off the device must be turned OFF (do not tick/check).
Additionally, check the Power and Sleep options. Depending on the operating system used, there may also be other tabs associated with power options. Search Advanced Power Settings/USB/ and suspend/disable power management or sleep function.
USB Disconnects and Other Hardware Issues
The list is almost infinite. However, for those using a number of interface cards and relays, a potential problem can be located with the USB cable, cleanliness and tightness of USB connections (including any USB hub), and loose wiring (especially if connectors have been used).
Clean the USB connections with a quality cleaner to ensure cleanliness and make sure the USB connectors are tight. If the connectors need tightening, this can easily be done by pushing the small tabs inward on the female USB connection.
Surprisingly, wires that have been connected to relays by connectors can also work their way loose either from the connector blade on the relay or from the connector themselves. This is caused by the continually opening and closing of the connected relays (movement and vibration), and by the continual heating and cooling of the wires (which can loosen wires from the connector).
Further information concerning USB disconnects: USB disconnects.
Terrain Database (DEM) Installation
The Terrain Database is a separate folder downloaded from the ProSim-AR website. The data when downloaded is in a zip file which when uncompressed should install the terrain data to a folder called DEM located at: C:/Program Data/ProSim-AR/.
Sometimes the installer doesn't function correctly. If this happens, uncompress the files to your computer's desktop (or wherever) and copy the folder called DEM (and its files) to the location above. When done correctly you should have folder called DEM in C:/Program Data/Prosim-AR/DEM.
Once the files are installed, run the ProSim737 main module (.exe file) and enter the menu at the top of the User Interface. Select CONFIG and rebuild the database. The User Interface should have displayed 'Terrain Database Available'.
The information from the terrain database is recorded in the logdbbuild.txt file located in the main ProSim module folder.
Navigraph Data Installation
Navigraph is the navigation database used by ProSim737. It is a purchased separately to ProSim.
The correct navigation database (at time of writing) to download from the Navigraph website is ProSim737 2.24b1 (and above).
Navigraph have an installer (FMS Data Manager) which a standalone program that is free to use. When setup correctly, the installer will download, uncompress, and install the Navigraph files to the correct folder structure on yuor computer.
Once the database is installed or updated, the ProSim737 main module (.exe file) must be run, and the database rebuilt (User Interface - select CONFIG and rebuild the database). The database AIRAC cycle number will be displayed in the User Interface.
If the database does not update, there is a possibility that either that downloaded file is corrupt, or more than likely the database has been installed to the incorrect folder structure.
In this case, uncompress the downloaded files to your computer desktop (or anywhere) and copy the database to C:/Program Data/Prosim-AR/Navdata.
A more recent article (Nov 2022) looks at this topic in more detail: Installing The Navigraph Datadase to ProSim-AR.
Important Point:
Whenever you install the Navigraph database, rebuild the database and check the AIRAC cycle.
.Net Framework
Without going into detail, .Net Framework (pronounced Dot Net) is a language that is designed to bridge other computer languages so that they can be understood. .Net Framework is designed and written by Micro$oft, and ProSim-AR have used it in newer releases of ProSim737.
.Net Framework must be installed to all client and server computers.
Windows 10 Updates
Windows 10 has a feature that automatically updates essential files (as determined by Micro$oft) when the computer is connected to the Internet. Often, the user is unaware that the files have been updated, as the update occurs in the background.
Sometimes a problem will occur when a Windows update deselects features in ProSim737 that are required. For example drivers.
The Windows 10 updating feature can be deactivated if you use Windows 10 Professional, however, it cannot be deactivated in the Home edition (without registry hacking and other work-arounds).
Batch Files and Shortcuts
It’s common for individuals to use a batch file to open ProSim737, or at the very least to use a shortcut to the original .exe file within a specific folder. It’s also commonplace to rename the .exe file to something meaningful other than ProSim Display (of which there are several instances).
DO NOT rename the original .exe file. Rather make a shortcut to the file (right click and make shortcut) and rename this file. If you do rename the original .exe file, the Version Manager will not replace the renamed .exe file and the release update will fail.
Hardware/Mapping
The config.xml file contains the information needed for ProSim to connect with whatever hardware you are using. Often this hardware changes as items become obsolete and are replaced - for example, interface cards may be updated. The Hardware/Mappings section of the config file will not these changes. Rather, it will add new hardware mappings to the list.
To clean up the mappings section, it is necessary to open the config.xml file in a text editor and delete all entries between the <Hardware> section headers. When the ProSim main menu is opened, a new hardware/mappings section will be generated that includes only the current hardware connected.
ProSim737 Flight Model
ProSim737 has a dedicated flight model for P3D and MSFS-2020.
The flight model has a built in installer which makes the process of installing straightforward - providing you follow the instructions as written by the developer in the opening screen. The flight model is installed to the main P3D folder or to the community folder if using MSFS-2020. If using the later, the flight model can be installed to a generic folder outside of the community folder and then linked to the community folder.
Prior to installing a new flight model, it is recommended to uninstall the earlier flight model. This can be done by using the add/remove program options in Windows or by opening the uninstaller program that comes with the flight model. Whichever option is selected, you must understand that the installation of the newer flight model will replace any existing files that relate to the model.
The files that are affected are those that reside in the aircraft folder. The below folder is the location of the folder in my computer running MSFS-2020. Your location will be different, however, the bolded entry is generic for all users.
D:\\Flight Simulator\MSFS2020Community Folder\Aircraft\prosim-B738-v2023\SimObjects\Airplanes\prosim-b738-2023.
Installation of a new flight model will replace any altered files, additional sound files, and added aircraft liveries with default files. I strongly recommend that you backup the aircraft folder prior to updating the flight model. After the new flight model is installed, you can then change-out any files that you want from the previous model.
Important Point:
Always backup the aircraft folder. Uninstalling or installing a new flight model will delete and replace any files within the aircraft folder with default files.
Dedicated Forum and Requesting Help
ProSim-AR has a dedicated forum that is actively monitored by the Development Group.
If unable to resolve your issue, the log.txt and crashlog.txt files can be posted to the forum along with a detailed subject line and description of the problem. In most cases, the Development Group rectify problems quickly. Failing this, you can submit a support ticket via the ProSim-AR website.
Important Points:
I cannot emphasis the importance of a detailed subject line. It's counter intuitive to think that someone will open a thread that says "Help Me" or "Problem PS Doesn't Work" as opposed to "Marker Sound Not Working With PS Audio", or "MCP Disconnects when Opening ProSim".
When your issue has been resolved, open the thread and write RESOLVED in the title line. This will stop forum members from opening your post to offer help, when in fact the problem is solved.
Disclaimer
The above mentioned information is valid as at the time of writing with Release Version 2.28b3. However, ProSim-AR frequently update their software, and a future update may change what I have documented.
Final Call
The procedure to update the ProSim737 avionics suite is relatively straightforward, and the updating process streamlined and effective. Nevertheless, the avionics suite is a complex piece of software and problems can occur following an update.
The User Interface and Version Manager are powerful tools that can be used to customize the way that ProSim737 is updated and configured, and be used to troubleshoot problems. Additionally, highly detailed logs can be generated which can be used by the Development Group to aid in rectifying problems. This said, often the easiest solution to resolve a problem is to reinstall ProSim737 to its virgin state (from the ProSim-AR website), and reinstall your backed up configuration files.
This article has dealt primarily with updating and some of the potential problems that may develop; troubleshooting has only been briefly addressed. Despite this, the above-mentioned recommendations should rectify most of the problems that may present when updating the avionics suite.
Acronyms and Glossary
Development Group - ProSim737 Development Group (software developer).
Level D/Type 7 Simulation - Full flight simulator (FFS) is a term used by national (civil) aviation authorities (NAA) for a high technical level of flight simulator. ... A Level D/Type 7 simulator simulates all aircraft systems that are accessible from the flight deck and are critical to training.
Manipulate - A term to mean move. It could be a switch, toggle, button, lever or anything else that can be physically moved.
Run - Term meaning to run or open a program.
User Interface - The User Interface used to access the customizable features of ProSim737. The User Interface is accessible by clicking the ProSim737 icon.
Version Manager – ProSim737 user interface used to configure and customise the ProSim737 avionics suite.
Update
Updated 11 April 2020
Updated 19 March 2023 (amended to include important changes made to the Version Manager in Version 3)
Flaps 2 Approach documents the construction of a Boeing 737-880 flight simulator using OEM aircraft parts.
Hosting and paying server costs is expensive. Please consider helping to pay these costs if you find the website helpful to you. This site does not have advertising. Thank you
© Copyright 2011 - 2024. Flaps 2 Approach. All Rights Reserved
