AP logic inconsistent
-
If I push AP, and then HDG, the FD does not come on.
Either one of these buttons should also turn on the FD.
If I then push AP again, the autopilot turns off and the FD comes on..
This is not right.. -
And here is a temporary fix, courtesy of Al Klayton:
<!-- Al's FD Fix -->
<UseTemplate Name="ASOBO_GT_Update">
<FREQUENCY>1</FREQUENCY>
<UPDATE_CODE>
(A:AUTOPILOT MASTER, bool) 1 ==
(A:AUTOPILOT FLIGHT DIRECTOR ACTIVE, bool) 0 == and
if{ (>K:TOGGLE_FLIGHT_DIRECTOR) }
</UPDATE_CODE>
</UseTemplate>The fix goes in the AnalogTBM.xml file (in the model folder)
-
Thanks for pointing this out. Upon reviewing the KMC-321 manual, pressing any of the mode buttons will indeed engage the flight director. I will make the fix for the next update. In the meantime, be advised that the above code will make it impossible to disengage the flight director while the autopilot is on.
-
Thanks for pointing this out. Upon reviewing the KMC-321 manual, pressing any of the mode buttons will indeed engage the flight director. I will make the fix for the next update. In the meantime, be advised that the above code will make it impossible to disengage the flight director while the autopilot is on.
@Black-Square said in AP logic inconsistent:
In the meantime, be advised that the above code will make it impossible to disengage the flight director while the autopilot is on.
The flight director either "tells" the autopilot what to do (i.e., drives the autopilot servos) if the autopilot is on, or if the autopilot is off, "tells" the pilot what to do via the flight director command bars. You would not want the autopilot on (servos active) with the flight director off. I have not come across an autopilot that lets the flight director be turned off when the autopilot is on.
Al
-
I just wanted to let you guys know that I made these changes today, and they will be in the next update. Thank you for the input!
-
I just wanted to let you guys know that I made these changes today, and they will be in the next update. Thank you for the input!
@Black-Square said in AP logic inconsistent:
I just wanted to let you guys know that I made these changes today, and they will be in the next update. Thank you for the input!
Great, thank you!
Do you have an idea about approximately when the next update might come out?
Thx,
Al -
I just wanted to let you guys know that I made these changes today, and they will be in the next update. Thank you for the input!
@Black-Square One more.. @ark just alerted me to the fact that the AP button when disconnecting the autopilot, also disconnects PIT mode. The red yoke button does not do that. I suspect that the following is the culprit:
(A:AUTOPILOT THROTTLE MAX THRUST, bool) if{ (>K:AUTO_THROTTLE_TO_GA) }
If I remove that line, the problem goes away..
Remaining question: Why does the AP button turn off YD, but the red yoke button does not? Is that intentional?
