ProSim 737 Glass Cockpit Avionics Suite - Review

prosim 737 version 1 opening screen

The ProSim737 Glass Cockpit Suite is software developed solely for the Boeing 737-800 aircraft and replicates the avionics required for the operation of the flight deck. ProSim737’s beginning was meager, however, the ongoing development, accuracy, functionality and above else, ease of use and reliability, has ensured that ProSim737 has an exceptionally strong following.  

The developers are based in Luxemburg which is why many users of the software are European based; however, flight simulation transgresses geopolitical boundaries and many users of ProSim737 are located in Asia, Australia, New Zealand and North America.

I’m not going to duplicate what can easily be read in the ProSim737 user manual.  The manual outlines much of what the software can and cannot do and I urge potential buyers to read it.

This review pertains to software release Version 1.

First Off - Caveat Emptor (Latin for buyer beware)

Before continuing, there are several flight avionics suites currently available on the market.  They all replicate the basic avionics functionality of the B737.  However, not everything is operational within each suite, and some functions behave differently between suites.  Therefore, it’s a good idea to research what works and what doesn’t before your purchase.  I have a written an earlier journal post addressing this.

Avionics Suite – The Heart

The heart is the most important organ in the human body.  Likewise, the avionics suite is the heart of the flight simulator, and provides the interface for instrumentation to operate.  If the software used is not reliable, robust and well tested, then problems may develop which ultimately will lead you into a minefield of frustration and confusion as you attempt to unravel the intricacies of the Boeing avionics system.

ProSim737 – Overview and Detail

ProSim737 is a complete avionics solution providing the ability to support all displays and logic found within the B737-800.  The software has been designed to run on one or multiple PC's in various configurations interfacing with FS2004 (FS9) or FSX, via a paid and registered version of FSUIPC.  Wide FS is not required, however can be used if networking other add- on programs.

To achieve this, the software is segregated into four broad modules: PS737 System, PS737 Display, PS737 MCP, and PS737 CDU.  Additional modules are PS737 Audio and PS737 Panel. 

I’ll discuss the details of each briefly.  For a more though dissection, I direct you to the ProSim737 website or user manual.

A short video at the bottom of this post will guide you through the various menus of the ProSim737 Systems Module.

PS737 Systems Module

The Systems Module is the main component of the ProSim family and it’s within this module that configuration of the switches, indicators, drives, and gauges occur.  In addition to providing the detailed logic to replicate the following aircraft systems and components: electrical, pneumatic, fuel, hydraulics, heating, fire detection, IRS and master cautions, the module provides access to a web-based instructor station and server that other ProSim737 modules connect to and from.

The Systems Module, because it houses the server, must be installed on the computer running flight simulator.  Likewise, for any other module to operate, the Systems Module must be opened.

PS737 Display Module

As the name implies, this module supports the main visual displays located in the Main Instrument Panel (MIP) that a pilot views when in the flight deck.  The module also provides several additional “virtual” gauges, such as clocks, stand by instruments and a flaps gauge for those flight deck builders who don’t use reproduction hardware gauges, or converted real instruments.

The following displays and gauges are included in the display module.

  • Captain and First Officer Pilot Flight Display (PFD) and Navigation Display (ND) -  various      configurations

  • EICAS display (upper & lower) with fully integrated EICAS messaging

  • Virtual Main Control Panel (MCP)

  • Virtual EFIS display (two)

  • Virtual overhead panel (forward & aft)

  • Virtual CDU display

  • Virtual stand-by instruments (good selection)

If you’re operating a full flight deck with appropriately supported hardware you won’t require the virtual MCP, EFIS, CDU and overhead displays.

prosim 737 virtual mcp

ProSim737 MCP Module

This module controls the Mode Control Panel (MCP) which is the auto pilot system in the aircraft.  The MCP communicates with the logic coming from the systems module to provide information regarding altitude, direction, speed and other auto pilot constraints.

ProSim737 allows the user to either configure the MCP as a “virtual” MCP panel displayed on a computer monitor, or for builders using a hardware MCP, display minimised.  The virtual MCP includes two Electronic Flight Instrumentation System (EFIS) modules in either Honeywell or Collins configuration.

This MCP module usually resides on the same computer as the systems module.

ProSim737 CDU Module

The Control and Display Unit (CDU) is used to assess information from the Flight Management System (FMS).   A user can either use one, two or any number of instances of the “virtual” CDU and each will display identical information.  If a hardware CDU is being used, there is the ability to turn off the “virtual” CDU and display the data on the hardware unit.  All CDU instances are linked to each other via the ProSim737 Systems Module.  It’s usual practice to install and run this module from a client computer.

ProSim737 Audio Module

The audio module is a stand alone module that allows user customised sounds to be played when various preset functions occur, such as when switches are toggled, speeds are reached, etc.  This module is needed to allow GPWS and TCAS cautions, in addition to V1, V2, Vr and altitude call outs.  The module can be installed and run from any computer and links to the ProSim737 systems module.  The module runs as an additive to ProSim737’s internal sound (located in the Systems Module).

The virtual forward overhead panel.  Many switches are functional and can be moved with the mouse

ProSim737 Overhead Module

This module provides the switches, gauges and dials for the forward and aft sections of the overhead.  The module is installed on the client computer and is usually left open full screen, unless you have a hardware overhead installed.  The module supports functionality essential to the basic operation of the B737.

Reliability, Robustness & User-Friendly

When you evaluate a product, it’s “usually” fairly easy to find inherent problems.  ProSim737 is a different beast; since I began using their software I have not had any problems that suggest inherent problems with the underlying software framework.  It’s a pleasing experience when you open software and it “just works”. 

Of course, variances between computer systems and a wide variety of FS add on programs, can cause minor nuisances to occur – this is normal with any software.

To avoid any issues, I advise that all flight simulator add on programs be removed before evaluating a software suite.  Once you’re happy that everything is functioning as it should, add each FS add on in turn, checking to ensure correct operation.  If a problem does occur, at least you will know which program is causing the issue.

ProSim737 is an exceptionally robust software platform and the program has never crashed despite me changing configurations, etc “on the fly”.  

Software Installation

Simplicity and easy of use are the mantra of the developers of ProSim737.  Opening the ProSim737 package will reveal a number of appropriately named folders.  To install the Systems Module you click an executable file and install to the computer on which flight simulator is installed.  The other folders are then copied to the client computer.  IP addresses must be known to allow communication between modules across the network.

You don’t have to open .ini files or configuration files during installation and you don’t need to copy and paste files between folders.  Basic configuration is achieved by right clicking the mouse which opens a configuration screen.  The set-up is uncomplicated and is logically set out.

The only files you need to cut and paste to a folder are the terrain files and navigation database.  Detailed instructions on how to do this are documented in the comprehensive and well-written manual.

prosim 737 Configuration display when using right mouse click - everything is easy to find and configure with minimal time outlay

Learning Curve and Ease of Use

Any new software has a learning curve; however the curve is very shallow when using ProSim737.  You don’t have to be a programmer or have in-depth computer knowledge to install or use ProSim737.  The software is very easy to install, configure and maintain. 

For example updates, which are frequent, do not require you to manually cut and paste a new version download to several folders.  An update button within the Systems Module completes the update task within minutes.  As you open other modules, they each in turn are updated from the Systems Module.

Another example, which shows the ease of use relates to the configuration of various displays provided in the ProSim737 Display Module.  To set-up a dedicated display, you mouse drag the required display to the monitor of choice and then right click the window to open the configuration menu; resizing the display is done using the mouse.  To avoid the problem of the display accidentally changing size in the future, you tick the “freeze constraints” box. It literally takes less than 10 minutes to establish the visual displays in the flight deck!

Configuring Your Switches and Buttons

Configuring buttons and switches to your set-up relatively uncomplicated involving opening a menu in configuration mode, scrolling to find the particular function you need, and then connecting the output type to a specific output.  Granted there is a learning curve, but the curve is low and essential tasks don’t requite extensive knowledge of computer code.  

Similarly, customised audio files can be added, linked and played in the Audio Module.

Navigational Database and Terrain Files

ProSim737 does not provide the navigational database that is needed by the aircraft.  This must be purchased as a separate item from Navigraph.  This is normal practice and all developers rely on Navigraph to maintain the latest navigation package. 

Installing the database requires you download the data and then extract the data, via an executable file, to a specific folder within ProSim737.  You then must build the database which is achieved by pressing a button within the configuration menu.  

Similarly, the terrain files must be downloaded from the ProSim737 website and manually copied to the appropriate folder.

Driver & Hardware Support

Today, there are several vendors ranging from high end to budget level that are replicating B737 hardware and instrumentation.  ProSim737 development is forward based, meaning they understand the need for avionics software to be compatible with as many hardware types as possible.  Flight Deck Solutions, Engravity, Go Flight, CP Flight, SISMO and Open Cockpits are all supported and several types of I/O cards are supported such as Pokey, FDS SYS and phidgets.  FSUPIC and FSUPIC offsets are also supported by ProSim737.

Determining which hardware is selected for your set-up is as easy as checking a box within the configuration screen of the Systems Module.  

Accuracy and Resolution of the Flight displays

You spend a lot of time staring at the various displays, whether it’s the Pilots Flight Display, Navigation Display, CDU or EICAS; therefore, it important that the graphics are of the highest quality possible; nothing is worse than staring at jagged corners, off-putting colours, or blurry lines.  

Although the quality of any graphics is linked to the resolution of the computer screen, if you use a high resolution screen you will not experience any anomalies associated with poor graphics.  The display graphics are crisp and sharp. 

  • To see images of displays navigate to the ProSim737 website.

All simulation enthusiasts strive for accuracy; some to a greater extent than others.  The displays depict what you would see if you were looking at the displays in a real B737 main instrument panel.  Only the very keen you will note the odd subtle difference between the simulation and the real display, and this is often determined to a certain extent, by the cockpit set-up and carrier options you select from within the instructor station.  

For example, the magenta course line in the Pilots Flight Display appeared to be slightly thinner than on the real aircraft, but no sooner had I noticed the disparity that Marty at ProSim737 had uploaded an update rectifying the issue.

What’s important to realize, is that the developer listens and if inaccuracies are noted rectifies the disparity quickly and without argument.  

ProSim 737 Screen grab showing variations of PFD and ND displays dependent on EFIS setting

Precision

Any software must provide precise outputs when its logic is queried; all virtual pilots demand that software outputs be precise in execution.  To date, ProSim737 has lived up to its reputation and I cannot highlight any major downfall in the precision of the software. 

ProSim 737 Screen grab showing variations of PFD and ND displays dependent on EFIS setting

Vertical Navigation (V-Nav)

