FFB Probe Diagnostic
Current site language English
Download
Hardware database · 0483:572C

CLS-60

0483:572C · 2 approved reports · first 2026-08-04, last 2026-10-25 · probe 1.1.2

Device class: joystick

Capability snapshots · latest per OS

What this device reports on each platform

Windows

2 reports · latest 2026-10-25 · probe 1.1.2

Microsoft Windows NT 10
Axes2
Buttons48
POVs1
FF sample period not reported reliably
Min time resolution not reported reliably
Firmware rev0x0000
Hardware rev0x572C
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
Supported effects 12
Constant Force
DIEFT_CONSTANTFORCE | FFATTACK | FFFADE
Ramp Force
DIEFT_RAMPFORCE | FFATTACK | FFFADE
Square
DIEFT_PERIODIC | FFATTACK | FFFADE
Sine
DIEFT_PERIODIC | FFATTACK | FFFADE
Triangle
DIEFT_PERIODIC | FFATTACK | FFFADE
Sawtooth Up
DIEFT_PERIODIC | FFATTACK | FFFADE
Sawtooth Down
DIEFT_PERIODIC | FFATTACK | FFFADE
Spring
DIEFT_CONDITION | SATURATION | DEADBAND
Damper
DIEFT_CONDITION | SATURATION | DEADBAND
Inertia
DIEFT_CONDITION | SATURATION | DEADBAND
Friction
DIEFT_CONDITION | SATURATION | DEADBAND
Custom Force
DIEFT_CUSTOMFORCE | SATURATION | DEADBAND
Reported by OS

Submission count by OS family

Windows 2 reports

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

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 2 reports
Did nothing x2
Friction 2 reports
Did nothing x2
Inertia 2 reports
Did nothing x2
Polarity sweep — DI east (right) (90°) 2 reports
Did nothing x2
Polarity sweep — DI north (away) (0°) 2 reports
Did nothing x2
Polarity sweep — DI south (toward) (180°) 2 reports
Did nothing x2
Polarity sweep — DI west (left) (270°) 2 reports
Did nothing x2
Saturation — 1 co-directional constants 2 reports
Did nothing x2
Saturation — 2 co-directional constants 2 reports
Did nothing x2
Saturation — 3 co-directional constants 2 reports
Did nothing x2
Sawtooth Down 2 reports
Did nothing x2
Sawtooth Up 2 reports
Did nothing x2
Sine 2 reports
Did nothing x2
Spring 2 reports
Did nothing x2
Square 2 reports
Did nothing x2
Triangle 2 reports
Did nothing x2
Two-axis diagonal — diagonal 2 reports
Did nothing x2
Ramp sweep — DI east (right) (90°) 1 report
Did nothing x1
Ramp sweep — DI north (away) (0°) 1 report
Did nothing x1
Direction consistency · constant-force direction tests

What the commanded directions actually did

Not enough direction answers to draw a conclusion yet.

Scored responses0
Matched0
Mismatched0
No direction8
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 No direction 0 0
90° east (right) Pulled left No direction 0 0
180° south (toward) Pulled forward No direction 0 0
270° west (left) Pulled right No direction 0 0
Technical results · all approved reports

Create / Play / Stop outcomes by effect

Effect Reports Create Play Stop
Damper 2
OK x2
OK x2
OK x2
Friction 2
OK x2
OK x2
OK x2
Inertia 2
OK x2
OK x2
OK x2
Sawtooth Down 2
OK x2
OK x2
OK x2
Sawtooth Up 2
OK x2
OK x2
OK x2
Sine 2
OK x2
OK x2
OK x2
Spring 2
OK x2
OK x2
OK x2
Square 2
OK x2
OK x2
OK x2
Triangle 2
OK x2
OK x2
OK x2
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
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.