Managed MOZA support

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

Version 1.4.2 gives AB6, AB9, and AY210 separate identities and model-specific policy. The base keeps its own configured feel until you Arm; FFB-Bridge owns the forces during flight and writes the exact pre-flight settings back at Disarm and at quit.

FFB-Bridge preparing a MOZA AB9 FFB Base for the current session FFB-Bridge preparing a MOZA AB9 FFB Base for the current session
The setup dialog shows configuration ownership being taken at device open; the base's own feel stays in place until you Arm.
Validated family support

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

AB6, AB9, and AY210 support cross-platform managed configuration, and all three have validated official Autopilot Follow. Input, force output, passive mechanics, and Force Sensing are admitted per exact device and backend.

AB6Exact identity 346e:1002. Input/PID output, managed configuration, local effects, and flight-validated official Autopilot Follow are supported; fixed-wing trim renders on the normal spring path.
AB9Exact identity 346e:1000. Validated directional mechanics, physical Autopilot Follow, continuous hat input for beep trim, and guided Force Sensing are supported.
AY210Exact identity 346e:1001. Validated independent HID/PID conditions and official physical Autopilot Follow use the same managed ownership and restoration lifecycle.
AY90Conditional support as an AY210-family base: same backends, firmware configuration ownership, autopilot follow, and damping floor, built on approved FFB Probe reports. Not yet validated on a physical AY90; reports from AY90 owners are welcome.
FFB-Bridge Hardware MOZA page showing pitch, roll, and Vibration and detail output ceilings, damping calibration, and Base resistance FFB-Bridge Hardware MOZA page showing pitch, roll, and Vibration and detail output ceilings, damping calibration, and Base resistance
Hardware → MOZA keeps the three physical output ceilings and Base resistance minimums separate from aircraft-specific tuning.
New in Hardware

The MOZA control centre

Open Hardware → MOZA to set the base-level pitch and roll output limits, the independent Vibration & detail ceiling, damping calibration, and the Base resistance resting minimums. Aircraft feel, effect gains, input mode, passive mechanics, and Autopilot Follow remain in Tuning.

Set the physical envelope first Pitch and roll independently bound steady axis authority. Vibration & detail directly bounds rumble, buffet, shudders, and transient cues from 0 to 100% of device command without changing either axis limit. Until set, it follows the lower axis ceiling. All three values are saved for the selected device.
Autopilot Follow Official physical Follow moves a linked yoke or stick to the simulator's autopilot-commanded control position. Authority limits travel and Follow speed controls how quickly the base moves.
Base limits here, aircraft feel in Tuning Hardware owns the physical output envelope, damping calibration, and the Base resistance resting minimums, which apply in every state. Tuning owns the aircraft's pitch and roll damping, friction, inertia, progressive-stop onset and strength, input mode, Follow controls, and every aerodynamic or mechanical effect; a profile can ask for more resistance than your minimums, never less. Master gain scales the complete armed profile.
Managed session

Prepare, fly, restore

1 · Prepare

Read the base and take configuration ownership

At device open FFB-Bridge journals the base's settings and takes configuration ownership only: communication modes, output gates, and the recovery journal. Nothing the hand feels changes; the base keeps its MOZA Cockpit-configured spring, damping, friction, inertia, strength, and advanced settings until you Arm.

2 · Fly

Arm hands the feel to the flight model

At Arm the base's own spring gives way to the app's centering, passive damping, friction, and inertia go to MOZA's factory floor on AB6 and AB9, and the advanced settings family is suspended. Exact-device paths provide axes, buttons, POV controls, flight forces, trim, and supported Follow or Force Sensing without assuming that every MOZA model behaves alike.

3 · Restore

Return the exact previous settings

Disarm, Safety Stop, and simulator exit write the exact pre-flight values back and verify them, so between flights the base feels the same as with FFB-Bridge closed. Quit restores and verifies the journaled originals and deletes the journal. Recovery evidence survives an interrupted prior session.

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 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 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

Ending ownership puts the base back the way it was

Your settings are untouched until you Arm, returned exactly at Disarm, and restored and verified at quit. 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 three bases share a safe ownership lifecycle and retain separate identities, mechanics, and physically admitted feature policy.
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 forces only while you are armed; at every other time, and after quit, the feel is your own base configuration.