A common thread in FS forums is that avionics software has difficulty in replicating Vertical Navigation (V-Nav).  This is especially evident with software supplied by Project Magenta and to a limited extent with Sim Avionics. 

ProSim 737 Screen grab showing variations of PFD and ND displays dependent on EFIS setting

The logic used to replicate V-Nav is not simple; it’s complicated, and the variability in V-Nav usage often causes issues to develop when using V-Nav.  The main problem is that the aircraft may not keep within the constraints entered into the CDU.  Often the aircraft will either over fly an altitude constraint or not maintain a entered speed constraint.

From the outset, V-Nav in ProSim737 has worked exceptionally well.  Altitude and speed constraints, if entered correctly, are maintained and the reliability of V-Nav surpasses those of other software suites I have used.

V-Nav Usage

V-Nav, even to qualified pilots can be a challenge to use correctly.  This is one reason why V-Nav should only be used as a guide and not as an absolute.  If V-Nav, for whatever reason does not function in a method you think is correct, then turn it off and use the more reliable L-Nav, Level Change or Vertical Speed functions.

The challenge, I have discovered when using V-Nav is two-fold.  First, you must use it within the designed capabilities of the program, and two, you must learn how and when to operate V-Nav.  If you enter data that the FMS cannot assimilate, such as an altitude that is too high or too low, for the time required to reach the waypoint, then expect an over fly of the entered restrictions.  This is not the fault of the software, but the fault of the user.

Display Lag

Display lag is term coined to explain the staggering of a display due to information overload, information bottleneck or lack of computer graphical power.  It typically manifests itself when a lot of information is required to be displayed at an identical time that computer processing is required.

For example, another software suite I have used displayed staggering on the altitude tape in the Pilots Flight Display (PFD) when ascending and descending with the “all waypoints” selected from the EFIS.  The staggering stopped when the “all waypoints” were deselected.

I have yet to experience any display staggering with ProSim737, even with the terrain simulation display activated.  

Weather & Terrain Display Functionality

The weather and terrain display function, which is activated either by pressing WXR or TERR on the EFIS unit is functional in ProSim737, however, the weather display is inaccurate and looks very outlandish in its “blocked in” colour display.  

I’m lead to understand that the weather functionality present within other software (Sim Avionics), reads directly from weather depicted by FSX, and then only presents a rough indication of what the weather maybe like at that particular time; it certainly does not mimic and display what the aircraft is actually flying through or about to fly through.  

I am hoping that the developers at ProSim737 will develop a radar module that actually reads the exact weather depicted in FSX and display this weather in a way that is similar to the real radar in the B737.  At the time of writing, the weather displays only in solid colours and does not mimic how real radar operates.  I hope that ProSim737’s developers improve this in due course.

ProSim 737 terrain files (two choices)

Two Terrain File Resolutions

Pressing the terrain (TERR) button on the EFIS unit, displays a graphical representation of the surrounding terrain on the Navigation Display.  There are two variations of the terrain graphics available; one display is slightly blocky and the other display is more detailed.  To select which display is active, right click the screen with your mouse and tick the appropriate box in the configuration menu.


Compatibility of Aircraft with ProSim737

It's always been a concern to what add on aircraft you can use with a particular avionics package.  As an example, Sim Avionics provides several aircraft .cfg files which have been tweaked to their software.  You load the particular aircraft.cfg file for the aircraft you are using and any vagrancy between the aircraft and avionics software is rectified.

ProSim737 has taken a completely different approach and designed a flight model called the JetStream 738, which is tweaked to operate flawlessly with ProSim737.  Of course, you don’t have to use the JetStream if you don’t want to; the default B737 can be used as can the PMDG B737 FS9 version with flight logic removed.  

I will review the JetStream738 in a separate journal post.

CDU - Background Software

No review of any avionics software is complete without a short segment on the CDU.

The ProSim737 CDU module is the controlling software that provides the intelligence behind the CDU.  It's amazing what this software can do, and do so with reliability and consistent behaviour.  More importantly, the software does not crash, even when incorrect data is inputted to the unit.

Many pages associated with a commercial CDU are modelled and updates continue to add new features and improve existing functionality. 

In the real B737 aircraft, not all CDU software is identical.  There are different software versions and each version has slightly different functionality; it’s the decision of the airline to which software version is chosen.  Likewise, not every company producing avionics software models the CDU identically.  In some respects, it depends on which software edition the developer has chosen to replicate. 

Unfortunately, many developers choose to not replicate something or to not provide full functionality.

Often CDU menus and pages may look similar in appearance, but you will be disappointed when trying to access a feature that appears to be modelled but has no functionality.  Some suites offer far greater functionality than others.  I believe ProSim737 provides more functionality than other higher end CDU software available, and more functionality is regularly added through software updates.

Some of the basic features modelled by the CDU software are:

  • Indent page on start-up (weights, fuel, fuel reserves, cost index, cruise altitude, etc)

  • Approach reference page with VREF selection

  • Route, LEGS, Arrival, Departures & Holding pages (user controlled including approaches, STARS, SIDS & transitions)

  • Progress pages (fuel, distance to go, ETA, wind, crosswind component, cross track error, fuel prediction etc)

  • Vertical Bearing Indicator (VBI)

  • V-Nav & L-Nav compliant (climb, cruise and descent)

  • Ground Service - push back

  • NAV/COM radio reference page (ADF, ICAQ, VOR & ILS data) & search

  • ACARS (future installment)

  • Captain & First Officer EFIS control

  • OAT

  • SIM MAINT page (separate commands to control SIM instead of using keyboard) such as pause, freeze & re-set FMC.

The software lacks the ability save a flight plan directly from the CDU; you must use the instructor station to save a flight plan. Also, it’s not possible to reverse a route from the CDU.  It would be helpful if this functionality can be implemented.

The software is compatible with CDU hardware produced by Fly Engravity and Flight Deck Solutions.

prosim 737 ios showing CAT visibility and push back & failures menu

Instructor Station

The instructor station included with the software is a web-based station, meaning you type in the appropriate address into the browser web bar and the instructor station opens on any computer connected to your network – even a laptop.  No other software is needed.

The instructor station is comparatively simple in layout, yet functional.  Without repeating the user manual, which outlines in detail what each section comprises, the station displays the following menus: Quick Start, Cockpit Set-up & Carrier Options, Global Database, Situations & Positions, Company Routes. Flight Plans and Failures.

prosim 737 ios failure screen

Two Instructor Station functions  deserve mention

Company routes allow you to store and manipulate routes you have loaded into a specific folder within ProSim737.  These routes, if not manually built using the CDU and FMS and saved to the instructor station, are usually downloaded from on-line route generators.  As the station has a built in editor these routes can easily be edited and re-saved.  You can also download from the station to the CDU any selected route.

The situation menu I find particularly useful.  Here you can instigate push back, execute day or night and switch to real time at the push of a button.  You can also define visibility as CAT I, CAT II or CAT III.   This can be done on the fly while the aircraft is flying.

The failures menu can be set-up to allow any number of single, multiple or cascading failures to occur either within a predefined time or at random.

ProSim737 Start-up Sequence

Ease of use and simplicity are important to ProSim737 and this mantra is carried through to the operation of the software.  Opening the ProSim737 Systems Module and other associated modules is exceptionally fast and the programs close with minimal lag time.  This is in stark contrast to other software suites which seem to take an eternity to open the various instances of the same program.

To simplify the start-up process when opening a flight session on my two networked computers, I’ve created shortcuts to the required ProSim737 modules and pasted them to the windows menu bar.  This is my start process (included are some add on programs I am running).

Server Computer

  1. Start PM Sounds

  2. Start ProSim737 main module

  3. Start ProSim737 MCP module

  4. Start ProSim737 Audio module

  5. Start FSX

  6. Start FSRAAS2

  7. Start Throttle Quadrant Phidgets

Client Computer

  1. Start PM Sounds

  2. Start ProSim737 Display (Captain PFD& ND)

  3. Start ProSim737 Display (First Officer PFD & ND)

  4. Start ProSim737 Display (EICAS)

  5. Start ProSim737 CDU

  6. Start ProSim737 Overhead Panel

  7. Start ProSim737 Audio module

  8. Start ProSim737 web-based instructor station

The time to start each program is no longer than 4 seconds; FSX takes the longest time to load.  Closure time is similar (mouse right click/close) from the menu bar.  To decrease closure times and mouse movement, a closure batch file can be created.

What is lacking & Possible Improvements

There will probably always be something lacking no matter what software you use, and some enthusiasts are never happy until they have everything – even if they never use or need it.  

The Aircraft Communications Addressing and Reporting System (ACARS) is not supported, although I believe this will be addressed in future updates.  I’ve already discussed some missing functionality with the CDU and touched on the inadequacy of the weather radar.

For the most part, all essential functionality is present within the system, although it would be nice to have more CDU functionality and a list of functions the CDU is capable of.  Currently no such list is available, and if using an official FMC guide it can be "hit & miss" working through he menus to see what is functional.

Several users have commented on the forum, that the %CG calculation in the CDU usually remains the same despite changing the aircraft's overall weight.  Users of TopCat pre-flight software have reported variances in %CG between ProSim737 and TopCat.  This variance may suggest an issue in the calculation of %CG which needs fine-tuning.

The list of hardware supported by ProSim737 is long and continuing to grow.  This said, I have noticed that the CP Flight ATC/Transponder unit which supports full TCAS operation is only partially functional within ProSim737.  TA/RA is inoperative.  Although the responsibility for this incompatibility probably rests with CP Flight, it would be very nice if ProSim737 attempted to rectify this.  CP Flight hardware is used universally and full functionality should be implemented across the complete CP Flight range of hardware.

Continual Development

In my opening paragraph I stated, “Avionics software is the heart of the simulator”.  Therefore, it’s pleasing to see continuing development of the software; updates that add or improve on existing functionality are released on a very regular basis.  Furthermore, the software designer is open to suggestions from users on how to enhance the software.  Shortcomings, when observed are quickly addressed.

One Aircraft - Mono Focus

One very important attribute of ProSim737 is that the developers only produce software for the B737 aircraft.  This means that they focus 100% of their time on replicating this airframe.  Other companies develop software for multiple aircraft and try to incorporate duel systems within their software.

Compromise & Expectations

It’s a fact that human beings rarely enjoy compromising – we want everything and we want it now. 

Some of you maybe "thinking" that ProSim737 has issues that need rectifying.  I'd be lying if I told you everything was 100% perfect - of course there are issues, but these are minor and differ depending upon your set-up.   But, in comparison to other software suites on the market, I feel confident stating that ProSim737 has less issues and rectifies niggling problems much more quickly than their counterparts.

