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

enable wasd control in lieu of joystick #6

Open
c2huc2hu opened this issue May 22, 2017 · 3 comments
Open

enable wasd control in lieu of joystick #6

c2huc2hu opened this issue May 22, 2017 · 3 comments
Assignees
Milestone

Comments

@c2huc2hu
Copy link
Collaborator

for testing purposes

@c2huc2hu c2huc2hu added this to the 2018 milestone May 22, 2017
@c2huc2hu c2huc2hu modified the milestones: 2018, Phoenix 1.0 Aug 9, 2017
@c2huc2hu c2huc2hu added the easy label Aug 9, 2017
@c2huc2hu
Copy link
Collaborator Author

Due Oct 28, along with relays for drive

@c2huc2hu
Copy link
Collaborator Author

c2huc2hu commented Sep 29, 2017

Adding WASD control

Goal

We want to be able to control the rover without having to connect a joystick so it can easily be tested at home. There are two ways we can do this:

  1. Enable WASD to control the rover. Example of WASD control

  2. Create a virtual joystick: Virtual joystick library (apologies for the name, it's the only decent library for this)

Files to modify

  • rover/RoverDashboard/app/Setup/setup.jsx, updateDriveGamepadPoller()

@c2huc2hu
Copy link
Collaborator Author

Steps

  1. Understand how updateDriveGamepadPoller() works
  2. Create a minimal demo of the joystick library that tells you the current position of the joystick at all times OR understand a demo from online
  3. Integrate the library with our code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants