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

Forums
FSUIPC
FSUIPC7
PFC MCP not working
 
Notifications
Clear all

PFC MCP not working

 
Page 2 / 4
Posts: 331
 FSUIPC Support
Moderator
July 20, 2026 10:36 pm
(@fsuipc-support)
Joined: 9 months ago

You can attach your logs and I'll take a look to see if I can see anything, but I think you need support from PM really.

I'm not familiar with the PM MCP or if that needs/used FSUIPC and/or the PFC driver - I will see if I can find anything about this tomorrow.


Reply
Posts: 331
 FSUIPC Support
Moderator
July 21, 2026 10:08 am
(@fsuipc-support)
Joined: 9 months ago

The PM MCP uses the FSUIPC offset area 0x04E0 - 0x0537. If you can set logging for IPC Reads/Writes in FSUIPC and show me a log file I can take a look.

Also, make sure that the PM software is running at the same privilege level as FSUIPC/FSX, otherwise it won't be able to connect.


Reply
Posts: 331
 FSUIPC Support
Moderator
July 21, 2026 10:13 am
(@fsuipc-support)
Joined: 9 months ago

Also, did you see the notes in the user guide on using the PFC MCP? 

If you are using a PFC 737NG MCP **(see Note below), please not that it already has a USB adapter built in, and can be connected directly to a PC USB port. The driver should have been supplied with it. Use the USB connection in preference to the serial connection. If you have another console, such as the Jetliner, connect that by serial cable to the MCP. At the time of writing the MCP normally operates at 19200 bps, but will have to be slowed to 9600 (by internal jumper) to allow the additional console to work.

...

** NOTE: The PFC MCP normally operates at 19200 bps, not the usual 9600 bps of other PFC devices. The PFC driver cannot detect this. If you have only the MCP connected and are using the PFC DLL for it rather than, say, the Project Magenta MCP.EXE connection, then you will need to add/or change the following parameter in the PFC.INI (or PFCFSX.INI file after running FS with the DLL installed for the first time. Close down FS and edit the file:

[Connection]Speed=19200


This post was modified 6 days ago by FSUIPC Support
Reply
Posts: 11
 Selkan
Registered
Topic starter
July 21, 2026 10:47 am
(@selkan)
Joined: 2 months ago

Attachment : PFCFSX.log

Attachment : FSUIPC4.log

Reply
Posts: 11
 Selkan
Registered
Topic starter
July 21, 2026 10:53 am
(@selkan)
Joined: 2 months ago

I have managed to add a couple of Log files for you.  I have tried setting the Connection speed to 19200 and adjusted the speed on the Com Port to match (19200 from 9600), but no joy.  Referring to your first post above.  'The Driver should have been supplied with it' - not sure what this means?  Also '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.


Reply
Page 2 / 4
Forum Jump:
  Previous Topic
Next Topic