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.

Saitek throttle quadrant lever axis problem

Featured Replies

Hello,

 

I've been using 2 Saitek throttle quadrants for a few years now. I have 4 engine throttles, prop pitch, and mixture set up on the 6 levers. I set the axis in FSX and calibrate them in FSUIPC (registered version). Everything was working fine until a week ago, when one of the levers somehow became the throttle for all engines. If this lever is assigned to the mixture for example, it would also advance the throttles. I've tried reassigning all axis calibrating them, disconnecting and reconnecting the throttle quadrant, but nothing has worked.

 

Do you all know what's causing this problem?

 

Thanks in advance!

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

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

Did you delete cfg file and rebuild? If not you may want to try this and see what happens.....make a copy first as always. Also insure you are not using both FS and FSUIPC assigments, one or the other. Using both can create problems.

You might also want to check the Flight Simulator axis assignments. I have an issue everyonce in awhile where FS decides to auto assign an axis to somethin like the throttle.

Brian Thibodeaux | B747-400/8, C-130 Flight Engineer, CFI, Type Rated: BE190, DC-9 (MD-80), B747-400

beta.gif   

My Liveries

You might also want to check the Flight Simulator axis assignments. I have an issue everyonce in awhile where FS decides to auto assign an axis to somethin like the throttle.

 

This is true and is documented from Pete in FSUIPC manual

  • Author

Thanks for the replies. I just checked the control settings in FSX. Everything looks fine. But when flying the axis in question still controls all engines.

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

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

Believe me, I have found that a total rebuild usually solves most problems, I hope you will consider the above from both of us and see if it helps.If it does not, there could be a more serious problem like the throttle goin T__up, like mine have on 2 occasions, same set up as yours, which I have since changed.

P.S.

"I just checked the control settings in FSX. Everything looks fine"...what does this mean?

  • Author

Believe me, I have found that a total rebuild usually solves most problems, I hope you will consider the above from both of us and see if it helps.If it does not, there could be a more serious problem like the throttle goin T__up, like mine have on 2 occasions, same set up as yours, which I have since changed.

 

Yeah I hope the throttle quadrant isn't going bad. As of now it's fine and the only thing I can't have is mixture axis. I'll try the suggestions above and see what happens. Maybe I'll also try assigning axis within FSUIPC. Thanks for all the replies!

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

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

Stay in touch,

  • Author

Ok I fixed the problem. I erased all the axis assignments within FSX and did them in FSUIPC and the problem is gone. I also managed to set reverse thrust to a button that a throttle lever triggers and it works pretty well.

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

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

Ok I fixed the problem. I erased all the axis assignments within FSX and did them in FSUIPC and the problem is gone. I also managed to set reverse thrust to a button that a throttle lever triggers and it works pretty well.

 

 

Hi mate

I use the area below the small detent on the throttle levers as reverse thrust .if you pull the levers down until you reach that, the area below is technically a button .so inside fsuipc you can assign that area to be throttle decrease.also tick repeat.that will now activate reverse thrust when you pull the throttles below the detent.you would have to do this 4 times .once for every lever.

hope i've explaned this so you get my drift.

steve-0 :smile:

REX SKYFORCE 3D

 

steve howlett

  • Author

Thanks for the tip and that's what I did as well. Worked like a charm. I'm really glad that I paid for a FSUIPC registration.

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

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

After a year of using this unit, all the cleaning, spraying, and hoping failed to stop the erratic performance of each lever. I stopped using it when one lever would affect another lever. As you describe it, moving one lever would affect the signals of the other lever.

 

It sounds as if your ( very cheap) Saitek throttles have begun to fail.

 

In some cases, FSUIPC works miracles. In mine, however, it didn't make much of a difference.

 

I finally took apart the throttle, replaced the pots with high quality ones, and building a homemade throttle quadrant, using the levers and the circuit of the original unit.

 

I wont buy another Saitek throttle unit until they change the lousy pots.

 

From what I've read, these units start failing after 2 years.

 

The yoke has been much better.

tc

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.