Live ATC - Listen to ATC In Real Time

Many virtual aviators are confused when it comes to understanding the language used by air traffic control and pilots.  The three questions often asked are:

  • What to say ?

  • When to say it ?

  • How to say it ?

There are several on-line tutorials available to learn air traffic control and aviation language, however, often a far easier and more interesting method is to actually hear ATC talking to pilots and vice versa.  This in conjunction with a little reading can get you up and flying quickly without making mistakes  when flying on-line.

To listen to live ATC, go to Live ATC, select your airport code and frequency and sit back a listen.  The frequencies are already on the website, so all you need is the ICAO or IATA code of your airport. 

Live ATC can be be listened to either via the web or if your "on the move" and really cannot be without ATC, then your android or i-phone. ATC is a volunteer organization, so expect some adverts on their website.

Video - Weber Pilot Seat Adjustment Capabilities

A short video clip to follow up on the installation of two 737 Weber pilot seats (Captain and First Officer) that have been installed into the simulator. The seats were retrieved from a South West 737-400 that was destined for the wrecking yard. This video demonstrates the various positions that the seat can be adjusted.

To read additional information on the seats, see these other Journal entries.

 
 

Flight Testing - The Good, The Bad & The Ugly

Flight Testing - Hardware & Flight Models

Now comes the fun and not so fun part - field testing.  Everything has been configured (throttle, MIP, yoke, etc) and requires flight testing to ensure correct operation.  Reliability is related to repeatability; therefore, to ensure reliability you must replicate the outcome several times before you can state something is working correctly.  This takes time and many takeoffs and landings.

As you can imagine, there are many systems that inter-finger to achieve the desired outcome, and all the systems, hardware, software and components must be correctly communicating between themselves to replicate flight.  Often a small problem can develop from something as insignificant as a loose wire or a incompatible computer part.  I've already had a few spanners thrown into the mix with faulty power packs, problematic USB cables and USB ports and a few user problems.

It's during this test period that I hope to iron out any niggle problems to ensure a robust and trouble-free system for the future.

  • Flight testing occurs whenever a new component is added, changed, or the avionics software is updated.

Word of Advice - Go Slow & Be Methodical

To determine the solution to any problem that may arise, it's important to know which hardware or software is causing the problem.  When in the test phase, it's best to only have the basic software installed.  When your happy with the result, add another piece of software and test.  This is the best way to build a robust system.  The temptation is to install everything and then field test, only to find an issue and not be able to work out what is causing the problem.  Develop and build in stages, try to take your time, be methodical, take notes and replicate the results before moving on.  It's a slow and often tedious process.

One benefit of going slow is that you will have the opportunity to learn your software and know what it can do and more importantly what it can't do. 

Bugs

Often individuals will state a piece of software has bugs as it doesn't do what they believe it should be doing.  Certainly some software is bug prone and should be avoided, however, for the most part high-end software and hardware more than often operates correctly and is trouble free. 

A piece of software or hardware can only function within the specifications of the, motherboard and other software you have installed.  It is not uncommon for one individual to state a bug whilst another has no issues what-so-ever.  Before crying BUG, it's best to check, double check and then check again.  Often the fault will be your computer set-up or your lack of knowledge to what the software can or cannot do with regard to the computer and computer components you are using.

Examining The Flight Models

Testing also includes evaluating the two flight models that interest me: the PMDG FS9 and default FSX 737.  At the moment I prefer the former; probably because this is the aircraft model I've used since it was release.  Each model has its differences and nuances.

I'll post a separate entry in the Journal outlining my thoughts on the two models in due course, although this is a personal preference.

Unfortunately, the CP Flight MCP PRO I purchased appears to be faulty and have been returned to Italy.  Using the virtual Sim Avionics MCP achieves the same outcome, but it's a bit ungainly using a mouse and separate MCP screen.  Hopefully a replacement MCP will arrive in a few weeks time which will flying easier and more enjoyable.

Testing Duration

To test anything properly requires at least a few weeks; as mentioned above repeatability must occur.

Eye Candy

