Hi,

I have a few questions regarding the new CPFlight MCP/MCP Pro interface driver for FS2004.

Right now I have the following configuration:

PMDG 737-600/700/800/900 and 747-400 airliners installed.

MCP (USB version) with 2 COMM's, 2 NAV's, 2 ADF's, transponder, EFIS and a daisy-chain adapter.

1. On the product page it says that for the PMDG 737NG this interface supports for an adittional 8 modules. I assume that additional modules are also supported for the PMDG 747-400? (e.g. 2 COMM's, EFIS and transponder).

2. I'm thinking about replacing the MCP (USB version) and EFIS with the MCPPro and EFISPro. Will all the other existing modules I already have work with the new MCPPro and EFISPro?

3. Do I have to buy the driver again if I replace the MCP (USB version) and EFIS with the MCPPro and EFISPro? (PS: I haven't bought the new driver yet for the USB version, but I will next month.?I'm planning on replacing the 2 units later this year. Will I have to buy the driver again at that time?).

4. What is the reason that the MCPPro and EFISPro now do work with PMDG? (when the new units were first released by CPFlight, there was no support for PMDG).

5. Will all of the transponder functions work with PMDG 737NG/747 (e.g. TA/RA and testmode)? Right now these functions are not operative with the current CPFlight driver.

I hope you can answer my questions.

Jon

Hello Jon-

to answer individual questions:

1. Yes- for FS9, those modules that "make sense" for a 747-400, are supported fully (i.e. no NAV, as the NAV functionality is embedded in the 747 CDU).

2. They all work properly (with the latest firmware, mind you).

3. Well- the driver supports both hardware modules (MCP and MCPPro), but they will come with different serial numbers, so they won't both be licensed to work. If I were you, I'd make a special request to CPFlight to ask for the same serial number as your original MCP to be placed on the MCPPro, in which case they will work with the original license you'll purchase.

4. Is this a philosophical question? There's still no support from PMDG on these modules... Flight Sim Labs had the resources to dedicate (both in man-hours and in technology investment) and the result is the newer drivers - as a third-party development.

5. Yes, they will work properly as they do within the software.

Glad to be of service. Don't forget: You can always freely download the product and test fully for yourself (it's only area-limited around the LGAV airport). Once you decide it fits your needs, you can then purchase a full license.

Best regards,

Posted By Lefteris Kalamaras on 10/09/2008 7:34 AM

Glad to be of service. Don't forget: You can always freely download the product and test fully for yourself (it's only area-limited around the LGAV airport). Once you decide it fits your needs, you can then purchase a full license.

Thanks for answering my questions. I know I can try the driver before I purchase it, but then I would have to upgrade the firmware of the MCP.

If for some reason I would decide not to buy the driver, then I cannot go back to the old firmware. Because the new firmware doesn't support PMDG anymore through FS_COM. And I probably cannot downgrade the firmware of the MCP.

I did not purchase the MCP (USB version) through CPFlight, but through a local flightsim retailer. So asking CPFlight to put the same serial on the MCPPro is not an option. Also I'm going to order the MCPPro through the same local flightsim retailer.

I think I will wait with buying the new driver until I have the MCPPro and EFISPro. That way I only have to buy the driver once.

Jon

I have just replaced my MCP and EFIS with the MCPPro and EFISPro modules. Also, I have purchased the driver for FS2004.

The hardware is working ok (MCPPro, EFISPro, 2 COMM's, 2 NAV's, 2 ADF's, XPNDR?and a daisychain adapter) with PMDG 737/747.

But I have come across a few issues that are not working 100% correctly.

PMDG 737:

1. When starting in a cold and dark cockpit, the MCP and radios (COM/NAV/ADF/XPNDR) are all illuminated. When using the previous CPFlight driver, all modules where off (not illuminated).

2. Switching on the panellights in the daytime does not activate the backlighting on the modules. However, the backlighting does come on when switching on the panellights in nighttime.

3. The "Test button" on the COM/NAV radios (CPFlight modules) no longer produce a "hissing sound" when the button is pressed. When using the previous CPFlight driver, the test buttons did produce this sound.

4. The transponder is working ok, except it's not possible to activate the TCAS test with the CPFlight module.

5. On the EFIS module it seems that the IN/HPA setting is reversed (when the CPFlight EFIS is turned to IN, then the PMDG EFIS displays HPA and vica versa).

PMDG 747-400:

1. Same problem as described with the 737 (dark and cold cockpit).

2. The bank angle limit switch does not work on the 747.

3. The backlighting on the CPFlight modules does not function at all (day or nighttime).

4. Same problem as described with the 737 (TCAS test).

5. Same problem as described with the 737 (IN/HPA setting).

And I've got a request. Would it be possible that the driver "remembers" what COM port and baudrate is previously selected? Now you have to select these items manually every time you connect the interface.

I hope I have contributed some feedback, and that most of these issues can be resolved in an update.


Best regards,

Jon

Jon-

thanks for your observations. I will run some tests on my end and let you know asap.

I discovered another issue with the PMDG 747-400 during flight.

When HDG Select is being pressed on the CPFlight MCPPro, then HDG Hold is activated on the PMDG MCP instead of HDG Select. This wasn't the case when using the previous CPFlight driver.

I hope this can be corrected too.


Jon

Jon-

regarding that last post: Yes, HDG Hold is activated we are consistent with the 737NG as well. If you wish to activate HDG SEL, use the CWS A button (or was it CWS B? :-)).

