Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

Slow LED response GF-MCP Advanced Autopilot

maclgbmaclgb
in General
I am running the GF-MCP Advanced Autopilot on my PMDG 737 NGX, everything working ok except that the LEDs are very slow to respond when turning the knobs on the MCP module. The LEDs in the SIMs Virtual Cockpit updates immediately but the LEDs on the GF-MCP module take a few seconds to update. The same thing happens whether I dial the setting from the SIM or the module. It's as if the command is going TO the SIM fast enough but the signal coming back from the SIM is slow. Anyone experienced this before?

Answers

  • admin_ppsadmin_pps
    edited April 2020 Answer ✓
    There are a few settings that can impact performance on the Settings tab. Try setting Write Delay and Cmd Delay to zero or lower values. You can also try lowering Device Update Time (this requires GIT to be restarted to be effective).

    Also check the Log tab for any errors that are firing when you turn the rotaries on the MCP.

    Also, does the MCP update slowly if the MCP in the Virtual Cockpit is used to change values?

    Best wishes
    Steve
  • maclgbmaclgb
    Hi Admin_pps

    Thank you very much for your reply. I will try changing the setting as you suggest.

    In answer to your question, the MCP does also update slowly if I adjust in the VC.

    I have noted a marked improvement since plugging the USB cable directly into the PC instead of via a powered HUB, but I am now experiencing lock ups in the display after say 10 minutes into a flight - all LEDs in displays and buttons freeze, but the dials and buttons still update the Virtual Cockpit very quickly. I have to completely restart everything to get it working again, even pressing restart in the GIT doesn't have any effect.

    I will start observing the log to see whats going on as well.

    Many thanks for the tips, I will report back soon.
  • maclgbmaclgb
    edited May 2020
    Hi Steve,

    Problem solved! Having followed your suggestion I set Write delay and CMD delay to zero on Both the MCP tab and the Settings tab and I have had no lock ups at all. Displays still responding nicely as well. When I reloaded the GIT later I noticed that it did not save the zero values in the settings tab but did save them in the MCP tab, but I still did not experience any problems, therefore it seems the only critical adjustment needed was setting the MCP values to zero.

    Thank you very much for your prompt assistance, you have saved me a lot of frustration and sleepless nights :-)

    Kind regards,
    Mark
  • maclgbmaclgb
    A further update: To make my system more robust I took the precaution to disable power management on all of my USB ports, plus having noticed it was plugged into a USB 3.0 port I plugged it into a USB 2.0 port, however then none of the LEDs or lights would work on the MCP panel (it would work okay functionally as the Virtual cockpit values were updating fine). I then plugged it back into anoth USB 3.0 port and it started working fine again. This has puzzled me because I hear throughout this forum that the GF MCP and other devices will not work through USB 3.0 yet on my system (DELL Precision T1700) it actually works better in a USB 3.0) Anyone have any idea why this is?
  • admin_ppsadmin_pps
    Answer ✓
    You need to run Windows8Fixer in the GoFlight directory. The GoFlight readme file has all the details.

    It's GoFlight that state no USB3.

    Best wishes
    Steve
  • maclgbmaclgb
    admin_pps said:

    You need to run Windows8Fixer in the GoFlight directory. The GoFlight readme file has all the details.

    It's GoFlight that state no USB3.

    Best wishes
    Steve

    Many thanks Steve, that did the trick.
Sign In or Register to comment.

© Vanilla Keystone Theme 2025