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

Implement odometry #5

Open
wxb1ank opened this issue Feb 2, 2022 · 3 comments
Open

Implement odometry #5

wxb1ank opened this issue Feb 2, 2022 · 3 comments

Comments

@wxb1ank
Copy link
Contributor

wxb1ank commented Feb 2, 2022

We need to track the robot's position relative to the hubs for the purpose of automated shooting. See the WPILib docs for how this can be done with a little math. We will probably want to put the odometry-updating code in one of the Robot::periodic* methods.

@wxb1ank
Copy link
Contributor Author

wxb1ank commented Feb 3, 2022

This may not be strictly necessary; we could use the ta (target area) output from the Limelight camera to determine the distance of targets (e.g., cargo, retroreflective tape) with the inverse square law.

But, having seen the output of the Limelight, I think its reported position of the target is far more accurate than the area.

@SomeoneMysterious
Copy link
Contributor

SomeoneMysterious commented Feb 26, 2022

As far as I've heard/remember, the team is planning to shoot from a constant distance from the hubs. However, this might still be useful and needed depending on the situation, but for right now I don't think it will end up being needed. Let me know if you guys have heard otherwise, however.

@BowlesCR
Copy link

BowlesCR commented Mar 9, 2022

Should be able to get something useful out of the NavX displacement... it does drift, but should be accurate to within a few inches over the course of the match.

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

No branches or pull requests

3 participants