List of B737 Carriers Worldwide - Interesting....

A Boeing B737 takes off or lands somewhere in the world on average every 5 seconds!

To date, the Boeing series of airliners is the most successful airliner the world has seen.    Boeing's success revolves around, amongst other things, the ability to be able to upgrade their aircraft from a basic overall design that has changed little since the first B727 rolled out of the hanger in the 1968, earmarked for the German airline Lufthansa.

So which nations place their trust in Boeing?  This link provides a list of worldwide carriers by nation.

Creating Waypoints on the Fly with the CDU

Often you need to inject into the flight plan an along track waypoint, that is defined by a distance from a known waypoint or navigational aid.  There are several ways to achieve this and each method is similar in operation, but is used in differing circumstances.  Depending upon the software version installed in the CDU, you can either use the LEGS or FIX page.

To create an along track waypoint in the CDU

1. In the LEGS page, type into the scratchpad the waypoint name, vector and distance.  The     distance is where the new waypoint will be created and is measured from the waypoint or navigation aid you are using as an anchor (LAV340/10).
2. After entering the information into the scratchpad in LEGS (LAV340/10), upload to the CDU by key pressing the appropriate waypoint, where you wish the along track waypoint to be created.
3. Clean up any discontinunity and execute.

• LAV is the waypoint, 340 is the vector, in degrees, that the along track waypoint will be created, And 10 is the distance from LAV that the new waypoint will be created.
• To insert the along track waypoint before the anchor waypoint, use the negative key - (LAV340/-10).  
• To insert the along track waypoint after the anchor waypoint, do not use any identifier (LAV340/10).
• Take note that the / is after the vector, and the waypoint name and vector are joined with no spaces.

If you want the new waypoint to be created along the current navigation track, type the vector that is displayed adjacent to the waypoint in the LEGS page of the CDU.  If you do not type a vector, then the location of the along track waypoint will be allocated automatically, which may not be along your current track course.

In the example shown (LEFT), I have created an along track waypoint called LAV02 which is located the aircraft side of the waypoint LAV.  I also have created a circle around LAV (see instructions below).

The CDU software will create along track waypoints with generic names (LAV01, LAV02, LAV03, etc).  In the example, I have already flown over LAV01 and LAV02 is now the next waypoint.

To create a circle around a waypoint using the FIX functionality in the CDU

There are many reasons why you may want to place a circle identifier around a waypoint or navigational fix at a specific distance.  Least of which to highlight a distance from a waypoint so it can easily be seen on the Navigation display (ND).

1. Press FIX on the CDU to open the FIX page.
2. Type into the CDU scratchpad, the name of the waypoint or navigation aid (VOR, NDB, etc) and upload to the FIX page (in the example, LAV).
3. Do one of two things:

• Type into the scratchpad the distance you require the circle to be drawn around the waypoint.  For example, LAV/15 and upload this to LSL1, or
• Type only the identifier (LAV).  This will only create a small circle around the waypoint.

A quick way to insert a waypoint from a flight plan is to press the waypoint name in the LEGS page.  This will automatically down select the waypoint to the scratchpad saving you the time typing the name.  Then select FIX and upload the waypoint from the scratchpad.

In the example shown (ABOVE), I have created a circle at a distance of 15 miles from LAV which can be viewed on the navigation Display (ND).    The straight, green dashed line displayed from LAV is the vector, which in this example is unimportant, as we are only creating a circle. 

The vector only becomes important when you want to create a waypoint that intersects the edge of the circle (see below).

How to create a single along track waypoint along the edge of the circle.

If you want to create an along track waypoint at the edge of the defined circle, and insert this waypoint in line with the aircraft's current navigation track, then the vector becomes more important. The vector will determine the bearing, from the waypoint anchor that the waypoint is created. 

If you want to ensure that the inserted waypoint is in line with aircraft's current navigation track, use the vector that is shown in the FIX page.  This will ensure that the new waypoint will be created along your current flight track at the distance entered (circle)  

In the example (BELOW), I have created the first, along track waypoint (ADM 01) as an entry point to an arc, directly in line with the navigation track of the aircraft.  The waypoint is at the edge of the defined circle.

To insert along track waypoints around the arc of the circle. 

Another variable of the above theme, often used when executing an NDB Approach, is to create several along track waypoints that intersect a defined circle.  The waypoints which are created at a set distance from an anchor waypoint or navigation fix, create an arc.

First, ensure you have a circle created around the waypoint at the distance required (FIX page).

1. Select the waypoint for the arc from the LEGS page and download to scratchpad.
2. Type in the scratchpad: ADMAR100/15, ADMAR130/15, ADMAR160/15, ADMAR190/15 and so forth.  This will create an arc 15 miles from ADMAR. 

