FFBeast support

[mburlic]

Hi @berarma ,

I wanted to bring to your attention this amazing DIY project we are using for a while now. It's called FFBeast . Most of us use it to build force feedback wheels from used hoverboard wheels. Here is the main website and community discord channel
https://ffbeast.github.io/docs/en/wheel.html
https://discord.com/invite/Gt6rnvrZKu
Despite being a very affordable DD wheel, it's really good, and can give forces up to 15Nm of torque with good enough motor.

I've tested it on Debian in AC and AMS2. Inputs work but there is no FFB so I came across your project. I've asked the creator of FFBeast if it is okey to contact you. Would you be interested in adding support for FFBeast in your project?
I am willing to provide you with the information needed and to do testing.

Not sure what to send you so here are some information to star from somewhere. I look forward to hearing from you.

045b:59d7 Hitachi, Ltd FFBeast(Wheel)

*-usb:1
                         description: Human interface device
                         product: DIY FFBeast(Wheel)
                         vendor: DIY
                         physical id: 2
                         bus info: usb@3:2.2
                         logical name: input10
                         logical name: /dev/input/event10
                         logical name: /dev/input/js0
                         version: 2.00
                         serial: 208333985031
                         capabilities: usb-2.00 usb
                         configuration: driver=usbhid maxpower=100mA speed=12Mbit/s```

looking at device '/devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb3/3-2/3-2.2/3-2.2:1.0/0003:045B:59D7.0008/input/input10/js0':
    KERNEL=="js0"
    SUBSYSTEM=="input"
    DRIVER==""
    ATTR{power/async}=="disabled"
    ATTR{power/control}=="auto"
    ATTR{power/runtime_active_kids}=="0"
    ATTR{power/runtime_active_time}=="0"
    ATTR{power/runtime_enabled}=="disabled"
    ATTR{power/runtime_status}=="unsupported"
    ATTR{power/runtime_suspended_time}=="0"
    ATTR{power/runtime_usage}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb3/3-2/3-2.2/3-2.2:1.0/0003:045B:59D7.0008/input/input10':
    KERNELS=="input10"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{capabilities/abs}=="ff"
    ATTRS{capabilities/ev}=="1b"
    ATTRS{capabilities/ff}=="0"
    ATTRS{capabilities/key}=="ffffffffffff 0 0 0 0 0 0 ffff00000000 0 0 0 0"
    ATTRS{capabilities/led}=="0"
    ATTRS{capabilities/msc}=="10"
    ATTRS{capabilities/rel}=="0"
    ATTRS{capabilities/snd}=="0"
    ATTRS{capabilities/sw}=="0"
    ATTRS{id/bustype}=="0003"
    ATTRS{id/product}=="59d7"
    ATTRS{id/vendor}=="045b"
    ATTRS{id/version}=="0100"
    ATTRS{inhibited}=="0"
    ATTRS{name}=="DIY FFBeast(Wheel)"
    ATTRS{phys}=="usb-0000:2f:00.3-2.2/input0"
    ATTRS{power/async}=="disabled"
    ATTRS{power/control}=="auto"
    ATTRS{power/runtime_active_kids}=="0"
    ATTRS{power/runtime_active_time}=="0"
    ATTRS{power/runtime_enabled}=="disabled"
    ATTRS{power/runtime_status}=="unsupported"
    ATTRS{power/runtime_suspended_time}=="0"
    ATTRS{power/runtime_usage}=="0"
    ATTRS{properties}=="0"
    ATTRS{uniq}=="208333985031"```

[berarma]

Hi. That's interesting, there's already a similar project, OpenFFBoard.

I can add the device ids but it will only make Oversteer detect the wheel for testing axes and buttons. It needs a driver and for that we need to know which protocol uses for the FFB. It probably uses HID for the axes and buttons and maybe HID PID for the FFB. There's already a driver (hid-pidff) for HID PID devices in the kernel but it may need updates to support new devices. But first we need to know if FFBeast uses HID PID.

[mburlic]

Thank you for answering.

udevadm info --attribute-walk /dev/input/by-id/usb-DIY_FFBeast_Wheel__208333985031-event-joystick 

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:08.1/0000:2f:00.3/usb3/3-2/3-2.2/3-2.2:1.0/0003:045B:59D7.000A/input/input28/event4':
    KERNEL=="event4"
    SUBSYSTEM=="input"
    DRIVER==""
    ATTR{power/async}=="disabled"
    ATTR{power/control}=="auto"
    ATTR{power/runtime_active_kids}=="0"
    ATTR{power/runtime_active_time}=="0"
    ATTR{power/runtime_enabled}=="disabled"
    ATTR{power/runtime_status}=="unsupported"
    ATTR{power/runtime_suspended_time}=="0"
    ATTR{power/runtime_usage}=="0"

sudo fftest /dev/input/event4
Force feedback test program.
HOLD FIRMLY YOUR WHEEL OR JOYSTICK TO PREVENT DAMAGES

Device /dev/input/event4 opened
Features:
  * Absolute axes: X, Y, Z, RX, RY, RZ, Throttle, Rudder, 
    [FF 00 00 00 00 00 00 00 ]
  * Relative axes: 
    [00 00 ]
  * Force feedback effects types: 
    Force feedback periodic effects: 
    [00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ]
  * Number of simultaneous effects: 0

Uploading effect #0 (Periodic sinusoidal) ... Error:: Function not implemented
Uploading effect #1 (Constant) ... Error: Function not implemented
Uploading effect #2 (Spring) ... Error: Function not implemented
Uploading effect #3 (Damper) ... Error: Function not implemented
Uploading effect #4 (Strong rumble, with heavy motor) ... Error: Function not implemented
Uploading effect #5 (Weak rumble, with light motor) ... Error: Function not implemented

there is no ffb

modprobe: FATAL: Module hid-pidff not found in directory /lib/modules/6.1.0-21-amd64

Port 2: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M

[olukelo]

It is standard FFB device so it uses HID PID as any other wheel

[berarma]

Every wheel doesn't use HID PID but if you're sure this one does, you can join this Matrix channel where other users are working together to make their HID PID wheels work.