-
-
Notifications
You must be signed in to change notification settings - Fork 147
OpenFFBoard (State and roadmap)
FFBWheel mode:
The setup procedure is not optimal but a FFB wheel with servos or steppers with ABN and SinCos encoders run great in most games.
For other motor drivers you can use different PWM modes and output the calculated torque effect value as PWM. You need an ABN encoder connected to the FFBoard.
You can select multiple button sources which will be combined into a gamepad button field of 32 buttons (maybe more later if needed. 32 is a common limit for HID, some programs support up to 128.) SPI, Thrustmaster wheels, the onboard digital inputs and a shifter are possible button sources.
Analog joystick style shifters like the G29, G27 and G25 for example can connect to analog inputs and a reverse button (SPI for G27 or digital pin for G29) and you will get 6+1 gears as buttons.
6 analog pins are available as gamepad axes (pedals...) with optional autoranging and can be disabled individually.
An E-Stop pin can be pulled down on the STM board to stop the FFB. For added security, the enable pin on the TMC can also be pulled down externally.
An ODrive can receive torque commands and report the encoder position via a CAN bus for FFB. Manual configuration of the ODrive required!
Setting steering angles or strength from external programs without the serial port. Currently in development.
Important for safe and stable startup
Complex. Will take time but planned in the future
Interesting for multi axis ffb.
Using the FFBoard as a CAN bus interface or adding analog/digital inputs via CAN.
Tunneling BISS-C or EnDat through the STM to the TMC as a position source. Would be very flexible but adds communication overhead
Back up of settings or quick start presets
Auto change steering degrees and intensity depending on game. Motor stats as overlay etc.
The FFBoard firmware is flexible so for different hardware, features have to be disabled or predefined
The setup is still a bit unstable depending on how its done. Maybe a wizard could help.
The TMC debug mainclass is very helpful for testing the driver with the Trinamic IDE (TMCL-IDE). The mainclass is hacky and not stable with the newest TMC ide.
With absolute encoders or encoders with home pulse, an absolute position can be searched at powerup and automatically set the center offset. Not possible with all encoders and may require slow rotations.