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

/

ana haneda (RJTT) Yamaguchi Yoshiaki from Japan, JA755A and JA06AN @HND RJTT (470097235), CC BY-SA 2.0

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

/

jal 737-800 rjaa (narita) https://www.pexels.com/photo/photo-of-airplane-wing-1928067/

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.

B737 Cockpit Companion Guide by Bill Bulfer - Review

/

737 Cockpit Companion: required reading

The 737 Cockpit Companion is a well known guide within the flight simulation community, having been published in several formats; each dealing with a specific release of a Boeing 737 aircraft series.

The guide, written by retired airline Captain Bill Bulfer, are very specialized and unravel each of the many 737 aircraft systems.  The 737 NG Cockpit Companion 600/-700/-800/-BBJ & BBJ 2 provides a detailed explaination into the following:

The companion may look small, but the information it includes is detailed and informative.  The small size allows easy storing in the side pockets of the throttle quadrant .  In my opinion, this guide is essential reading and answers many questions often asked by flight deck builders and virtual pilots. 

CONTENTS

  • AFT Panel

  • Forward Overhead Panel

  • Glareshield Panel

  • Captain’s Panel

  • Center Panel

  • First Officer’s Panel

  • Forward Electronics Panel

  • Control Stand (throttle)

  • Aft Electronics Panel

Example of a page from the Cockpit Companion

It is important to note that this guide provides much more information than just indicating a name for something.  Each system's functionality is explained in detail along with comprehensive sketches, diagrams and fold out schematics.

For example, in the Captain’s Panel section, there are several pages that explain, the elements that make up the Pilots Flight Display (PFD) and Navigation Display (ND).  There are two pages that deal only with the speed tape providing information dealing with the various options indicated by the tape during ascents and descents. 

Another page details the intricacy of Navigation Performance Scales (ANP and RNP) providing operational information on how to read and decipher the scales in relation to whatever flight mode is set on the MCP. 

A final example is several pages that detail the functionality of the EFIS unit and what exactly occurs when you push a button on the EFIS unit.

Flight Deck Builders

The guide is essential if you are constructing a flight deck and want to simulate the 737 systems.  Apart from systems information, the guide indicates switch functionality and provides information to which lights illuminate for what functions and when.

The guide is not a procedures manual; it is a technical reference manual.  The content will not provide instruction on how to fly the 737.  Rather it provides a detailed study of each system and provides information explaining the relationship between systems. 

No matter what your skill level, It is a very handy reference and strongly recommended.  I often leaf through the pages to cross reference something that I don’t quite understand.

B737 Pocket Reference Guide

Pocket Reference - PFD / ND Flags and FMC Messages

Often when you fly, a message will show on the Pilot’s Flight Display (PFD) or Navigation Display (ND).  Remembering what all the abbreviations mean can be daunting, and often you don’t have the time to open a manual t wade through copious pages that have nothing to do with what you want.

Enter the pocket reference guide.  This small and very handy leaflet guide outlines all the PFD, ND flags and FMC messages and provides a brief description of the flag displayed.  The pocket reference is sold separately to the cockpit companion.  It's size is 10 cm x 5 cm.

Example of page from 737 Pocket Reference Guide

Written by an Aviator for Aviators (real or virtual)

The Cockpit Companion and Pocket Reference Guide, written by an aviator for aviators, is very concise, easy to read and understand.  As with its sister companion, the FMC Guide, it’s a high quality production.

If your serious about how you fly your simulator or are developing your own simulator project, the Cockpit Companion is certainly a must have in your training material.

The guide that is most relevant to the 737 Next Generation is titled: The 737 NG Cockpit Companion 600/-700/-800/-BBJ & BBJ 2

It can be purchased from Leading Edge Publishing.

I will be reviewing another of Bill Bulfer's text in the near future - FMC Guide.

My Rating 10/10

  • I am not affiliated with Leading Edge Publications and do not receive any commission from them.

Headset Communication - Flight Sound X Adapter - Review

/

Occasionally you come across a device which really makes your simulation life simpler.  I wanted to use the David Clark headset (model H10-13-S) I have owned for sometime in the simulator; however, the two plugs on the headset are the large style plugs suitable for insertion into an appropriate audio module in the real aircraft – not a computer sound card.

Real Headsets Verses PC Headset

Apart from the obvious difference, a real aviation headset is constructed to a very high standard, is robust, and provides a high fidelity sound rarely replicated by an inexpensive PC style headset.  Unlike a PC headset, real aviation headsets are designed to produce excellent sound whilst providing maximum buffering of ambient sounds (aircraft engines, wind, etc). In the simulation world, ambient sound can be dogs barking, cars driving down the street or daughter's yelping... 

Flight Sound X

The Flight Sound X adapter allows you to use a variety of real aviation headsets with your simulator, to filter out engine and ambient noise and hear and communicate with air traffic control (VATSIM, etc).  It’s as easy as plugging in the two plugs from your headset into the device and flying – it is that easy!

The device does not require a separate power source, is small, and connects directly to the USB of your computer via a USB cable.  WIN7 64 bit recognises the device on start-up and additional software and drivers are not required.  A small LED light on the device indicates the unit is operational (red light).

Initial device set-up requires you open the sound module in Windows, navigate to the appropriate menu and change a few settings within your sound card to allow sound and microphone ability to be transferred to your headset.  Instructions (with pictures) are supplied with the device, so you cannot make a mistake – even if you do not read English.

A benefit to using this device is that it’s small and can fit more or less anywhere within your flight deck.  Another pleasant surprise is the device’s construction; it is made from aluminium (painted black) rather than plastic.  As such, it looks quite attractive and is far more robust than plastic counterparts.  Another benefit is the actual placement of the plugs which is at the side of the device rather than at the top of the device.  This ensures that your headset cable and plug are not in a position where you may accidentally stand on them!

Technical Details:

  • USB 1.1 and 2.0 compatible

  • Plug and Play with Windows 7/Vista/XP and Mac OS X

  • Uses standard General Aviation headset connectors (PJ-068 and PJ-055B)

  • Supports headset impedance of 100 to 600 Ohms

  • Supports Mono and Stereo Headsets

  • Compatible with standard microphone types (electric, dynamic and powered dynamic)

  • Powers microphone bias (+9V) from USB port (no external power needed)

  • Zero delay voice feedback (side tone) feature

  • Output frequency response (20Hz-20KHz)

  • Weight: 100g

  • Size: 65 mm(L), 55 mm(W), 25 mm(D)

  • Compact, robust, anodised aluminium enclosure  

Made in New Zealand

The device is made in New Zealand.  The Kiwis usually make innovative and functional products – good work New Zealand…

This device would have to be the simplest item I have purchased, set-up and used with flight simulator.  And it WORKS too!

My rating is 10/10

In a future post we will discuss how to separate sound, so you can hear engine sounds from one pair of speakers and ATC, call outs and navigational aids through the head set.

  • I am not affiliated with Flight Sound X and do not receive remuneration from them.

Navigation and Multi-COMM Radios by Flight Deck Solutions - Review

/

Navigation and M-COMM radio.  Note the even backlighting and well defined seven -segmented displays.  Also note DZUS connectors

The avionics that are used in the center pedestal are important; they are used regularly, are always visible, must function correctly, and be robust to sustain long use.

This review will discuss the radios produced by Flight Deck Solutions (FDS). In particular, the navigation (NAV 1/2), multi-comm (M-COMM) and ADF (1/2) communication radios.

The navigation and M-COMM radios are USB driven, while the ADF radios use Ethernet.

  • For brevity, I’ll discuss the construction of the panels together, as each of the panels has been constructed and along similar grounds, and functions similarly.

The navigation radio is a single channel radio unit designed to handle navigation frequency selection and management.

The M-COMM is a multi-channel communications radio that replicates the latest radio used in the Next Generation airframe.  The radio encapsulates VHF 1, VHF 2 and VHF 3, HF, HF2 and AM.  For simulation purposes, the M-COMM is an advantage to those who only wish to purchase one communications radio, rather than the two radios (COM 1 and COM 2) traditionally used.

fds ADF radio with rear of radio in background.  The finish of the panel is above par.  Note that the ADF/ANT and OFF/ON switches can be toggled, but are not functional

Appearance and Construction

The panels are constructed using the same technique that FDS to fabricate their Main Instrument Panel (MIP).  

Each upper panel is made from CNC machined acrylic which produces a very crisp finish and allows any stencilled letter cut-outs to be very well defined.  Each of the radios use a dual concentric rotary encoder with a stainless steel stem.

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 from the encoder as the knobs are turned.  The push keys are plastic moulded, back-lit 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 seven-segmented display and are very easy to read.  

The colours of the digits are amber yellow for the navigation and ADF radios and warm white for the M-COMM radio.  The seven segmented display in the ADF radio is a slightly different font to the those in the navigation and M-COMM radios.  The colour is also a tad more orange in hue.  Although slightly different, this doesn’t distract from the overall appearance.

Layer cake design to accommodate the circuitry and the easy to use push clips to connect 5 Volt power (IBL).  Also, note that the circuitry board is not flush to the edge of the panel, enabling the radio to drop easily onto DZUS rails (drop & fly).  Also note the inclusion of OEM DZUS fasteners

Construction

The electronic components needed for the radios to function are contained within each panel. 

As such, The radios do not require interfacing with an interface card and are literally ‘plug and fly’.   The decision by FDS to incorporate all the circuitry within the panels minimises the wiring required, and the problem in finding space to attach an interface card.  

Depending on the radio, there are up to three layers that various electronic circuitry is attached, that includes integrated backlighting (IBL).  The front panel of the radio is backed by a piece of grey-coloured aluminium that adds strength to the unit and assists to dissipate heat from the 5 volt bulbs used to backlight the panel.  An electronics friend had a look at the electronics and was impressed with quality of the electronics board.  

What this amounts to is a well presented avionics panel that accurately replicates the radio in the Boeing 737 aircraft.  The radios are 1:1 in size.

Painting and Finish

All panels fabricated by Flight Deck Solutions, which includes the radios, are professionally painted in Boeing grey.  

Rather than one coat of paint which can easily be chipped, FDS apply several thin coats of paint to increase the durability of the final layer.  Although this point may appear token, the quality of paint and how it’s applied is important, because the radios 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 radios.  Further, as the radio panels are flat, dust will accumulate requiring dusting and cleaning.  Low quality paint will scratch, fade and wear thin within a short period of time.  In my opinion, the quality of workmanship used by FDS, when it comes to painting is second to none.

DZUS Compliant

If you are using OEM parts in the simulator, in particular the center pedestal, then any panel that is DZUS compliant is advantageous, because it enables the panel to be dropped directly onto the DZUS rails to be secured by DZUS fasteners.  The radios can be placed directly onto the rails of an OEM center pedestal and the DZUS fasteners turned to secure the radio to the rail.

FDS IBL Series Distribution Expansion Board.  This board, the size of a credit card, enables 5 Volts to be distributed to several panels.  The coloured wires connect to 5 volts

Integrated Backlighting (IBL) and Power requirements

The radio panels are evenly backlit by FDS’s integrated backlighting (IBL).  IBL has been designed specifically to backlight panels in the identical fashion as is done in the real Boeing aircraft.

Rather than use LEDS for backlighting, FDS use OEM bulbs.  The primary advantage of IBL is the ‘throw of light’ which is greater from a single bulb than a LED (which is pin point).  The only way to achieve a similar light coverage to bulbs with an LED, is to use several LEDS mounted in close proximity to each other.  

Another point for consideration is that bulbs have a different colour temperature to LEDs.  Bulbs are warmer and produce a soft golden glow as opposed to LEDs that generate a harsher cooler light

The backlighting is superb.  The ‘throw of light’ covers all the stencilled letters and there are no dark or bright spots.  The only downside of IBL (if there is one), and this really doesn’t deserve mention, is that bulbs generate quite a bit of heat.  The life of a bulb is also less than a LED, however, FDS claim their bulbs have a life span of ~40,000 hours.

To power the backlighting will require a 5 volt power supply.  Although 5 Volts can be connected directly to the connectors on the rear of the panel, it’s recommended to use a IBL Series Distribution Expansion Board (FDS IBL DIST).

The expansion board will enable 5 volt power to be shared between several panels.  It’s all pretty straightforward and involves connecting some prefabricated wires with clips to the rear of each radio and to the card.  The card is then connected directly to the 5 Volt power supply.  The card I use is secured within the innards of the center pedestal.

To power the M-COMM 12 volts is required, in addition to 5 Volts for backlighting.

fds Ethernet switch and pen for scale

Connection and Set-up

If you are using avionics software other than ProSim737, software will need to be downloaded from the Flight Deck Solutions website (Texworx).

The software is very easy to use and installation self explanatory.  

Configuration of the radios is done via the software and involves indicating which NAV module is operated by which pilot (Captain or first Officer).  The M-COMM module uses the same software (you check the option for this panel during set-up).  The software is not required if using ProSim737.

If using ProSim737 avionic software, the ProSim-AR generic driver will recognise the FDS radios when they are plugged into your computer.  The radios will need to be configured (Captain or First Officer) and this is done in the config/driver section of ProSim737.

The concept of USB doesn’t need discussion, however, the ADF radios are connected via Ethernet. 

While it's possible to connect each radio separately to the main network switch, it’s easier to use a smaller network switch as a hub.  The switch I’ve used is supplied by FDS, is relatively small, can handle 8 Ethernet devices (expandability), and can be mounted into the center pedestal.  A single Ethernet cable then connects the FDS switch (hub) to the main network switch (and then to your computer).

If using Prosim737 avionics software, the radios (USB or Ethernet) can be connected to and run from the client computer.

Rear of ADF radio showing PCB, rear of encoders and push clips

Reliability and Performance

I’ve had the occasional dropout of the navigation and M-COMM radios, however, the ADF radios have worked flawlessly. 

I suspect that the reason for the navigation and M-COMM radios dropping out, is that the USB cables are connected to a powered hub, along with several other items.

I did trial the Tekworx software (using Sim Avionics) and I had several dropouts with the navigation radios that could not be rectified.  These dropouts stopped when I transferred to ProSim737.  

In some radios, there is a time lag when charging the radio frequency.  This time lag may be system dependent and/or a response to the limitations of USB.  This delay is not evident with the FDS radios.

Support

Support from FDS is either directly via e-mail or by a dedicated forum.  The support provided by FDS is outstanding and all e-mails are answered in a timely manner.  

Quick List (pros and cons)

PROS

  • Well designed & constructed (plug and fly).

  • Excellent workmanship.

  • Excellent painting.

  • Realistic Integrated Back-Lighting (IBL) with excellent illumination.

  • Realistic quality machine-injected switches & rotaries.

  • Size ratio is 1:1.

  • Very high attention to detail.

  • OEM DZUS compliant (drop & fly).

  • Easy to use and set-up software (if not using ProSim737).

  • M-COMM radio ideal if space is limited in pedestal.

  • Native support for Sim Avionics and  ProSim737.

CONS

  • Expensive price (subjective).

  • Tekworx software (V 1.8.8. & V 1.9.9) caused disconnection (drop-outs), however, no issues when using ProSim737.

Final Call

The radios are solid, well constructed and the attention to detail is as you would expect from Flight Deck Solutions.  The quality of the radios is very high and suits the high-end enthusiast to professional market.  

My rating for the Tekworx software is 5/10  (V1.8.8. & V 1.9.9)

My rating for the modules is 9/10

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

  • Updated 13 July 2020.

Populating the B737 Center Pedestal

/

oem 7373400 center pedestal (two bay). avionics include cp flight, flight deck solution and oem. this pedestal has since been replaced with a three bay pedestal

The centre pedestal I’m using is a real aviation part procured from a South West 737-300 series aircraft. The pedestal came attached to the throttle quadrant and is the more uncommon two bay style. The Next Generation uses a three bay center pedestal.

I was reluctant to destroy a piece of aviation memorabilia, so rather than cut the pedestal from the throttle and discard it, I decided to keep the two bay pedestal and limit myself only to essential avionic modules.

Apart from the nostalgia of using an OEM pedestal, I really like the DZUS rails that are used in a OEM pedestal, which allow you to drop the various panels into place and secure them with a DZUS fastener.  To read about DZUS fasteners, navigate to my earlier post.

In this post I will discuss populating the center pedestal with panels, and touch on using the panels from a comparative newcomer - SISMO Solicones. I will also discuss some of the problems I had with installing reproduction panels to the OEM center pedestal.

No International Standard  - Variation

There is no international standard established to indicate which model/type avionics are installed in a center pedestal; more often than not, it will come down to the type of aircraft and a particular airline’s requirements.  Early series 737s were fitted with a two bay center pedestal which minimised the number of panels that could be fitted.  Later model 737 aircraft and the Next Generation aircraft series use a three bay center pedestal that enables installation of the latest navigation and communication equipment.  There are benefits to the thinner two bay pedestals, the main positive being more room to climb into the flightdeck.

