Solomon Wiznitzer

Commenting to prevent issue from closing.

Note that when I tried to pull this branch and do a clean build, I ran into a linker error caused by moveit_ros_robot_interaction. The MR at https://github.com/ros-planning/moveit2/pull/1617 fixed the issue.

@sea-bass, yep - that's definitely another option. But actually, in some cases (like the one here), you wouldn't need to specify a bunch of piece-wise way points. You would just...

Hey @rhaschke, Thanks so much for merging that in! I assume that will be merged into the ros2 branch soon as well?

Thanks @gavanderhoorn, can you share a link to an example where this 'dedicated interface' approach was implemented?

Having this 'data' param though could be helpful for this PR: https://github.com/ros-planning/moveit_task_constructor/pull/355. In that PR, a feature is added to allow you to use MTC to change controllers for a...

> I've mostly seen solutions where a dedicated interface is created (in the hardware interface) which exposes a way for a dedicated "coordination controller" to configure system modes (that's not...

Hi @destogl, Thanks for the feedback! I did think of your approach originally (but slightly after creating this Issue - thus, the reason it's not in the 'Describe Alternatives you...

Still seeing this issue in January of 2023.

This may be relevant. You can look at the Issue linked in the following PR https://github.com/ros-controls/ros2_control/pull/1012 Specifically, at least the way I intend to use that PR is as follows:...