Jump to content
Sign in to follow this  
Andy675

Throttle doing its own thing

Recommended Posts

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 by Andy675

Share this post


Link to post
Share on other sites

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. 


Ryzen 5900X, RTX 3080, 32GB, Win 10. MSFS2020 & XP11. Fulcrum, VKB & Virpil controllers.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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 by 109Sqn

OS:     Win11 Home; Mobo: Asus TUF Gaming Z690-Plus WiFi D4; CPU: Intel i5-12400 (Alder Lake) 4.4 GHz
RAM: Corsair Vengeance DDR4 64Gb (4x16GB) 3600 MHz; GPU:  MSI Radeon RX 5700XT [8GB] 
SSD:  Corsair Force MP510 (for OS);  2x 1TB & 1x 2TB Sabrent Rocket Nvme PCIe 4.0 (one for sim, two for addons)
HDD:  Seagate 3TB (Data); Seagate 1TB (Programs), ASUS TUF Gaming VG32VQ1B Curved 31.5" monitor, 1440p, 38Mbs ethernet 

Fulcrum One Yoke, Honeycomb Bravo throttle, Thrustmaster Airbus TCA sidestick & throttle, Logitech Pro pedals, Xbox wireless gamepad (1st gen)

Share this post


Link to post
Share on other sites
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.

  • Like 1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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 by Maxis

AMD Ryzen 5900X / Asus Strix B550 F Gaming Wifi / Powercolor AMD 6800XT Red Devil / 32GB Gskill Trident Neo DDR4 3600 / 2x ADATA XPG 8200pro NVME / Arctic Liquid Freezer II 280 / EVGA Supernova 750 GT PSU / Lian Li Lancool II Mesh Performance /

Viotek 3440x1440p Freesync / Schiit Bifrost DAC+ Schiit Asgard AMP /  Sennheiser HD 558 / Thrustmaster T.16000M + TFRP Rudders

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...