Autoland "RETARD" Bug

[nrcrate 40]

Hey all, This may or may not be a bug, but it sure is annoying to me and I can't see why it would do this. I have my aircraft set up for a full autoland with rollout... When I get the "RETARD" annunciation just before touchdown and the AT brings the throttle back, I've noticed that it brings it back to flight idle, and not full idle. For example, I just landed at KORF and before landing when "RETARD" illuminated, it went back to flight idle. This does not seem to happen all the time though... I have a key on my flight stick mapped to hold F2 when I press it in and press F1 after I release it. It seemed to take an extremely long time to go from AT flight idle to full idle and then reverse thrust... I should not have to pull it back manually from flight idle to full idle, should I? In the end, I did not get reverse until 65 knots, which by then there is no point. This does not seem like normal behavior to me; but if it is, please enlighten me! P.S.- She autolands beautifully! One of the best I've seen!

Edited August 12, 2011 by NickC

[RickButler 0]

Mine does this to, I read in another post it is because of having your throttle axis mapped through FSUIPC, and not through by the native software for your unit. Although mine is not assigned via FSUIPC it still does it.

[nrcrate 40]

I'll give it a shot- I have mine through FSUIPC because my flight stick does not have the best axis in the fact that it jumps around alot, but let me try without FSUIPC.

[JC75 22]

Yes I seem to have a similar situation often also - even manual landing with A/T initially on. I fly the approach manualy with A/T engaged - about 50ft click the soft a/t disengage button - pull my throrttles to idle (also tried mapping button on throttles so if all way back it presses F1) touchdown - and then try to engage reverse - they dont - throttles to idle again and eventually can get reverse to kick in but like the OP almost pointless at that point or if heavy too late at that point! I did some testing on the ground pushing my throttles forward - spooling engines up then back to idle on the throttle while engine rpm still high and then select reverse and it works fine with how my joystick/buttons are set up the reverse will engage. Just seems to be a problem when touching down - seems like I cant manually reduce thrust below flight idle even though the a/t is now disengaged. Anyone else find reverse dificult to engage at touchdown?ive tried both with FSUPIC enabled and with Direct FSX mapping(with all enteries in FSUPIC deleted) and pretty much same issue - in fact more likely to get reverse activated when they through FSUPIC than when to FSX direct

[nrcrate 40]

...ive tried both with FSUPIC enabled and with Direct FSX mapping(with all enteries in FSUPIC deleted) and pretty much same issue - in fact more likely to get reverse activated when they through FSUPIC than when to FSX direct

I experience the exact same thing!

[nrcrate 40]

Anybody else experiencing this or have a suggestion we can try?

[nrcrate 40]

Bump- I just experienced it again. This is not a HUGE deal, but it's something that needs looked into.

[kjjj11223344 48]

I asked this a while ago. It is normal behavior; it is known as approach idle.

[nrcrate 40]

I asked this a while ago. It is normal behavior; it is known as approach idle.

So it doesn't allow full idle on touchdown? This is what sees to be hindering us from going into reverse quickly. Edited August 13, 2011 by NickC

[kjjj11223344 48]

So it doesn't allow full idle on touchdown? This is what sees to be hindering us from going into reverse quickly.

Correct. As for the not getting into reverse quickly, I use f2 and it goes into reverse instantaneously.

[nrcrate 40]

Correct. As for the not getting into reverse quickly, I use f2 and it goes into reverse instantaneously.

Hmmm, this is extremely odd. Then how is there a difference with a button programmed to hold F2 while held and F1 when released? Edited August 13, 2011 by NickC

[kjjj11223344 48]

Hmmm, this is extremely odd. Then how is there a difference with a button programmed to hold F2 while held and F1 when released?

I can't quite comprehend what you mean. Have you tried pressing the button multiple times? I probably press f2 more than once when activating reversers without even noticing it probably, but they do come on instantly.

[nrcrate 40]

I can't quite comprehend what you mean. Have you tried pressing the button multiple times? I probably press f2 more than once when activating reversers without even noticing it probably, but they do come on instantly.

Ok, I have a button on my flight stick that is supposed to hold​ F2 when I hold the button in, and then press F1 when I release the button. I think maybe the NGX is not retarding at the right time. Now that I think of it, it's not at idle when I hit the ground. Maybe it's not that it's at flight idle, but rather that it's not going into idle at the right time to be in idle after the nose lowers... I'm going to go do some circuits and see what I find out.

[kjjj11223344 48]

Ok, I have a button on my flight stick that is supposed to hold​ F2 when I hold the button in, and then press F1 when I release the button. I think maybe the NGX is not retarding at the right time. Now that I think of it, it's not at idle when I hit the ground. Maybe it's not that it's at flight idle, but rather that it's not going into idle at the right time to be in idle after the nose lowers... I'm going to go do some circuits and see what I find out.

I'm not flying now but I'm pretty sure ground idle activates as soon as you touchdown (I've accidentally pressed f1 sometimes and get ground idle thrust).

[3-2-1-Now 126]

I've found the EECs increases thrust (e.g. on selection of flaps or gear) but it will not reduce it again if the condition that demanded the increase is removed again (e.g. gear up). I'm not sure if this is by design though - I have not scrutinized the FCOM yet. It may even require the maintenance manual to resolve. Best regards,Robin.