FFB Probe Diagnostic
Current site language English
Download
Hardware database · 346E:1000

MOZA AB9 FFB Base

346E:1000 · 8 approved reports · first 2026-06-05, last 2026-10-24 · probe 1.1.2

Device class: other

Capability snapshots · latest per OS

What this device reports on each platform

Windows

7 reports · latest 2026-10-24 · probe 1.1.2

Microsoft Windows NT 10
Axes8
Buttons128
POVs1
FF sample period not reported reliably
Min time resolution not reported reliably
Firmware rev0x0000
Hardware rev0x1000
FF driver ver0x0001

A reported force-feedback interval or resolution of 1,000,000 µs (1 Hz) or more is firmware filler rather than a capability, and 1,000,000 µs is what this device reports. It is shown as unreported instead of being republished here.

Capability flags: DIDC_ATTACHED | DIDC_EMULATED | DIDC_FORCEFEEDBACK | DIDC_FFATTACK | DIDC_FFFADE | DIDC_SATURATION | DIDC_DEADBAND | DIDC_STARTDELAY
Supported effects 11
Constant Force
DIEFT_CONSTANTFORCE | FFATTACK | FFFADE | STARTDELAY
Ramp Force
DIEFT_RAMPFORCE | FFATTACK | FFFADE | STARTDELAY
Square
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Sine
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Triangle
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Sawtooth Up
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Sawtooth Down
DIEFT_PERIODIC | FFATTACK | FFFADE | STARTDELAY
Spring
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Damper
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Inertia
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY
Friction
DIEFT_CONDITION | SATURATION | DEADBAND | STARTDELAY

CachyOS

1 report · latest 2026-06-06 · probe 1.0.2

Unix 7
Axes8
Buttons13
POVs0
FF sample period 0 µs
Min time resolution 0 µs
Firmware rev0x0111
Hardware rev0x0000
FF driver ver0x0000
Capability flags: Linux evdev EV_FF; event=/dev/input/event4; ff_effects_max=64
Supported effects 14
Rumble
EV_FF 0x50
Periodic
EV_FF 0x51
Constant
EV_FF 0x52
Spring
EV_FF 0x53
Friction
EV_FF 0x54
Damper
EV_FF 0x55
Inertia
EV_FF 0x56
Ramp
EV_FF 0x57
Square
EV_FF 0x58
Triangle
EV_FF 0x59
Sine
EV_FF 0x5A
SawtoothUp
EV_FF 0x5B
SawtoothDown
EV_FF 0x5C
Gain
EV_FF 0x60
Reported by OS

Submission count by OS family

Windows 7 reports
CachyOS 1 report

Test strength: 35% (1 report), not recorded (7 reports)

Test strength is the share of full force every effect played at, set on the app's checklist and never above 75%. Read weak or did-nothing answers against it. Reports from app versions before 1.1.1 do not record it.

What testers felt · all approved reports

Chip selections by effect

Damper 7 reports
Damped x7
Friction 7 reports
Drag x3 Sticky x3 Strong friction x1 Weak friction x1
Inertia 7 reports
Heavy x4 Resists changes in motion x3 Did nothing x1
Saturation — 1 co-directional constants 7 reports
Pulled back x4 Pulled forward x1 Soft pull x1
Saturation — 2 co-directional constants 7 reports
Strong pull x4 Pulled back x3 Pulled forward x1
Saturation — 3 co-directional constants 7 reports
Strong pull x5 Pulled back x3 Pulled forward x1
Sawtooth Down 7 reports
Asymmetric ramp pulses x4 Repeated ramping x2 Strong x2 Fast x1
Sawtooth Up 7 reports
Asymmetric ramp pulses x4 Repeated ramping x2 Strong x2 Fast x1
Sine 7 reports
Smooth oscillation x6 Fast x1 Rocking back and forth x1 Strong x1
Spring 7 reports
Centered x3 Returns to center x3 Springy x2 Strong spring x2 Soft spring x1
Square 7 reports
Sharp pulses x6 Strong x2 Fast x1
Triangle 7 reports
Smooth oscillation x5 Strong x2 Fast x1 Rocking back and forth x1
Two-axis diagonal — diagonal 7 reports
Pulled diagonally x7 Pulled back x1 Strong pull x1
Polarity sweep — DI east (right) (90°) 5 reports
Pulled left x5 Strong pull x1
Polarity sweep — DI north (away) (0°) 5 reports
Pulled back x5 Strong pull x1
Polarity sweep — DI south (toward) (180°) 5 reports
Pulled forward x5 Strong pull x1
Polarity sweep — DI west (left) (270°) 5 reports
Pulled right x5
Ramp sweep — DI east (right) (90°) 2 reports
Built up gradually x2 Pulled left x1
Ramp sweep — DI north (away) (0°) 2 reports
Built up gradually x2 Pulled back x1
Linux Sawtooth Down 1 report
Asymmetric ramp pulses x1
Linux Sawtooth Up 1 report
Asymmetric ramp pulses x1 Repeated ramping x1
Linux Sine 1 report
Smooth oscillation x1
Linux Square 1 report
Sharp pulses x1
Linux Triangle 1 report
Rocking back and forth x1
Linux constant force - backward pull 1 report
Pulled back x1
Linux constant force - forward pull 1 report
Pulled forward x1
Linux constant force - left pull 1 report
Pulled left x1
Linux constant force - right pull 1 report
Pulled right x1
Linux damper 1 report
Damped x1
Linux friction 1 report
Sticky x1
Linux inertia 1 report
Lagging x1
Linux ramp force - backward pull 1 report
Built up gradually x1 Pulled back x1
Linux ramp force - left pull 1 report
Built up gradually x1 Pulled left x1
Linux rumble 1 report
Tapping x1
Linux spring 1 report
Returns to center x1
Polarity sweep — DI east (0°) 1 report
Pulled forward x1
Polarity sweep — DI north (270°) 1 report
Pulled right x1
Polarity sweep — DI source east / right (90°) 1 report
Pulled left x1
Polarity sweep — DI source north / away (0°) 1 report
Pulled back x1
Polarity sweep — DI source south / toward (180°) 1 report
Pulled forward x1
Polarity sweep — DI source west / left (270°) 1 report
Pulled right x1
Polarity sweep — DI south (90°) 1 report
Pulled left x1
Polarity sweep — DI west (180°) 1 report
Pulled back x1
Direction consistency · constant-force direction tests

