-
Notifications
You must be signed in to change notification settings - Fork 21
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
Make ROS 2 compatible support packages available (URDF, etc) #73
Comments
I've pinned this to increase visibility. |
Do you think it would be possible to support both ROS1 and ROS2 in a revised support package repository? It seems like this should be possible with a tool like |
Yes, that should be possible. I don't believe we need RICB for that though. In the end, I believe "all" that would be needed would be a marker for the resource index, perhaps some meta-data for colcon and indeed installing things in the correct places. For support pkgs specifically though there is one thing that we'd need to check additionally: IIRC, |
Related discussion: ros-industrial/motoman#584. |
As a heads up: I intend to update gavanderhoorn/motoman@ros2 soon. It's currently behind Due to the way the fork/branch works, this update will be in the form of a Edit: current state of the update: gavanderhoorn/motoman@ros2_rebased_and_cleaned. |
We have a set of support packages available over at gavanderhoorn/motoman@ros2.
More will be added in the future, and the changes will be merged upstream.
Note these support packages still use the old joint name convention from MotoROS1 (ie:
joint_l_s
, etc). This is no longer needed with MotoROS2, and the names will be changed to the more genericjoint_1
,joint_2
, etc.See also Can names of joints be changed? in the FAQ.
The text was updated successfully, but these errors were encountered: