Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Autothrottle disconnects during takeoff (Tutorial 1)

Featured Replies

Hello,

 

I'm just starting to learn the NGX but I have ran into a problem. After setting up the plane as per the instructions in Tutorial #1, I slowly moved the throttles to 40% N1, then clicked TOGA. In about 3 seconds, the autothrottle disconnects. I've done the tutorial 1 twice and A/T disconnected during takeoff on both occasions.

 

I have a Saitek Throttle Quandrant and I calibrate it using FSUIPC.

 

Am I doing something wrong? What's seems to be the cause of this problem?

 

Many thanks in advance!

 

Nick

Fulcrum One Yoke / FSProjects Airbus Side Stick, Honeycomb Bravo, Slaw Device RX Viper V2

Intel Core Ultra 9 285K, PNY RTX 5080, 48GB RAM

Unfortunately this is common, you have to setup as separate way, there are already many thread on it.

Throttle must setup in FSX.

 

 

Unfortunately this is common, you have to setup as separate way, there are already many thread on it.

Throttle must setup in FSX.

Interesting seeing how I have mine set up just fine through FSUIPC...

Thanks!
Nick Crate
Chief Executive Officer
FedEx Virtual Air Cargo

  • Author

Just tried Tutorial #1 again with just 1 axis set for all throttles. A/T doesn't disconnect but doesn't advance the throttle to takeoff speed after clicking TOGA. It stayed at 49% N1 and wouldn't go up. The tutorial says to establish 40% N1 which I did (and stayed at 40% for about 5 secs), but for some weird reason TOGA doesn't kick in completely.

Fulcrum One Yoke / FSProjects Airbus Side Stick, Honeycomb Bravo, Slaw Device RX Viper V2

Intel Core Ultra 9 285K, PNY RTX 5080, 48GB RAM

what FMA says?

[color=#a9a9a9][size=1][size=4][img]http://forum.avsim.net/public/style_images/flags/rs.png[/img][/size] Lj. Prodanovic[/size][/color]

Just tried Tutorial #1 again with just 1 axis set for all throttles. A/T doesn't disconnect but doesn't advance the throttle to takeoff speed after clicking TOGA. It stayed at 49% N1 and wouldn't go up. The tutorial says to establish 40% N1 which I did (and stayed at 40% for about 5 secs), but for some weird reason TOGA doesn't kick in completely.

Maybe attach a picture and we can see if it's a config error. Remember that you do not arm spoilers, and you must have both FD's on.

Thanks!
Nick Crate
Chief Executive Officer
FedEx Virtual Air Cargo

You need to make sure your trim is in the correct position on your yoke or stick move it around when trying to hit AP switch this is the problem well not actually a problem just something you need to be aware of try it you'll like it, over & out.

Rich Sennett

               

  • Author

Thanks for the replies.

 

I followed the tutorial to the letter and both FD were on. Trim was set correctly and I double-checked it as well. Spoilers were not armed.

 

I'll try and do it again and take pictures if something weird happens.

Fulcrum One Yoke / FSProjects Airbus Side Stick, Honeycomb Bravo, Slaw Device RX Viper V2

Intel Core Ultra 9 285K, PNY RTX 5080, 48GB RAM

  • Author

Tried the tutorial again and I was able to complete it. One strange thing was that on final approach with GS locked I didn't see "LAND 3" in PFD. Instead, SINGLE CH popped up. But the autoland went without a hitch. I just need to be more careful following the tutorial to avoid any mistakes.

 

I found a imperfect way to bypass the FSUIPC autothrottle problem. I set up the axis in FSX and calibrate them in FSUIPC. Then on takeoff, I use the keyboard (F3) to advance the throttle to 40% N1. The A/T didn't complain. However, I'm sure there will be instances when the above won't work.

 

Thanks again for all your help!

 

Regards,

 

Nick

Fulcrum One Yoke / FSProjects Airbus Side Stick, Honeycomb Bravo, Slaw Device RX Viper V2

Intel Core Ultra 9 285K, PNY RTX 5080, 48GB RAM

Nick when you find what works be it software or hardware and combination of both stick with it sounds like you are getting the hang of it well done.

Rich Sennett

               

Tried the tutorial again and I was able to complete it. One strange thing was that on final approach with GS locked I didn't see "LAND 3" in PFD. Instead, SINGLE CH popped up. But the autoland went without a hitch. I just need to be more careful following the tutorial to avoid any mistakes.

It would be because you aren't in a dual channel mode where both autopilots are active for the approach (Or you you haven't gotten to about 1500ft agl). You must the nav frequency set in both nav radios, as well as the course in both course selectors. Then you will be able to perform a dual channel approach and autoland.

 

Now, if your aircraft is fail-passive, then you can conduct an autoland and rollout where it will be able to maintain the centerline until disconnect. This is an expensive option in real-world, so very few carriers have it installed.

Thanks!
Nick Crate
Chief Executive Officer
FedEx Virtual Air Cargo

Fabrizio

 

 

that was a great post. I remember reading it some time ago and passed it by, thinking my throttles were ok. After re reading it, I deleted the joystick calibrations in FSUIPC and set my thrust lever axes as throttle 1 set and throttle 2 set, sending to FS for calibrations (as per Jason's post). Auto throttle seems to be rock steady now, no more disconnects. I can also take advantage of the blue arc as well as move my thrust levers without having the AT disconnect. Glad this topic was revisited. Thanks.

 

 

Ed

Ed Burton

www.737ngxca.com

My throttle issues disappeared when I reverted to setting them up entirely within FSUIPC.

 

Bruce

Bruce Bartlett

 

Frodo: "I wish none of this had happened." Gandalf: "So do all who live to see such times, but that is not for them to decide. All we have to decide is what to do with the time that is given to us."

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.