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
Thanks for both your Posts above. I will report back to you ASAP on all points raised.
Posted by: @selkanThanks for both your Posts above.
Sorry, missed this and corrected/added info to my last post...
Hi, I have my PC Chap coming here on Friday afternoon, so will report back thereafter.
I thought I would respond as I can answer some of your questions:- Need to run a file checker to see if MCP is detected.
Tried my other Com Port (4), and changed MCP ini file to reflect CP number - no joy. I then plugged my Jetliner into CP 3, changed in ini file to CP 3 and that worked fine.
Previously, JetLiner and MCP were plugged into two separate Com Ports, on main Server PC, and always worked fine for 20 years! I have read the PFC manual (many times!). I don't have USB drivers for the USB port on the MCP, nor do I know of a method to change 19200 bps to 9600 bps to be the same as the Jetliner. I have written again to PFC about this for advice, but nothing coming back yet.
Yes, PFC MCP is connected to main Server PC.
I ran the PM software on a client PC simply as an experiment. Somewhere in their manual it does say the MCP software can be run on a Client PC, as WideServer/WideClient will see this along with what ever PM program is being used on that PC. In my case this was my Pilot instrumentation on Client PC. The manual then does say this would normally be run on the same PC running FSX, and that is how I have always run in the past. As I say just an experiment that did not work.
Will report back ASAP
Posted by: @selkanPreviously, JetLiner and MCP were plugged into two separate Com Ports, on main Server PC, and always worked fine for 20 years!
I understand this, but what I would like to know is if this was using the PM MCP software, and not by using the PFC dll/driver. I don't think the PFC dll driver will detect your PFC MCP when set-up this way (according to the driver documentation), so I suspect it was the PM MCP.exe which was driving the PFC MCP. If this is the case though, I don't see why you would need the COM entries in the FSUIPC ini file for the PFC MCP, unless the PM MCP software also reads the FSUIPC4.ini file.
Do you need to configure any COM ports in the PM MCP software? i.e. does this software talk directly to the PFC MCP, or only to FSUIPC?
I will check with Pete, but I think you have two options:
1. If you want to use the PM MCP software to drive the PFC MCP, then I can't help any further with this and you will need support from PM and/or PFC. And if you run the PM MCP software on a client PC, then I would suspect that the PFC MCP also needs to be connected and configured on the client (but am not sure about this...!).
2. If you want to use the PFC dll driver, you need to connect and set the baud rate (for which I understand you also need PFC support) as documented in the PFC dll/driver documentation.
Anyway, lets see if Pete has any ideas on this - I'll report back when I hear anything...