If your expectation is to have software that is absolutely perfect without any glitches at all, then I'd strongly suggest that building a flight simulator is not really your calling. There are so many variables with computer equipment, drivers and the like that minor issues will pop up from time to time.

Developing software that replicates the B737 avionics to the tenth degree is a noble thought, as is maintaining a reasonable price.  However, what builders often fail to remember is that the Boeing software cost millions of dollars to design and implement with a solid team of developers.

ProSim737 delivers an exceptionally good package that is more advanced and feature-rich than its counterparts.  It’s not perfect, but the developers strive for perfection and improvements continually are being released on a regular basis.

Documentation and Support

The definition of osmosis is; “The gradual, often unconscious, adsorption of knowledge or ideas through continual exposure rather than deliberate learning”.  In the previous software suite I used, “osmosis” was very much the method of learning, as were mistakes, wasted time and frustration.

It’s good to see that ProSim737 includes a very detailed and well-written instruction manual which explains how to do nearly everything you need to know to configure the software to your set-up.  Failing this, there is a dedicated interactive forum that is very regularly reviewed both by users, beta testers and ProSim737 staff. 

If a problem does occur, support can be reached either by Private Messaging or e-mail.  

You will not be left “high and dry” by the developers.  They are very enthusiastic about their product and keen to help wherever possible.

A short video will guide you through the various menus of the ProSim737 Systems Module.

 
 

Recommendation & Overall Score

ProSim737 is a stable, well tested and tried software platform that provides most of the real-world avionics of a B737 jet-liner.  The software is easy to install, use, and does not require advanced computer knowledge to get you in the air.  Furthermore, a vast collection of hardware and interfacing cards are supported and new functionality is added on a regular basis.

At the time of writing, if you purchase ProSim737, the software includes full support and updates for an unlimited time period. 

This has been a long post, and if you have read this far, I hope you have gained some incite into ProSim737.

To download a free trail version of the software, visit their website – ProSim737.

My Rating is 9.5/10

Please note that this review is my opinion only and is not endorsed.

Update

on 2014-02-12 23:38 by FLAPS 2 APPROACH

  • Please note that since this review has been written, ProSim737 developers have released several updated versions of the software and three incarnations; Version 3 being the latest (2024).

  • The content of the review is outdated and has been left on the website for historical interest.

Construction Commenced - New Platform to Install OEM Control Columns

I thought it time to post what’s happening with regard to the construction of the simulator.  Additions and improvements are in the pipeline and it’s hoped that OEM control columns and a new platform will be installed very shortly.

Currently the simulator is mounted on a fiber-board and wood platform, which I constructed when I received my Main Instrument Panel (MIP) just before Christmas 2010.  The platform has served me very well and was perfect for the installation of the ACE yoke and Precision Flight Controls (PFC) rudder pedals.  

Soon after constructing the platform and purchasing the ACE yoke, I was able to secure two OEM B737-500 control columns. I was surprised to find these units so quickly and I was fortunate that my timing coincided with the dismantling of a late model B737-500.

Fitting the OEM control columns to the wooden platform appeared to be problematic, as the platform was a tad low in height and it was awkward to retrofit the linking rod that connects the control columns for duel operation.  Therefore, I decided that a new platform was required; custom designed  to fit the control columns.

Aluminium Modular Design

Rather than use wood and fiber-board, I selected aluminium tubing cut appropriately and TIG welded together.  To facilitate future transport, the platform has been constructed in modular form.  The forward portion comprises three modules bolted together in strategic places, while the rear part of the platform (not shown), where the seats and center pedestal reside, abuts snugly to the forward section.  It’s intended to use high density ¼ inch plastic/vinyl as the upper cover on the platform  as this material is easier to work than aluminium sheeting, is light in weight, very strong and comes from the factory in Boeing grey.

In the photographs (click to enlarge) you can see the control columns (striped completely) fitted to the forward modular section of the platform.  The control columns are connected to each other by a ¾ inch heavy duty shaft and heavy-duty double bearings.  Forward and aft movement of the control column is controlled by a heavy duty spring and left and right roll movement is controlled by another spring. 

Control Column Pull Pressures

The pull pressure on the control column is set to 24 pound which is slightly less that the standard pull in the B737 which is 34 pound.  The pull can be easily altered by moving the spring forward or backward on the spring retainer.  The pressure on the roll component is presently 12 pounds.  I've been told the roll pressure as per the Boeing maintenance manual is +_15 pound; therefore, I'm well within the ball park.

Throttle Thrust Problem - Loosing Thrust at N1 - The Solution

oem 737-300 throttle

The throttle installed into the simulator is a converted genuine B737-300 throttle.  Lately, I have observed inconsistent power thrust issues during the take off roll and climb out. 

As I begin the take off roll, engage TO/GA and rotate, but before acceleration altitude or acceleration height is reached, one of the throttles looses or gains power.  Moving the throttle handle reinstates throttle power, but the power is dependent on where the actual throttle lever is physically positioned. 

When the aircraft is above thrust reduction altitude (1500 radio altitude) the problem rectifies itself.  The problem cannot be replicated when flying above 1500 feet.  I also noted, and this may also be part of the issue, that the power indicators located on the EICAS display fluctuate (twitch) a little as I moved the throttle levers.

This problem only began to occur after I transferred the avionics software to ProSim737.

Process of Elimination

Problems like this are not uncommon when interfacing real aircraft parts and the challenge is finding the cause of the problem.  The only method to determine solutions to problems such as this is to systematically, through the process of elimination, identify the problem area.

My first thought was that one of the potentiometers in the throttle quadrant maybe damaged, although I considered this to be unlikely as the units are still relatively new.  The throttle has four potentiometers: throttle 1, throttle 2, flaps and spoilers. Flight testing indicated that the power loss alternated between engine 1 and engine 2; therefore, the likelihood of two potentiometers failing at the same time was minimal. 

The next step involved checking the wiring within the throttle quadrant, to ensure there wasn’t damage to the outer coating of the wires.  A damaged or loose wire can easily short on the throttle frame and generate a spike.  However, if the wiring was loose or damaged, the problem would also occur when flying at altitude, and I had clearly demonstrated that the problem only occurred during the take off roll and climb out to thrust reduction altitude. 

The next step was to ensure that calibration of the throttle unit was correct.

Re-Calibration Using FSUIPC

I decided to re-calibrate the throttles using FSUIPC rather than FSX.  This process isn’t difficult and FSUIPC allows you to fine tune each throttle with greater accuracy than is possible with FSX. 

After re-calibration, the “twitching” of the power indicators ceased, but the initial problem remained.

The Cause of the Problem

The only culprit I could think of to cause this problem was ProSim737.

To check whether ProSim737 was actually the cause of the problem, it is necessary to remove any input from the ProSim737 software.  This is straightforward.  Either use another avionics software package or use FSX itself.  I did twenty trial flights using both Sim Avionics and FSX and the problem did not replicate. 

ProSim737 Excellent Support and Advice

I contacted the developers at ProSim737 explaining my problem in detail, and I received a response to my questions within a few hours.  Marty was especially helpful and we discussed several potential reasons for this issue and possible workarounds.  I must stress that the response I received from ProSim737 was absolutely 100% top notch. 

Marty genuinely wanted to help resolve the issue – whether it be with ProSim737 or otherwise.

Real B737 Throttle Operation

Now this where the comment “as real as it gets” does have meaning…. 

The developers of ProSim737 have designed their software to replicate the logic used by the real B737 auto throttle.  The software (ProSim737) is doing exactly what it’s supposed to do in relation to power thrust, and the issue I was experienced is caused by using a real aircraft throttle without automation.  Let me explain.

In the real aircraft, when TO/GA is enabled, the auto throttle logic has control of the aircraft.  The throttles are off-line and power thrust cannot be manipulated by the pilot.  The flight mode annunciator (FMA) illuminates N1. 

As 84 knots is passed the FMA changes from N1 to THR HOLD.  At this time, the actual throttles come back on-line, meaning that you can manually alter throttle power by moving the levers.  After rotation and at 800 radio altitude the auto throttle system is ready to change from take off power to climb power and the FMA changes from THR to ARM.  When in ARM mode the throttles are still on-line. 

When the aircraft reaches 1500 RA which is the thrust reduction altitude, the throttles go off-line and the AT logic is controlling the power thrust of the throttles.  The FMA changes from ARM to N1.

Throttle Anomaly

The B737 does not have a manual throttle, but an automated throttle.  The software is programmed to move the throttle levers to the correct position mimicking the actual power thrust called for by the auto throttle logic.

If you use a manual throttle (genuine or otherwise) the connection to the automated physical movement of the throttle levers is missing; you must counter this by moving the levers yourself.  This issue should not occur with a correctly calibrated automated throttle.

Using an Auto-throttle

If you have an auto throttle, the levers will automatically and physically move to the indicated thrust position as determined by the auto throttle logic (90%N1 at TO/GA).  When the FMA illuminates THR HOLD at 84 knots, and the throttles come back on-line for possible pilot intervention, the auto throttle logic will not sense any change in the throttle lever position, and power thrust (90%N1) will be maintained.   This is because the automated system placed the throttle levers in the correct position when TO/GA was initiated.

Using as Manual Throttle

However, if you’re using a manual throttle, the throttle levers MUST be physically positioned at the correct location on the throttle quadrant, otherwise the auto throttle logic will sense a change in position of the levers and alter the power thrust accordingly to this new level. 

This is what was occurring in my situation.  I was resting my hand on the throttle and only advancing the levers 3/4 of the way forward.  TO/GA indicated 90%N1, but when the throttles came on-line at 84 knots, the auto throttle logic noted that the position of the throttle levers was not at 90%N1 and subsequently altered the power thrust accordingly.

The reason the issue was inconsistent is that I didn’t always advance the throttle levers to the same position, and if I did the problem did not occur.

LEFT:  B737-300 throttle quadrant converted to Flight Simulator use.  The TQ is a manual throttle meaning that the thrust levers are not automated and must be moved manually.  I have used a pencil to lightly mark the metal adjacent to the most commonly used N1 settings.  This ensures the levers are moved the correct location during take off.  Lever position is set to 90%N1 and flaps 5.

Solution – Change in Procedures

The solution to this anomaly of using a real “manual” throttle is relatively simple.

You must determine where on the throttle quadrant the various N1 power settings are and then ensure, after engaged TO/GA that you move the throttle levers to the correct position (90%N1).  In my situation, the procedure is to advance the throttle to 40%N1, engage TO/GA, and then manually push the throttle levers to 90%N1.

Thank you

I’d like to thank Marty at ProSim737.  Marty worked with me to solve the issue, which ultimately was not really a problem with either ProSim737 or my set-up, but is an anomaly of using a genuine throttle unit without automation.

