Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xbox Series S Controller support #56

Open
fbottarel opened this issue Jan 24, 2024 · 1 comment
Open

Xbox Series S Controller support #56

fbottarel opened this issue Jan 24, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@fbottarel
Copy link

Describe the the feature you would like
According to the documentation, only the PS4 and Logitech controllers are supported by the clearpath packages. Supporting the Xbox controller would be a great step since these well manufactured, readily available and feature both USB and Bluetooth connectivity.

Other notes
Since our Husky did not ship with a controller and we had some Xbox Series S controllers in the lab, I added the configuration to our unit. What I did was:

  1. install xboxdrv package via apt
  2. pair the controller using bluetoothctl
  3. make a custom udev rule to map any such xbox controller to /dev/input/xbox
  4. added a custom teleop_xbox.yaml config for teleop_twist_joy in clearpath_common/clearpath_control/config/a200 and clearpath_common/clearpath_control/config/generic
  5. modified clearpath_config/clearpath_config/platform/platform.py so that the xbox string is acceptable as joystick parameter.

I am not sure if I missed something, but after this I can write xbox in the joystick tag in the robot.yaml general configuration file and everything works as expected. Shall I compile a PR for this? How should the udev rule be installed by the Clearpath Installer script?

@fbottarel fbottarel added the enhancement New feature or request label Jan 24, 2024
@Mechazo11
Copy link

Hi @fbottarel

I might have been successful in pairing Xbox One S controller with a simulated husky robot. For step one, I used xpadneo instead. Will be opening a PR soon as soon as I get the simulated robot to move. For some unknown reasons there is an issue with the twist_mux node that I haven't been able to figure out yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants