ioridev / precision-fighting-board

Fighting board running at 8000hz

Precision-Fighting-Board

We all need to use this board in 20XX.
Discussions

Description

This project aims to develop the fastest game controller by utilizing the power of Teensy 4.0. We strive to achieve a polling rate of 8000Hz, delivering unparalleled responsiveness for an immersive gaming experience.

Where to Buy

Available for purchase on Booth. Buying from this shop directly supports the developers. For international customers, shipping outside of Japan is possible using address forwarding services like Buyee and Tenso.

https://iori-giken.booth.pm/

Features

• High-speed USB communication using Teensy 4.0
• Targeting an impressive 8000Hz polling rate
• Precise and instantaneous input response
• X-input support
• No waiting time for debounce

Installation

Open the PrecisionFightingBoard.TEENSY40.hex file in Teensyduino 1.53 and write to Teensy 4.0.　

Pin Number	Button
0	Up
1	Down
2	Left
3	Right
4	Home
5	Back
6	Start
7	Y
8	X
9	RB
10	LB
11	A
12	B
14	RT
15	LT
18	L3
19	R3

Tips

Not good at soldering or making wires?
Some models are equipped with pins from the beginning, so you can skip this complicated process by using this type of wire and wire for Brook.
Teensy 4.0 Pins

One GND with a pin is missing, so it must be branched with a breadboard or similar.　

Or you can purchase Breakout Board on Amazon.

Breakout Board for Teensy 4.0

Setting Up the Development Environment

Install Arduino IDE 1.8.13 and Teensyduino 1.53.

Clone this repository and copy the x-input/ArduinoXinput_Teensy/teensy directory to C:\Program Files (x86)\Arduino\hardware.

Open PrecisionFightingBoard.ino with the Arduino IDE, go to Tools, change the USB Type to XInput, and then upload it to the Teensy 4.0.

Benchmark

Polling rate test results

I caught the continuous X-input button loop in my Python program and confirmed that it was around 0.125 ms.

The program used for the test is in Precision-Fighting-Board/x-input/tester and anyone can try it out.

Comparison with PicoBoard

tester/gamepad_response_time_comparison.py
Gamepad 1 is a Precision-Fighting-Board.
Gamepad 2 is a gp2040-ce

Comparison with Brook PS4+ Audio Fighting Board

Gamepad 1 is a Precision-Fighting-Board.
Gamepad 2 is a Brook AFB

Use with WingmanFGC　

This is a test on a PC, but when used with WingmanFGC.
Gamepad 1 is a Precision-Fighting-Board with WingmanFGC.
Gamepad 2 is a gp2040-ce

Good results with input lag of up to 5 ms.　　　

Contributing

Contributions are welcome! If you'd like to contribute to this project, please follow these steps:

1. Fork the repository.
2. Create a new branch.
3. Make your enhancements or bug fixes.
4. Test thoroughly.
5. Submit a pull request detailing your changes.

License

This project is licensed under the MIT License. Please see the LICENSE file for more information.

Acknowledgements

We would like to express our gratitude to the developers and contributors of Teency 4.0 for their amazing work and support.

precision-fighting-board's Issues

Strange results from x-ipunt polling rate test　

Run x-input/tester.ino and loop through button presses while x-input/tester.py takes data.

The expected value is around 125 µs, but the actual result is thus an alternating output of slow and fast values.　

Time difference: 79.7999997138977 μs
Time difference: 919.7000002861023 μs
Time difference: 95.49999976158142 μs
Time difference: 907.7000000476837 μs
Time difference: 76.59999990463257 μs
Time difference: 922.9000000953674 μs
Time difference: 102.0 μs
Time difference: 896.2999999523163 μs
Time difference: 90.29999995231628 μs
Time difference: 910.0 μs
Time difference: 88.10000014305115 μs
Time difference: 917.6000001430511 μs
Time difference: 83.69999980926514 μs
Time difference: 901.2999999523163 μs
Time difference: 75.70000004768372 μs

I wonder why, is there a problem with TestScript?　

Comparative testing with other boards is needed.

Use eager debounce algorithm

The default debounce algorithm added in #7 adds latency to the button presses. Use this alternative algorithm instead (sometimes known as "eager debounce") to avoid this.

SOCD

The x-input Polling rate appears to be 1000 Hz.

Testing Xinput with tester.ino and tester.py　

Expected to be 125us

Firmware update Application

https://github.com/luni64/TeensySharp

Support analog stick so that pad can be built.

Saving user settings

Change polling rate or input mode and save

Program / Flash Memory
Teensy 4.0 has 2 Mbyte of flash memory intended for storing your code. The flash memory can also store read-only variables and arrays. A portion of the flash memory may be used for file storage using the LittleFS library. The top 64K of this memory is reserved for EEPROM emulation data and the LED blink restore program.
https://www.pjrc.com/store/teensy40.html

I want to automate the distribution hex file with Github Action.

Console support?

I am trying to figure out if I should support the console.
Obviously this spec is geared towards PC users, so I don't think we should support consoles.
Also, there is no way to verify that the console is receiving 8000 Hz input.

X-input support

Console support

wip
https://github.com/ioridev/Precision-Fighting-Board/tree/multiconsole-support

better product name idea

Do you have an idea for a better product name? Post them in this thread.　

Change the product name displayed by the pc