I have removed the case from the MCP II to add my own panel face. I removed the on/off switch to turn the MCP on and off with a 5V relay. All lights up fine and Test Mode Shows on the Comm screen.
 

Using a new USB cable and plugged into a 2.0 port, Windows 10 device manager shows no device connected to COM 1 port (the only device connected).
 

However, LINDA has recognized the presence after Setup with COM 1 but no MCP connection to P3D V4.5. Green OK in Summary screen next to VRInsight. P3D and FSUIPC is shown running. Using FSX Default entries.

 

The comm screen still displays Test (AP DNA, AP . or AP 🙂
 

Any direction to troubleshoot?

Does any of the above prevent connectivity?
 

Thanks,

Dave Simmons

Tennessee, USA

If the MCP2 is in test mode it suggests that the panel AP cutoff switch has been made or not been implemented.

Sorry, I have looked all over the internet, MCP II Manuals and the front of the unit. Can't find the panel cutoff switch unless it is the power switch on the rear.

If you could point me to the location of its description or define it for me, I would be most appreciative. 

Sorry, I have looked all over the internet, MCP II Manuals and the front of the unit. Can't find the panel cutoff switch unless it is the power switch on the rear.

If you could point me to the location of its description or define it for me, I would be most appreciative. 

The Disengage Switch is in the down position. If this is an issue I cannot find any documentation.

NEVER MIND. FOUND IT.

NOWHERE CAN I FIND THAT THE DISENGAGE SWITCH IS ON IN THE DOWN POSITION. MAKES SENSE IF ONE LOOKS AT THE "REAL" BOEING AP AND ITS BAR.

NO BAR ON THE MCP, JUST THE SAME SWITCH AS ANY OTHER ON THE UNIT. UP IS NORMAL FOR ON.

Sorry, I have looked all over the internet, MCP II Manuals and the front of the unit. Can't find the panel cutoff switch unless it is the power switch on the rear.

If you could point me to the location of its description or define it for me, I would be most appreciative. 

The Disengage Switch is in the down position. If this is an issue I cannot find any documentation.

I don’t think the test mode is documented anywhere. I either found it by trial and error or it was in the additional material VRInsight supplied developers.

On the MCP2A (Airbus) it is the Baro InHg/hPa switch.

Well, the Disengage is off, both displays show the startup message. Installed VRSim and ran it. No device could be found. VRSim installed a new driver during installation.

Prior to removing Test and installing VRSim, hidden device showed COM 1 which I put in LINDA. The device manager showed no device connected. LINDA showed VRInsight OK in green.

Now, no COM/PORT devices are shown at all. VISIT shows no devices. Have not gotten anywhere near connecting to P3D V4.5 FSX at all. 

Any advice at all? Seems a Windows 10 issue. I contracted VRInsight but all the sent was directions to install their recent software.

VRSim and LINDA are mutually exclusive. Run one or the other.

If VRSim running on its own cannot find the MCP2 then there is some wrong with your set up. Do you have the FDTI USB to serial drivers installed? Check Device Manager COM ports. What is the COMPort number?

I'm in a Drs office right now. I will uninstall VRSim when I get back and follow your input. Let you know. 

No need to uninstall vrisim. Just don’t run it at the same time as LINDA. 

Edited December 30, 20205 yr by ScotFlieger

Right now I found the FDTI driver. In a little while I will install, check Windows 10 and try again. My gut tells me it's Win 10 and an incompatible driver either on Win 10 or VRI side.

I'll let you know. I'll do some Windows diagnostics and event determination.  The dings occur on both the insert and removal of the USB cable with the port.

I have found this site. I'll try it in the morning. Apparently Windows 10 has issues with USB to Serial Com. The driver on my machine is 2016 and is the latest from Microsoft. The attached URL uses a driver that costs ~$130. There are other solutions presented.

I'll use the steps presented below and use the FDTI driver you recommended. As a last resort, I'll buy the driver below.

https://www.virtual-serial-port.org/articles/com-port-on-windows-10/#native

PS - The machine I am using to test is refurbished with pre-loaded Windows 10. Knowing these issues, I wouldn't have bothered you.

I'll keep you posted.

With your help, I solved it. I went to the FDTI site as you recommended.

https://www.ftdichip.com/Drivers/VCP.htm

I downloaded the Windows 10 Installation Guide and Setup Executable for the driver (rather than manual install). Read the guide and followed the instructions (the above are under the column Comments on the Windows row).

The MCP II device was listed as COM3 in the USB Serial Port in the USB devices.

I started Linda and the port wouldn't change from COM1 to COM3. I entered FSUIPC6.ini and below [LINDA] was [VRInsight]. Under there, 1=COM0 and 2=COM1 were listed. I deleted the COMs and entered 1=COM3 (as listed in VRSim).

Opened P3D V4.5 then Linda, started the Lear 45XR aircraft at the end of the runway.

Everything worked fine.

Wondering if VRI's MCP can be interrogated? A friend has written an app for the Lear 45 CDU (another built the hardware). The software (in C++) interrogates all open com ports, receives a code from the CDU and connects to that port. Could Linda do that with VRInsight?

Thanks for your help.

Edited December 31, 20205 yr by dhsimmonsfsx