1.0.9 - Master caution "Flaps not in T.O. config" after landing

[C. Schaffhausen]

Hello team, during my past few flights I have consistently got the Flaps not in takeoff config warning after I've landed. Throttle is at idle/in reverse in those scenario. May I know how the warning is triggered in your simulation? Video attached as reference, thank you! 

 

Landing at 10:46

https://youtu.be/sAayNOi76sA

[C. Schaffhausen]

I have narrowed down the issue to the way I map my thrust reverser through FSUIPC. I use the Honeycomb Bravo, I aim to have independent thrust reverse control for 4 engines, including a setting to reach idle reverse. I map it as below.

1. A lever to pull (works as a button), which engages idle reverse by multiple presses at once on Throttle X Decrease to set the reverse to just at idle reverse. (X being the Engine No.)
2. If I pull the thrust lever all the way to be bottom (works as a button), it sends repeats of Throttle X Decrease to engage full reverse.
3. When I release the throttle back to position set in step 1, it release the button in step 2, Throttle X Idle and the throttle return to idle reverse.
4. Lever in step one released, which sends a Throttle X Set 0 (Lever position 0 - Idle) command to throttle.

I've tested multiple times and step 1 seems to be the main cause of the takeoff config warning, sometimes even when idle reverse is still engaged and I was still decelerating on the runway at over 70kts. 

Can the team look at the issue, and see whether it is possible to stop the warning from being triggered; Or to provide a way to engage idle reverse of each engine independently? Much appreciated.

Edited yesterday at 05:12 AM by C. Schaffhausen

[IniJamir]

Hi,

I will push this along to the team, I do not have a Honeycomb Bravo it may take a little bit longer to get back around to responding here but it has been noted.

[C. Schaffhausen]

Thank you, I tried using the command "F1" instead of the above setup, still have the Takeoff config warning. I saw a similar thread on discord as well. I used the calibrated output for all four throttle axis, and FSUIPC send the throttle position to the sim with the range of 0 to 16380 instead of -16380 to 16380. I can tell because my idle position starts in the mid-point of the throttle calibration page, I'm not sure but the aircraft might have thought I'm taking off because of that. Thank you for following up.

Edited 6 hours ago by C. Schaffhausen