• If you want the first waypoint to be along your navigation track, use the vector for this initial waypoint indicated in the LEGS page of the CDU.

In the example (LEFT), I have created a number of along track waypoints, separated each by 30 degrees, that intersect the circle 10 miles from ADMAR.  With a little imagination, it's easy to uncover several uses for such funtionality: terrain avoidance, approach protocols, etc.  Click image to enlarge.

It’s important to note that user and along track waypoints are given generic names by the software (ADMAR01, ADMAR02, ADMAR03, etc). 

To ensure that the waypoints are sequential when displayed (01,02,03,04,05, etc), upload the new waypoints to the LEGS page, to the same waypoint name that was used to create the along track waypoint.   In this example it is ADMAR.

Understanding the CDU

What I've described above is but a very brief and basic overview of some functions that are easily performed by the CDU.

CDU operation can appear to be a complicated and convoluted procedure to the uninitiated.  However, with a little trail and error you will soon discover a multitude of uses.  It's important to remember, that there are often several ways to achieve the same outcome, and available procedures depend on which CDU software you are using.

I am not a professional writer, and documenting CDU procedures that is easily understood is challenging.  If this information interests you, I strongly recommend you purchase the  FMC Guide written by Bill Bulfer.  Failing this, navigate to the training section of this website and download some of the FMC tutorials.

Construction Commenced - New Platform to Mount B737 Yokes, Columns & Rudder Pedals

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 genuine yokes, columns, rudder pedals and a new platform will be installed very shortly.

Currently the simulator is mounted on a fiber-board and wood constructed platform, which I constructed when I received my Main Instrument Panel (MIP) just before Christmas 2010. (picture here).  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 genuine B737-500 yokes, columns and rudder units. 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 genuine yokes 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 two yokes for duel operation.  Therefore, I decided that a new platform was required; custom designed  to fit the yokes, columns and rudder pedal assemblies.

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 yokes and columns (striped completely) fitted to the forward modular section of the platform.  The yokes are connected to each other by a ¾ inch heavy duty shaft and heavy-duty double bearings.  Forward and aft movement of the yokes is controlled by a heavy duty spring and left and right roll movement is controlled by another spring.  Currently the pull pressure on the yoke 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.

Replacement Power Sources

In addition to a replacement platform, I'm also looking at alternatives to supplying power to the simulator.  My thoughts are a number of power packs rated to various voltages, mounted in parallel and connected to either fuses or circuit breakers, is a far better and more safer solution than using a computer power pack and in line fuse board..

I’ll post more detailed pictures and further information in a future post.

Telex Airman 750 Headset - Adding To Realism With Real Parts

For the most part, to listen to Air Traffic Control and ATIS, and to numb 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 PPL (private pilots license).  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 on 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 sometimes bargains are still to be found!

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 ProSim 737 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 envirionmental 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.

Personally, 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).