All 737s will have as a minimum the following avionics installed:  Fire Suppression module, NAV1/2 COMS 1/2, ADF 1/2, audio, rudder trim and transponder.  The important modules will be duplicated for First Officer use and redundancy should a failure occur.  Depending upon the aircraft series, the following may also be installed: thermal printer, HUD set-up, radar, cargo door panel & floodlight switches, alternate communications, etc, etc (the list is almost endless).  Much of what is installed depends on the use of the aircraft, civil regulations in the country of use and the requirement of the particular airlines.

Module Location

As with colour, there is no standardization to the location within the pedestal for any particular panel - perhaps with the exception of the fire suppression panel and NAV 1/2 module which (usually) occupy the forward part of the center pedestal.  Modules are fitted wherever they fit and in line with whatever specification that the airlines requires.  For example, I have observed Audio Control Panels (ACP) mounted toward the rear of the pedestal, which I believe is the favoured position, and also towards to front of the pedestal.

Another interesting aspect to observe is the different knobs on the NAV and ADF radios.  Often simmers became mentally entangled in attempting to standardise everything across their simulator.  This is not necessary; it is realistic if you mix-match panels to a certain degree.

The center pedestal is populated with the following modules:

  • NAV-1 (Flight Deck Solutions)

  • NAV-2 (Flight Deck Solutions)

  • M-COMM (Flight Deck Solutions) new style module that incorporates all radios in one module

  • ADF-1 (CP Flight) - replaced with Flight Deck Solutions.

  • ADF-2 (CP Flight) - replaced with Flight Deck Solutions.

  • Rudder Trim (CP Flight) - replaced with OEM.

  • ATC (transponder) (CP Flight) - replaced with OEM.

  • Fire Suppression Module (OEM 737-400 converted for FS use) - replaced with 737-600 NG.

  • Audio Control Panel (2) (ACP) (OEM 737-400 unit – at the moment, wired only for backlighting)

Avionics Mania

Unless you have an unlimited budget, or have panel sickness, you may want to think about how often you will use a particular panel.  Navigation (NAV 1/2 & ADF 1/2) and communication (COM1/2) modules will be used on every flight; therefore, it’s best to purchase a high-end panel for consistency and reliability. 

The rudder trim module and Audio Control Panel (ACP) are rarely used, with the exception of engine out operations and for turning on/off the audio for the various navigational aids. 

This is a side benefit to using a two bay center pedestal:  there is only so much room available, so you are forced to decide on which panels take precedence over others.

Maintaining Brands – almost impossible

I had wanted to maintain the same brand of modules across the sim to minimise the number of different system cards and interfaces, however, this was difficult to do. 

Flight Deck Solutions, a premium upper shelf supplier of simulation parts to the professional and enthusiast market, do not at the time of writing, manufacture and sell an ADF navigation radio panel.   Further, FDS do not produce the older style ATC (transponder) panel; they only manufacture the newer push button type, and I favoured the older style.

As the MCP I am using is manufactured from CP Flight, and I also have an older style CP Flight transducer, I decided to opt for the CP Flight ADF navigation radios. CP Flight have an easy method to daisy chain panels together. Unfortunately due to supply issues this was not to be the case.

OEM Panels

Nothing beats OEM panels and I am hoping in time to replace many of the reproduction panels with OEM components. In the meantime, I will be using reproduction panels.

SISMO Solicones

A relative newcomer to the scene attracted my attention – a Spanish company called SISMO Solicones.  Their products are reasonable quality for the price paid, are 1:1 ratio to OEM panels, use Ethernet rather than USB, and relatively easy to configure. 

I was very keen to trial Ethernet as a method to connect the modules to the computer. 

SISMO SOLICONES. Note the electronics tab that needs to clear the DZUS rails for installation.  A poor panel design if using an OEM center pedestal

Module Size – Size Matters!

It’s very important to check that the panel will fit correctly to whatever pedestal you are using.  If you are building your own pedestal without rails, then this is not an issue as you can easily fashion a template to drop the panels into.  However, if you are using an OEM panel, you will need to ensure that the panels are built in such a way that they drop into the existing rail system in the pedestal, otherwise you may need to alter your rails.

ADF Navigation Radio Panels – Attaching to the DZUS Rails

The avionics panels made by Flight Deck Solutions are literally drop & forget as all FDS panels are DZUS compliant and fit OEM DZUS rails perfectly.  The ADF radios from SISMO are a different matter.  Each of the panels has a small tab on the electronics board which is too wide to navigate past the DZUS rail in the pedestal.  This is a major issue as the panel cannot be dropped onto the rails.  Why SISMO designed them this way is beyond me, as many serious simmers use OEM center pedestals.

