[Solved] PFC MCP not working

Hi, I have now completed the installation of PM MCP build 496 on my Pilot Client PC.  No joy - upon start up the instrumention is seen and working properly (FSX shows Client connected).  But still no MCP.  I am going to drop another line to PFC to see if they can provide any drivers for the USB connection, but as they stopped making the MCP years ago and not hopefull.  A friend of mine used to be a computer teacher until recent retirement.  He's going to come over and take a look.  Never know he might come up with something.

Ok, thanks for the update. To confirm, it is the PM MCP software program that isn't working, no?

Is the PFC MCP detected and working? I presume this can work independently of the PM software, no?

I will ask Pete to take a look at this thread to see if he has any advice on what could be the issue.

For clarity.  The PM MCP software does appear to be connecting with FSX.  Moving knobs and switches on the 2D MCP on my main screen is responding within FSX MCP.

PFC MCP is not detected.  There is a red light on the back of the Unit.  Like the Jetliner Console, I believe this should be flashing to indicate it is receiving data - just a constant red light.  I tried to run the MCP without the PM software running in the back ground, but no luck.

If Pete can come up with anything that would be good.  Just one other thing.  I have an old PFCFSX.dll from many years ago.  Just incase part of the up to date dLL had been altered because the PFC MCP is no longer available, I tried this old dll (placing in the modules folder with FSUIPC), but no joy.

Posted by: @selkan

↑

PFC MCP is not detected.  There is a red light on the back of the Unit.  Like the Jetliner Console, I believe this should be flashing to indicate it is receiving data - just a constant red light.  I tried to run the MCP without the PM software running in the back ground, but no luck.

Ok, then I think you should forget about the PM MCP software for now and concentrate on getting the PFC MCP detected and working first, and come back to the PM MCP softwre after this has been fixed. So, back to my very first question, which was unanswered - does the PFC driver / connection check see this device? Have you tried switching COM ports? Have you read the PFC driver user manual?

There is quite a bit in that document about using the PFC MCP, and I really think you need to connect your Jetliner console via the MCP, as the PFC driver user manual does say:

The MCP can also be used in combination with one of the consoles provided the console is connected through the MCP and the latter is set to run at 9600 bps)

This makes me suspect that you do need to connect this way to see both devices, although you do say they were previously both directly connected to your PC. But why not at least try this method of connection?

Presumably your PFC MCP is connected to the server PC and not the client, no?

Also, reading the driver documentation, it seems that you have a choice of either using the PFC driver we supply to control the PFC MCP, in which case you do need to follow the instructions given in the user manual (vis-a-vis connection of jetliner console via the MCP and changing the baud rate of the MCP to 9600), OR, alternatively, using the PM MCP software (MCP.exe) to drive the PFC MCP. I presume that it was previously set-up like this, and so it would be an issue with the PM MCP software (and not the PFC driver) not detecting your PFC MCP, in which case it is PM support that you need to resolve this.

Also, if the PM MCP software is running on the client PC, then shouldn't the PFC MCP also be connected to the client, as it is the PM software that is acting as the driver? How was this set-up previously when working?