Important Point To Know (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 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.

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 jouranl 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 ProSim 737 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 the box”.

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

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 “specialist” 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 – B738 Sound"

Using ProSim 737 – Basic Operation

The methodology of manipulating sound in ProSim 737 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 ProSim 737 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 ProSim 737, 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 ProSim 737

ProSim 737 also provides alternate ways for customizing sound.  This is done through the main ProSim 737 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 pre-defined and 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 FSUPIC or via another device such as an I/O card.

ProSim’s alternate methods of adding and linking sound appear to be quite convoluted and confusing (at least to me).  I direct you to the PS737 manual for further information and instructions on how to do this.

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 FSX.  To hear sounds from each computer on your networked set-up requires that PMS be installed on each computer.  PMS comes with a large selection of sounds and you can easily select which sound you require by checking or un-checking the box and “pushing Q” on the keyboard to save the selection.  Activation of the sounds is achieved by running PMS before you start FSX.  The rest just works…

Adding Customized Sound to PMS

To add customized sound to PMS, 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 PMS, you then must edit the sound.cfg to reflect the sound name, file name and location.

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

PMS 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've attempted to provide, within the last two journal posts, an incite into audio separation using Sim Avionics and ProSim 737.  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.

B737 Cockpit Companion Guide by Bill Bulfer - Review

The B737 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 guides, written by retired airline Captain Bill Bulfer, are very specialized and unravel each of the many B737 aircraft systems.  The 737 NG Cockpit Companion 600/-700/-800/-BBJ & BBJ 2 investigates the following subjects:

LEFT:  The companion may look small, but the information it includes is detailed and informative.  The small size allows easy storing in the throttle side pockets.  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
• Centre Panel
• First Officer’s Panel
• Forward Electronics Panel
• Control Stand (throttle)
• Aft Electronics Panel

It’s important to note that this guide provides much more information than just indicating a name for something.  Each system area’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’re putting together a flight deck simulating a B737.  Apart from systems information, the guide indicates switch functionality, such as annunciators, and provides information to which lights illuminate for what functions and when.

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

No matter what your skill level, It’s a very handy reference and I’m often leafing through the pages to check on something that I don’t quite understand.

Pocket Reference - PFD/ND Flags, FMC Messages

Often when you fly, a message will show on the Pilot’s Flight Display.  I’ll be honest I cannot remember what all the acumens mean, and often you don’t have the time, because of the flight phase you are in, to wade through a guide to find the information. 

Enter the pocket reference guide.  This small and very handy leaflet guide outlines all the PFD, ND flags and FMC messages providing 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.

Written by an Aviator for Aviators (real or virtual)

The cockpit companion, 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 B737NG is titled: The 737 NG Cockpit Companion 600/-700/-800/-BBJ & BBJ 2

It can be purchased from Leading Edge Publishing.

My rating 10/10

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

Striving For Realism - MCP, EFIS - AFDS & MIP Lighting

One aspect that everyone strives for when building a flight deck is authenticity.   We try to mimic the real flight deck whenever possible.    This isn’t possible with everything, and different people have varying perceptions to what is a suitable aesthetic compromise.   Equally, flight simmers become fixated with certain aspects of their flight deck. 

I know simmers who fastidiously try to replicate the switches of their overhead to replicate the real B737 switches, or try to mould their glare shield so they fit and look “just right”.  I have always been fixated on the MCP unit; I wanted the unit to mimic the appearance of the real unit as much as possible.

I was a little disappointed when I discovered that the CP Flight MCP and EFIS unit I was using, did not fit snug into the FDS MIP. There was small vacant gap along the edge of the unit when fitted into the MIP.  Further, at certain angles the MIP and AFDS flood lighting could be seen along the edge of the MCP.  I thought the latter was particularly unrealistic.  I was incorrect….

I recently came across a selection of photographs taken inside the flight deck of an Alaska Airlines B737-700 (image above).  I was very surprised (if not pleased) to observe that the MCP and EFIS unit had a gap around the edge of the unit and the MIP and AFDS flood lighting could be seen shining along the edge of the MCP unit - exactly the same as in the simulator.

I now can sleep soundly knowing that what I look at in the simulator is very similar to that of a real aircraft.  :) "just kidding - I can sleep anywhere"

I've made the image larger than normal to show the detail I am referring.  Please note that this photograph is copyright and cannot be used without permission.

Populating the B737 Center Pedestal

The centre pedestal I’m using is a real aviation part procured from a South West B737-300 series aircraft. The pedestal came attached to the throttle quadrant and is the more uncommon two-column style for this series aircraft, rather than the three-column NG style.

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-column pedestal and limit myself only to essential avionic modules.

LEFT: A mix-match in colour and manufacturers.  The center pedestal is a real aviation part as is the throttle unit.  The fire suppression panel came from a scrapped B737-500 whilst the F/O Audio Control Panel (ACP) came from 500 series aircraft.  The other modules are: FDS NAV & M-COMM and a  ATC transducer module made by CP Flight in Italy.  For those unfamiliar with a real pedestal, the flat pieces if metal with the light green paint on the upper side, fold down and are aluminium coffee cup holders !

Apart from the nostalgia of using a real bay, I really like the DZUS rails that are incorporated in a real bay which allow you to drop the various modules into place.  To read about DZUS fasteners, navigate to my earlier post.

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 B737s were fitted with a twin column pedestal which minimised the number of modules that can be fitted.  Later model B737 aircraft and the NG series incorporate a three column pedestal to allow installation of the latest navigation and communication equipment.  There are benefits to the thinner two column pedestals, the main positive being more room to climb into the flight deck.

All B737s 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 module - perhaps with the exception of the fire suppression module 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've 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.

LEFT:  Note the ACP units are located further forward than what is considered the norm.  Also note the rudder trim module mounted in the centre of the pedestal and the rather larger thermal printer (?) toward the lower right. 

Another interesting aspect to observe is the different knobs on the NAV and ADF radios.  Often simmers became "mentally entangled" in attempting to standardize everything across their simulator.  This is not necessary and actually is more realistic if you mix-match slightly.

This pedestal is mounted within a B737-700 aircraft and represents the more usually found three column pedestal in this series aircraft.  The pedestal I am using came from an earlier 400 series aircraft and is the two column type.

