Melodic devel staging #617
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* moved ur_e_description meshes files to ur_description
* one for each models
* removed each model specific xacro * use of yaml files * pass yaml files as parameters * common ur_robo macro * remved ur_gazebo specific parts
* use of yaml files parameters * added e_series * create a common launch file to avoir duplicated
* added e-series
* added e-series
* default in melodic
Urdf with args and yaml configuration
the kinematics parameters can be retrieved from a calibration mechanism to precisely represent the robot's kinematics.
This model is only correct in the kinematics structure. Meshes and dynamics parameters have to be corrected.
Add Ur16e support
Links first, then joints.
Align them with other ROS-I support packages.
avoid deprecation warnings.
Use new name.
Align with other models. For #265.
Align them with other ROS-Industrial support packages.
So remove badge.
readme: there are no Kinetic dev jobs any more
…588) With the common xacro file the robot name will always be "ur". However, the moveit config packages expect the robot name to be e.g. "ur10e". This commit will use the macros containing the model name already.
Update MoveIt! configurations to new description structure. Co-authored-by: Luke Dennis <luke.j.dennis@gmail.com> Co-authored-by: gavanderhoorn <g.a.vanderhoorn@tudelft.nl> Co-authored-by: RobertWilbrandt <wilbrandt@fzi.de>
fixing deprecation warning
The visual and collision mesh of the base of the ur5 has to be moved 3 mm upwards in order to close the gap between the shoulder and align its bottom in the xy-plane. Otherwise the ur5 collides with the surface it is directly placed on.
In 9d02cca robot launchfiles were forwarded to their specialized launchfiles instead of setting the robot model in the load_ur.launch file.
* Update README according to current package state * Added a note about ur_modern_driver for CB1 and CB2
In order to make the simulation more consistent to the ur_robot_driver (and ur_modern_driver) this adds a tool0_controller frame. For the driver this corresponds to the tool transformation published by the robot controller directly. As this doesn't exist for the simulated robot, this adds the frame using an identity transform from tool0.
* Add ur_kinematics parameter sets for all e-Series robots * Add a README with a notice to ur_kinematics * Set correct IKFast plugin name in kinematics.yaml * Add ignore files for releasing ur_kinematics Since the state of this package questionable at the current point, let's disable releasing it for now.
melodic.ignored
Outdated
| @@ -0,0 +1 @@ | |||
| ur_kinematics | |||
There was a problem hiding this comment.
Wouldn't this have to be added to the release repository?
There was a problem hiding this comment.
I was going after https://answers.ros.org/question/66545/to-ignore-some-pkgs-upon-release-by-bloom/?answer=66548#post-id-66548 but you might be right. I've never done that.
Those should go to the release repository instead
Gazebo effort controllers
RobertWilbrandt
approved these changes
Nov 10, 2022
There was a problem hiding this comment.
With #619 merged all breaking changes should now be done and there is no more reason to delay a release.
|
Not deleting the source branch, since there are many references on that. |
This was referenced Nov 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I believe that melodic-devel-staging is elaborate enough to be merged into melodic-devel.