These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
Posted by: @selkanI have tried setting the Connection speed to 19200 and adjusted the speed on the Com Port to match (19200 from 9600), but no joy
But the speed should be 9600, set by the jumpers and in the ini file, not 19200.
And also check your connections and com ports. Please read thye advice again carefully - it says prefer the USB connection, and with your Jet Liner Console that should be connected via serial cable to your MCP.
Posted by: @selkanReferring to your first post above. 'The Driver should have been supplied with it' - not sure what this means?
It means that there should be a software driver that you need to install to use the MCP via a USB cable.
Posted by: @selkanAlso 'slowed to 9600 (by internal jumper)' - again not sure what this means. If it means doing something inside the MCP I would not have a clue.
Yes, it would mean setting/checking/changing some jumper switches in the MCP (could be on the outside or inside - check any documentation you have) to set the correct baud rate. You need to set the rate to match that set in the ini, and this should be 9600 and not 19200.
Sorry but I can only repeat what I see in the documentation. Have you tried PFC support?
Your logs show nothing of interest (and no IPC Read/Write logging avtivated). Maybe some logging also needs to be set in the PFC.ini file - I will check.
What does the PFC Control Connection Check window show?
If find it slightly confusing that you are using both the PFC MCP as well as the PM MCP though. I thought the PM MCP was/is a software MCP shown in a window, which you won't need if you have a hardware PFC MCP. Again, from the documentation on the controls connection check (note the section highlighted):
Here all of the main PFC connections are okay (yoke, pedals, throttle quadrant and avionics stack), but there’s no Project Magenta CDU or RCDU, and no MCP (whether the hardware PFC MCP or the Project Magenta MCP program).
Not sure how this works if you have both a hardware and a software MCP.
Btw, is this a new set-up, or was it previously working? If so, what has changed?
Have you read the PFC driver user guide? If not, please read that carefully as there may also be some other setings that are relevant.
I'd also make sure Windows is actually detecting the PFC MCP correctly before launching the sim, and if you've recently updated FSUIPC or MSFS, a clean restart of both can sometimes fix connection issues. It's surprising how often that helps.
Hi, I have run PM File checker and took this up to my PC Chap who is now coming in on Thursday. He said straight away that the Path to FSX is not correct, and that is why a lot of errors came up. I have FSX in default location C:\Programs 86x\Microsoft Games\Microsoft Flight Simulator X. The Path shown is \\SERVER\MFS X. I don't know why this would happen, but my Chap I am sure can sort this. Regarding the MCP - I have had my cockpit now for twenty years. My MCP Hardware has always been connected by SCP as has my Jetliner Console. Never had this issue before. I am aware one can wire the Jetliner Console through the MCP, but I don't have any drivers for the USB connection. As I say, have always had both items plugged into my two Com Ports without any issues. I have been in touch with PFC over this matter, but support is very limited because they stopped making the MCP many years ago.
The PM MCP is designed to simply run in the background on the Server without the 2D MCP visable. It must act as a duplicate MCP from within FSX and in turn those inputs are transfered to the Hardware MCP. (or visa versa). I can see why this might sound confusing having the two items running. I guess the idea must be if you don't have the MCP Hardware, you might use the program on a Monitor screen within a cockpit. Not ideal of course, but would work.
The only, but large change is a new PC running Windows 11 Home. From what my chap has said this may simply be a 'Path' issue, and once that is sorted perhaps the MCP program will been seen etc.
Thank you again for your input. I think the best thing to do now is wait for my Chap to come in on Thursday afternoon, and I'll report back on how we have progressed.
There could be an issue to the fact that you have installed FSX under 'C:\Program Files (x86)\', which is a windows-protected folder. Each version of windows is getting stricter and stricter on apps ran from this folder. You could try re-installing FSX into a non-windows protected folder, or maybe try running everything with Admin privileges to see if that makes a difference.
I'm not sure why the FS UNC path is incorrect, but maybe check any registry entries under (HKLM) 'SYSTEM\\CurrentControlSet\\Services\\lanmanserver\\Shares' (as I can see the code checks there when generating the UNC path)..