Managed MOZA support

Plug in the base. Let FFB-Bridge prepare it.

Version 1.3 manages the AB6, AB9, and AY210 for the whole session. Normal flying no longer depends on a separate configuration utility or a carefully preserved slider preset.

Download FFB-Bridge 1.3 Read the MOZA guide

FFB-Bridge preparing a MOZA AB9 FFB Base for the current session — Startup feedback makes the temporary device takeover visible instead of hiding it in a log.

Validated family support

AB6, AB9, and AY210 are supported across Windows, Linux, and macOS

AB6, AB9, and AY210 are confirmed supported and working with cross-platform managed configuration. Effect-specific evidence remains device- and backend-specific.

AB6AB6 is confirmed working through the shared 346e:1002 managed family. Effect-specific depth remains device- and backend-specific.

AB9The full flight-stick path, including continuous hat input for beep trim and managed native effects.

AY210Validated yoke input and force output with the same automatic prepare, monitor, and restore lifecycle.

FFB-Bridge Hardware MOZA page showing device status, live position, output limits, and mechanical-feel tests — Hardware → MOZA separates physical base limits and isolated tests from aircraft-specific tuning.

New in Hardware

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.

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.

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.

Read the MOZA guide Tuning guide

Managed session

Prepare, fly, restore

1 · Prepare

Read the base and apply a clean session state

FFB-Bridge saves the settings it owns, enables output, selects the required mode and gains, and neutralizes stored effects before forces can engage.

2 · Fly

Keep the required state correct

The base is monitored while FFB-Bridge is open. Platform-native input and force paths provide axes, buttons, POV controls, spring, and flight forces; AB6/AB9 damping and friction use the managed firmware-local serial path.

3 · Restore

Return the exact previous settings

After a normal exit, FFB-Bridge closes its force backend, restores the saved device values, and verifies the result before finishing.

No competing configuration tools

On Windows, close MOZA Cockpit before the session

Two programs should not write the base configuration at the same time. FFB-Bridge detects the conflict, explains what to close, and checks again when you are ready.

FFB-Bridge dialog asking the user to close MOZA Cockpit before continuing — The session waits instead of racing another program for the base.

FFB-Bridge restoring the previous settings on a MOZA AB9 FFB Base — Shutdown stays visible while the exact pre-session state is restored.

Your settings outside FFB-Bridge

A normal exit puts the base back the way it was

The original output state, mode, strength, and built-in effects return after the session. If a crash or power loss prevents exit work, recovery state is retained for a later clean session.

Explicit control

Hardware setup without taking over your buttons

Raw input fixes held controls such as beep trim, but it does not claim a hat or button. FTR and beep trim remain unassigned until you learn buttons or enable a dedicated hat.

AB6, AB9, and AY210The flight-stick bases share one managed policy; the yoke uses its validated device behavior and the same lifecycle.

Keep the vendor utility for maintenanceUse it for firmware, calibration, lighting, and features outside FFB-Bridge. It is not required to prepare the base for a normal FFB-Bridge flight.

Quit cleanly when possibleA normal application exit is what performs immediate restoration. Do not disconnect power while the restore message is visible.

Make the base a natural part of every flight

FFB-Bridge owns the session behavior; your previous base state remains yours when the session ends normally.

Download FFB-Bridge 1.3 Read the MOZA guide