DrBrown Posted April 3, 2019 Report Posted April 3, 2019 Hello, My sim has a MCP737PRO2 in it. Nice unit. However when I try to connect the driver via FS_COM it tells me I don't have FSUIPC. But I do. I have a registered version I believe it is FSUIPC4. I just ran the installer (several years ago) and it works fine in FSX. I'm not sure where FS_COM is looking? Any help would be greatly appreciated. Kind Regards, Paul
Pete Dowson Posted April 3, 2019 Report Posted April 3, 2019 Sorry, i've no idea what "FS_COM" is or what it wants with FSUIPC. Perhaps you need to look at its documentation or contact it's author's support? Who makes the MCP737PRO2? Pete
DrBrown Posted April 3, 2019 Author Report Posted April 3, 2019 Hi Pete, It's an MCP made by CPFlight. I send them requests for help many many times but they do not reply? This MCP is an ethernet connected device and part of the setup is connecting to fsx via a program named FS_COM that comes with CPFlight. It's just a setup window that allows you to enter the IP address of the MCP so that the drivers connect. The documentation says it needs FSUIPC. I have FSUIPC installed so I do not know what the issue is. In FSX under add ons I see FSUIPC but CPFlight is not there. I believe this is causing connection problems. At times the MCP stops working. I tried running FS_COM this morning and received the error stating I needed FSUIPC. Then I closed FS_COM and ran it again. The FSUIPC message doesn't appear now but the software doesn't seem to work. I click connect but nothing happens. Then I close the window and another FS_COM window opens? That keep happening over an over until I use task manager to end it. Got no idea what is going on. Thanks, Paul
Pete Dowson Posted April 3, 2019 Report Posted April 3, 2019 1 hour ago, DrBrown said: The documentation says it needs FSUIPC. I have FSUIPC installed so I do not know what the issue is. In FSX under add ons I see FSUIPC but CPFlight is not there. And no error message from FS_COM? 1 hour ago, DrBrown said: tried running FS_COM this morning and received the error stating I needed FSUIPC. If FSUIPC is running at the time (as you can see by its entry in the AddOns menu), then FS_COM has a problem. 1 hour ago, DrBrown said: Then I closed FS_COM and ran it again. The FSUIPC message doesn't appear now ... In that case it sounds like the first time was too soon, not allowing time for the Sim to be "ready to fly" -- which is when FSUIPC is ready to service applications. 1 hour ago, DrBrown said: but the software doesn't seem to work. I click connect but nothing happens. Then I close the window and another FS_COM window opens? That keep happening over an over until I use task manager to end it. Sorry, but this is all adding up to be a definite problem with that FS_COM program. I'm afraid your only recourse is the supplier. Of course try reinstalling it first, or even re-downloading it as well. Pete
DrBrown Posted April 4, 2019 Author Report Posted April 4, 2019 Hi Pete, Thanks for getting back to me. I did not have FSX running at the time I tried to make the connection. So, I'll give it another go with FSX running and see what happens. Then I'll get back to you about the results. Kind Regards, Paul
Pete Dowson Posted April 4, 2019 Report Posted April 4, 2019 22 minutes ago, DrBrown said: Thanks for getting back to me. I did not have FSX running at the time I tried to make the connection. Well that would certainly explain it! FSUIPC cannot run until FSX loads it. it is a module within FSX, not a separae program! Best to use the [Programs] section of FSUIPC's settings to get the program automatically loaded at the start, (and optionally closed at the end). Pete
DrBrown Posted April 4, 2019 Author Report Posted April 4, 2019 Hi Pete, Okay I ran fsx and of course FSUIPC shows up in the add ons. Now I run FS_COM and get this.
DrBrown Posted April 4, 2019 Author Report Posted April 4, 2019 Hi Pete, Got it working by running FS_COM as administrator. Ha. Thanks for your help! Regards, Paul
Pete Dowson Posted April 4, 2019 Report Posted April 4, 2019 3 hours ago, DrBrown said: Got it working by running FS_COM as administrator. Sounds like you are running FS "as administrator" then. Programs need to be at the same privilege level in order to share memory, part of the data exchange protocol. Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now