Use CH pedals with a Saitek yoke and throttle on PC. Get the correct USB setup, rudder and toe-brake bindings, and fixes for reversed axes.
Yes. On a Windows PC, USB CH Pro Pedals work alongside a Saitek or Logitech G Flight Yoke and throttle quadrant. The brands need not match: assign pitch and roll to the yoke, engine controls to the quadrant, and rudder plus independent toe brakes to the pedals in the simulator’s control settings.
This applies to general PC flight simulation, including Microsoft Flight Simulator 2020 and 2024, FSX, X-Plane and Prepar3D. Windows treats the pedals as a separate game-controller device, while the simulator combines their inputs with those from the Saitek hardware.
Older units may appear under the Saitek Pro Flight name and later ones as Logitech G hardware. That branding difference does not prevent them from working with CH pedals.
How do I connect CH pedals to a Saitek yoke and throttle?
Connect the native USB pedals and yoke to the PC separately, confirm that Windows can read every axis, and then make the assignments inside the simulator.
- Check which CH pedals you have. Native USB CH Pro Pedals provide a rudder axis and two toe-brake axes. Older pedals with a gameport plug are different: a passive USB adaptor may not preserve all three axes, so compatibility cannot be assumed.
- Connect the Saitek throttle correctly. The quadrant supplied with the classic Flight Yoke connects to the dedicated socket on the yoke and normally appears as part of the yoke controller. Do not connect that plug to a computer’s legacy keyboard or mouse socket. A separately sold USB throttle quadrant connects directly to the PC.
- Connect the pedals by USB. Use a direct computer USB port during initial setup. An unpowered hub, including a heavily loaded hub built into another controller, can cause detection or disconnection problems.
- Test the hardware in Windows. Run
joy.cpl, open each controller and move every control through its full travel. The CH pedals should show one axis for yaw and two independently moving axes for the toe brakes. A bundled throttle quadrant may be listed under the yoke rather than as its own device. - Calibrate before changing simulator settings. Centre the yoke and rudder pedals, release both toe brakes and complete the Windows calibration where available. Add dead zone only if an axis fails to settle when released.
- Inspect every controller profile. Open the simulator’s controls screen and select the yoke, pedals, throttle and any gamepad or joystick in turn. Change the filter to show all controls if axis assignments are hidden.
- Remove duplicate bindings. Clear automatically assigned rudder, brake, throttle, pitch and roll inputs from devices that should not control them. A gamepad trigger assigned to a brake axis is an especially common cause of unwanted braking.
- Assign and test the axes. Save a named profile, check that released brakes show no input, and test the rudder and each wheel brake separately. Once the setup is stable, keeping the controllers in the same USB ports can help older simulators retain their assignments.
For CH-specific calibration and axis details, see our guide to setting up CH Products pedals on a PC.
Which axes should I assign to the rudder pedals?
Assign the pedals’ sliding movement to the rudder or yaw axis, then assign each toe pedal to its corresponding proportional brake axis.
| Controller | Recommended assignments | Assignment to avoid |
|---|---|---|
| Saitek or Logitech yoke | Aileron or roll axis; elevator or pitch axis | A second rudder or brake axis when pedals are fitted |
| Throttle quadrant | Combined throttle, propeller and mixture axes, or engine-specific axes | Mapping both a combined throttle and individual engine throttles at the same time |
| CH pedals | Rudder or yaw axis; left brake axis; right brake axis | Digital left/right brake commands in place of proportional axes |
The exact labels vary, but choose entries containing axis rather than button-style commands. Pressing only the left toe brake should increase only the left brake input; the same test applies on the right.
On a twin-tail aircraft, the rudders still respond to the same single yaw input; they are not bound separately. Many light aircraft also link pedal input to nosewheel steering. Larger aircraft may model limited pedal steering and a separate tiller, but a tiller assignment is not required for the basic mixed-brand setup.
Microsoft Flight Simulator 2024 uses device profiles and a controls interface that differs from earlier editions. Our MSFS 2024 Saitek and Logitech profile instructions cover axis searches, duplicate inputs and profile management. FSX users can instead follow the FSX yoke-and-pedal assignment procedure.
Why do the rudder and toe brakes work backwards or fight each other?
Reversed brake axes, duplicate assignments and simulator assistance cause most incorrect pedal behaviour; mixed brands are rarely the problem.
- Brakes remain applied when released: reverse the left and right toe-brake axes individually. Many simulators initially interpret the released position as maximum braking.
- One pedal applies both brakes: remove the general brake command and bind the two proportional brake axes separately. Also confirm that the parking brake is released.
- Rudder jumps fully left or right: make sure the pedals are assigned to a continuous rudder axis rather than rudder-left and rudder-right button commands.
- Rudder drifts while centred: recalibrate the pedals and add only enough central dead zone to remove unwanted movement.
- Inputs double or oscillate: check the yoke, gamepad and joystick profiles for another rudder assignment. Disable auto-rudder, assisted steering or similar assistance after confirming that the physical pedals work.
- Windows detects movement but the simulator does not: verify that you are editing the pedals’ profile, expose all available controls and check whether legacy profiling software has replaced the physical device with a virtual controller.
- No movement appears in
joy.cpl: this is a USB, power, driver or hardware problem rather than a simulator binding problem. Try a direct motherboard USB port and remove unnecessary hubs before reinstalling software.
If the yoke, throttle or pedals disappear or never register in Windows, use our hardware detection and non-moving-axis checks.
Do CH pedals and a Saitek yoke need matching drivers?
No matching software is required because the controls are independent USB devices. Use the simulator’s own assignments first and install manufacturer software only when Windows needs a supported driver or a specific device feature.
Avoid merging the yoke and pedals into one virtual controller unless a particular older simulator requires it. Legacy profiling software can hide the original devices, duplicate commands or make fault-finding harder. If you use an external mapping utility, assign each axis in either that utility or the simulator—not both.
Will CH pedals and a Saitek yoke work on Xbox or PlayStation?
Treat this mixed-brand combination as a Windows PC setup. Xbox Series X|S and PlayStation 5 consoles recognise only peripherals supported by the individual simulator and platform; ordinary Windows USB compatibility does not carry across.
Microsoft Flight Simulator 2024 is available on Xbox Series X|S, PS5 and PS5 Pro, but its PlayStation release does not make CH USB pedals or a PC Saitek yoke automatically compatible. Microsoft Flight Simulator 2020 remains limited to PC and Xbox. A USB hub merely adds ports and cannot translate an unsupported controller, so both exact devices must be recognised by the console edition.