Cutting the Rail – Delicate Operation

Although I was reluctant to cut the DZUS rail, I realized that this was the only method available to correctly fit the SISMO ADF panels.  The rail had to be cut and a portion removed that corresponded to the size of the tab. Removing a portion of the rail would allow the panel to then be dropped into the pedestal. 

OEM 737-300 CENTER PEDESTAL WITH RAIL CUT TO ENABLE REPRODUCTION PANEL TO BE INSTALLED

The DZUS rails are attached at regular intervals to the inner side of the pedestal by several aluminium rivets.  The rivets are not moveable and unfortunately a rivet was located directly where the rail was to be cut. 

After triple checking the measurements, I used a dremel power tool and small metal saw to gently cut into the aluminium rail until flush against the edge of the pedestal.  The cut piece of aluminium rail then was able to be removed; however, the rivet body remained.  I then used a metal file to carefully grind away the end of the rivet head until flush with the pedestal side. 

In addition to this, each of the attachment holes of the panelss needed to be enlarged slightly to accommodate the male end of the OEM DZUS fastener.  This job was relatively easy and I used a quality drill bit to enlarge the hole.  A word of caution here – SISMO do not use metal backing plates, so if you’re over zealous with a drill, you will probably crack the plastic board.

Once the sections of DZUS rails were removed, it was only a matter of dropping the panels into the pedestal and securing them with DZUS fasteners.

SISMO SOLICONES rudder trim and ADF module with power pack.  The rudder trim is A MEDIOCRE reproduction of the real unit. however, it lacks finesse in its final construction. I DO NOT RECOMMEND USING THESE PANELS

System Cards & Wiring – Location, Mounting & Access

I was very surprised at the number of cards required to use SISMO panels.  An Ethernet card is required as is a daughter and servo card.  There are also two power sources: 5 volt powers the small servo moto) that moves the rudder trim gauge and 12 volts powers the module backlighting. 

My main concern was where to mount the cards.  Initially, I was going to mount them under the main simulator platform, but access for maintenance was a problem. I decided to utilise the inside of the pedestal beneath the modules.  This area is rather cavernous and a good place to house the cards and wiring needed for the modules (out of sight and out of mind).

Constructing an Internal Board – to attach cards to

I cut a piece of thin MDF board to roughly the height of the pedestal interior and fitted it in such a way that it created a vertical partition.  To this board, using both sides, I attached the various cards needed.  To ensure that the flat cables had enough room to reach the various cards, I cut a slot in the center section of the board.  I also made sure there was enough room at each end of the board to allow cabling to snake around the partition. The most important point to remember is to ensure that none of the cards touch the metal sides of the pedestal or each other; to do so will cause an earthing problem. 

Wiring wasn’t much of an issue, as SISMO supplies prefabricated flat wiring with plastic clips.  All you need to do to attach the correct clips to correct attachment point on the card – very easy with absolutely no soldering.  As the Ethernet card is mounted within the pedestal, the only wires that need to be threaded through the lower throttle section of the pedestal are the power cable and the Ethernet cable.  The later connects to the Ethernet switch box that is mounted to the shelf of the FDS MIP.

The pedestal innards are now full of intestinal-looking wires attached to an assortment of cards.  It looks messy with all the wiring, but as the wires are flat wires with solid connectors, it is very secure and logically set out.  Access to the wiring and cards is achieved by removing two or three modules. 

Update

on 2012-07-25 05:48 by FLAPS 2 APPROACH

After trialling the panels manufactured by SISMO, I wasn't impressed.  The ADF navigation radio gave spurious results which were intermittent, and the frequency change switch did not provide consistent operation - sometimes it worked and at other times it was sticky and needed to pressed a few times to initiate the frequency change.

The rudder trim module also did not work correctly, even with the correct SC Pascal script. 

The Transponder ATC module looked OK, but never worked as a script was not supplied.  The Audio Control Module looked absolutely awful with poor quality switches and cheap and nasty-looking plastic buttons.

Rather than fight with cards, wires, and a software medium (SC Pascal scripts) which I don't have the knowledge to edit, I decided to box everything and send it back to SISMO for refund.

The SISMO panels have been replaced with panels made by CP Flight and OEM panels.