Skip to content
This repository has been archived by the owner on May 20, 2024. It is now read-only.

Support Drive-By Targetting #61

Open
dkt01 opened this issue Feb 4, 2020 · 2 comments
Open

Support Drive-By Targetting #61

dkt01 opened this issue Feb 4, 2020 · 2 comments

Comments

@dkt01
Copy link
Member

dkt01 commented Feb 4, 2020

Calculate aiming offset to hit target while robot is still in motion.

Possible inputs include:

  • Target yaw angle (relative to robot)
  • Target distance (relative to turret)
  • Robot velocity (relative to field)
  • Robot yaw rate (relative to field)

Possible outputs include:

  • Yaw offset for aiming (account for robot velocity across field)
  • Shooter speed offset (increase/reduce FC velocity to account for robot motion towards/away from target)
@dkt01 dkt01 added this to the Week 5 milestone Feb 4, 2020
@dkt01 dkt01 modified the milestones: Week 5, Week 6 Feb 10, 2020
@dkt01 dkt01 modified the milestones: Week 6, MWR Feb 17, 2020
@dkt01
Copy link
Member Author

dkt01 commented Feb 22, 2020

Here's a possible approach in a spreadsheet to help with testing
LimelightCalculations.xlsx

@dkt01
Copy link
Member Author

dkt01 commented Feb 22, 2020

img-99bc872f6a52d5ba
Where theta_turret=0 180 degrees away from psi_robot=0 and both have positive in the clockwise direction.
Where theta_skew is positive on the left side of the target
Where theta_limelight is positive when the target is on the right side

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

No branches or pull requests

1 participant