
HDG of the MCP on a breadboard
After programming and testing the entire weekend, the Lateral Navigation part of my MCP is operational on the hardware side. Next step is developing the software link between the hardware and FSX.
My MCP exist of several modules which can be used independent of each other. Only what you need is the Central Autoflight Module (CAM) which is responsible for the communication between the flight simulator and the autoflight modules.
What is supported on the hardware side:
– Three digit heading display with Rotary Encoder to select a heading from 1 to 360 degrees.
– HDG HOLD with LED when activated. When HDG HOLD activated, LNAV will be automatic disactivated. HDG HOLD button can also be configured as HDG SEL.
– HDG SEL integrated in the rotary encoder of the heading selector. This button can be configured for other purposes as HDG HOLD, SET 180 or 360 degrees, swap intervals between 1 or 10, etc.
– LNAV with LED when activated. For aeroplanes without LNAV, it can be also configured as NAV. You find this mode for example back in Cessna’s, Beech Baron or a King Air.
– APP button with LED when activated.
– VOR LOC button with LED when activated.
– Bank Angle rotary switch with 6 position for Boeing’s.

LCD readout of HDG PCB
Course displays for NAV 1 and 2 (see Boeing 737 MCP) are considered as Lateral Navigation but to keep our system modular for each type of aircraft, it will be build on a seperate PCB.
All settings are send over the CAN BUS to the CAM. To check out or the CAM does receive all data traffic from the other modules, I connected it temporary to a LCD screen.