Throttle doing its own thing

[Andy675 41]

After installing the latest FBW A320 (Dev version) I have had an unusual occurrence with the throttle. On short final into EGLL and in clear view of the runway I was advised by ATC to 'go around'. With nothing visible on the runway I continued my descent when suddenly the engines powered up. I placed the throttles to idle but the engines remained powered up.  Hoping this was an isolated incidence I tried a flight again to EGLL, and the same thing again occurred after being advised to 'Go Around'. I had the AP and Auto throttle disengaged. All my assist options are 'off' apart from 'assist take-off'. Is this a bug? Just me? Is it normal?

For reference I am using DX11, the first occasion was with windows 10 the second with windows 11 ( I took a gamble and upgraded!)

 

Thanks

 

Edited November 24, 2021 by Andy675

[wim123 758]

you need to find some fbw landing manual..i see  a few on yt.

[Donka 642]

Also check your options under the assistance menu. Make sure these have not been reset to easy since the last update as it as for me. There is a setting for AI assistance on landing etc. which could be at play. 

[Andy675 41]

I  have just had a perfect landing at EDKK , I did not receive a 'go around' command. Early days but it does suggest a problem with the 'Go Around' command or possibly with Heathrow.

[109Sqn 1,553]

I've no idea how familiar you are with Airbus systems (and I'm no expert!), so ignore me if you already know this. You say you had Auto-throttle (AKA Auto-thrust) disarmed, but are you certain it didn't switch back on as your throttle powered itself back up? I'm not sure on the exact parameters, but if the plane's systems believe you are in error (too little speed), AT will take over to get you out of potential trouble.

Someone with  more experience will put that better (or tell me I've got it all wrong!😁 ).

 

Edit: I couldn't remember the term - it's Alpha Floor or A.Floor.

Edited November 24, 2021 by 109Sqn

[Andy675 41]

21 minutes ago, 109Sqn said:

You say you had Auto-throttle (AKA Auto-thrust) disarmed, but are you certain it didn't switch back on as your throttle powered itself back up? I'm not sure on the exact parameters, but if the plane's systems believe you are in error (too little speed), AT will take over to get you out of potential trouble.

Thanks for your reply. On the first occasion I had the Auto-Thrust engaged, on the second I switched it off to see what happened (it did not re-engage). The air speed was well within the permitted parameters. A few more flights into Heathrow I think are required.

[gdjak 176]

If you want to skip the testing part I'd recommend you come to the fbw discord and post the .fdr of your flights with ap disconnection issues. There's usually someone around who can parse it and figure out what happened.

Quote

FlyByWire Support | Flight Data Recorder

Please send us your FDR (flight data recorder) files for further investigation. In your work folder, you will find the FDR files for the flight you did. You should recognize the correct one by the filename, which is the date of the flight. For a long flight, it might have been split into several files. Compress/Zip the files and upload them to a sharing site (e.g. Swisstransfer.com) as these files are likely to be too large for Discord. Detailed instructions on how to locate your FDR files can be found here. This file will allow us to see more details about your flight to understand what happened.

[Maxis 1,855]

Turn off "assist take off" and retry the scenario... If you are advised to go around the sim may interpet it the same as cleared to take off and your sim may activate the assist. Especially likely since as you said the ap and at were off. They wont turn on by themselves..

Edited November 24, 2021 by Maxis