HARDWARE COMPATIBILITY:

Due to the differences of the new series MCP737 and expansion modules (yellow digits) respect the previous version (Red digit); there are some considerations about modules connection. The main difference consists in the power supply requirement; the new series require a 6Vdc power supply while the old series is powered by 5Vdc. To connect different version modules an adapter is needed.
It is possible to connect the new series Radios to the RS232 MCP version using the VDC Buffer adapter or the "Daisy chain adapter"; if you need to connect "old" style radios to the USB MCP version use the VDC reductor. All adapters are available at purchase page.

IMPORTANT NOTE ABOUT EXPANSION BOARDS:

The use of the expansion boards requires somewhat technical capability. It is important to know the functions that you need to implement on your cockpit and see on the manual if the board support and match your requirements. Please do not email with questions about where to find a certain switch or that LED, or to ask if this LED it goes well or not. We receive hundreds of email and we are not in a position to find and check hundreds of technical specification to answers to these questions.
We have to remark that the board is supplied as it is; the characteristics, the technical specifications and the possible suggestion are reported in the manual; we cannot take part in the building of tens of cockpit with different setup.

FUNCTIONALITY CHECK:

To check the hardware functionality use the CPflighttest utility. The CPflighttest allows testing the MCP and all the expansion modules connected to the daisy-chain. CPflighttest does not allows to test the MCPEX1 expansion board; to test the MCPEX1 use the MCP_CONF configuration software. Both test and configuration program are placed into the cpflighttools folder during the CPflight drivers installation and you can find it in the Windows program start menu.
Due to the continuous product development some functions come added in different moments depending by the changes in the FS, in the supported aircraft, in Project Magenta software, or for improvements. Before any other action check to have installed the last revision of firmware, of the CPflighttools software, of Project Magenta software (if any), and FSUIPC.
Before Run the CPflighttest utility check the MCP Power supply: Disconnect and reconnect the power supply and the USB cable to the MCP. Insert the plug firmly, do not to force laterally and make sure that make a good contact. If the supply is ok the Right course display will show for some seconds the firmware revision.
Run the CPflighttest utility (to correctly check the hardware only the CPflighttest have to run; close FS, Project Magenta or any other program before run the utility).
The CPflighttest will show on the screen the possible connected hardware; when you run the utility for the first time you will have to select the communication port; select the correct port (see also MCP737 operations manual).
The MCP will start-up and the connected modules will be highlighted on the screen. Mouse click on the module which you need to test and check on the screen the right reaction to the actuated commands. If all hardware function is operating probably there is an issue in the software installation compatibility or setting-up.
If you find problem in the hardware test see the following tips before to contact the email support:

HARDWARE TROUBLESHOOTING:

START-UP
PROBLEM	POSSIBLE CAUSE	SOLUTION
The MCP doesn't start-up	Power supply disconnected or fault	Disconnect and reconnect the power supply cord and USB cable from the MCP Insert the plug firmly, do not to force laterally and make sure that make a good contact. The revision number will appear for some seconds on the Right course display.
	Communication fault	Check cable connection Run the configuration software MCP_CONF and select the correct communication port (see also MCP manual ) Be sure to not have other software that takes possession of the selected port
	Antivirus or firewall setting prevent the data exchange	Check if any antivirus or firewall setting prevent the data exchange with the selected COM port or cpflight applications. Disable or insert the CPflight applications (CPflighttest, FS_COM and MCP_CONF) in the Firewall exceptions
	Project Magenta MCP or others CPflight software already running before you connect supply to the MCP	Close Project Magenta and CPflight program (In the windows task manager close any running CPflight application). Restart the MCP and run CPflighttest

DAISY-CHAINED ADD-ON MODULES
PROBLEM	POSSIBLE CAUSE	SOLUTION
No reaction from add-on modules	Connection to the MCP without disconnects power supply	The external modules are detected by the MCP at the power-up (when connecting the power supply); before connect any external module to the MCP disconnect power supply and USB cable
	Two same modules settled to the same function. (Example: both navigation radios settled to NAV 1)	Check the jumper setting on the back of modules
	MCP firmware out-off-date (for example the module is more recently developed than the installed firmware)	Download the last version of the firmware and upgrade (follow the enclosed instruction)
Some add-on module not working properly	Hardware fault of a module (note that a broken module can compromise the operation of all the others)	Disconnect all the modules and insert module one by one to find the fault one. Do not forget to disconnect power supply and USB cable every time you add a module. (To avoid damaging the DC socket of the MCP for the numerous interventions, better to disconnect the adapter on the AC side)
	"Old" and "New" style modules connected on the daisy-chain without proper adapter	Check modules configuration (see Hardware compatibility section in the top of this page)
	Too long connection cables between modules	Use shorter 5 pole cables between contiguous modules
	Too many modules on the Daisy-chain	Depending by the number of modules the "Daisy chain adapter" DCA001 can be required (see on purchase page)
Some add-on module restart continuously	Too many modules on the Daisy-chain	With a high number of modules a dedicate power supply to the Daisy chain adapter can be required. Connect a power supply adapter to the DCA001. Features for the power supply adapter are: Output: 6 to 7,5Vdc Current capability: at least 500mA Connection: standard 5,5x2,1mm coaxial plug, positive inner.
The new COM/NAV/ADF/XPDR modules does not works with the MCP737 RS232 version	The new series modules require 6 to 7,5 VDC where the RS232 version works with 5Vdc.	Insert the VDC buffer in the daisy-chain connection. See on purchase page. (Also the "Daisy chain adapter" can be used with a standard 6 to 7,5 Vdc power supply adapter; suggested if you have mixed old and new modules. ( See related manual)

EXPANSION BOARDS
PROBLEM	POSSIBLE CAUSE	SOLUTION
Connecting the MIP737 expansion board in the Daisy-chain, some expansion module doesn't works correctly	Too high load on the daisy-chain	If you have a high number of modules on the daisy chain the use of a dedicate supply for the MIP737 board is advisable. Connect a dedicate supply adapter to the MIP737 board. (See the MIP737 operation manual here).
Too low light on the MIP737 connected LED's	Too low efficiency LED's	The digital outputs of the MIP737 board are settled to drive High efficiency LED's. In low current mode setting (see manual) each output supply ~5mA to the LED; in High current mode setting each output supply ~10mA on each LED (in both case 2V drop LED's are considered). The effect of the indication and warning lights will depends by the type of LED, we recommend using high efficiency LED only and to make some test with different type of LED's to match the brightness of different color LED (amber, red and green)
	The used annunciators and legends obstruct the light transfer	Use transparent annunciators and legends (or annunciators with low dimming effect).
A selector connected to the MIP737 board works on the related function, but also affect other different functions	Short circuit in the common pole of two different Input groups	Check wiring connections, do not wire together the common poles of two different group (see manual)
On the MIP737 a single LED output turn-on more LED's	Short circuit in the common pole of two different LED group.
A LED connected to a MCPEX1 digital output have reverse action	Wrong connection to the N.O. (Normally Open) and N.C. (normally closed) relay contact.	Exchange connections on the terminal block. See also MCPEX1 user manual