The outside model, what the Americans call eye candy is not of great importance to me.  Most of the time I like to fly IFR in inclement weather, so looking out the front or at the exterior is not that important; I spend most of my time reading instruments, manuals and looking at charts (yes I like paper charts although I do also have an electronic flight bag).

External Visuals

At the moment, during the initial flight testing stage I am using a rather small computer display; functional when building and testing, but not that exciting to fly with.  Following construction, more suitable external visuals will be looked at.

Update

on 2013-06-17 23:00 by FLAPS 2 APPROACH

Time has been limited, however, I have completed several flights using the two flight models that interested me - the default B737 FSX and the PMDG (FS9 version) B737.  Although both flight models depict the same aircraft, there is considerable variation in how each model behaves. Many of the differences are small and probably would not be noticed by a casual flier who has only experienced one flight model.

Easy to Nit Pick

It's easy to fall into the trap comparing flight models for entirety and nit-pick each to death without coming to a conclusion.  Put simply, it's about compromise.  Each model has its benefits and failings.  After considerable time and effort, I've decided that the PMDG FS9 model is suitable to my style of flying (at the present time).

Main Differences - PMDG FS9 Model & Default FSX 737 Model Using ProSim737

The main differences that I have noted is that the default B737 model, in many respects, is VERY EASY to fly.  Its responsive to flight inputs and generally speaking is not challenging when flying - even in a cross wing.  Some of the methods in which instrumentation interact with the model is also slightly different. For instance, when flying in command mode (auto pilot on), the default B737 will not allow you any roll CWS using the yoke.  You must depress the CWS button on the MCP to allow the aircraft to be rolled whilst the auto pilot is controlling the aircraft.

In contrast, the PMDG FS9 flight model is generally more difficult to fly and control.  Landing in a cross wing requires far more concentration as does a normal take off and climb to altitude.  Interestingly, the CWS issue mentioned above is not a problem with the PMDG model.  If the aircraft is in autopilot mode with command activated and you wish to alter course, all you need do id move the yoke and CWS roll or pitch is activated whilst the auto pilot is maintained.  This has obvious benefits.

A few other variables that I was not happy with when using the default model are;

  • Instability in pitch during a VNAV descent

  • Instability in pitch when using the speed brake

  • Overpowering of engines during take off and climb

  • Flaps extension and retraction appears to be very fast

  • CWS roll/pitch requires engagement of CWS button & disengagement of auto pilot

  • Poor outside visuals (aircraft in spot mode)

Many of the above issues can be easily rectified by editing the constraints in the Air File.

One of the benefits of the default model is it allows connection and configuration to any of the standard FSX controls (aircraft lighting, various buttons, etc).  It's unfortunate that the same level of interaction is not possible when using the PMDG model (without further configuration & work around).  As an example, the navigation and strobe lights cannot easily be connected to an outside switch using PMDG.  This is because PMDG has configured their model outside the standard defaults of FSX.

I have no doubt that there are other nuisances that I've yet to discover. 

Which Flight Model - PMDG FS9...

Personally I prefer the PMDG FS9 model as it delivers greater flight accuracy than the default model.  For this reason I will most likely use the PMDG as a standard model.  This said, once some tweaks are made to the default model's Air File to counter the above mentioned dot points, the model flies quite well with full button capability.  However the CWS roll & pitch discrepancy, for me, places the PMDG FS9 model ahead of the default model.

Update

on 2012-06-20 03:30 by FLAPS 2 APPROACH

After spending the last few months on and off flight testing, I thought I'd share my final decision to which flight model the simulator will be using. 

ProSim 737 and JetStream B738

I spent May and June field tested ProSim 737 as an alternative to Sim Avionics.  ProSim737 can be used with a number of add on aircraft, however, they also produce a dedicated flight model to the their own software called the JetStream Advanced Flight Model B738.

I'm impressed  with the JetStream and believe it to be the par of the PMDG FS9 model.  Certainly, the external visuals do not match PMDG, but this is not the concept behind the JetStream.  The concept ProSim wanted to deliver was an aircraft model that provided a top shelf flight model compatible with ProSim's flight avionics suite.  As such, external visuals are as per the default FSX 737.

I'll be compiling and posting to the journal section  an evaluation of the JetStream shortly.

  • The avionics suite chosen is ProSim737 and the flight model is the JetStream 738 (as at June 2012).

