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

Add mode of control in talos_control_manager to check the corresponding limits. #22

Open
wants to merge 3 commits into
base: devel
Choose a base branch
from

Conversation

NoelieRamuzat
Copy link

The control modes are: position, velocity, torque, freeflyer (no control)
The velocities limits cannot be checked because the robotUtils object lacks of them.
Can plug signal q_predicted while torque control to check the position limits.
And likely can plug tau_predicted while position control to check the torque limits.

NoelieRamuzat and others added 3 commits August 5, 2021 18:18
Because the talos-control-manager expects a state vector of size n+6 (freeflyer)
In torque it is not welcomed, so add a way to handle this problem by adding the freeflyer at the beginning of the command. Then set a particular command for the freeflyer.
Control mode = position, velocity, torque, freeflyer (no control)
The velocities limits cannot be checked because the robotUtils lacks of them.
Can plug signal q_predicted while torque control to check the position limits.
And likely can plug tau_predicted while position control to check the torque limits.
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

Successfully merging this pull request may close these issues.

1 participant