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

MOZA AY210 FFB Base

346E:1001 · 6 approved reports · first 2026-06-06, last 2026-10-09 · probe 1.1.2

Device class: other

Capability snapshots · latest per OS

What this device reports on each platform

Windows

3 reports · latest 2026-10-09 · 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 rev0x1001
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

3 reports · latest 2026-07-10 · probe 1.0.5

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

CachyOS 3 reports
Windows 3 reports

Test strength: 35% (1 report), not recorded (5 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 3 reports
Damped x1 Sluggish x1
Friction 3 reports
Drag x2 Weak friction x1
Inertia 3 reports
Heavy x1 Lagging x1 Resists changes in motion x1
Linux Sawtooth Down 3 reports
Did nothing x2 Asymmetric ramp pulses x1
Linux Sawtooth Up 3 reports
Did nothing x2 Asymmetric ramp pulses x1
Linux Sine 3 reports
Did nothing x2 Smooth oscillation x1
Linux Square 3 reports
Did nothing x2 Sharp pulses x1
Linux Triangle 3 reports
Did nothing x2 Smooth oscillation x1
Linux constant force - backward pull 3 reports
Did nothing x2 Pulled back x1
Linux constant force - forward pull 3 reports
Did nothing x2 Pulled forward x1
Linux constant force - left pull 3 reports
Did nothing x2 Pulled left x1
Linux constant force - right pull 3 reports
Did nothing x2 Pulled right x1
Linux damper 3 reports
Did nothing x2 Damped x1
Linux friction 3 reports
Did nothing x2 Sticky x1
Linux inertia 3 reports
Did nothing x2 Heavy x1
Linux ramp force - backward pull 3 reports
Did nothing x2 Built up gradually x1 Pulled back x1
Linux ramp force - left pull 3 reports
Did nothing x2 Built up gradually x1 Pulled left x1
Linux rumble 3 reports
Did nothing x2 Sharp pulses x1
Linux spring 3 reports
Did nothing x2 Centered x1
Saturation — 1 co-directional constants 3 reports
Pulled diagonally x1
Saturation — 2 co-directional constants 3 reports
Did nothing x1 Pulled back x1
Saturation — 3 co-directional constants 3 reports
Soft pull x1
Sawtooth Down 3 reports
Buzzing x2 Repeated ramping x1
Sawtooth Up 3 reports
Asymmetric ramp pulses x1 Repeated ramping x1 Weak x1
Sine 3 reports
Smooth oscillation x2 Slow x1
Spring 3 reports
Centered x1 No centering x1 Springy x1
Square 3 reports
Sharp pulses x2 Tapping x1
Triangle 3 reports
Buzzing x1 Rocking back and forth x1 Smooth oscillation x1
Two-axis diagonal — diagonal 3 reports
Pulled forward x1 Pulled left x1 Strong pull x1
Polarity sweep — DI east (right) (90°) 2 reports
Pulled left x1 Strong pull x1
Polarity sweep — DI north (away) (0°) 2 reports
Pulled back x1 Pulled left x1
Polarity sweep — DI south (toward) (180°) 2 reports
Pulled forward x1 Soft pull x1
Polarity sweep — DI west (left) (270°) 2 reports
Brief jerk x1 Pulled right x1
Polarity sweep — DI east (0°) 1 report
Pulled left x1
Polarity sweep — DI north (270°) 1 report
Pulled back x1
Polarity sweep — DI south (90°) 1 report
Pulled right x1
Polarity sweep — DI west (180°) 1 report
Pulled forward x1
Ramp sweep — DI east (right) (90°) 1 report
(no labels)
Ramp sweep — DI north (away) (0°) 1 report
Faded away x1
Direction consistency · constant-force direction tests

What the commanded directions actually did

Direction reports are inconsistent

Scored responses13
Matched9
Mismatched4
Consistency69%
No direction11
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 left x2 Pulled back x2 2 2
90° east (right) Pulled left Pulled left x2 Pulled right x1 2 1
180° south (toward) Pulled forward Pulled forward x3 3 0
270° west (left) Pulled right Pulled right x2 Pulled back x1 2 1
Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect Reports Create Play Stop
Damper 3
OK x3
OK x3
OK x3
Friction 3
OK x3
OK x3
OK x3
Inertia 3
OK x3
OK x3
OK x3
Linux Sawtooth Down 3
OK x3
OK x3
OK x3
Linux Sawtooth Up 3
OK x3
OK x3
OK x3
Linux Sine 3
OK x3
OK x3
OK x3
Linux Square 3
OK x3
OK x3
OK x3
Linux Triangle 3
OK x3
OK x3
OK x3
Linux constant force - backward pull 3
OK x3
OK x3
OK x3
Linux constant force - forward pull 3
OK x3
OK x3
OK x3
Linux constant force - left pull 3
OK x3
OK x3
OK x3
Linux constant force - right pull 3
OK x3
OK x3
OK x3
Linux damper 3
OK x3
OK x3
OK x3
Linux friction 3
OK x3
OK x3
OK x3
Linux inertia 3
OK x3
OK x3
OK x3
Linux ramp force - backward pull 3
OK x3
OK x3
OK x3
Linux ramp force - left pull 3
OK x3
OK x3
OK x3
Linux rumble 3
OK x3
OK x3
OK x3
Linux spring 3
OK x3
OK x3
OK x3
Sawtooth Down 3
OK x3
OK x3
OK x3
Sawtooth Up 3
OK x3
OK x3
OK x3
Sine 3
OK x3
OK x3
OK x3
Spring 3
OK x3
OK x3
OK x3
Square 3
OK x3
OK x3
OK x3
Triangle 3
OK x3
OK x3
OK x3
Polarity sweep — DI east (right) (90°) 1
OK x1
OK x1
OK x1
Polarity sweep — DI north (away) (0°) 1
OK x1
OK x1
OK x1
Polarity sweep — DI south (toward) (180°) 1
OK x1
OK x1
OK x1
Polarity sweep — DI west (left) (270°) 1
OK x1
OK x1
OK x1
Ramp sweep — DI east (right) (90°) 1
OK x1
OK x1
OK x1
Ramp sweep — DI north (away) (0°) 1
OK x1
OK x1
OK x1
Saturation — 1 co-directional constants 1
OK x1
(none) x1
(none) x1
Saturation — 2 co-directional constants 1
OK x1
(none) x1
(none) x1
Saturation — 3 co-directional constants 1
OK x1
(none) x1
(none) x1
Two-axis diagonal — diagonal 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.