Never Do This - Changing Voltage Will Destroy Your Computer

I am using two computers networked.  I was doing some tests in an attempt to separate the sound between the two computers so I can utilize a headset when I heard a horrible grating noise coming from one of the computers.  I've heard the sound before so knew what it was; one of the fans was either failing or required lubricant in the bearing.  A little odd considering both computer are less than 3 months old.

Variable Fan Switch

The computer has a variable fan switch on the rear toward the power cord.  I lent down behind the MIP to either turn the switch to low or off in the hope of isolating the fan noise.  As I selected the switch I heard "BLIP" and the computer stopped.  I closed the other computer down, found a torch (flashlight) and peered behind the computer console.  I saw the switch, but to my horror I also saw another switch.  Sliding the computer out from behind the MIP I authenticated what I had thought.  Instead of switching the variable fan switch I has tripped the switch that changes the computer from 240 volt to 110 volt.  Both switches reside almost side by side.

Voltage

Never change a voltage switch on the rear of the a computer from your countries voltage requirement.  Depending upon which direction you move the switch and what voltage you are current on, will indicate the resultant effect.  240 V - 110 V "blip"!  110 V to 240 V "BANG" with everything "fried" beyond repair.

In some respects I was lucky, I only "fried" my power source.  A replacement was relatively easy  and I had a IT friend check the computer to ensure there were no other issues.  Oh - and the noisy fan was isolated and replaced.  It was the fan on one of the video cards (there are three video cards.  The video card was replaced under warranty.

Advice For The Future

Use a piece of tape to cover the switch so it cannot be inadvertently tripped.

Landing Lights, But No Overhead - Go Flight Module

The 737 Project has been reasonably well mapped out and the work schedule revolves around specific aircraft systems. I try to finish work on one system (for example, the automation on the throttle) before moving to the next.

One of the provisos when I started this project was that I wanted the simulator to be working during construction. I was afraid that without using the simulator the project would loose traction.

The overhead is not scheduled for sometime (it is one of the last systems to completion).  In the interim, I am using the Sim Avionics virtual overhead, and moving a mouse around a screen is hardly realistic.

There are a number of switches on the forward overhead panel that can be easily mapped and configured to a toggle switch, and the switch mounted somewhere within the simulator.  Although unrealistic it is a better option than the mouse.

I have several GoFlight modules from my earlier simulator that were gathering dust; therefore, I decided to use two Go Flight T8 button modules to act as a interim overhead. I use the module to turn on and off the various lights - such as landing, taxi, navigation, collision and beacon.  The toggles also operate the anti-ice, CDU mode, seat belts, no smoking lights, yaw dampener and re-circulation fans.

The modules have been mounted into the center pedestal.  Although rather crude and certainly not realistic it works and fills the gap until the overhead is completed; making it easier to access the landing and a few other switches that are are used on every flight.

Video - Operational Trim Wheels & Indicators

Now that the throttle quadrant is operational, USB hubs working and the Phidgets correctly configured, I thought I’d post a short video clip showing the trim wheel operation.  The wheel spin is controlled by inputs either from the auto pilot or from electric trim switches located on the yoke.  When the wheels spin, there is corresponding movement of the trim wheel indicator tabs; the indicators, which are coloured white show the pitch of the aircraft.

Currently, the trim wheels spin at only one speed (mono-speed adjustable in the Phidget settings).  Later on, when I have time I'll be altering the speed to variable-speed  This will allow the wheels to spin at differing speeds dependent upon whether the aircraft is being controlled manually or by the autopilot.  This configuration requires some extra time with Phidgets and is not essential at the present time.

The trim wheels are connected to a 12 volt DC servo motor.  The motor is mounted inside the throttle quadrant near the actual wheels. To control the power to the servo motor I have used a Phidget advanced servo motor controller.  Double click video to view full screen.

 
 

Safety First

The trim wheels have a white line painted on them for a very good reason (not invasion markings for D-Day 1944).  The spinning wheels are dangerous – keep your fingers well away when they are operational!  The white line, when spinning acts as a visual warning to pilots that the wheels are spinning.  It also provides a means with which to calibrate the rotation speed of the trim wheels.  Each wheel also has a pull out handle that can be used to control trim manually.  Like your fingers, if your knee is in front of the handle when the wheels spin expect a solid whack on your knee cap.  I’ve been told by a real world B737 Captain, that there have been several occasions when pilots have suffered injuries to knee caps from being whacked by spinning wheels, after inadvertently leaving the handle extended.  As for me, well when they first "spun" into action the cup of coffee that was resting slightly against the wheel spun across the floor  :)

Stab Trim Switch Cut Out

As you can image, spinning trim wheels can be slightly annoying and very noisy – especially if you’re flying at night and others in the house are attempting to sleep.  Therefore, to stop the trim wheels spinning, I have programmed the trim stabilizer (stab trim) switches on the throttle quadrant to cut the power to the servo motor.  Push the stab trim switches to normal and the wheel spin; push the switch down and spinning stops.  Although the spinning stops, the trim indicator tabs still move.

In a real B737 this switch is used to stop run away trim wheels, so there is a certain amount of authenticity connecting this functionality to this switch.

Trim Tabs – Why Are They Important?

The use of trim tabs (elevator & pitch) significantly reduces pilot’s workload during continuous  flight maneuvers (sustained climb to altitude after takeoff or descent prior to landing), allowing them to focus their attention on other tasks such as traffic avoidance or communication with ATC.

Trim affects the small trimming part of the elevator on jet airliners. Trim (controlled by the trim switch on the yoke) is used all the time after the flying pilot has disabled the autopilot, especially after each time the flaps are lowered or at every change in the airspeed, at the descent, approach and final.   Trim is most used for controlling the attitude at cruising by the autopilot.

Correct trim frees the pilot from exerting constant pressure on the pitch controls for a given airspeed / weight distribution. Typically, when the trim control is rotated forward, the nose is held down; conversely, if the trim wheel is moved back, the tail becomes heavy and the nose is held high.

Trim Tabs - Technical Hype (the basics)

When a trim tab is employed, it is moved into the slipstream opposite to the control surface's desired deflection. For example, in order to trim an elevator to hold the nose down, the elevator's trim tab will actually rise up into the slipstream. The increased pressure on top of the trim tab surface caused by raising it will then deflect the entire elevator slab down slightly, causing the tail to rise and the aircraft's nose to move down. In the case of an aircraft where the deployment of flaps would significantly alter the longitudinal trim, a supplementary trim tab is arranged to simultaneously deploy with the flaps so that pitch attitude is not markedly changed.

Belkin Hubs - An essential Add On

 

BELKIN powered hub with external case removed

Throttle Commands Not Working

Refurbishing a throttle quadrant is not without its problems.  In an earlier post, I touched briefly on the issue of the throttle commands not responding.  The connection between flight simulator and the throttle would drop out and anything related to the throttle quadrant would cease to function.

Determining the problem was time consuming, however, the culprit was a faulty power supply that powered a Belkin USB powered hub.  The power supply I had been using was a standard computer power supply unit (PSU) and it was not new.  The PSU was overheating, and when it reached a particular temperature it would cause the powered Belkin hub to disconnect.  When the PSU returned to normal temperature (after being turned off) the Belkin hub worked perfectly.

USB Hubs - always use a powered hub

Hubs are an important piece of gear when putting together a simulator or running anything that has a lot of peripherals.  Unless you have a city of USB ports on the rear of your computer (unlikely) then you will need a hub.  Hubs are good as they minimize the number of USB cables that need to be connected to your computer.

When selecting a hub only use a powered hub. The reason being is that there is often a lot of information being transmitted, via the hub, between your device and the computer.  A powered hub helps maintain the integrity of the hub and stops information drop outs.  I only use non-powered hubs for devices such as keyboards and mouse.

Phidgets and Hubs

I learned from experience (computer crash & scrambled phidgets) that it is not a good idea to connect phidgets directly to your computer via the USB cable.  I'm not exactly sure why this is not possible, but it is recommended on the Phidget forum to always use one or two powered hubs when connecting phidgets to your computer.

Outstanding Service - You Tell Me....