Possible Update

I may update the throttle quadrant to enable automation of the throttle levers and speed brake, however, for the time being the throttle quadrant will not include automation.

Update

on 2013-04-23 23:56 by FLAPS 2 APPROACH

 

diagram 1: a clear diagram that helps explain the problem discussed in the article (thanks to frazier @ prosim737 forum)

 

Vertical Bearing Indicator (VBI) - How To Calculate A Controlled Idle Descent

vertical bearing indicator (vbi) displayed on reproduction cdu manufactured by flight deck solutions (fds)

Often you are requested by ATC to alter altitude, or must intercept a desired point in space at a certain altitude for operational reasons. There are several methods available to the pilot to initiate the change in altitude; outlined below are three methods.

A: Initiating Level Change or Vertical Speed on the MCP will activate an advancing and contracting green line arc (Altitude Prediction Line) on the CDU.  This green arc identifies the location that the aircraft will reach ,if the vertical speed is maintained, in relation to the active CDU waypoint.

B:  You can calculate the distance and vertical descent using mathematics, but this can be cumbersome and may illicit possible mistakes. 

C:  You can alter the LEGS page of the CDU keying in the new altitude constraints (this assumes you are using VNAV & LNAV.

The CDU Vertical Bearing Indicator (VBI) can help you.  The VBI is basically an angle calculator that provides "live" vertical speed information based upon a desired descent angle.  An example using the waypoint TESSI is provided.

  • Navigate to Descent page by pressing the DES key.

  • At lower right hand side of the DES page you will see the following: FPA, V/B, V/S.  This is the Vertical Bearing Indicator.

  • Key RSK3 (right line select 3) and enter the waypoint and altitude (TESSI/17000)

The VBI provides 3 fields:

  • FPA (Flight Plan Angle) is the vertical path in degrees that the aircraft is currently flying.

  • V/B (Vertical Bearing) is the vertical path in degrees that the aircraft SHOULD be flying to reach the keyed waypoint (TESSI/17000).

  • V/S (Vertical Speed) is the vertical bearing (V/B) converted into vertical speed for easy input into the MCP.

Observe the V/B.  The idle descent in a 737 is roughly 3.0 degrees (PMDG use 2.7 degrees)

Wait until the V/B moves between 2.7 and 3.0 degrees (or whatever descent angle you require)

When the value is reached, dial in the required altitude and indicated Vertical Speed on the MCP

The Altitude Prediction Line will now intersect the selected waypoint (TESSI) and the aircraft should fly a perfect idle descent to TESSI.  Note that the original altitude selected for the pinpoint in the LEGS page does not reflect the new change.

Benefits

One of the advantages in using the Vertical Descent Indicator is that the pilot can instigate an accurate controlled idle descent, following a desired glide path to the desired waypoint.  This advantage can be used in a number of scenarios:

  1. Descent from cruise altitude.

  2. Approaching the runway from a straight-in approach course.

  3. Approach the runway from base or via an ARC approach.

  4. Approaching the runway for a downwind approach.

I often use the VBI from FL10 to FAF on approach, when other constraints are not required.

Video

I’ve made a short video showing the procedure. 

In the video, TESSI has been selected from the LEGS page and downloaded to the scratchpad.  Pressing DES opens the required page where the VBI resides.  In the scratchpad, the altitude constraint is entered for the waypoint – TESSI/17000 and uploaded to the WPT / ALT section of the Vertical Bearing Indicator (right line select 3). 

If you watch the indicator you will see the V/B and V/S changing as the aircraft approaches TESSI. 

Select the new altitude and vertical speed on the MCP (17000 & 780 - or nearest numeral) and you will note the FPA begins to change, indicating the new vertical path of the aircraft.  The Navigation Display (ND) will then show the Altitude Projection Line moving towards and stopping at TESSI.  The aircraft will now descend at the nominated angle of descent until reaching TESSI.  Note that the original altitude in the LEGS page does not reflect the new change.

 
 

Avionics Software - Selection and the Future

south West at phoenix sky harbor airport (aeroprints.com, N643SW Boeing 737 Southwest (8401799774), CC BY-SA 3.0)

Southwest Airlines is the largest low cost airline in the United States, and has maintained its success on a simple business model - its decision to fly only one type of aircraft, the Boeing 737.  By streamlining their fleet to only one aircraft type, savings can be made in maintenance, logistics and support.

Southwest only need to employ maintenance personnel knowledgeable on one aircraft type, pilots do not need to be cross trained, and more importantly flight and support crews can be airlifted anywhere to begin work immediately should a problem arise.  There is no time delay waiting for a type pilot or engineer to be found.  In the airline business, lost flight time means a loss in revenue.

So what has this got to do with flight simulator or avionics software suites?

Avionics Software Suite – What’s this?

Before proceeding, the avionics suite is the software that controls the aircraft’s avionics systems within the simulator.  The avionics suite controls nearly everything associated with the simulator that is automated and includes among others: the integration of the Main Instrument Panel (MIP) and Main Control Panel (MCP) and the projection of this data to the Navigation Display (ND) and Pilots Flight Display (PFD).  The software does not replace the main flight simulator platform (FSX or whatever), but acts as a separate platform.

It’s important to realize that this software is VERY important.  It is the backbone of any simulation and directly controls whatever flight model you are using.  Any software used must be accurate, robust, replicate real aircraft systems, be reliable, and be able to replicate its outputs on a consistent basis.

There are two broad types of suites – those that can be used in a full flight deck simulation and those that are more suitable to a desktop set-up.

State of Play - Software Contenders

Historically, Project Magenta (PM) was only one contender if you wished to tackle the task of building a 737 simulation.   At the time, the software was complicated and required the user to network several computers.  The software developed by Project Magenta initially led the way, laying the building blocks for others to follow (bravo to PM).

In 2012, contenders are several: Project Magenta, Sim Avionics (Sim-A), Orion, Aerosoft Australia, Flight Deck Software, ProSim737, Precision Manuals Development Team (PMDG), i-Fly and several lesser known companies produce software that emanates the avionics of the B737.  Other software suites “pop up” on the horizon from time to time as talented software engineers attempt to enter the marketplace.

Which Avionics Software Suite Should I Use?

This is a personal decision and I’m not going to publish a “tit for tat” discussion to which suite from which company is better or worse.  I will say that each company’s software brings different aspects of the flight deck to realization – some with greater accuracy, detail and finesse than others.  Before you purchase a suite, it’s vital to investigate exactly what that suite can and cannot do in relation to the hardware you have installed in your simulator.

Software suites offered by rival companies are NOT identical to each other.  Some developers have added functions and displays to their software in an attempt to make them more user friendly, or to be used for multiple aircraft types.  Other developers try to replicate the displays in the real aircraft.

Before purchase, you should identify what aspects are important to you, will work your simulator, and represent the functionality you expect.  Flight deck building and simulation is often very much about compromise.

Just because software is expensive or inexpensive, doesn't imply it's well tested and stable; try and see beneath the marketing veil.  Some of the smaller lesser known software suites are very good and provide excellent value for money.  For example, Aerosoft Australia has released a very competitively priced avionics suite which is more than enough for the average simmer who does not want to use an overhead panel.

Reliability, Repeatability, Accuracy, Expectations and Support

The most important facet of any software is reliability and repeatability; both mutually support each other.  Unfortunately, not all suites are reliable or have the ability to repeat defined outcomes.  Some high end and expensive software suites are plagued with teething problems, which for the most part, are left to customers to solve or report to the developer, in the hope that an update will rectify the issue.

As discussed earlier, software suites are not identical in functionality or appearance, even though in theory should replicate what is found in the real aircraft.  Although some of these variables are aesthetic, such as font type, size and colour; attributes that many virtual pilots deem important.  Other issues are not aesthetic and may relate to the available functionality of a particular system – such as the Flight Management Computer (FMC).  Depending upon the developer, upgrades to a software suite maybe frequent or only once every six months.

I have reviewed Sim Avionics in an earlier post.  ProSim737 will be reviewed shortly.

Expectations

It’s important to understand that replicating all the systems of a fully functional 737 is a continual challenge.  Real simulators can cost upwards of 15 million dollars and expecting the same level of performance, reliability and repeatability from a software suite, for less than $1500.00, is not reasonable.  Add to this the vast array of different computer designs and installed hardware and you can easily see why minor problems can occur.

EVERY software suite has teething and minor issues.  This said; please don't go away with the notion that every piece of software is a nest of problems - this would be incorrect.  What is important, is to go away with the notion of "reasonable expectation".

Some developers, in an attempt to work around complicated issues have chosen not to implement certain systems or parts thereof.  These same systems in another suite may work perfectly or not at all.  For the most part, problems stem in the accurate development and execution of Vertical Navigation and the integration of a “fully functional” Flight Management Computer (FMC).

Support from the development team of the suite you have chosen is paramount.  Many issues can and are easily solved.  But a prompt and efficient support base, regularly visited and updated by the software developers is essential.  It also should be noted, that many developers work closely with users to rectify teething issues within their software.   

Connectivity with Micro$soft Flight Simulator and Prepar3D

Most virtual pilots use FSX or the earlier FS9 as their baseline program.  These programs are no longer being developed or supported by Micro$oft and are quite ancient with regard to much of their software architecture.  Other than X-Plane and a few other “no shows” the only program being developed as a baseline program for flight simulator is the Lockheed Martin Prepar3D.  I am not using Prepar3D, however, I envisage I probably will be within two years.  It’s important to ensure compatible with what well may replace FSX.

The Future

What does the future hold?  As computers became faster and software advances continue, almost exponentially, I envisage that avionics software will become more sophisticated and refined in how fluid they interact with, and parallel real aircraft systems.  If the recent release of PMDG’s 737 NGX is anything to go by, it’s only a matter of time.

Two Camps

Presently, there are two camps; desktop users and those using partially or fully developed flight decks.  This is not including turn-key type full LEVEL D simulators.

PMDG, closely followed by i-Fly have taken the limelight in the production and release of the NGX. However, the NGX simulation is more suitable for desktops than a flight deck.  I-Fly has taken a step forward, but only has partial functionality to cater to flight deck builders.

Technology doesn't remain static and improvements will drive more companies to produce dedicated software; the days of one or two companies reigning is quickly paling.

Market Share

Historically, Project Magenta was the suite of choice for those wishing to develop a fully functional flight deck, however PM is no longer the “strawberry fox” and is now showing its age, being surpassed by new “high end’ contenders such as Sim Avionics and ProSim737.  Put simply, these new contenders produce software that is more reliable and sturdier, easier to understand, install, and configure, and can operate on a minimal number of networked computers.

Project Magenta in an attempt to regain market share has also extended its reach to support different jet aircraft including general aircraft. Sim Avionics has followed suit; in addition to the 737-800 NG, they also produce avionics suites for the 747, 767, 777 and the A320.

Southwest's Business Model

Other than i-Fly with its duel platform approach, and a few lesser known manufacturers, the only “high end” company dedicated ONLY to the development of the B737 for use in a full flight deck is ProSim737.  Like Southwest Airlines, ProSim see benefit in producing only one avionics suite, doing it to the best of their ability and providing continued development until, if you excuse the phase “it’s as good as it gets”.

Leaders and Followers

The future is blurred, but in relation to a fully functioning B737 flight deck simulation, I believe that ProSim737 and Sim Avionics will run “neck and neck”.  Presently, ProSim is more advanced in some aspects than Sim Avionics; but Sim Avionics comes under the mantle of Flight Deck Solutions which is a forward-moving company with a history of aggressive and progressive development.  I don't expect Sim Avionics will sit idle and wither on the vine...

Leadership in desktop simulation will probably be left to the current two major players PMDG and i-Fly; both which will “heckle” for the leadership, with i-Fly probably keeping feet in both camps.  

The other "lesser" contenders will always be there, and this is a good thing.  Competition drives development and improvement, which translates to increased functionality, greater simplicity and more stable software.  This can only benefit the consumer - YOU.

Flight Path Vector (FPV) - Explanation and Use

FPV button located on the Electronic Flight Instrument System (EFIS) unit on the Captain and First Officer side.  EFIS unit produced by CP Flight (Pro model)

I often get asked what the FPV button does on the EFIS unit.  Pressing the button doesn’t do anything grand or remotely obvious, unless you are observant and note that an oddly shaped circle with lines has instantly appeared on the Primary Flight Display (PFD).

What is the Flight Path Vector and What Does it Do - The Basics

The FPV is a small circular symbol which, when the FPV button on the EFIS is depressed, superimposes over the Attitude Indicator (AI) part of the Primary Flight Display (PFD). The circular symbol represents the aircraft's axis in relation to the vertical and lateral movement referenced to the Earth's surface.  If you were stationary on the ground, the circle would be on the horizon line and centered in the display.

The data received by the FPV is derived mostly from the Internal Reference System (IRS) of the aircraft; therefore, the Flight Path Vector provides an almost instantaneous display of flight path angle and drift information.

For example, if an aircraft took off in a 15 Knot crosswind the Flight Director (FD) bar would register the pitch of the aircraft while the circular FPV would be located above the horizon and to the right or left.  The lateral deviation of the FPV provides a visual indication of drift caused by the crosswind, while the vertical deviation shows the aircraft's attitude or pitch.

Flight Path Vector (FPV) in ProSim737 avionics suite.  The FPV symbol is in small circle with three lines. It reads roughly 2.5 - 3 degrees nose up.  The aircraft is in TO/GA command mode ascending at 1100 feet per minute to flaps up speed.  There is no crosswind so the symbol does not show a deviation (drift) from center

When the aircraft changes from climb phase to level flight, the FD bar is commensurate with the configuration of the aircraft (speed, weight, flap, etc.) and the FPV would be on the horizon line, indicating level flight.

Descending in approach phase on a 3 degree glidepath, the position of the FD and Horizon Heading Scale (aircraft symbol bar/pitch bar) is  dependent upon the speed, flap and gear extension, but the position of the FPV will stay at 3 degrees, unless the flight controls are used to alter the aircraft's pitch. 

The FPV will provide greater accuracy than the Horizon Heading Scale as it does not 'lag' behind real time as other instruments can do; therefore, it is sensible for flight crews to include this tool in their routine scan.

Boeing provides a caveat in their literature, stating that the FPV is not a primary flight instrument.  Therefore, information displayed by the FPV should be used to augment data from the primary instrumentation.

Flight Path Vector (FPV) Advantages

The Flight Path vector is a very helpful tool:

  • It enables you, at a glance, to assess the performance of the aircraft. If the FPV is in the blue part of the Primary Flight Display, you are definitely ascending. Vice-versa when you are in the brown.

  • If you are unlucky enough to have a windshear encounter, the first instrument to warn you other than the  aural warning will be the FPV as it assumes an unusual position (drops away or rushes up). The other instruments (altitude, vertical speed and airspeed) have significant lag before they accurately show the true picture of what is occurring, but the FPV provides an almost immediate indication (live-time). 

  • It is an ideal tool to use during non-precision approaches as it provides the flight crew with additional situational awareness, especially during night operations.

  • The FPV is an ideal tool to gauge the accuracy with which the aircraft is flying a glideslope and can be used to cross check against other information.

  • The FPV is an ideal tool to monitor non-automation phases of the flight (manual flying) as the flight crew need only to keep the FPV on the horizon to maintain level flight.

  • The FPV registers the smallest trend almost immediately, while the flight director (FD) will only correct an issue after a deviation has occurred. 

  • The FPV can be used to provide additional information during crosswind landings. If you look at the FPV as part of your usual instrument scan, the FPV will provide visual display to whether you are correctly aligned with the center line of the runway (the FPV will display the drift).

The last point requires expanding upon, as the FPV can be used to determine the correct rudder deviation to use when using the side slip method for a crosswind approach and landing. A crosswind will push the FPV circle in the direction that the wind is blowing TO. Rudder inputs will cause the FPV symbol to move towards the the center of the Altitude Indicator.  Once the the FPV is centered in the Altitude Indicator, the aircraft is aligned correctly (no drift).

The Flight Path Vector is a small unobtrusive icon located on the PFD that pays large dividends when used correctly.  Not only can this device warn you of impeding problems but it can be used to facilitate greater flight accuracy in a number of conditions including approach, straight and level flight, and crosswind landings.

 

Diagram 1: Schematic of the Flight Path Vector showing how it relates to aircraft axis, angle and drift (copyright felix M)

 

CP Flight ADF Radio Modules - Review

cp flight ADF radio, NAV 1/2 and M-Comm communication module (Flight Deck Solutions).  Note the use of oem 737 DZUS fasteners

CP Flight in Italy is well known for its production of quality simulator parts, in particular their Main Control Panel (MCP) units that work out of the box – literally plug and fly.  This short review is for the ADF Radio modules that I have recently installed into the simulator center pedestal to replace the radios made by SISMO Solicones. Although this short review pertains to the ADF radios, all CP Flight modules are made similarly to the same quality and utilise the same methods of connection.

ADF radios may appear “old school” with many virtual flyers more concerned in learning and understanding the more modern LNAV, VNAV and GPS navigation systems.  It’s important to realize that not all countries comply with the aviation regulations enforced within the United States (FAA).  Many developing nations still use VOR and ADF stations as the primarily means of approach.  Further, knowing how to use and having the appropriate equipment installed to be able to follow these “older style” navigation beacons is often good practice for redundancy and to cross check the results from primary navigation.  Using VOR and ADF navigation is also more challenging, interesting and enjoyable.

Construction and Appearance

The modules are constructed using the same technique that CP Flight uses to produce all their modules and panels.  Each upper panel is made from CNC machined acrylic which produces a very crisp finish and allows any letter cut-outs to be very well defined.  The electronics board, rather than being left “naked” like other manufacturers, is sealed within a lightly constructed metal case.  To allow the user to drop the module directly onto the pedestal rails, each module has overlapping wings that conform to the width of the rail.  To ensure long life, the ADF radio modules incorporate dual concentric rotary encoders with stainless stems rather than plastic stems.

Inspecting the pictures of the ADF radios. you will observe a thin line of light between each illuminated digit.  This is not visible in true life and is only an artifact of using a rather long shutter speed to take the photograph.

High Quality

The knobs and switches, which are custom machine injected, are true to life and are tactile in feel.  As you click through the frequencies the movement is stable and well defined.  There is no catching as the knobs are turned.  The push keys on the units are plastic moulded, backlit and work flawlessly; they do not stick in the down position when depressed, and click back into position when pressure is released.  The frequency displays are 7 segment digits and are very easy to read.  Digit colours are in amber yellow. 

The upper panel of the module is attached to the electronic circuitry within the lower section by a metal backing plate; this increases the strength of the unit and assists in the dissipation of heat.  The modules are a well presented piece of avionics that accurately replicates the functionality found in the real 737 navigation radio. The panel is 1:1 with the OEM counterpart.

A light metal case protects internal electronics and two 5 pin DIN plugs supply connection and power to and from the radio and to other CP Flight components

No System Boards and Daisy Chaining

The modules do not require control boards - they are completely stand-alone.  This minimises the wiring involved and the challenge of finding another location for yet another I/O card.  However, to operate the modules you will require either the CP Flight Main Control Panel (MCP) or the 737MIP board.  Both of these devices provide the power and ability for the modules to connect to and communicate with the main computer and FSX.

CP Flight uses what has to be one of the simplest methods for module connection – daisy chaining.  Daisy chaining is when you have several modules linked by 5 pin DIN style connectors and one cable.  The cables connect in relay between whatever modules you are using and eventually link to either the CP Flight Main Control Panel (MCP) or 737MIP board for connection to the computer via a single USB cable.

Boeing Grey

All CP Flight B737 series modules and panels are professionally painted in "Boeing grey".  I’m not sure how many thin coats of paint are applied, but to date I have experienced no problems with regard to paint chipping or flaking.  Although this last comment may appear trivial, the quality of paint is important.  The modules will be used for many years and during the course of operation, you will be placing pens, clipboards, charts, coffee cups, etc on the center pedestal and the modules.  Further, as the units are flat, dust will accumulate requiring dusting and cleaning.  Low quality paint will scratch, fade and wear thin with time.

The observant will note that there is a difference in colour shade between the modules made by CP Flight and Flight Deck Solutions.  A purist may argue that this is not realistic, however, I disagree.  Through time, Boeing has used several shades of what has been coined "Boeing Grey" and it is not unrealistic to have modules sporting different shades of the baseline colour.  Different avionics manufacturers (in the real world) also use different colour shades of "Boeing grey". 

DZUS Complaint

If you are utilising real aircraft parts in your simulator, in particular a center pedestal, then any module that is DZUS complaint is advantageous as it allows for the module to be dropped directly onto the DZUS rails and secured by the DZUS fasteners.  Unfortunately CP Flight fails in this area as their modules are not DZUS complaint.  Each module has the appropriate holes drilled; however, they only fit replica DZUS fasteners (supplied).  The width of the hole is too small to install genuine DZUS fasteners; you will be required to drill the hole a little larger to accommodate the genuine B737 fastener.

This picture illustrates the fit of the CP Flight ATC panel to the rails of an oem center pedestal Each panel is very closely aligned to the holes in the rail enabling the replacement of reproduction dzus fasteners with oem dzus fasteners

Back-Lighting

The ADF modules are back-lit by several strategically placed LED lights.  This is commonplace within the industry with the exception of some high-end suppliers such as Flight Deck Solutions which use their own IBL back lighting systems utilising real aircraft bulbs.  I have no issue with the back lighting and the module is evenly lit, illuminating all cut out letters.

CP Flight Module Set-up

The modules are stand-alone and do not requite software to be installed for operation – they are plug and fly; however, to connect the modules (via daisy chaining) to the computer via a single USB cable, either requires the CP Flight Main Control Panel (MCP) which acts as a power source amongst other things, or the dedicated 737MIP board.  Software is required for the operation of the MCP and 737MIP board and can be downloaded from the CP Flight website.  The software is easy to install and to configure. 

Downside – Ghosting of COM Port

I’ve already discussed the simplicity of daisy chaining and the benefits of not needing to use a multitude of wires and I/O cards; but, everything comes at a price and CP Flight’s “Achilles Heel”, is the method they have chosen to connect everything to the computer.

Modules are connected to and from each other and to the MCP or 737MIP board via daisy chaining.  The MCP or 737MIP board provides the power to run the module and allow information to travel between the computer and the module. The MCP or 737MIP board is then connected to the computer via a single USB cable.  To connect to the computer requires that a COM port is ghosted to replicate a serial port. 

Whilst this process is automatic, and occurs when power is applied to the MCP or 737MIP board, many users experience problems with the software ghosting the port.  Usually the ghosting issue is solved with appropriate drivers and once the connection is made once, rarely is this problem again experienced.

Reliability and Performance – Software and Modules

Software

No problems, other than the initial connection problems that “maybe” associated with the ghosting of the COM port.

Modules

There is no time lag when altering frequencies; the digits spin as fast as you can turn the dial.  Drop outs have never occurred.  The tone switch operates correctly and always listens for and connects with the correct marker morse tone.  It’s important to note that the tone switch does operate as designed and can be used to switch off the “somewhat annoying” morse tone which is heard, when in range of the ADF.

Support

Support from CP Flight is either directly via e-mail or by a dedicated forum.  The support provided by CP Flight is exemplary.  Paolo from CP Flight stands by the products he sells and every effort is made to ensure your modules work as advertised.  There is absolutely no problem dealing with this company as the owners are very trustworthy and deliver what they promise.

Quick List – Pros & Cons

PROS

  • Well designed & constructed

  • Realistic quality machine-injected switches & stainless rotaries (not plastic)

  • 1:1 to the real B737 series aircraft

  • Good attention to detail

  • Operational morse tone switch

  • Strategically positioned backlighting

  • Very easy to set-up and connect (daisy chaining)

CONS

  • Ghosting of COM port can be an issue when using MCP as connecting equipment (no experience with 737MUIP board)

  • Non DZUS compliant

Overall Opinion

I am very impressed with these modules.  They are solid, well constructed and operate flawlessly out of the box!  The quality of the modules is very high and it’s a pity that they are not made to be DZUS compliant.  They suit the high end enthusiast to professional market.  

My rating for the modules is 9/10

Please note that this review is my opinion and is not endorsed by CP Flight.

Telex Airman 750 Headset - Adding To Realism With Real Parts

oem telex 750 headset

To quieten some of the ambient sounds (dogs barking), I use a David Clark aviation headset (model H10 13-S) which is a left over from when I did my ]private pilots license (PPL).  This particular headset is a marvel of engineering and works exceptionally well for real world flying and simulator use.

