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

VelocityControl with relative setpoints #21

Open
jveijck opened this issue Sep 9, 2023 · 0 comments
Open

VelocityControl with relative setpoints #21

jveijck opened this issue Sep 9, 2023 · 0 comments

Comments

@jveijck
Copy link
Collaborator

jveijck commented Sep 9, 2023

Currently the VelocityControl has an input wanted position in Field Coordinate System (FCS).
For most use cases this sufficient. In some use cases the user want to move relative (using RCS).

Use case: testing or experiments
A use case is during testing or experimenting on the field.
User want have options to move the robot 1 meter to the right, or rotate 90 degrees. etc.
In that case the user can translate a relative move to FCS based on the current position (in FCS).

Use case: substitute procedure
Another use case can be during the substitute procedure. Then a user can move the replaced robot to location near the team area (possible non-green area). The robot can use self localization to move to a intermediate position near the team area. The move from the intermediate position into the team area can not be performed using FCS (assume self loc is not working properly outside the green field). Therefore a relative move would be useful. For the substitute robot is located in the team area. the robot should move relative to an intermediate position in the green field. On the intermediate position, the self localization becomes valid, and it can continue to its desired position on the field.

Proposal
Extend inputs for VelocityControl with enum which indicates if wanted position is in FCS or RCS.

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

1 participant