Christmas and New Year is the worst time for anything technical and complicated to arrive - period.  Stores close, technicians take vacation, and managers and owners hide from the public.  For many, Christmas is a religious and/or festive day.  For most, it's a time to escape the pressures of work and relax with friends and family.

Software Installation & Configuration Questions

It was a few days before Christmas Day, the MIP had arrived a few days earlier. For some reason I couldn't get the FDS software to function correctly, I didn't have a registration key to unlock the software, and basically was a little clueless on how to get this animal moving! 

Several e-mails had transpired between Flight Deck Solutions and Sim Avionics - but it was slow going.  I was keen to get the basics set up so I could navigate through the various configuration options during the Christmas week.

Then, on Christmas eve - 2130 Canadian time my cell phone rang....  "Hi this is Peter Cos from Flight Deck Solutions, I hear you have a problem!  I can sort this out for you quickly.  I realize there are many systems to get in place and your feeling overwhelmed at the moment - no problems.  Let's work through each issue in turn and get you flying"  

From this post, you may think that the configuration of FDS and Sim Avionics software is difficult; this is far from the truth.  Once you are steered in the right direction, have the correct folder structure established on your computer, installation is very straightforward. 

Now, for those who are really bored and have read through this website in entirety, you may remember that one of the reasons I bought from Flight Deck Solutions was because of the backup service.  Tell me - what better service can you expect when the owner of the company rings you, from the sidewalk outside a restaurant in Canada, to try and solve your issue......ON CHRISTMAS EVE!

Following this phone call, I received prompt e-mails from Mark Hastings (United Kingdom) and Nat (Australia).

Thank you Peter Cos, Steven Cos, Mark Hastings and Nat for your time and patience.

  • All the issues were solved over the next few days via e-mail and telephone calls.

UPDATE - Progress Report

primary flight display sim avionics

Well, Christmas and new year has passed and I'm still working on the simulator.  There have been some niggle-like teething issues that every infant must succumb to.

Faulty Power Supply

A problem developed with the throttle quadrant which had me baffled for several hours (read days).  The throttle quadrant would stop working or some of the controls/commands would give spurious results.  Was it incorrect FSUIPC offsets or was it dodgy wiring or loose connections (?).  I went through the construction and set up with a tooth comb.  Then the solution was found.  It was a power supply which was powering the Belkin hub that a few of the USB cables were connected through to the computer.  I noticed the power supply was quite warm and getting warmer, then it would just stop working to begin working again when it cooled. 

Replacing the power supply plug seems to have solved the issue.  This said, I'm a little wary of running too many important USB connections through a hub.  Therefore, tomorrow I intend to add another row of USB interface connectors to the motherboard and maybe an additional powered hub to help share the load.  One important snippet of information important to know when using Phidgets is NOT to connect them directly to your computer.  They should be connected to a powered hub (this comes from the Phidget forum).

Sim Avionics

As you know the MIP has arrived as has Sim Avionics and some other assorted software.  Everything is installed and I'm going through a learning stage with correct software set-up and operation.  It takes considerable time testing to ensure the best set-up.

Sim Avionics is complex, but no unfathomable.  The interface is very clean and very easy to use once set up correctly.  Currently, I've been put to the test remembering (or learning) flight operations that either I have forgotten or never knew!  A quick glance at the PFD display will give you a idea what this beast is capable of - amazing stuff when you think about it.  Reading, learning and asking questions takes time!

I'll put together a basic report on the MIP, CDU and Sim Avionics software in a few weeks time - once I've got a good handle on its functionality.

MCP Issue

The MCP I am using is produced by CP Flight in Italy.  For the last two weeks or so I've been struggling to get the MCP to connect correctly to flight simulator.  After in-depth testing with CP Flight and others, CP Flight have asked that I return the unit for replacement.  Over the years I've used many products from CP Flight, and for the most part all there products are exceptionally solid and robust.  Hopefully a replacement unit will soon land in Australia as flying using a virtual MCP isn't exactly easy and fun!

Other than this, I've been touching up some painting, cleaning up the wiring, fabricating two side panels to fit between the throttle quadrant and the front of the MIP and a few other bit and pieces here and there.