Set up a USB throttle quadrant in MSFS 2024/2020, GeoFS and other sims; fix detection, reversed axes, detents and A220 calibration.
To set up a USB throttle quadrant, first confirm the operating system detects every lever, then map the correct analogue axes inside the simulator and remove duplicate bindings. Set direction and range in the sim, but calibrate thrust detents and reverse zones in the aircraft’s own utility. This applies to MSFS 2024/2020 and other simulators.
This is general simulator guidance for Microsoft Flight Simulator 2024 and 2020, X-Plane, Prepar3D, FSX, DCS and browser-based GeoFS. The menu names differ, but the four separate jobs remain the same: hardware detection, simulator axis assignment, conflict removal and aircraft-level calibration.
How do I set up a USB throttle quadrant step by step?
The reliable method is to test the hardware first and build a clean controller profile containing only the assignments you need.
- Connect the quadrant before opening the simulator. Use a direct USB port for the initial setup. Avoid an unpowered hub, and do not change ports after creating profiles unless necessary; Windows and some simulators may treat the new connection as another device.
- Verify every raw input. In Windows, press the Windows key, run
joy.cpl, select the quadrant and open its properties. Move one lever at a time and check that the corresponding indicator moves smoothly through its full range. Test all buttons, rocker switches and below-idle detent switches. If the device is absent here, simulator settings cannot fix it. - Install only required device software. Many quadrants are standard USB game controllers and need no additional driver. Install manufacturer firmware or configuration software only when the model requires it. Confirm that the unit is genuinely standalone USB: some quadrants supplied with a yoke must connect through that matching yoke.
- Create a clean simulator profile. Use an empty profile where possible, or duplicate a working default and remove unwanted assignments. Separate profiles are useful for single-engine aircraft, multi-engine aircraft and airliners with thrust detents.
- Assign analogue axes. Bind each lever to a command containing
Axis, such as a combined throttle axis or an individual engine throttle axis. Do not use digital commands such as throttle increase or decrease for a lever. Move only the intended lever while the simulator is detecting an input. - Remove duplicate bindings. Search the active profiles for every connected yoke, joystick, gamepad, throttle and virtual controller. Delete any unwanted combined throttle, individual throttle, mixture, propeller or reverse-thrust assignments. A mistake we see constantly is leaving the combined throttle active alongside Engine 1 and Engine 2.
- Set direction and response. Enable axis inversion if advancing the physical lever reduces power. Begin with a linear response and the full usable range. Add only enough dead zone or filtering to stop genuine input noise; large corrections can prevent idle or full power from being reached.
- Test the basic range before adding detents. Move each lever slowly while watching the cockpit controls and engine indications. Confirm idle, intermediate power and maximum power first. Configure reverse thrust and aircraft-specific detents only after normal forward travel works correctly.
Microsoft Flight Simulator users can follow our MSFS controller-profile, axis and sensitivity guidance for the control-screen differences between simulator generations. Owners of common hardware may also need the Logitech/Saitek detent and calibration procedure or our instructions for mapping the individual CH quadrant levers and switches.
Which throttle axes should I bind?
Choose a combined axis when one physical lever should operate every engine, and engine-specific axes when each engine has its own lever.
| Physical arrangement | Recommended assignment | Assignment to remove |
|---|---|---|
| One throttle lever | Combined throttle axis | Engine-specific axes on other controllers |
| Two throttle levers | Engine 1 and Engine 2 throttle axes | Combined throttle axis |
| Three levers for a piston aircraft | Combined throttle, propeller and mixture axes | Unneeded engine-specific axes |
| Four throttle levers | Engine 1 through Engine 4 throttle axes | Combined axis and incorrect engine order |
| Spare analogue lever | Flaps, speedbrake or condition lever where supported | A control accepting only fixed button positions |
Test multi-engine assignments by moving one lever at a time. If both cockpit levers respond, a combined axis or duplicate binding is still active somewhere.
Where should a USB throttle be calibrated?
Use the operating system to diagnose the raw hardware, the simulator to set axis behaviour and the aircraft’s utility to define specialised thrust detents.
- Operating system: Confirm that each axis appears, travels smoothly and reaches both ends. Do not repeatedly run Windows calibration when the raw indicator is already correct. Use hardware calibration only when the manufacturer calls for it or the raw range is genuinely incomplete.
- Simulator: Set inversion, sensitivity, response, saturation or extremity controls. Start with a linear curve and reset large dead zones before investigating missing range.
- Aircraft: Use the electronic flight bag, tablet or configuration panel supplied with a detailed aircraft. This calibration layer normally records idle, forward-thrust detents and reverse zones.
Some simulators provide both a forward-only throttle command and a full-range command covering forward and reverse. Choose the forward-only axis when reverse is triggered by a button or switch below idle. Choose the full-range axis only when the hardware supplies genuine analogue travel through idle into reverse.
How do I set up a USB throttle quadrant in GeoFS?
GeoFS reads controller input through the browser, so the device must be visible to the operating system and available to the active browser tab before it can be assigned.
- Connect and verify the controller. Attach the quadrant before opening the browser. On Windows, confirm its levers in
joy.cpl; if Windows cannot see it, GeoFS cannot see it either. - Open GeoFS and activate the page. Click inside the flight view, then move a lever or press a controller button. Some browsers do not expose a game controller to a page until the user has interacted with both the page and device.
- Open the control assignments. Go to GeoFS settings and open the controls, joystick or controller assignment panel. Labels may change with interface updates, but use the panel that displays detected controller inputs.
- Assign the throttle axis. Select the throttle control and move only the desired lever through a clear portion of its travel. Use the analogue throttle assignment rather than keyboard-style increase and decrease commands.
- Check direction and range. Advance the physical lever and confirm that indicated power rises. Use the available reverse or invert option if the direction is wrong, then check that the lever reaches idle and full power.
- Remove other throttle inputs. Clear unwanted assignments from gamepads, joysticks and virtual controllers. Test with those devices disconnected if the throttle jumps or keeps returning to another position.
- Save and verify the mapping. Use the apply or save control if one is shown, return to the aircraft and test the full range. Reload GeoFS once to confirm that the browser retained the assignment.
If GeoFS does not recognise the USB throttle, restart the browser with the controller already connected and use a maintained browser with game-controller support. Keep the GeoFS tab focused and check the browser’s site permissions if it exposes a gamepad or controller permission. Privacy restrictions, private-browsing mode, blocked local site storage and clearing browser data can prevent detection or erase saved mappings.
How should reverse thrust and throttle detents be configured?
The correct reverse-thrust setup depends on what the hardware sends after the lever reaches idle.
| Hardware behaviour | Binding to use | Calibration check |
|---|---|---|
| Analogue travel continues below idle | Full-range forward-and-reverse throttle axis | Record the idle boundary so reverse does not begin too early |
| A button activates below the detent | Forward-only axis plus reverse hold, reverse toggle or the aircraft’s supported reverse command | Keep normal axis travel calibrated from idle to full power |
| Separate reverse lever or axis | Dedicated reverse axis, if the simulator or aircraft provides one | Do not bind the same movement to normal and reverse axes |
| No physical reverse control | Forward-only axis plus a separate button or keyboard command | Verify that returning to idle cancels reverse correctly |
Axis inversion only changes the direction of normal travel; it does not create a reverse zone. If a physical detent is difficult to hold, widen that detent’s tolerance slightly in the aircraft utility rather than adding a large dead zone to the whole throttle.
How do I complete A220 throttle calibration?
A220 throttle calibration should be performed in the specific simulated A220’s own electronic flight bag or configuration utility whenever one is provided.
What should I check before calibrating an A220 throttle quadrant?
Three setup errors account for most failed A220 calibrations.
- Remove the combined-throttle binding: With two physical levers, retain only Engine 1 and Engine 2 throttle axes. A single-lever setup may use a combined axis if the aircraft supports it.
- Choose the correct axis range: Use a forward-only axis for hardware whose reverse detent sends a button. Use a full-range axis when the levers produce analogue travel below idle.
- Check the aircraft’s calibration display: Confirm that the utility can distinguish forward travel, idle, reverse and every detent it asks you to record. Simulator movement alone does not prove the A220 has accepted those positions.
- Create an A220-specific controller profile. Assign the left lever to Engine 1 and the right lever to Engine 2, then search all active controllers for remaining combined or individual throttle conflicts.
- Reset excessive response changes. Begin with linear axes and confirm that both virtual levers move in the same direction and over a similar range.
- Open the A220 calibration utility. Use the aircraft’s own tablet, electronic flight bag or configuration panel. The names and number of calibration positions vary between A220 simulations, so follow the labels displayed by that aircraft.
- Record every requested position. Capture the forward endpoint, idle, reverse endpoint and thrust detents in the order requested. Move both levers together or separately according to the utility’s instructions.
- Save and test each zone. Move the levers slowly through their range and verify that the cockpit indications settle at idle, each forward detent and reverse without jumping between zones.
Do not assume an A320 detent preset will match an A220 throttle quadrant. If the simulated A220 has no aircraft-level calibration utility, retain a dedicated simulator profile and make only small range or sensitivity adjustments. Failure to enter reverse usually indicates the wrong axis-range command or a below-idle switch being treated as analogue travel.
USB throttle quadrant not working / no funciona
If the USB throttle “no funciona”, isolate the failure by layer: first hardware detection, then simulator assignment, then the individual aircraft’s calibration. Recalibrating repeatedly will not fix a duplicate axis or an undetected controller.
| Symptom | Likely cause | Fix |
|---|---|---|
Not detected in Windows or absent from joy.cpl | USB connection, insufficient hub power, required device software or a quadrant designed to connect through a yoke | Reconnect it to a direct port, restart Windows, verify the model’s connection method and install only its required software. Test another port or computer to separate a hardware fault from a system problem. |
| Detected by Windows but no response in the simulator | Wrong profile, no analogue axis assignment, input filter or simulator launched before connection | Select the correct device profile, bind an Axis command, clear filters and restart the simulator with the quadrant connected. |
| Intermittent USB disconnects | Unpowered hub, unstable port, loose connection or USB power-saving | Use a direct or powered connection, reseat the plug and try another stable port. On Windows, disable power-saving for the affected USB hub or controller while diagnosing the fault. |
| Power changes with the lever untouched | Autothrottle, AI assistance, duplicate assignments or noisy input | Test with automatic thrust and assistance disabled, then clear throttle bindings from gamepads, virtual controllers and unused devices. Check the raw axis for movement. |
| Cockpit lever jitters or flickers | Raw electrical noise or two controllers fighting over the same axis | Watch the indicator in joy.cpl. Jitter there points to hardware or USB input; clean raw input with in-sim flicker points to duplicate assignments. Add only a small dead zone or filter after removing conflicts. |
| Throttle movement is reversed | Axis direction is inverted | Toggle the simulator’s invert or reverse-axis option. Do not alter reverse-thrust bindings to correct normal direction. |
| Only half the lever travel works | Forward-only and full-range axis types are mismatched, or an old calibration or response curve is clipping the range | Select the axis type matching the hardware, reset curves and saturation, then retest both endpoints before recalibrating detents. |
| One lever controls every engine | Combined throttle remains assigned alongside engine-specific axes | Delete the combined axis and retain Engine 1, Engine 2 and any other required individual axes. |
| Reverse thrust will not engage | Below-idle movement sends a button, the wrong axis range is selected or the aircraft requires its own reverse calibration | Identify the signal in the raw-input display, choose the matching reverse method and record idle and reverse again in the aircraft utility. |
| Works in one aircraft but not another | Aircraft-specific profile, custom throttle logic or separate detent data | Check which profile is active and reset only the affected aircraft’s bindings or calibration. Do not alter a global setup that works elsewhere. |
Will any USB throttle quadrant work on Xbox or PlayStation?
No. USB describes the plug and data connection; it does not guarantee console or simulator compatibility.
Microsoft Flight Simulator 2024 is available on PC, Xbox Series X|S, PlayStation 5 and PS5 Pro, but supported peripherals differ between those platforms. A quadrant that works on Windows or Xbox cannot be assumed to work on PlayStation. Microsoft Flight Simulator 2020 remains available on PC and Xbox only and was never released for PlayStation.
Check support for the exact quadrant, console and simulator before buying. Windows tools such as joy.cpl, PC drivers and desktop calibration utilities are unavailable on consoles, where an unsupported generic USB controller may provide no input at all.