MOZA AB6, AB9, and AY210

FFB-Bridge manages supported MOZA bases for the whole session on Windows, Linux, and macOS. Normal use does not require a separate configuration utility or a special saved preset.

What happens at startup

1. FFB-Bridge identifies the connected AB6, AB9, or AY210 and selects its device- and platform-specific managed force-output policy.
2. It reads and journals every device setting that the session may change.
3. It neutralizes stored autonomous effects, enables force output, applies the required mode and gains, and opens the force backend.
4. It verifies the resulting state before the setup message closes.

The journal covers 13 settings the session may change. FFB-Bridge prepares and verifies them before arming, watches for drift while open, then restores and verifies the exact captured values on a normal exit.

Close MOZA Cockpit on Windows

If MOZA Cockpit is running, FFB-Bridge asks you to close it and checks again. Two applications must not write the device configuration at the same time.

What FFB-Bridge owns during the session

The managed policy stays active while FFB-Bridge is open and corrects relevant device-state drift.

• Force output, physical strength, overall gain, and game-force gain are placed in a known state.
• Stored autonomous spring, damper, inertia, and friction are neutralized so they cannot compete with the flight model.
• AB6 and AB9 use their firmware-local damper and friction path; AY210 uses its validated native PID one-to-one path. FFB-Bridge selects the device-specific renderer instead of treating every raw-force path as identical.

The MOZA control centre

Open Hardware → MOZA to see session ownership, live device evidence, the base-level output envelope, and isolated mechanical-feel tests in one place. This page configures the physical base; aircraft feel remains in Tuning.

Read status and live evidence correctly

Ownership and health are operational checks. Position and torque update as informational evidence for movement and load; they are not an automatic smoothness pass/fail test.

Set the physical envelope first

Pitch, roll, and texture limits bound active output at the base. Start conservatively, prove direction and the safety stop, then increase only if the mounting and full travel remain controlled.

Test one mechanic at a time

Secure the base, stay disarmed from live simulator output, choose one low-strength damping, friction, inertia, or progressive-stop test, and stop it as soon as the feel is clear. Each isolated test has a 15-second maximum and leaves the aircraft profile unchanged.

• Damping should resist faster movement more strongly without pulling the control toward centre.
• Friction should create steady breakout and sliding resistance, largely independent of movement speed.
• Inertia should oppose changes in movement, most noticeably when starting, stopping, or reversing direction.
• Progressive stop should rise only near the selected end of travel; it must not drive the control by itself.

AB6, AB9, and AY210 behavior

AY210 can apply passive mechanical coefficients per axis. AB6 and AB9 expose one firmware-local coefficient for each passive condition, so FFB-Bridge safely uses the stronger requested axis. Unsupported native conditions remain inactive instead of being simulated silently.

Base limits here, aircraft feel in Tuning

Hardware owns the base envelope and isolated proof tests. Tuning owns the aircraft's pitch and roll damping, friction, inertia, progressive-stop onset and strength, and every aerodynamic or mechanical effect. Master gain then scales the complete armed profile.

Tuning guide

Buttons remain explicitly assigned

Choose Set up… for the FTR button, optional force-trim on/off button, or beep-trim 4-way control. Each opens the same guided modal, waits while device input is prepared, then animates only while a press or direction can be captured. Nothing is assigned automatically, and simulator keybindings are never changed.

What happens on a normal exit

FFB-Bridge stops forces, closes the backend, restores the exact values captured at startup, and verifies the result before quitting.

When to use the vendor utility

Use it when updating firmware, calibrating the device, changing lighting, or using features outside FFB-Bridge. Close it before starting a flight session.

Troubleshooting

• Setup will not continue: close MOZA Cockpit completely, including its tray process, then choose Check again.
• Forces feel weak or too strong: set the physical ceiling under Hardware, then use aircraft gains under Tuning. Do not compensate with a second utility.
• Use one physical hat-shaped control for top, bottom, left, and right. FFB-Bridge listens to both input formats and saves either one POV hat or four buttons—whichever the device actually reports. The tested AY210 uses four buttons. Cancel or failed verification restores the previous assignment.
• Setup or restoration fails: export a support bundle before reopening another configuration utility.

See the MOZA family overview