This section consider that you already have tested the MCP and/or the connected expansion modules as described in the "HARDWARE TROUBLESHOOTING" section and the hardware correctly works with the CPflightTest program.

SOFTWARE COMPATIBILITY:

The MCP737 supports Project Magenta, default FS aircraft and third part add-on aircraft using FSUIPC data format and offset. Freeware and commercial add-on aircraft using their own software modules or gauges may use different data format and offset and it is not possible to assure of the compatibility. See compatibility table here.

SOFTWARE TROUBLESHOOTING:

We have to remark that the hardware have not an its own intelligence on board, it establish an interface to set and select controls substituting the computer keyboard and/or mouse; logics, operating modes and aircraft behavior are managed by the Flight simulator software (or Project Magenta software if any).
Often the MCP cannot engage a function because there not exist the right flight condition to engage this function, for example if you attempt to engage the "APP" mode without having an ILS tuned or when the aircraft is above to the allowed altitude for approach, the "APP" mode will not engage and the key light will remain turned off. This does not mean that there is any hardware failure.
If you have a doubt about a similar situation, check the same condition directly with the mouse before any other thing, obviously if the function does not works using the mouse you can't engage it with the MCP hardware.
In any case there are some exception in B737 FS default because the driver FS_COM filter some command to simulate the real B737 behavior. For example if you move the altitude knob on the hardware the value will be sent to FS only if VS or LVL CHG mode are engaged.

EXPANSION BOARDS
PROBLEM	POSSIBLE CAUSE	SOLUTION
The MCP does not start	Communication port setting	Run the configuration software MCP_CONF and select the correct communication port (see also MCP manual)
The MCP displays stay dark	Aircraft setting conditions	The MCP extinguish the displays to simulate a "cold and dark" situation in the cockpit depending by the status of battery, alternator and avionics switches. Switch them on.
Unable to light-up the panel backlight.	The backlight is related to the "Instrument Light" status. On the FS default 737 the Instrument Lights are linked with he "Navigation Light"	Turn on the "NAV" light.
Run-time error '13' when Running the configuration software MCP_CONF	The base configuration files was corrupted	Reinstall the CPflighttools software. (Note that the system keep the configuration files when you uninstall the cpflight software, this allow to keep the configuration when you upgrade/ reinstall the software. If you need to have a clean installation uninstall the cpflight software and before to reinstall it remove the Cpflighttools folder from the system).
In the configuration software drop-down list there is not the needed function to assign to a MCPEX1 digital input	The list only hold the most common functions. Where not present in the list, a function may be added if (supported by FSUIPC).	See MCPEX1 user manual appendix. Note that this issue require a certain experience with FSUIPC offset and values. See also "FSUIPC for programmers" document in the FSUIPC SDK. Download at: http://www.schiratti.com/dowson.html

USE WITH FS 2000/02/04/X
PROBLEM	POSSIBLE CAUSE	SOLUTION
MCP works correctly with test program or MCP_CONF but doesn't work with default Boeing 737 in Flight simulator	The FSUIPC dll is not installed in FS Module folder	Download FSUIPC at Peter Dowson web site and install in your pc.
	FSUIPC release version	Check FSUIPC release version, download latest version on Peter Dowson web site.
	Others software already running when you run FS_COM (configurator or test program)	Close any possible CPflight program that already run on the computer (In the windows task manager close any running CPflight application) and restart FS_COM
CPflight splash-screen freeze on the FS screen when running FS_COM Nothing happen	"Pause in the application" settled in FS global setting menu.	Disable the checkbox "Pause within application" in the FS global setting menu.
The MCP and/or add-on modules doesn't works or partially works	The selected add-on aircraft is not supported by the FS_COM driver	See Software compatibility table here.

USE WITH PROJECT MAGENTA
PROBLEM	POSSIBLE CAUSE	SOLUTION
The MCP doesn't start-up when running Project Magenta MCP	FSUIPC release version	Check the FSUIPC release version, download latest version on Peter Dowson web site.
	Project Magenta MCP.ini file not correctly configured	Close Project Magenta MCP. Edit MCP.ini file (in the Project Magenta MCP folder) and set the correct COM port number in the [SerialConnection] item CPFlightComm= ? (Ex.: if you use COM 1 port set CPFlightComm = 1 ). Save the file and run Project Magenta MCP again.
Delay in the data update from Cpflight MCP and Project Magenta	Flight Simulator and Project Magenta MCP don't run on the same computer.	Even if Project Magenta (and CPflight) MCP may run on a client through wideFS, in most of case the data update result more fast if Project Magenta and CPflight MCP are both installed on the server, in special way if you use external I/O extensions board. This also may depends by the network setting.
The Project Magenta Glass Cockpit does not swap the displays using the DU's selectors connected to the MIP737 board	Project Magenta Glass Cockpit software is not settled in "Extended Mode"	Set the Project Magenta Glass Cockpit in "Extended Mode" (F6), disable the unused elements and resize displays on all machines. See also MIP737 operation manual
Switches connected to the MCPEX1 expansion board doesn't works with Project Magenta	CPflight Input/Output disabled in the Project Magenta MCP.ini file	Close Project Magenta MCP. Edit MCP.ini file (in the Project Magenta MCP folder) In the [SerialConnection] area set CPFlightIO=On Save the file and run Project Magenta MCP again.
	The Project Magenta MCP does not find the configuration files	Close Project Magenta MCP. Edit MCP.ini file (in the Project Magenta MCP folder) In the [SerialConnection] area set CPFlightIO=On Save the file and run Project Magenta MCP again. Copy all configuration files in the Project Magenta MCP folder every time you change anything in the confuguration. Files are: Preferences.txt, DigitalIN.txt, DigitalOUT.txt, AnalogIN.txt and AnalogOUT.txt, you find them in the CPflighttools folder. See also MCPEX1 operation manual
The MCP goes dark when I change the battery or alternator status in the overhead	Project Magenta MCP.ini file setting (The MCP can extinguish the displays to simulate a "cold and dark" situation in the cockpit when the aircraft battery is Off)	Close Project Magenta MCP. Edit MCP.ini file (in the Project Magenta MCP folder) In the [SerialConnection] area change the setting for IgnoreBattery Set it to: =On or =Off depending by your preferences. Save the file and run Project Magenta MCP again.

USE WITH PMDG737 NG and 747
PROBLEM	POSSIBLE CAUSE	SOLUTION
Cpflight MCP displays doesn't match PMDG MCP display values	Wrong version setting	Check to have enabled the correct PMDG version in the MCP_CONF software "Main Setting" Tab.
	Wrong key definition	Change the Key definition in the PMDG keyboard command menu. (See the list of suggested setting here
	Duplicate key definition	Another FS software add-on use the same key combination; change setting.
	Others CPflight software already running when you launched FS_COM driver	Do not run more than one CPflight software at a time. Close any possible CPflight program that already run on the computer (In the windows task manager close any running CPflight application) and run FS_COM again
	Wrong start-up sequence	When use PMDG, load the aircraft before to run FS_COM
	Too old CPflight software version	Update the CPflighttools driver. Download here
Cpflight MCP synchronizes data at the start-up but can't modify data with PMDG	Keyboard ini files lie in different hard disk or disk partition	If you have more hard disk or more partition on your hard disk copy the PMDG key definition file (737kbd.ini and/or 747400kbd.ini) into \..\CPFlightTools folder. If you change assignment in the PMDG key assignment menu copy again the modified file into \..\CPFlightTools folder.
Some key combination doesn't work	Unusable or duplicate key definition Old MCP firmware version	Close FS_COM then change the assignment in the PMDG keyboard command menu. Then run FS_COM again. See valid key combination here Update the Firmware. Download here and follow the enclosed instruction to upgrade.