Posted By KingCat on 10/13/2008 8:41 AM

I have just replaced my MCP and EFIS with the MCPPro and EFISPro modules. Also, I have purchased the driver for FS2004.

The hardware is working ok (MCPPro, EFISPro, 2 COMM's, 2 NAV's, 2 ADF's, XPNDR?and a daisychain adapter) with PMDG 737/747.

But I have come across a few issues that are not working 100% correctly.

We'll try to help you with your questions, answering one by one below:

PMDG 737:

1. When starting in a cold and dark cockpit, the MCP and radios (COM/NAV/ADF/XPNDR) are all illuminated. When using the previous CPFlight driver, all modules where off (not illuminated).

The backlight illumination command is sent to the hardware only if received by the PMDG aircraft. If the driver does not receive it, it shouldn't send it. Is that not the case?

2. Switching on the panellights in the daytime does not activate the backlighting on the modules. However, the backlighting does come on when switching on the panellights in nighttime.

That's a "feature" of the PMDG aircraft. Daylight backlighting is "forbidden". However, as it's a common request, we'll try to implement some sort of checkbox in the dialog window in a future release.

3. The "Test button" on the COM/NAV radios (CPFlight modules) no longer produce a "hissing sound" when the button is pressed. When using the previous CPFlight driver, the test buttons did produce this sound.

Aircraft sounds are not produced by the driver interface - we leave that to the PMDG aircraft simulation (you'll notice there's no warning siren or fire bells either).

4. The transponder is working ok, except it's not possible to activate the TCAS test with the CPFlight module.

Did you try pushing the knob inwards? It should work.

5. On the EFIS module it seems that the IN/HPA setting is reversed (when the CPFlight EFIS is turned to IN, then the PMDG EFIS displays HPA and vica versa).

Did this only start happening when you switched from the EFIS to the EFIS Pro module? If so, it's an issue for CPFlight to look into, perhaps.

PMDG 747-400:

1. Same problem as described with the 737 (dark and cold cockpit).

2. The bank angle limit switch does not work on the 747.

3. The backlighting on the CPFlight modules does not function at all (day or nighttime).

4. Same problem as described with the 737 (TCAS test).

5. Same problem as described with the 737 (IN/HPA setting).

And I've got a request. Would it be possible that the driver "remembers" what COM port and baudrate is previously selected? Now you have to select these items manually every time you connect the interface.

I hope I have contributed some feedback, and that most of these issues can be resolved in an update.


Best regards,

Jon

The COM port and baudrate are saved in the /FSLabs/FSLabs_CPMCPPro.ini file, if you check the "reconnect" box before hitting the Connect button. Can you check yours and see if that is indeed the case?

Hope this helps!!!

Posted By Lefteris Kalamaras on 10/21/2008 1:24 PM

Jon-

regarding that last post: Yes, HDG Hold is activated we are consistent with the 737NG as well. If you wish to activate HDG SEL, use the CWS A button (or was it CWS B? :-)).

I've tried the CWS A button, and indeed that activates the HDG SEL button on the PMDG 747-400. However, I think that HDG SEL should be activated by pressing the button HDG SEL instead of the?CWS A button.

I can understand that you're saying that you're trying to be consistent with the PMDG 737, but?I have to say that the previous CPFlight driver did have this feature (activating HDG SEL with the HDG SEL button in the 744). So?I think in this case that the CPFlight has better support for the PMDG 747-400.

Jon?

Thank you for your reply to the issues I mentioned in an earlier post. However I think there has been some miscommunication, as there are some questions unanswered. So, I'll go over each one of them and respond to your reply.

PMDG 737:

1. I'm not talking about the backlighting of the modules in a dark & cold cockpit, but I meant that the radios and MCP are on (i.e. the numbers on the display should be off). When using the previous CPFlight driver the modules were completely off (i.e. all displays are off).

2. Daylight backlighting can be "forbidden", but I assume that doesn't prevent me as a pilot to turn them on if I want to? ? I understand that this will be implemented in a future update.

