-
Notifications
You must be signed in to change notification settings - Fork 64
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 actionlib interface for basic Joint Group Command #60
base: kinetic-devel
Are you sure you want to change the base?
Conversation
|
||
# A command to the joints listed in joint_names. | ||
# The order must be identical. | ||
float64[] command |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wold it make sense to make this command more explicit, e.g. trajectory_msgs/JointTrajectoryPoint
. This would probably avoid future extensions and fields can be used explicitly (positions, velocities, accelerations).
Does this makes sense for you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pros:
- Could allow for dual command types (e.g. position with a max velocity/acceleration)
- Explicit command is easier to interpret
Cons:
- Doesn't allow for non-traditional joint commands (only position, velocity, acceleration, effort) outside of overloading a variable
- Makes the coding in ros_controllers a bit more difficult (need to add logic that detects the command type and writes to the appropriate field)
I think the pros can outweigh the cons, so let me make the changes in both packages.
@destogl Sorry for the delay. Updated action and corresponding ros_controllers PR (ros-controls/ros_controllers#569) accordingly |
In service of ros-controls/ros_controllers#568
Tested via velocity_controllers/JointGroupVelocityController on Kinova JACO2