-
Notifications
You must be signed in to change notification settings - Fork 1
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 support for jazzy #4
Conversation
Signed-off-by: Luca Della Vedova <[email protected]>
Signed-off-by: Luca Della Vedova <[email protected]>
Signed-off-by: Luca Della Vedova <[email protected]>
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.
I followed the instructions in the README and I can now control the arm through moveit.
It is admittedly a minimal PR, I commented in place the changes I did (or didn't) make.
has_acceleration_limits: true | ||
max_acceleration: 50.0 |
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.
moveit will refuse running if no acceleration limit is set, I put a random value here but should probably double check it
trajectory_duration_monitoring: true | ||
|
||
moveit_controller_manager: moveit_simple_controller_manager/MoveItSimpleControllerManager | ||
|
||
controller_names: | ||
- joint_trajectory_controller | ||
moveit_simple_controller_manager: | ||
controller_names: | ||
- joint_trajectory_controller | ||
|
||
joint_trajectory_controller: | ||
action_ns: follow_joint_trajectory | ||
type: FollowJointTrajectory | ||
default: true | ||
joints: | ||
- joint_1 | ||
- joint_2 | ||
- joint_3 | ||
- joint_4 | ||
- joint_5 | ||
- joint_6 | ||
joint_trajectory_controller: | ||
action_ns: follow_joint_trajectory | ||
type: FollowJointTrajectory | ||
default: true | ||
joints: | ||
- joint_1 | ||
- joint_2 | ||
- joint_3 | ||
- joint_4 | ||
- joint_5 | ||
- joint_6 |
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.
This change is the same as upstream PickNikRobotics#60, note that if we don't merge rolling
the abb_irb1200_5_90_moveit_config
package will still be broken, but I didn't want to merge upstream since it added a lot to this diff.
joint_limits_yaml = { | ||
"robot_description_planning": load_yaml("abb_irb1200_5_90_moveit_config", "config/joint_limits.yaml") | ||
} |
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.
I hardcoded the package name abb_irb1200_5_90_moveit_config
since it's what is done in the rest of the launch file but I find it very confusing. We have a moveit_config_package
parameter that is used to get the urdf but everything else is hardcoded to the abb_irb1200_5_90
? This means that as soon as a user sets the parameter to anything different this will stop working in very confusing ways?
Still, didn't address it to avoid blowing up the size of this PR but happy to do it in a followup.
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.
Yeah we'll need to switch to moveit_config_builder instead of manually specifying these configs. That can be a follow up to the upstream repo.
No description provided.