Recently, I saw for sale in a wrecking yard, an airliner style Telex Airman 750 headset.  The price was $30.00 including freight from the USA to Australia.  To be honest, I wasn’t expecting too much – after all, what does one get for $30.00 these days!  I was pleasantly surprised when I opened the FEDEX sachet and an almost brand new headset, equipped with boom mike and tell-tail aviation style audio connectors and cable, fell onto the floor.  The foam ear pieces were still good condition, as was the small clip that attached the cable to your collar (to stop the cable from snagging).

After plugging in the headset to the Flight Sound X Adapter (click to see earlier review), I was even more surprised when the headset worked!  Sounds were crisp and easy to hear and the weight of the headset minimal.  The boom mike relayed my voice more than adequately across the network to VATSIM.

Using real aircraft parts adds to the realism of flight simulator; a headset being just one item.  I guess bargains still do exist.

Runway Awareness & Advisory System (RAAS) - FS Add On

A runway incursion is an incident where an unauthorized aircraft, vehicle or person is on a runway. This adversely affects runway safety, as it creates the risk that an airplane taking off or landing will collide with the object.  Runways incursions are not uncommon.  One carrier, Alaska Airlines has introduced an additional warning system in their flight decks to counter against this potential problem.  The system is called RAAS or Runway Awareness and Advisory System.

