salfter/USB4VC
1
0
Fork 0
mirror of https://github.com/dekuNukem/USB4VC.git synced 2025-10-31 11:26:46 -07:00
Code Issues Packages Projects Releases Wiki Activity

fixed switch pro controller button not holding down, added compatibility matrix, updated doc

Browse Source
This commit is contained in:
dekunukem
2022-03-18 23:57:15 +00:00
parent 46b63382c8
commit 7bfc54c85e
6 changed files with 47 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

77
getting_started.md
View File

@@ -8,6 +8,16 @@ Thank you very much for beta testing USB4VC! Here is a short guide on getting st
Please note that the code is most likely NOT 100% bug free at the moment, so if you run into any issues, [do get in touch](#questions-or-comments) so I can try fix it! I have also compiled a list of [known issues](#known-issues), with comments and remedies. Please note that the code is most likely NOT 100% bug free at the moment, so if you run into any issues, [do get in touch](#questions-or-comments) so I can try fix it! I have also compiled a list of [known issues](#known-issues), with comments and remedies.
## Pick a Raspberry Pi
* USB4VC is designed for **Raspberry Pi 1/2/3/4 Model B**.
* Any RPi with a **40-pin header** *should* work, although **Model B/B+** is preferred.
* No need to get the latest model, even the earliest RPi B+ is plenty fast enough.
![Alt text](photos/rpis.jpeg)
## Prepare SD card ## Prepare SD card
It's a good idea to **burn an SD card with the latest updates** before using. It's a good idea to **burn an SD card with the latest updates** before using.
@@ -34,16 +44,6 @@ Check the cable too! Cheap ones tends to have unreliable connections and large v
It's a good idea to make sure your Raspberry Pi works first. It's a good idea to make sure your Raspberry Pi works first.
USB4VC is designed for **Raspberry Pi 1/2/3/4 Model B**.
* No need to get the latest model, even the earliest RPi B+ is plenty fast enough.
* Older Pis might not have built-in Bluetooth. So if you want BT, a USB dongle is needed.
* Pi Zeros *might* work, but you need to solder a male header, and use a USB hub.
![Alt text](photos/rpis.jpeg)
Insert SD card in Raspberry Pi, and hook it up to a monitor. No need for anything else. Insert SD card in Raspberry Pi, and hook it up to a monitor. No need for anything else.
Power on, and it should boot and execute the program, showing a bunch of text. Power on, and it should boot and execute the program, showing a bunch of text.
@@ -152,34 +152,43 @@ With protocol selected, and everything connected, time to power on the computer!
If everything goes well, you should be able to use it as normal, now with USB inputs! If everything goes well, you should be able to use it as normal, now with USB inputs!
Please do keep reading for more information though 😅! Please **do keep reading** for more information though 😅!
![Alt text](photos/guide.gif) ![Alt text](photos/guide.gif)
## Using Gamepads ## Using Gamepads
For best results, please use a **Xbox One/Xbox 360 controller**. Those are the only kinds I have, so I used them for development. Other controllers might be buggy in button and axes mapping. I'll try to borrow a few more before the public release. Currently, USB4VC officially supports the following controllers:
* The easiest way is plug it in via a USB cable, and it should just work. * Xbox 360 / Xbox One / Xbox Series X
* You can also try to pairing it with Bluetooth. If keeps failing, you might need to [update the controller in Windows 10](photos/xbupdate.png), [source here](https://atar-axis.github.io/xpadneo/). * PlayStation 4 / PlayStation 5
Once connected, you can enable `15-Pin Gamepad` Protocol on IBM PC Card, and it should behave like a generic gamepad with **4 buttons and 4 analog axes**. Default mapping is: In my testing, gamepad compatibility seems to depends on the RPi models:
| XBox Controller | 15-Pin Gamepad | ![Alt text](photos/matrix.png)
|-----------------|-------------------------|
| A | Button 1 | * Raspberry Pi 3 Model B seems to be the most compatible.
| B | Button 3 |
| X | Button 2 | * The easiest way is using a USB cable, and it should just work.
| Y | Button 4 |
| LB | Button 1 | * If pairing fails, remove the BT device in the menu, reboot USB4VC, and try again.
| RB | Button 2 |
| Left Stick | Joystick 1 | Once connected, you can enable `15-Pin Gamepad` Protocol on IBM PC Card, and it should behave like a generic gamepad with **4 buttons and 4 analog axes**.
| Right Stick | Joystick 2 |
| D-pad | Joystick 1 | With **officially supported controllers**, the mapping is:
| Trigger | Joystick 2 Vertical Axis |
| Menu Button | Esc Key | * 4 Face buttons to 4 Gameport Gamepad buttons
| View Button | Enter Key |
* Left and right trigger to Gameport Gamepad button 1 & 2.
* Left Stick to Gameport Gamepad Joystick 1.
* Right Stick to Gameport Gamepad Joystick 2.
* Left & Right Analog Triggers to Joystick 2 Y Axis.
Unsupported USB controllers might still work, but the mapping might be a bit wonky.
## Joycheck DOS Program ## Joycheck DOS Program
@@ -211,19 +220,13 @@ When the RPi is off, you can press `POWER ON` button to turn it back on.
Here are a couple of bugs and issues that I am aware of, and the corresponding comments and remedies. Here are a couple of bugs and issues that I am aware of, and the corresponding comments and remedies.
#### Screw head is slightly too tall on the bottom plate, making the anti-slip pad not as effective.
* Will switch to a flatter screw for public release.
* Try double-up the anti-slip pads, or use a thicker one.
#### Boot time can be faster #### Boot time can be faster
* Currently it takes about 15 seconds to boot with a decent SD card. * Currently it takes about 15 seconds to boot with a decent SD card.
* Might look into disabling some services to speed it up. * Might look into disabling some services to speed it up.
* Would be great to get it under 10 seconds with the help of RPi experts. * [Let me know](#questions-or-comments) if you'd like to help!
#### 15-Pin Gameport Power Backfeeding #### 15-Pin Gameport Power Backfeeding
@@ -233,8 +236,6 @@ Here are a couple of bugs and issues that I am aware of, and the corresponding c
* Make sure to power on USB4VC before the computer. (this is what you should do anyway) * Make sure to power on USB4VC before the computer. (this is what you should do anyway)
* I might add a diode in the production run.
#### ADB Collision Resolution #### ADB Collision Resolution
* ADB collision resolution has not been fully implemented yet. * ADB collision resolution has not been fully implemented yet.

BIN
photos/matrix.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 51 KiB

2
user_program/login.sh
View File

@@ -1 +1 @@
ssh pi@192.168.1.56 ssh pi@192.168.1.61

4
user_program/sync.sh
View File

@@ -2,5 +2,5 @@
# sh sync.sh; ssh -t pi@192.168.1.67 "pkill python3;cd ~/usb4vc/rpi_app;python3 usb4vc_main.py" # sh sync.sh; ssh -t pi@192.168.1.67 "pkill python3;cd ~/usb4vc/rpi_app;python3 usb4vc_main.py"
scp ./* pi@192.168.1.56:~/usb4vc/rpi_app scp ./* pi@192.168.1.61:~/usb4vc/rpi_app
ssh -t pi@192.168.1.56 "pkill python3;cd ~/usb4vc/rpi_app;python3 usb4vc_main.py" ssh -t pi@192.168.1.61 "pkill python3;cd ~/usb4vc/rpi_app;python3 usb4vc_main.py"

2
user_program/usb4vc_shared.py
View File

@@ -1,4 +1,4 @@
RPI_APP_VERSION_TUPLE = (0, 0, 6) RPI_APP_VERSION_TUPLE = (0, 0, 7)
code_name_to_value_lookup = { code_name_to_value_lookup = {
'KEY_RESERVED':(0, 'kb_key'), 'KEY_RESERVED':(0, 'kb_key'),

5
user_program/usb4vc_usb_scan.py
View File

@@ -590,7 +590,10 @@ def raw_input_event_worker():
pcard_spi.xfer(list(last_mouse_button_msg)) pcard_spi.xfer(list(last_mouse_button_msg))
# Gamepad buttons # Gamepad buttons
elif BTN_SOUTH <= event_code <= BTN_THUMBR or event_code in gamepad_buttons_as_kb_codes: elif BTN_SOUTH <= event_code <= BTN_THUMBR or event_code in gamepad_buttons_as_kb_codes:
gamepad_status_dict[this_id][event_code] = data[4] this_btn_status = data[4]
if this_btn_status != 0:
this_btn_status = 1
gamepad_status_dict[this_id][event_code] = this_btn_status
# event is relative axes AKA mouse # event is relative axes AKA mouse
elif data[0] == EV_REL and event_code == REL_X: elif data[0] == EV_REL and event_code == REL_X: