How do I fix a MOZA AB6 axis with no range of motion?

To fix a MOZA AB6 axis with no range of motion, first confirm that the axis moves in MOZA Cockpit, recalibrate the base, then test it in Windows before changing simulator bindings. If Windows shows full travel, remove duplicate assignments and reset the simulator’s dead-zone, sensitivity and endpoint settings for that axis.

This diagnostic order applies across PC flight simulators. Force feedback and axis input are separate parts of the chain: resistance at the grip does not prove Windows is receiving pitch and roll data.

Where should I test the AB6 axis first?

Test the axis in MOZA Cockpit, Windows Game Controllers and the simulator, in that order. The first place where movement disappears identifies the part that needs attention.

For the Windows stage, use joy.cpl and watch the crosshair or axis bars on the device’s test page. Our Windows flight-stick testing procedure explains how to interpret those readings.

How do I recalibrate the MOZA AB6?

Recalibrating the AB6 should restore the minimum, centre and maximum values used for pitch and roll.

1. Close the simulator. Secure the base and clear the area around the grip because an active force-feedback base can move during a calibration or effect test.
2. Check power and USB. Confirm that the base is detected in MOZA Cockpit. Connect it directly to a motherboard USB port while troubleshooting rather than through an unpowered hub or extension.
3. Save the existing profile. Then load the default AB6 settings so an extreme curve, dead zone or force profile cannot mask the result.
4. Run the built-in base calibration. Follow MOZA Cockpit’s prompts exactly. Some calibration routines require the controls to be left alone while the base moves; others request full pitch and roll movement.
5. Inspect the live axis meters. Pitch and roll should each travel smoothly from one end to the other and return near centre. A completely fixed meter means this is not yet a simulator-binding problem.
6. Test in Windows. Open joy.cpl, select the AB6 and inspect its raw movement. Use Windows calibration only if the device exposes that option and the manufacturer calibration has already been completed.

Do not use a firmware update as the first experiment. If MOZA Cockpit offers an applicable update, install it only with stable power and USB connections, restart the base afterwards, then calibrate again. For the wider order of operations, see our PC joystick calibration and endpoint checklist.

Why does the axis work in Windows but not in the simulator?

If the AB6 reaches full range in Windows, the base and its position sensors are working; the fault is inside the simulator’s control profile or an intermediary utility.

• Bind pitch to the simulator’s analogue elevator axis and roll to its analogue aileron axis. Do not use digital commands such as elevator up, elevator down, bank left or bank right.
• Clear duplicate pitch and roll assignments from throttles, pedals, gamepads and virtual controllers. A second device held at centre can override or fight the AB6 input.
• Confirm that the correct aircraft or controller profile is active. Many simulators store separate bindings per aircraft or per device preset.
• Reset the axis curve to linear, use only a small dead zone if needed and restore saturation or endpoints to their full-range defaults. An extreme endpoint dead zone can make a healthy axis appear motionless.
• Temporarily remove reversal, filtering and sensitivity changes. Add them back only after full raw travel has been restored.

If the result changes depending on which utility is running, use our hardware-versus-simulator isolation checks. When FSUIPC handles the axis, clear stale minimum, centre and maximum values or record them again; our FSUIPC axis calibration instructions cover that route. Avoid assigning the same axis independently through both FSUIPC and the simulator.

What if the input meter moves but the aircraft controls do not?

If the simulator’s input meter reaches full range, the AB6 problem is fixed. Check the aircraft for a control lock or gust lock, unavailable hydraulics, an engaged autopilot, fly-by-wire limits or an aircraft-specific control profile.

Judge the raw input meter before using the external control-surface animation as evidence. Some aircraft limit or alter surface movement according to airspeed, hydraulic state and flight-control logic.

What if the stick is physically unable to move?

A physically locked AB6 requires a different check from an axis whose electronic reading is fixed.

1. Stop applying force. Do not push the grip against heavy resistance or attempt to force it past a hard point.
2. Switch off and disconnect base power. Once the motors cannot apply force, gently check whether pitch and roll move through their normal mechanical travel.
3. Inspect external obstructions. Check the mount, desk, grip cable and any extension for contact that blocks movement.
4. Compare powered and unpowered movement. If it moves freely without power, restore a default force-feedback profile and reduce spring, friction and force levels before testing again.

If the grip remains jammed when unpowered, grinds, or has sharply unequal travel, stop using the base. Do not open the housing; that points to a mechanical fault requiring MOZA service or warranty support.

When does no axis range indicate a hardware fault?

Treat the AB6 as potentially faulty when one axis remains completely fixed in both MOZA Cockpit and Windows after a default-profile reset, successful calibration, direct USB connection and computer restart.

If both axes disappear together, investigate power, USB detection and software installation first. If only pitch or only roll remains dead while the other axis works normally, a failed position sensor, internal connection or base electronics becomes more likely.