The Runway Awareness and Advisory System developed by Honeywell in 2003, provides pilots with audible alerts when they approach and enter taxiways and runways. The system confirms runway identifications to help ensure pilots are on the correct runway with enough distance to complete takeoff, and provides an audible warning if a pilot inadvertently accelerates for takeoff while on a taxiway. 

RAAS is not compulsory in the real world, but is an option that is purchased by an airline.   The use of RAAS is a nice addition to include in your flight deck.  Dongjin Shin, a software engineer has developed RAAS for us to use in flight simulator.  His program is called FsRAAS Runway Advisory.

Software Installation and Make Runways

The program is a stand-alone program, meaning it does not need to be installed into flight simulator; it can be run from anywhere on your computer, however, I have been 'informed' the recommended place for installation of the software is in the same folder that FSUPIC is installed (FS10 root directory/modules).

Once the program has been installed, it is necessary to synchronise the runway data in your scenery file with FsRAAS.  To not do this will cause erroneous call-outs.  To synchronise the runway .bdl file you run MakeRunways 4.692 developed by Peter Dowson.  This software is stand-alone and can be downloaded for free (MakeRunways).  Follow the instructions carefully and once the software has been run, copy the generated r4.csv file found in the modules folder to the same folder that you have FsRAAS installed.  Copying this file will ensure that FsRAAS is synchronised with the airports in your scenery file.   It's important to remember that if you update your scenery, MakeRunways will need to run again and the file copied across to FsRAAS folder.

FsRAAS can be started before or after FSX; I prefer to start the program after FSX has been configured for flight.  I have a shortcut to FsRAAS on my desktop menu and after FSX is running I click the shortcut and FsRAAS immediately starts and minimises. At the moment, FsRAAS cannot be run from client computers as it does not support WideFS.  However, the computer workload of running this very small add on is not noticeable on high-end computers.  The program does require FSUPIC for correct operation.

Evaluation

My initial evaluation of FsRAAS has been excellent and I’ve incorporated this program into my flight deck.  The program will provide, at the minimum, the following audible call-outs;

  • Approaching/crossing taxiway

  • Approaching/crossing runway

  • Flaps not set call out (flaps flaps flaps)

  • Lined up on runway (ie: runway 34R call-out)

  • Runway distance remaining after take off roll (eg: 2000 feet remaining call-out)

  • Runway distance remaining after landing and roll out

  • Approaching runway on final approach (approaching 34R call-out)

The software's .ini file can be easily altered to reflect certain changes in the various call outs such as distance to a runways, approach speed, etc.  The .ini file is found in the FsRAAS folder.

My only vague criticism (if pushed) is that the call-outs are slightly delayed when approaching a runway or taxiway.  The program is currently a free program and can be downloaded directly from Shin's blog site, or search the AVSIM library for FsRAAS11-1, or the latest release FsRAAS 2.

Below is a short embedded video of the FsRAAS courtesy of the developer.

 
 

Update

on 2012-07-03 06:16 by FLAPS 2 APPROACH

A new version of FsRAAS has been released which rectifies some of the shortcomings in the original version and adds additional functionality.  It is called, not surprisingly FsRAAS V2.

Update

on 2018-03-23 11:53 by FLAPS 2 APPROACH

Recently, FsRAAS V2 stopped working on my client.  Despite considerable fault-finding I could not establish why this occurred.  Speaking with other enthusiasts, I discovered that I was not alone as others had the identical problem.  Therefore, I did further research to determine if another RAAS add on was available.

Note that FsRAAS V2 does not operate on the Prepar 3D simulator platform.

I purchased from FS2Crew FS2Crew Professional RAAS.  The Software replicates the original callouts produced by Honeywell (the developer of the RAAS system). 

Aircraft Liveries & Textures - Adding a Livery Texture To Your B738

For many flight simulator enthusiasts, there’s enjoyment knowing your flying the correct aircraft livery in the correct airspace.   For others, opening the exterior views to play back your landing sequence from the flight video just looks better with a nicely painted texture or livery.  FSX comes bundled with several B738 aircraft liveries, but most of us dislike them; it’s common for individuals to search forum sites such as AVSIM in an attempt to find a livery that suits their virtual airline.

Recently, I found a FS add on that includes 164 liveries of the B738 aircraft suitable for FSX.  The file, which includes an automatic executable, can be downloaded from the French flight sim website http://www.rikoooo.com/en/downloads/viewcategory/55.   The program will download to your simobjects/aircraft folder a folder named 164 aircraft.  Within this folder can be found all the textures and a correctly constructed aircraft .cfg file.  The program also includes a correctly configured airlines file which will over right your existing airline file with all the correct ATC calls for the various liveries.  This is a wonderful time saver for those who use ATC.  Access to the aircraft is as you would usually load an aircraft, airport and weather situation..  Note that you will be required to register to the forum site before you can download the program.

Below is a list of livery textures included in the package