I’ve populated the center pedestal 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)
• ADF-2 (CP Flight)
• Rudder Trim (CP Flight)
• ATC (transponder) (CP Flight)
• Fire Suppression Module (genuine B737 unit converted for FS use)
• Audio Control Panel (2) (ACP) (genuine B737-500 unit – only wired for lights at the moment)

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 currently produce an ADF radio module.   Further, FDS do not produce an older style ATC (transponder) module; they only manufacture the newer push button type and I favoured the older style.

CP Flight produces some excellent modules with a very easy to use daisy chain system for linking the modules together; it would have to be the easiest and less hassle-free system on the market.  As I already had the older style CP Flight transducer module left over from my older simulator, and am using the CP Flight MCP (which is required for daisy chaining if you do not use thier "black box"), I decided to incorporate this module.

I would have also used the ADF radios made by CP Flight, however, at the time of writing these modules are unavailable and there is no date determined to when they will be available.

Real Modules

Nothing beats real modules aesthetically...  I am hoping that as the project develops to replace some of the reproduction modules with real B737 modules converted to flight simulation use.  Currently, I only have the fire suppression module and Audio Control Panel (ACP) converted.  More research is required to learn how to convert other modules.  Perhaps real ADF modules :)   An ongoing project!

SISMO Solicones

Therefore, 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 real Boeing modules, use Ethernet rather than USB, and relatively easy to configure. 

I was very keen to trial Ethernet as a method to connect modules to the computer.  In a future post, I will review the actual modules and the benefits of Ethernet instead of USB.

Avionics Mania

Unless you have an unlimited budget, or have “module sickness” necessitating every module possible, you may want to think about how often you will use a particular module.  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 module 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.  The later can be particularly annoying when tracking an active ADF.

This is a side benefit to using a two column pedestal:  there is less room so you can only select those modules with provide required functionality.  The extra space also helps when climbing into the flight deck  :)

Module Size – Size Matters!

It’s very important to check whether the module will fit correctly to whatever pedestal you are using.  If you’re building your own pedestal without rails, then this isn’t much to worry as you can easily fashion a template to drop the modules into.  However, if you’re using a real Boeing part, you will need to ensure that the modules 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.

LEFT:  Note the electronics tab that needs to clear the DZUS rails for installation.  A poor module design if using a real pedestal.  If I had know this before purchase, I'd have selected ADF radios from another supplier.

ADF Radio Modules – Attaching to the DZUS Rails

The avionics modules made by Flight Deck Solutions are literally “drop & forget” as these modules are DZUS compliant and fit the DZUS rails perfectly.  The ADF radios from SISMO are a different matter.  Each of the modules has a small tab on the electronics board which was too wide to navigate past the DZUS rail to slide into the bay.  This was a major issue as the module cannot be dropped onto the rails.  Why SISMO designed them this way is beyond me, as many serious simmers use real aircraft 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 modules.  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 module to then be dropped into the pedestal. 

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 checking my measurement more than three times, 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 modules needed to be enlarged slightly to accommodate the male end of a 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 radio modules into the bay and securing them with DZUS fasteners.

System Cards & Wiring – Location, Mounting & Access

I was “surprised’ at the number of cards required to use SISMO modules.  An Ethernet card is required as is a daughter and servo card.  There are also two power sources: 5 volt powers the small servo (motor) that moves the rudder trim gauge, and 12 volt powers the module back-lighting. 

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).

LEFT:  SISMO rudder trim and ADF module with power pack.  The rudder trim is quite a good reproduction of the real unit, however, it lacks finesse in its final construction.  I may switch the unit to a CP Flight rudder trim module in the near future.

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. 

Avionics Modules – A Review

After I have evaluated each of the modules I am using for reliability and functionality, I will post a review as a separate journal post.  I'll also post a few images of the pedestal once the twin ACP units have been fully converted to simulator use.

Update on Wednesday, July 25, 2012 at 3:48PM by FLAPS 2 APPROACH

I had intended to use SISMO Solicones to supply some of the modules for the center pedestal.  I was impressed with the idea of how they use Ethernet technology rather than USB.  As such I populated the pedestal with two ADFs and a rudder trim module made by SISMO.  I also was going to use their transponder ADF module and Audio Control Module.

I was shocked at the number of cards and extensive number of flat wires connecting the various modules, but installed the modules all the same. 

After trialing the modules, I wasn't impressed.  The ADF gave spurious results which were intermittent and the frequency change switch did not provide consistent operation - sometimes it worked and at others it became 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 of to edit, I decided to box everything and send it back to SISMO for refund.

SISMO modules have been replaced with Modules made by CP Flight and with genuine B737 modules converted toFS use.

I'll post a detailed review of SISMO products and service in the near future.