3. Fair enough if you say that if PMDG didn't model the "hissing sound" that you're also not modeling it in your driver. However the CPFlight driver did have this "feature" added to their driver. I consider this as "extra service" and that raises the quality of the overall experience and realism.

4. I haven't tried pushing the knob inwards on the 737 (will try that soon), but I can say that pushing the knob inwards on the PMDG 747-400 does NOT work in any case. Hope this can be corrected.

5. Yes, this only started happening when switching from the EFIS to the EFISPro. I'll contact CPFlight?about this issue and let you?know what they have to say about this.

PMDG 747:

Unfortunately?you haven't answered any?of the issues I mentioned concerning?the PMDG 744.?Some of them are the same as the 737, but not all of them (e.g. the backlighting I mentioned does not work in day or nighttime. The bank angle limit switch not working, and the?TCAS test button not working on the?transponder of the PMDG 744).

About saving the COM port and baudrate. My request would be to have the "remember function" added to the driver as a basic feature instead of having to check "reconnect". Checking "reconnect" is for reconnecting?on startup. I'm?not?using this feature. I do not want the hardware to connect automatically on startup.

On a personal note: for me the advantage of?using the FlightSimLabs driver lies in the fact that it's now possible to use the MCPPro with PMDG. Other than that?if I was still using the?previous CPFlight MCP, I would prefer the CPFlight driver, because in the CPFlight driver the issues I mentioned just do not exist. I just hope that certain issues can be resolved.


Jon

Jon-

I am in Paderborn, Germany at the moment, but as soon as I get back on Monday, I'll take a look at those issues and make sure we resolve them in a satisfactory manner for you and our other customers! We take pride in our customer support, so I want to make sure you will be rewarded for selecting Flight Sim Labs!

Have you had any chance yet to take a look at the issues I mentioned?

BTW. Pushing the knob inwards on the CPFlight transponder with the PMDG 737 to activate the TCAS test, didn't work either (also on the PMDG 744 pushing the knob inwards does not activate the TCAS test).

On another note. I already mentioned that the IN/HPA setting on the EFISPro and the PMDG EFIS do not correspond (i.e. when IN is set on the CPFlight EFISPro, then HPA is set on the PMDG EFIS). I can tell you that this ONLY happens with the PMDG 737. On the PMDG 744 the settings correspond (CPFlight EFISPro and on the PMDG EFIS). I will contact CPFlight about this, and let you know.

Jon

Hi Jon-

I've been working on these issues as reported. Some observations:

1) The TCAS test knob works well on our end- can you check the debug box to see if, when pressing the TCAS knob, you see a line in the debug window saying "From CPFlight: Z00037" ? If you don't, then it's a hardware issue (i.e. no event is being sent from the hardware to the driver). If you do (but still see no tests running in the software), then it's our problem and we'll have to look deeper into it.

2) I have sent CPFlight an email requesting an EFISPro module, as I only have the older EFIS one available in our labs for testing. As soon as I receive it, I'll take a look at the IN/HPa problem.

We're also making the following updates to the driver interface, which will be released soon:

3) We've been working on the backlighting issue and we believe we have a good solution which allows the user to override the PMDG backlighting settings, as requested.

4) The COM port is now saved to the .ini file, regardless of whether the Reconnect checkbox is checked.

5) Bank limit angle knob now works for the 747 (goes from AUTO to 20 degrees, as there are differences between 737 and 747).

6) Still discussing with CPFlight how to implement the N1 -> TO/GA functionality (which is unrealistic, btw); there will be further updates for this, possibly with the help of CPFlight (and a future firmware update).

Jon-

I had sent you private email - did you get it?

Yes, I got your message, thanks for the invitation. I have just dowloaded the software, and I will report back tomorrow (10-11-08). Would you like me to post my findings in this forum, or through a private message?

Jon

Jon-

I'll send you private email.

I have sent you a detailed e-mail with my findings.

Jon

Hello Lefteris!

Whoa! Many great news! Can you give us information about the release date? (I hope so will this year.) ?

6) Still discussing with CPFlight how to implement the N1 -> TO/GA functionality (which is unrealistic, btw); there will be further updates for this, possibly with the help of CPFlight (and a future firmware update).

Its true, but this function is very usefull who didnt have PM and full size cockpit with control stand...

I wish very sucessfull developing.

Steve

ps: sorry for my english

Lefteris,

The link you provided to CPFlight's website for downloading the most recent firmware for the MCPPro does not contain version 1.04 that is required. The "old" firmware is still listed on their website (1.03). Could you please contact CPFlight and ask them to update their website with the current firmware for the MCPPro? That way other users can benefit as well from the new update.

Jon