Adam Air, Aeromexico, Aerosvit, Air Asia Indonesia, Air Astana, Air Berlin, Air Canada, Air China, Air China Olympic, Air Europa, Air France, Air Jamaica, Air New Zealand, Air One, Air Slovakia, AirTran Airways, Air Vanuatu, Alaska , Alaska.com, Alaska Spirit of Seattle, Alaska Starliner 75, Alitalia, All Nippon Airways (ANA), ALOHA, American Airlines, America West, Ansett Australia, Austrian Airlines, Batavia Air (x3), Bmibaby, British Airways, Brussels Airlines, Bulgaria Air, Caribbean Airlines, Cebu Pacific Air, Continental Airlines, Copa Airlines, Corendon Airlines, Cubana De Aviación, Cyprus Airways, Czech Airlines, Delta Airlines, DHL Cargo, EasyJet, Eastern AIrlines, El Al (Israel), EgyptAir, Europe Airpost, FedEx Cargo, Ferrari, Ferrari Cargo, Finnair, First Choice, Flash Airlines, Fly Dubai, Flyglobespan, Frontier Airlines, Garuda Indonesia, Garuda SkyTeam, GOL, Gulf Air, Hainan Airlines (x2), IRONMAIDEN, Japan Airlines (JAL), JAT Airways (old and new), Jet2 (grey and white), JetAmerica, JetTime,Kenya Airways, Landmark (Coliseum tail), Lion Air (Indonesia), LOT (Polish Airlines), Lufthansa, Luxair, Malaysia Airlines, MALEV, Mexicana (x4), Military Woodland Camo, Mongolian Airlines (MIAT), Montenegro Airlines, Myanmar Airlines (MAI) , NASA, NAVY, Norwegian Air, Northwest (NWA), OceanAir (Avianca), Olympic Airlines,  Pan-Am, Philippine Airlines, PIA (Pakistan Intenrational Airlines), Prague (Czech Republic), Primera Air JetX (Iceland), PrivatAir, Qantas, Ryanair, Ryanair Guinness, Ryanair Kilkenny, Ryanair Vodafone, Scandinavian Airlines (SAS), Singapore Airlines, South African Airways, Southwest Airlines (Blue, Gold, New Mexico), Sterling (Australia), SunExpress, Swiss Air, TAM (Brasil), TAROM (Romania), Thomson Airways, Transavia, TUIfly (x7), Turkish Airlines, Ukraine International Airlines (UIA), UNITED (old and new), UPS Cargo, US Airways, Varig (old and new), VASP (Brazil) , V Australia, Vietnam Airlines, Virgin (blue and red), WestJet, XL Airways, XL Airways Excel.com, XL Airways Öger Tours and XL Airways Viking.

I think you will agree, that anyone should be able to find something they like from this list.

Installing to the ProSim 737 JetStream

To use the textures in the ProSim737 Jetstream B738 aircraft, it will be necessary to edit the aircraft.cfg file.  I’ve outlined the process below.  Before proceeding, make a backup of the JetStream folder BEFORE making changes.  It’s always good policy to do this just in case a problem is experienced.

A:  Copy all the aircraft texture folders (located in the 164 folder), or the ones you want as 164 edits can take a long time...., to your Jetstream folder located in simobjects/aircraft.

B:  Open two windows, one with the aircraft .cfg file opened from the 164 aircraft folder and one with aircraft .cfg file opened from the Jetstream folder. 

C:  Open/click the Jetstream aircraft .cfg file for editing. There are four main edits that need to be made.

  1. The FLTSIM number needs to be edited to reflect the correct order within the file.  Check and make sure the first airline entry is 1 followed by 2, 3, 4, 5, 6, 7 and so forth.

  2. The TITLE must be title=Jetstream738 B737-800 Air New Zealand (or whatever livery)

  3. The Sim must be sim=Jetstream738

  4. The UI manufacturer must be ui_manufacturer=”A Jetstream-Boeing”

Duplicate the text from the above mention 4 lines from the 164 aircraft.cfg, for the aircraft liveries you want, to the Jetstream aircraft.cfg file.  it's important to do these edits as you want to link the livery texture to the Jetstream flight model.  The image shows a screenshot of one of the aircraft textures from my JetStream aircraft.cfg file.

I’ve bolded and coloured red the entries that need to be edited to reflect the new aircraft textures.  You may also wish to change the ATC flight number, but this isn’t necessary for correct operation.

You have probably observed that my naming structure is a little different to the norm.  The reason I begin the name with the letter A, is so that when I open the select aircraft tab in FSX, I don’t have to scroll down to J for JetStream.  Instead, the correct folder is located at the top of the list (The letter A is at the beginning of the English alphabet).

There you have it.  The methodology explained here can be used to add textures for any aircraft livery.   

Using PMDG 737-800 NGX Sound In The Default 737-800

I have received a few e-mails from individuals asking how to replace the default sound with the sound from the PMDG 737-800 NGX.  This is a relatively easy task and the improvement in audio quality and experience over the default B737 sound is second to none. 

Before continuing, I should state that PMDG have designed their NGX audio package to only be used with the PMDG flight model.  As such sounds that PMDG have mapped to specific actions within their flight model will not work outside the PMDG flight model.  I'm sure there is a way to strip the actual "specialist" sounds, but the time required outstrips the enjoyment.  This said, the basic engine sounds and environmental sounds are easily separated for use in other flight models, such as the default 737 and ProSim JetStream738 flight model.

In the examples below, my main FSX folder is located in a directory on C:/ drive and is named FS10.  You may have a different directory location and name for FSX.

Let's Begin....

When you install the PMDG 737NGX, the program copies audio to the following folders:

  1. FS10/simobjects/airplanes/PMDG 800 NGX/sound    (main engine sounds & some environmental sounds)

  2. FS10/sound/PMDG 737-800NGX/sound......   (specialist sounds such as gear lever movements, switches, call outs, etc)

The default B737-800 model’s audio is located in the default 737/800 folder (FS10/simobjects/aircraft/737-800/sound)

Make a copy of the sound folder and store to desktop in case of an issue.  Then, delete the sound files in the folder so you can start afresh

Two Methods - Back-up, Copy & Paste or Alias

There are two methods to access or link to the actual PMDG sound files.  You can either copy all the sounds (from the PMDG 737-800NGX/sound folder) and paste them into the default 737-800 sound folder – OR – alias the sounds.  

If you decide to alias the sound, you do NOT need to copy the files.

Either way you MUST have a sound.cfg file in your audio folder.  If you alias the sound.cfg, the content of the sound.cfg file located in the sound folder should look like this:

  • [fltsim]

  • Alias=PMDG737-800NGX/sound

If you have issues opening the sound.cfg file, use notepad as your editor.

If you decide to actually copy the files, then ensure the sound.cfg is also copied to your default sound folder.

I prefer the alias method......

The above process will allow you to play and hear the NGX engine package when flying the default B737 flight model (basic FSX B737-800).  You can also use the same methodology to replace the default sounds with the with the ProSim JetStream 738 fight model and with the FS9 version of the PMDG 737-800.

Following On - Replacing Audio

Following on the theme of the last two journal posts, you may wish to add additional sounds to the NGX audio package, for example, the TSS sounds Gear Up and Gear Down sounds.  This is easy to do.

Copy the TSS sound to the SAME folder as the PMDG sounds (if you did the alias method this will be the PMDG folder).  Now, open the sound.cfg file.  Search until you find the Gear Up and Gear Down entries.    Now, you have to modify the file name in the sound.cfg file so it matches the TSS.wav file you just copied into the audio folder.  In this example, the pertinent lines that need altering are in bold and include the actual name of the action (gear up) and the file name for the action that you wish the program to play (TSS gearup).  

  • [gear up]

  • Filename = TSS-gearup (or whatever the .wav file name is)

Make sure you do NOT have two files that do the same thing, such as gear up TSS and gear up PMDG – your computer will explode!!! (not really, but the sound will not be heard correctly).

Gauge Commands

PMDG, i-Fly and several other sound designers configure their custom sounds to play only when specific actions or commands are triggered - these are called gauge commands.  A sound initiated by a gauge command only works when that gauge is moved by whatever action.  Often it's not possible to use these sounds without some major editing work to the sound.cfg file.  For example, I've been attempting to use the speedbrake sound in ProSim737, but as yet have not been able to do so.  This is because the speedbrake is configured to a specific "in house" command or action - in this case the speedbrake. 

You cannot just grab any sound, copy it to the audio folder, and then expect it to play.  There has to be some logic to when the sound is played.  This can be most challenging and frustrating part of manipulating custom sounds.

I hope this journal post, as an addition to the last two sound related posts, helps more than confuses.  Sound can be a nightmare and can be challenging to explain in a short journal entry.  It is also very much a trail and error activity (the Americans say suck and see) - Good Luck.

Separating Audio To Different Speakers - Sim Avionics & ProSim 737

When I did my PPL some years ago, I had purchased a David Clark headset for use during my flight training.  The headset was a wonderful aid to hear ATC and my instructor whilst filtering out the engine noise and other ambient sounds found in a small cockpit of a Cessna 182.

Although it’s not common place to use a pair of David Clark headsets in a B737 (unless a military version), I decided to use the headset to filter out engine noise, ambient noise, and to hear ATC and ATIS announcements a little more clearly.

Using a real headset

Using a real headset with FSX isn’t that complicated if you’re satisfied with the way flight simulator separates audio.  It only becomes complicated when you want to attempt to replicate exactly what occurs in real flight deck. 

In a real flight deck, all communication and navigation sounds (ADF, DME, markers, etc) can be heard through the headset and /or flight deck speaker.  Unfortunately, in FSX the opposite occurs, with navigational sounds being heard through the main speakers only.   FSX only separates ATC and ATIS (voice).

So how do we separate audio to hear various sounds through different speakers and the headset.

Separating Audio – Choose Your Poison

There are several methods to achieve audio separation; some methods are easier than others.

You can either utilize what is already available on your computer through FSX.  This is the easier and simplest method and works well with my policy of KISS (keep it simple stupid). 

If you’re feeling more energetic, and wish to separate sounds to several strategically placed speakers, then a second sound card is probably your only option. With two sound cards on your computer, you can now select which sounds play through which sound card. 

If you’re loath to install a second card to the innards of your computer box; then, explore one of the several add on sound cards that can connect to your computer via USB – some cards offer 5:1 surround sound while others offer just a basic sound card interface.

Another method (which I have chosen to follow) is to duplicate sound programs and run them on separate networked computers.  High-end flight avionics software such as produced by Project Magenta, Sim Avionics and ProSim737 support this.

The Easy Way with FSX

FSX supports the separation of basic audio.  It’s as easy as opening the sound menu in FSX and selecting which sound is played on which device - speakers or headset.  Engine sounds will be diverted to the surround speakers and ATC and ATIS will be diverted to the headset.  This works very well, however, only ATC and ATIS voice is diverted to the headset.  Navigation sounds, call outs, etc are not heard through the headset.  To divert these sounds requires a little thinking outside of the box.

I’ve attempted to explain basic audio segregation using two popular flight avionics suites: Sim Avionics and ProSim737.

Using Sim Avionics – Basic Operation

One of the upsides of using Sim Avionics or ProSim 737 is that it allows you to simultaneously operate different facets of the flight deck from multiple computers.  In my set-up I am running two computers – one with FSX installed (called the server PC) and one with Sim Avionics installed (called the client PC).  Both computers have speakers attached. 

To install audio on both computers you will need to copy the sound.exe file and audio folder found in your Sim Avionics main directory to the server PC (computer that has FSX is installed).  You will also need to copy the Client_TCP.exe file as this file allows Sim Avionics to communicate between networked computers.  Once copied to the server PC, click the executable sound.exe file after you have opened FSX.   Sounds will now be heard through speakers on both the client and server PC.

