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.
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.
Wierd issue with Auto Throttle in iFly 747
Can anyone help me to troubleshoot the strangest issue:
Everything is working as it should on the Goflight MCP Pro and EFIS devices. All switches are responsive and displays are updating smootly with just one exception:
When AutoThrottle is flipped up, it initally responds as it should do with the up switch correctly reflected on the iFly panel.
When AutoThrottle is flipped down, it does not respond at all.
When AutoThrottle is flipped up again, it responds with a downward switch on the iFly panel.
So essentially, the Up switch action is just toggling from what ever state it is already in.
Down switch does nothing - well ALMOST nothing:
When the switch is flipped down, there is no visible response but there is a "click click click" audio response.
I don't know what action this represents but it happens every time.
I thought it might be a actual hardware problem with the physical switch but PMDG 747 works exactly as it should and the GoFlight testing tool also shows nothing wrong and reflects Up-Down actions as they should.
I even disabled FSUIPC in case that was running some other script but it made no differnce.
Who can help?
Is something running somewhere that overrides the GFIT?
Everything is working as it should on the Goflight MCP Pro and EFIS devices. All switches are responsive and displays are updating smootly with just one exception:
When AutoThrottle is flipped up, it initally responds as it should do with the up switch correctly reflected on the iFly panel.
When AutoThrottle is flipped down, it does not respond at all.
When AutoThrottle is flipped up again, it responds with a downward switch on the iFly panel.
So essentially, the Up switch action is just toggling from what ever state it is already in.
Down switch does nothing - well ALMOST nothing:
When the switch is flipped down, there is no visible response but there is a "click click click" audio response.
I don't know what action this represents but it happens every time.
I thought it might be a actual hardware problem with the physical switch but PMDG 747 works exactly as it should and the GoFlight testing tool also shows nothing wrong and reflects Up-Down actions as they should.
I even disabled FSUIPC in case that was running some other script but it made no differnce.
Who can help?
Is something running somewhere that overrides the GFIT?
Comments
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_TOGA
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_DISENGAGE
Try assigning the disengage event to a some other hardware and see if the same behaviour occurs.
Best wishes
Steve
I did as you suggested and assigned AT disengage to a P8 button. I also assigned AT_ARM_ON and ARM_OFF to P8 buttons,
These worked as expected but did not change the behaviour of the MCP Pro. It still toggles AT on the up switch and triggers TOGA on the down.
The MCP PRO uses these on the AT ARM switch:
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_DISENGAGE
So I think the right commands are assigned.
Best wishes
Pollypot Software
But the problem is still there.
I'm not sure if something got corrupted but is there any config files I can edit or replace?
Thanks.
I noticed that there are 4 Autothrottle events:
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM_OFF
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM_ON
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_DISENGAGE
To experiment, I assigned all four to P8 buttons and found the following associated actions:
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM
Toggles A/T ARM from it's previous state.
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM_OFF
Switches A/T ARM to OFF. Does nothing if already off.
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM_ON
Switches A/T ARM to ARM. Does nothing if already on.
KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_DISENGAGE
This pushes the "Autothrottle Disconnect Switch"(es). These are a pair of switches on the throttle quadrant which (obviously!) disconnect autothrottle but does not affect the ARM/OFF status on the MCP. This is an entirely different function from the A/T ARM switch on the MCP
So, I think there might be an incorrect assignment after all.
The correct assignments should be:
A/T ARM Up: KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM_ON
A/T ARM Down: KEY_COMMAND_IFLY744_AUTOMATICFLIGHT_AUTOTHROTTLE_ARM_OFF
What do you think?
Thx
Steve