Hi Everyone,
As I mentioned previously I'm installing ProSim B738 for the first time in my cockpit, and I'm having trouble getting my CP-Flight equipment recognised by the system.
To be honest I'm sure this isn't a ProSim issue, but I see from a forum search that this seems to be a common complaint but with few successful outcomes, or at least they were not documented.
I now have the FDS SYS cards, Go-flight modules and Leo Bodnar cards all recognised and working fine in ProSim but the CP-Flight MCP and twin EFIS units are resisting all my attempts to get them Interfaced.
The MCP Lights up and announces it's serial number and firmware version but will not start even with it's own hardware test program.
I believe it's a Windows 10 issue that does not allow the installation of a driver, but the system has never reported a problem. Yet when I try to install the USB driver CP-Flight supply, it says the best driver is already installed. Again I nave seen lots of ways this should (or could) be done but they have not worked so far. The windows system shows a Com 1 port but does not show the CP-Flight serial port that they mention in their documentation. Which I think is the problem.
When I load the CP-Flight test program, a window pops up over the graphic asking for the COM port, yet showing COM 1 selected. If I click okay it simply reappears, which leads me to believe that's the issue.
Any thoughts or advice on how to proceed would be gratefully received.
Thanks Joe.
Hi Joe
It does seem like your COM port is not set up correctly.
What CPFlight MCP do you have? I have the MCP737PRO.
Two things to try...
(1) Download the latest USB com driver from the FTDI website (not the CPFlight website). Specifically install that one. That is the one that I am using. That is where you assign the connected COM port.
(2) Are you sure that the MCP is connected to COM 1? Try unplugging the MCP to be sure. Observe what happens in Windows Device manager. COM 1 should disappear when the MCP is unplugged, and should reappear when it is plugged back in.
I hope your issue is as simple as that.
Fred K
Hey Joe,
Just checking a few things to help you. Okay, if this is the older CPFlight with USB connector, do you know which USB version it is...1.0, 1.1, 2.0, or 3.0? I'm guessing it's 1.0 or 2.0.
Next, make sure the PC USB port you're using matches; 2.0 is easy, but if your PC doesn't have a 1.0 or 1.1 you'll have to go into the BIOS and turn on legacy USB or something worded similar to that. This will turn on the older USB versions.
Have you found the listing of the com1 like Frank described, when you plug and unplug it? Make sure you see where it shows up. Also, directly plug it into the USB port and no hubs and/or USB extensions for now.
To clarify, there is no interface card in between right, you know like the G2 or G3 cards? If there is one, please tell what it is.
Lastly, how did you use it before ProSim737? Which avionics software, which version of Windows, which Flight Sim program, and is it the same PC as before or a different one? If you still have the older setup running, hook the MCP back up too make sure it still works like normal. That way you'll know nothing has happened to it while you were changing things around....
John
Fred:
Mine is the same unit, MCP737Pro and COM1 doesn't disappear when I unplug the cable. What does happen is the Human Interface Devices list opens on it's own, yet doesn't show any error (no exclamation mark).
I believe that this would indicate that the serial
John:
I believe it's an original first edition. when it's plugged in it shows the serial number first then 00 rel 105. which I believe refers to the firmware version.
It is plugged directly into the USB port on the PC, with no other cards involved.
This is a completely new PC to the previous one, I built it for the flight deck about a year ago but have not had it working in this new construction.
I wrote all of the above in the middle of trying the suggestions from you guys, when I downloaded and installed the drivers from the FTDI site the serial adapter appeared with COM3. I checked with the CP-Flight Hardware test and eureka!!! it works.
Thanks both for all your input, I knew someone would have an answer for me.
My best regards.... there will be more questions I'm sure!!!
Joe.
Awesome Joe! Glad you got it sorted, and it's now working with ProSim737 as well right?
John
Yes, at least as soon as I run ProSim system the MCP lights up so I assume it is.
I have quite a lot yet to do but I'm trying to make sure every element is working before moving on to the next part.
Thanks for asking John.
Joe.
That's good news Joe! Keep us posted 😁
John