Using Sim Avionics – Separating & Customizing Sound

This is comparatively easy and involves selecting the sounds you do not want to hear and either removing them from the audio folder or renaming them.  In the audio folder on the server PC, I have removed most of the sounds  and have left in the folder the sounds that I wish to hear only through the headset (navigation aids, TCAS warnings, GWPS warnings & call outs – V1, V2, VR, etc).  Therefore, the sound program on the server computer only has those sounds I want to hear through the headset.

On the client PC, to avoid duplication , I have removed the above mentioned sounds from the audio folder.  It’s important to edit/remove the sounds from the audio folder that you do not want to hear.  Failure to do this will result in duplication of sound.  In other words you will hear V1, V2, Vr, etc through your headset and through the main speakers being run from the client computer.

Therefore, what you now have running is:

Server PC – engine sounds being heard through the surround speakers, ATC and ATIS being heard through the headset (via FSX sound separation), and customized sound (navigation, call outs, etc) being heard through the headset (via separately installed Sim Avionics sound program).

Client PC – all other non general sounds being heard through the attached speakers (via separately installed Sim Avionics sound program).

Adding Customized Sound

Adding customized sound can often is challenging.  Add the sound file (.wav format) to the audio folder.  Then search and find the sound .cfg file.  Edit the .cfg file to reflect the added sound and when/how you want the sound to be played. 

The easiest method is to duplicate the section relating to sound from an already operating sound.  Then edit to reflect the new sound.  This way you do not run the chance of making a syntax or topographically error.

I explained how to edit a sound file in my earlier Journal post: Are the Engines Running – 738 Sound.

Using ProSim 737 – Basic Operation

The methodology of manipulating sound in ProSim737 is similar to Sim Avionics. 

You copy the ProSim sound program from the server PC to the client PC so each program can send customized sound to separate speakers on each computer.  To select which sound you want to hear, open each sound program and select/deselect the appropriate sound from the list.

Adding Customized Sound

If you are wishing to add additional customized sounds to the sound program, you can do this in the configuration section of the ProSim737 main program. 

First, you need to add the actual sound to the audio folder.  All sounds should be in .wav file format.  The sounds are usually kept on the ProSim737 main folder/Audio folder (but can be linked from any folder if you wish).  After adding the customized sound, to ensure correct operation, you may need to edit the actual sound file.  This file is found in the ProSim 737 main folder/audio.  The file you are looking for is named config.xml.  Unlike other software, which uses config (.cfg) files, ProSim 737 uses the .xml file format.  To edit this .xml file right click the file with your mouse and choose edit.  Whenever editing anything, always make a back-up first.

Once the new sound file has been added, you need to link the file within the sound program.  To do this, open the file tab in the main Pro Sim 737 program menu and select “add audio”.  Follow the prompts to name and link the .wav file.  Then, you should be able to see and select the sound file from the Pro Sim sound program.  Click the sounds you want to be heard and press “test” to hear your sound.

In ProSim737, as opposed to Sim Avionics, you only enter the sounds once through the main Pro Sim 737 program interface (installed on the server PC).  Any installation of the sound program on client computers has access to this main audio folder. 

Alternate Methods in ProSim737

ProSim737 also provides alternate ways for customizing sound.  This is done through the main ProSim737 main program.

One method involves selecting an internal audio for the added sound in the file/config/audio tab.  This triggers the main program to read the sound automatically.  Another way to join a sound to a specific task is to use what Pro Sim call a gate.  A gate can be used to link the sound to a bespoke sound and generic named action.  This method is very easy if your defined sound output is actually named in the pull down menu list. 

If the added sound is linked to a button press or specific action, then you can link the sound using FSUIPC or via another device such as an I/O card.

ProSim737’s alternate methods of adding and linking sound appear to be quite convoluted and confusing (at least to me).  The ProSim737 manual provides addition information and instructions.

PM Sounds – an easy way to add additional sounds

I have used PM Sounds (PMS) for many years and have enjoyed its simple interface and ability to just work out of the box.  PM Sounds is a small, stand-alone add on released by Project Magenta used to supply customized sound to their fleet of products.  The program is is compatible with many other avionics suites.

The program is stand alone and does not load into the file structure of the simulation platform.  To hear sounds from each computer on your networked set-up requires that PMS be installed on each computer.  PM Sounds comes with a large selection of sounds and you can easily select which sound you require by checking or not checking the box and pushing Q on the keyboard to save the selection.  Activation of the sounds is achieved by running PM Sounds before you start FSX.  The rest just works…

Adding Customized Sound to PM Sounds

To add customized sound to PM Sounds, it’s a matter of finding the audio folder (located under PM Sounds/) and adding the sound (in .wav format).  To hear the sound within PM Sounds, you then must edit the sound.cfg to reflect the sound name, file name and location.

To use PM Sounds on any computer other than the computer running FSX requires you have a copy of Wide FS as PM Sounds uses this program to communicate between the server computer and the clients.

PM Sounds can be used in addition to whatever sound program you are using.  The program can be found on the Project Magenta website.

Important Point To Know (Gauge Commands)

Several sound designers configure their custom sounds to play only when specific actions or commands are triggered - these are called gauge commands.  A sound initiated by a gauge command only works when that gauge is moved by whatever action.  Often it's not possible to use these sounds without some major editing work to the sound.cfg file.  For example, I've been attempting to use the speedbrake sound in ProSim, but as yet have not been able to do so.  This is because the speedbrake is configured to a specific "in house" command or action - in this case the speedbrake. 

You cannot just grab any sound, copy it to the audio folder, and then expect it to play.  There has to be some logic to when the sound is played.  This can be most challenging and frustrating part of manipulating custom sounds.

There You Have It…

Sound can be as easy or as complicated as you want it to me. 

I have attempted to provide, within the last two journal posts, an incite into audio separation using Sim Avionics and ProSim737.  Certainly, the process described above has worked relatively well in my simulation set-up.  Your configuration may differ to what I have, but what will not alter is the basic method of audio segregation.

Are The Engines Running - B738 Sound

One of the main purposes of building a flight deck is to increase the realism and immersion levels when simulating flight.  You want to move real yokes, flick real switches and spin real rotaries whilst maintaining focus on real instruments within a modern glass flight deck. 

Simmers 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 engine sounds.

But what about sound……

All of us have had that dejavoo feeling when we have smelt a certain smell or heard a certain noise and are projected back to that event and time.  Vietnam veterans often have vivid flash-backs when they hear news helicopters flitting overhead.  We all can recall a song within out romantic past which conjures up images of a past partner or event.  The power of sound and smell cannot be underestimated. 

If the engine sound of your chosen aircraft is perfect or near perfect you will barely notice it – the sound will blend with everything else.  However, if the sound is not correct or is video arcade game-like, you will always be thinking how it can be improved.  This is especially so if you’re using the standard stock FS9 (FS2004) or FSX aircraft engine sound.

I feel confident saying that: “with decent sound, your one notch higher concerning realism and immersion”. 

Sound makes a huge difference to the simulation experience.  When on final approach, concentrating on flight adjustments and jigging with the throttle to obtain the correct thrust, the sound you hear, if realistic, will make you forget you’re sitting in your spare room!  It’s like that smell or sound I mentioned earlier – you’re mentally transported back to the source.  I recently trialled the PMDG 737-800NGX in the simulator, and the first thing my girlfriend in an adjoining room exclaimed was “that sounds like a real plane”.  

The recently released PMDG 737NGX has an exceptional sound package; however, not everyone flies this aircraft model.  What is available to augment or replace the default flight simulator sound files?

Turbine Sounds Studio (TSS)

Turbine Sounds Studio (TSS) produces a variety of different sound packages that are direct recordings of the real aircraft engine sounds.  The sounds have been professionally recorded from specific aircraft types and in my opinion are exceptionally good and eons ahead of anything supplied by Microsoft. 

The package to purchase for the B737NG is the: Boeing 737NG CFM56-7B HD Sound Pack for FSX.  If you fly the older classic series B737, TSS also produces a sound package specific to the 300,400 and 500 series aircraft.  To actually hear a sample of the sounds, I recommend your navigate to their website at http://www.turbinesoundstudios.com/

turbine sound studios have a large collection of sound packages available

TTS – Software Installation

The software provides you with an executable file, which when selected, will download to your desktop a “sound” folder containing a number of engine, instrument and ambient sounds specific to the aircraft type.  It’s just a matter of backing up your original sound folder in the aircraft of choice and copying the TSS sound folder in its place. 

How To Add Custom Sounds

If you’re not happy with every sound in the package, it’s quite easy to remove or replace a particular sound with another favourite.  Search for the sound folder, usually located within the aircraft folder (FS10/sim objects/aircraft).  Within this folder you will discover various sounds and a sound.cfg file.  If there are no sound files within the folder, they maybe aliased to another folder in another aircraft. Open the sound.cfg file and note the folder/file location.  Follow the trail until you actually discover where the .wav files are stored.

It's important that when you replace sounds, that the replacement sound is in the same format and has the same file name as the file you are replacing.  If the file name is different, you will  need to alter the specific parameter in the sound.cfg file to reflect the file name change.  The same is for the location of the sound (if this if different).  The sound.cfg file must have the correct name, format and location of the actual .wav sound. 

Always back-Up Before Editing

Always backup the folder and files you wish to edit BEFORE editing anything.  If you make a mistake or something is not quite right, it's then easy and straightforward to put your system back to where it was beforehand.

In my set-up I am using the base NGX sound pack installed into the FS9 737-800; but I have customized a few of the sounds to those that I prefer.

If you want a more or less accurate sound set for the B737, but don't want to go to spend the time hand-picking, renaming and customizing your sound files, then either give TSS a fly or use the PMDG NGX sound set, which is a tad more realistic than the set provided with the PMDG FS9 737.  Whichever set you choose (or combination thereof), it will be far better than the default sound that comes packaged with flight simulator. 

In a future post I’ll tackle the issue of separating sounds to different speakers on different networked computers.  This allows you to have ATC through the headset, engine sounds left and right of the flight deck and other sounds played through another pair of strategically placed speakers..

Well, I’m more or less pleased with my sounds.  Should I throw some avgas on the carpet to get that aviation smell….

Update

on 2020-06-18 03:08 by FLAPS 2 APPROACH

Since the release of this product there have been many advances in sound capture and generation.  Turbine Sound Studios (TSS) have produced a selection of products for varying aircraft types.  To see the complete collection of available sounds, navigate to Turbine Sound Studios.

  • Note I have no affiliation with this store and do not receive any endorsement from them.