What the commanded directions actually did

Consistent with the documented DirectInput mapping

Scored responses32
Matched30
Mismatched2
Consistency94%
No direction0
Several directions0
Unparseable0

Scoring covers the Windows polarity sweep and the Linux constant-force tests. A commanded direction is the direction the force comes from, so 0° should move the stick toward the tester. Scoring uses the documented mapping: 0° → Pulled back, 90° → Pulled left, 180° → Pulled forward, 270° → Pulled right. Answers that name more than one direction are counted separately and never scored.

Commanded Expected Observed Matched Mismatched
0° north (away) Pulled back Pulled back x7 Pulled forward x1 7 1
90° east (right) Pulled left Pulled left x8 8 0
180° south (toward) Pulled forward Pulled forward x7 Pulled back x1 7 1
270° west (left) Pulled right Pulled right x8 8 0
Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect Reports Create Play Stop
Damper 7
OK x7
OK x7
OK x7
Friction 7
OK x7
OK x7
OK x7
Inertia 7
OK x7
OK x7
OK x7
Sawtooth Down 7
OK x7
OK x7
OK x7
Sawtooth Up 7
OK x7
OK x7
OK x7
Sine 7
OK x7
OK x7
OK x7
Spring 7
OK x7
OK x7
OK x7
Square 7
OK x7
OK x7
OK x7
Triangle 7
OK x7
OK x7
OK x7
Polarity sweep — DI east (right) (90°) 2
OK x2
OK x2
OK x2
Polarity sweep — DI north (away) (0°) 2
OK x2
OK x2
OK x2
Polarity sweep — DI south (toward) (180°) 2
OK x2
OK x2
OK x2
Polarity sweep — DI west (left) (270°) 2
OK x2
OK x2
OK x2
Ramp sweep — DI east (right) (90°) 2
OK x2
OK x2
OK x2
Ramp sweep — DI north (away) (0°) 2
OK x2
OK x2
OK x2
Saturation — 1 co-directional constants 2
OK x2
(none) x2
(none) x2
Saturation — 2 co-directional constants 2
OK x2
(none) x2
(none) x2
Saturation — 3 co-directional constants 2
OK x2
(none) x2
(none) x2
Two-axis diagonal — diagonal 2
OK x2
OK x2
OK x2
Linux Sawtooth Down 1
OK x1
OK x1
OK x1
Linux Sawtooth Up 1
OK x1
OK x1
OK x1
Linux Sine 1
OK x1
OK x1
OK x1
Linux Square 1
OK x1
OK x1
OK x1
Linux Triangle 1
OK x1
OK x1
OK x1
Linux constant force - backward pull 1
OK x1
OK x1
OK x1
Linux constant force - forward pull 1
OK x1
OK x1
OK x1
Linux constant force - left pull 1
OK x1
OK x1
OK x1
Linux constant force - right pull 1
OK x1
OK x1
OK x1
Linux damper 1
OK x1
OK x1
OK x1
Linux friction 1
OK x1
OK x1
OK x1
Linux inertia 1
OK x1
OK x1
OK x1
Linux ramp force - backward pull 1
OK x1
OK x1
OK x1
Linux ramp force - left pull 1
OK x1
OK x1
OK x1
Linux rumble 1
OK x1
OK x1
OK x1
Linux spring 1
OK x1
OK x1
OK x1
Run errors · all approved reports

Path-redacted error log

  • MOZA firmware not in DirectInput mode / output gated — results measured with force output blocked. Control mode is Integrated — DirectInput effects are ignored. x1
Diagnostic visibility · current policy

Technical diagnostics are aggregated on this page so driver authors and tool builders can compare what multiple testers saw, including Windows and Linux runs for the same VID:PID. They use closed result names and path-redacted errors; the private response-notes field includes typed text and the probe-measured motion.

What's NOT on this page

The one private field

The per-effect responses[].notes field stays off this page. It can contain optional typed text and the probe-measured motion. Capability flags, supported effects, OS breakdown, test strength, chip labels, result codes, failed effects, and run errors can be published in aggregate or as a latest-per-platform snapshot. Read the full privacy contract →

Measured motion is what the probe saw on the stick's X and Y axes while each effect played: the signed peak movement as a percentage of the axis's half range, for example X peak +25.1%. It is measured from where the stick rested when the effect started, so it can exceed 100% when the stick rests off-centre. Condition effects such as spring and damper are not expected to move a centred stick.

Got this stick?

Run FFB Probe and share your result to improve this page.