k9dog Posted November 18, 2003 Report Posted November 18, 2003 Hi Pete. We recently purchase the CPFLIGHT 737NG MCP and we are having some problems. Our simulator is composed of four networked computers (TCP/IP). 1. FS2004, FSUIPC, WIDEFS,PFC.DLL (latest versions), PFC Jet Liner console connected to com1 2. PM PFD and ND, WideClient 3. PM EICAS, MCP, CPFLIGHT MCP connected to com1, WideClient 4. PM CDU, WideClient The set-up works perfectly without the new hardware, however we have problems with our new MCP, after a few minutes of operation the MCP stops operating. I was wondering if there is any thing we need to add to our ini files (pfc.ini, fsuipc.ini, etc) in order for this hardware to work correctly. Any good ideas? Thanks in advanced Lyle RH
Pete Dowson Posted November 18, 2003 Report Posted November 18, 2003 The set-up works perfectly without the new hardware, however we have problems with our new MCP, after a few minutes of operation the MCP stops operating. I was wondering if there is any thing we need to add to our ini files (pfc.ini, fsuipc.ini, etc) in order for this hardware to work correctly. There certainly is nothing specific in any of my software to deal with or recognise anything about any such MCP, so the answer is "no", there is nothing in the INI files which is likely to make any difference whatsoever. I'm a bit curious as to why would you think it would? The INI files are basically just reflections of the options you select in the option screens in FS in any case. I'm afraid know almost nothing about this new MCP. Have you asked the suppliers? Does it use FSUIPC? I see you have it running on a Client PC, so does it use WideFS, or connect to FS or PM some other way? I thought from assorted messages on the PM Newsgroup that PM had specific direct support for it on its own COM port? Since you have PM's MCP and the hardware MCP on the same PC, I would assume there is no connection between the hardware MCP and any of my programs. Do you think there is? Regards, Pete
k9dog Posted November 18, 2003 Author Report Posted November 18, 2003 Pete Thanks for the replay.... I’m running out of ideas. I thought maybe the PFC module needed some configuration in order to use some other external MCP instead the one on the PFC Jet Liner console. Anyway, thank you very much and back to de FS lab for more testing. Lyle
Pete Dowson Posted November 18, 2003 Report Posted November 18, 2003 I thought maybe the PFC module needed some configuration in order to use some other external MCP instead the one on the PFC Jet Liner console No, it knows nothing about any other MCP you have. And it doesn't need to. You will just get two ways of controlling the A/P instead of one, that's all. PFC.DLL's MCP controls talk to one of FS's AP, PM's MCP or 767PIC. What happens then is up to them. But it will only send new Alt, Heading, VS or speed values when you change them, and similarly for the modes. Lke the Aerosoft COM-port based MCP, any other MCP should co-exist quite happily. It sounds like something is going wrong between the new hardware MCP and PM's MCP. I hope you get the answers you need from the PM Newsgroup. Regards, 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